Site Package Handoff Checklist: Review Evidence, Revisions and Exports

Write down the intended decision and the limits of the work. Confirm the boundary, address, jurisdiction, proposal description and revision. Ask the recipient which outputs they need and which application or review process will receive them.

Do not label early screening as a complete development appraisal. Record any excluded topics, inaccessible sources or areas outside the evidence coverage.

Use one register row per finding or unresolved question. Record the source, relevant section, date and extent. Separate the date you accessed a source from its publication or effective date. If an edition is unknown, write that explicitly.

For changing policy, revisit the issuing authority before relying on a saved extract. If two sources disagree, keep both references and identify the reviewer who will resolve the difference. Do not silently select the more favourable answer.

An observation describes what the source shows. An assumption fills a gap for a stated purpose. An unknown remains open. Those states should not look interchangeable in a summary.

Illustrative item	Evidence state	Next action
A source map shows a designation near the boundary	Observation; site intersection not yet checked	Compare the source geometry and agreed boundary
A massing option uses an assumed access location	Design assumption	Confirm access requirements and relevant rights
An export has no recorded vertical reference	Unknown	Request its reference before using elevations

These are invented examples for using the checklist, not results for an actual site.

Open each representative file in the receiving application. Check that it contains the intended site and layers, and inspect units, origin, extent and known reference points. Record the receiving software/version, any conversion and the outcome.

For GeoJSON following RFC 7946, longitude/latitude positions are in decimal degrees. Confirm any projection or conversion needed for a metre-based drawing. A file extension or successful download does not prove positional accuracy or compatibility.

If an output fails, keep the failure in the register and agree a replacement. Do not mark the package accepted while an essential file remains unusable.

Give the recipient a short decision summary, the agreed outputs and the evidence register. List outstanding issues with an owner and next action. State which revision replaces which earlier issue and how material corrections will be communicated.

Use the blank evidence register as a starting template, adapting the rows to the project. It does not replace an agreed information-management process or prove that the checks were performed.