A findings list arrives and the instinct is to answer everything at length. That instinct costs projects weeks, because a long answer to a narrow question invites follow-up questions, and follow-up questions on a verification can escalate into scope that was never in play.
Findings Come in Grades
| Type | Meaning | Must be closed before issuance? |
|---|---|---|
| Corrective action | Something does not conform; fix it | Yes |
| Clarification | The assessor cannot tell whether it conforms | Yes |
| Forward action | Acceptable now, fix before next period | No |
The distinction matters because the appropriate response differs completely.
A clarification is answered with evidence, not with changes. The project was probably fine; the documentation did not show it. Supply the missing document and stop.
A corrective action requires an actual fix and evidence the fix happened. Supplying explanation without remedy does not close it.
A forward action requires acknowledgement and a plan. Attempting to fix it immediately is usually wasted effort that delays the current issuance.
The Mistake That Widens Scope
Answering a clarification by changing the methodology or recalculating.
If the assessor asks how a parameter was derived and the project responds by deriving it differently, the assessor now has a new calculation to assess, a discrepancy with the previously reported figure, and a reason to ask whether other parameters share the problem. One narrow question has become three broad ones.
The correct response to "how did you derive this" is the derivation. Not a better derivation.
Answer the Question Asked
Findings are written narrowly on purpose. Reading a broader concern into one and pre-emptively addressing it volunteers information nobody requested.
That is not concealment, as everything a standard requires must be disclosed. It is scope discipline. Assessors work to a defined scope and a budget, so expanding it unprompted serves nobody, and it delays the issuance the project is waiting on.
Evidence Beats Explanation
The response that closes a finding fastest is a document, not an argument.
"The QA/QC remeasurement was performed" closes nothing. "Attached: remeasurement records for plots 7, 22 and 41, dated 14 March, signed by the independent team, with the tolerance comparison" closes it.
Projects with good records find most findings close on the first response. Projects without them enter a cycle of explanation, follow-up and partial evidence that can run for months.
When the Finding Is Right and Expensive
Occasionally an assessor identifies something real that cannot be fixed cheaply, such as a pool excluded that should not have been, a systematic measurement issue, or a baseline assumption that does not hold.
The temptation is to argue. Where the assessor is correct, arguing delays an outcome that will not change and damages the relationship with the body you will work with again.
The better move is to concede quickly, propose the remedy, and be explicit about what it does to the reported figures. A project that reduces its own claim in response to a valid finding is in a considerably stronger position than one that litigates and loses, including with the buyers who eventually read the verification report.
Move beyond estimates
Verifiers test sampling design, uncertainty and whether a number traces back to the field. TREEO dMRV captures that evidence in real time, in one auditable chain.
