A gap list is most useful when it describes the evidence state without assigning unsupported blame. For each line, state the requirement or source, the item expected, what has been received, what remains unclear, the responsible role, the requested action and the due date. Distinguish a missing file from a file under review or one returned with comments.
Use neutral language: “No final revision located in the supplied folder as at [date]” is more precise than “contractor failed to comply.” Attach a link or reference to the source requirement and avoid drawing technical conclusions. If the issue concerns a certificate, test result, design or statutory approval, send it to the appropriately qualified or authorised person.
Review the list with the package owner, update status only when evidence arrives, and retain the history. A gap list is a coordination tool, not an acceptance decision or compliance certificate.



