Software
Xactimate estimating for roofing contractors
Everything produced here is read by somebody with the authority to accept it or not. That reader is never us.
What this desk produces in the format
A scope built in the structure the file uses, with the supporting material attached against the items it supports rather than bundled at the end. Measurements carried through from whatever source the company already relies on. A clear note of anything the material did not establish, kept as a question rather than resolved by assumption.
Around that, the correspondence a file accumulates: what was asked, what was answered, what is still outstanding, and when each of those happened. Files that go back and forth several times are the ordinary case, and the company that can say precisely what it sent and when is in a very different position from the one relying on somebody’s recollection.
We write in a format somebody else adjudicates
Every other system in this layer holds a company’s own record. What goes in is read back by the same company, and if it is unclear the person who wrote it is available to explain. This one is different in a way that governs everything about how the work is done: the output leaves, and it is read by somebody with the authority to accept it, return it or ask about it.
That reader has not seen the property. They were not there when the crew was, they have no access to the conversation that produced a figure, and they are working through a queue. Whatever the file does not say for itself, it does not say. There is no clarifying phone call in the ordinary course — there is a decision, and then there is whatever follows from it.
So the standard the work is held to is not "is this correct". It is "does this stand up to a stranger reading it once, in order, without help". Those are different bars and the second is considerably higher. A scope can be entirely accurate and still fail it, because the backup for the contentious item sits three screens away from the item.
And the last word is not ours. This desk can make a file complete, internally consistent and easy to follow. It cannot make it accepted. Anybody who tells a roofing contractor otherwise is describing an outcome they do not control, and that promise is the single most common misrepresentation in this corner of the trade.
What makes a file easy to say yes to
Structure first. A reader working through a queue follows the order the file presents, so an item whose justification is adjacent to it is assessed on its merits, and an item whose justification is somewhere else is assessed on whatever the reader can see. Nothing about that is unfair; it is simply what reading in order means.
Restraint second. A file that claims more than the material supports invites scrutiny of everything else in it, including the parts that were solid. The costly outcome is rarely the item that gets removed — it is the additional attention the rest of the file then receives.
Xactimate certification is held here, and this is the part of the work where it is relevant: the structure the file uses has conventions, and producing work in it properly is a matter of training rather than of working it out from the outside. That is the whole of the claim. It says something about how the work is produced and nothing whatever about what a reader will decide.
What stays with a person is judgement about scope, which is a question about the building rather than about the software. Whether an item belongs is a decision for whoever can see the property and carries the responsibility for the job — and where that judgement has consequences, it is not this desk’s to make.
Access you extend, files that stay put
Access granted from your side, for the work at hand. Not a shared credential. On material that is read by an outside party and may be revisited long afterwards, being able to say who prepared what is part of what makes it defensible.
Nothing is copied out. No parallel archive of your claim files at our end, nothing to secure and nothing to return.
The scope decisions are yours. We prepare and document; what a job requires is a judgement made by whoever is responsible for the work.
Roofing Back Office is not affiliated with, endorsed by, or certified by any software vendor named on this site. All product names and trademarks are the property of their respective owners.
Picking up a file that is already moving
Most handovers start mid-stream: files already submitted, some already returned once, and correspondence spread across an inbox and somebody’s memory. The opening work is establishing where each one actually stands, which is more often unclear than owners expect.
New work is taken from the beginning immediately, because the first submission sets what every later exchange argues about. Files already in motion get a shorter treatment: what has been sent, what came back, what is outstanding, and whether the material supports what was claimed.
Where an existing file rests on something the material does not support, that is said plainly rather than carried forward. Inheriting a claim and continuing to make it is how a small optimism becomes a company position nobody remembers adopting.
What owners ask before handing over a file
Do you deal with the insurer directly?
No, and the line is worth stating precisely because it is narrower than it sounds. Preparing and documenting a file is administration. Negotiating a settlement on behalf of the insured is a licensed activity in most states and it belongs to the licensed party. The estimating-project department page sets out that boundary and the primary sources it rests on; this desk stays on the preparation side of it.
What actually comes back to us?
A scope written in the structure the file expects, with the backup attached in the places a reader will look for it, and a note of anything the available material did not establish. That last part is deliberate: a gap raised is a question somebody can answer, while a gap filled in is a figure with no origin that everybody downstream will treat as fact.
You are certified. What does that get us?
Xactimate certification is held here, and what it means in practice is narrow and worth stating plainly: the work is produced by somebody trained in the structure the file uses, rather than approximated by somebody working it out. It is a fact about competence in a format. It does not mean an estimate is more likely to be accepted, and anybody suggesting otherwise is selling you something.
What happens when something comes back queried?
It gets read as information rather than as a setback. A query is usually one of two things — the backup did not reach the reader, or the reader disagrees about scope — and those need completely different responses. Telling them apart quickly is most of the value, because resubmitting a scope disagreement as though it were a paperwork gap can consume weeks and change nothing.
Can you work from what our crews already send?
That is the normal starting position. What determines whether a file can be built well is whether the material establishes the condition, not whether it was captured with a particular system or in a particular order. Where it does not, you will hear that before the file goes anywhere rather than afterwards.
Who owns the files if we stop working together?
You do, and they never moved. Access is granted from your side and withdrawn from your side, and there is no copy of anything at our end to return. What transfers is the account of how the work was being run — which is the part a company almost never has written down.
The estimating desk this sits inside · Every platform we work in.
Read your last file the way a stranger would
Once, in order, with no phone calls. Wherever you had to already know something, the reader on the other side did not.