It surfaces the same way every time. A homeowner calls because the second opinion they got from your own company does not match the first one, and now you are the one explaining why two people wearing your shirt saw different roofs.
Everybody treats this as a competence question — one of them is wrong, find out which. Usually it is not. Two careful people can walk the same slope and come down with genuinely different reads, and if your answer is to work out who to trust, you will be doing that forever.
The disagreements that are not disagreements
Before you referee anything, separate the kinds.
Most of what looks like conflict is coverage. One walked all four slopes, the other worked the two he could reach safely on a wet morning. They do not disagree about anything; they looked at different amounts of roof. This dissolves the moment both records state what was and was not observed, which is the argument for saying plainly what you could not verify.
Some of it is vocabulary. One writes "granule loss," the other writes "weathering," and they are pointing at the same shingle. That is a glossary problem, and it is the cheapest one on this list to fix.
Some is threshold. Both saw the mark. One counted it, one did not. This is the real one, and it is where a company either has a standard or discovers it never did.
What is left after those three — two people who looked at the same thing, named it the same way, and still read it differently — is rare. It is also the only category that deserves a conversation.
Build the standard out of the disagreement
The instinct is to write a policy first. It works better in the other order: let the disagreements tell you where your standard is missing.
When two reads conflict, log the specific thing. Not "Dave and Mike disagreed on the Whitaker roof" — "north slope, three marks under half an inch, Dave counted them, Mike did not." Do that for two months and you will have a list of every place your company has no shared threshold, ranked by how often it actually comes up.
Then write those down, in the plainest language you can, with photographs of your own from real jobs. Not an industry document — a page that says what your company counts and what it does not. Standardizing across inspectors is the general version of this; the disagreement log is how you find out which parts matter.
Recordings make this a five-minute conversation
Two written reports in conflict is an argument. Two recordings of the same roof is a review.
When the walks are recorded, you stop reconstructing what each inspector saw from what each inspector wrote. You watch. Nine times out of ten the answer is visible in about four minutes: he was on a different slope, or the light was flat, or the mark is right there and got missed. Nobody has to defend their memory.
That changes the emotional shape of it too. A disagreement about a record is a normal professional conversation. A disagreement about whose recollection is better is a fight about character, and people defend their character harder than they defend a finding.
It is also the only version of this that scales. Once the owner stops doing every inspection, the ability to check a call without re-climbing the roof is the difference between a company with a standard and a company with a collection of individual habits.
What to tell the customer
Do not hide it, and do not resolve it in front of them before you have resolved it internally.
"Two of our inspectors looked at this and read one area differently. I am reviewing both walks today and I will call you tomorrow with our position." Then do that.
Customers handle this far better than people expect. What they cannot handle is a company that quietly picks the answer that suits it, or one that lets two employees argue in a driveway. A firm that says "we caught a difference internally and here is how we settled it" reads as a firm with a process, which is exactly the impression a second opinion was testing for.
And when you deliver the settled answer, describe what was observed and leave the rest alone. What it is worth and what an insurer should do about it are not yours to say.
Disagreement is not a sign the crew is sloppy. In a company with real volume it is a sign the work is being looked at. The failure is having no mechanism to turn it into a standard. The use cases page covers how crews run reviewable walks, and how it works has the mechanics of what gets captured.
InspectStream records what an inspector observed. It is not a public adjusting service and does not prepare, negotiate, or advise on insurance claims.