Start with the decision
Define completeness as whether the information needed for a particular decision has been supplied and scoped. It depends on the brief: a recovery enquiry and a formal lifecycle comparison require different inputs. Keep that purpose next to the result.
Build the record
Record each required field as present, missing, ambiguous or outside scope. Name the responsible source and version. Separate evidence quantity from review quality and independence. A thick document folder can still fail to address the supplied variant, current site or intended service.
Check before acting
Show environmental dimensions separately: mass, content, service, repair, carbon and recovery where applicable. A more complete record may reveal an adverse finding, while an incomplete one may concern a feasible product with unanswered questions. Do not turn unknown values into favourable zero scores or reward sponsors for document volume.
Worked example — illustrative
A fictional team compares two display faces. One has comprehensive records that include a difficult recovery route; the other has little information. The completeness view highlights the second option’s gaps, while the performance table shows the first option’s actual limits. Neither is assigned a universal green badge from completeness alone.
Keep a useful handover
Record the responsible person, decision date and next review trigger with the evidence version. Keep planned actions distinguishable from confirmed activity. If later information changes the result, preserve the earlier record and update current guidance.
- Define the review purpose.
- List required scoped inputs.
- Separate completeness and assurance.
- Show adverse findings.
- Keep environmental dimensions distinct.