Deliverable formats
The fourth lesson on the Records & documentation track — the twin-pair deliverable shape the closeout package takes when it ships: the contractor-actionable tier (action-first, recommendations memo + findings map + field-report summary) and the municipal-records tier (records-first, per-utility registry + bounded-negative annotations + calibration evidence + as-built alignment notes). One dataset, two shapes, bound by the segment-ID namespace contract.
Track each section as you finish it
Five sections — intro, twin-pair tier shape, format rules, common errors, knowledge check — plus a practice exam and the next-step card. Sign in to mark sections complete; progress shows up on your dashboard and across sessions.
New to deliverable-shaping? Take Module 01 · Module 02 · Module 03 first.
Why this lesson exists
A closeout package shipped as a single artefact collides with two readers who want different shapes. The contractor bids the work and reads action-first; the municipality files the closeout and reads records-first. One dataset, two shapes, bound by a segment-ID namespace that both tiers share.
- Senior field technicians and report writers about to assemble the closeout package into tier-specific PDFs — the moment the recommendation memo separates from the records-tier summary.
- Project engineers and contract managers preparing two distinct submittal tiers — the contractor-actionable edition for the bid and the municipal-records edition for the records desk.
- Owner-side oversight staff reviewing deliverable submittals against the segment-ID namespace contract — the moment a tier-renamed segment forces reconstruction at audit.
By the end of the lesson you should be able to assemble a contractor-tier PDF and a municipal-tier PDF from the same underlying findings dataset, bind them by segment ID, ship them in PDF as the default format, and stamp each with its own signature block.
- 01Shape the contractor-actionable tier with the three artefacts the contractor reads — the findings map (surface-mark positions, depth estimates, APWA colour as utility-class key), the recommendations memo (per-finding what-to-do), and the field-report summary that links the two by segment ID.
- 02Shape the municipal-records tier with the four artefacts the municipality reads — the per-utility registry (ASCE 38 level stamp on every segment), the bounded-negative annotations, the calibration evidence (model, serial, calibration date, calibration log reference), and the as-built alignment notes.
- 03Bind the two tiers by segment ID — same namespace, never by page number, never by paragraph order — so a contractor claim and a municipal review can verify against the same evidence.
- 04Ship PDF as the default deliverable format and a CAD overlay as an optional addition for the engineering reviewer — PDF is the long-term archival format; CAD overlays are engineering-review tools that do not survive a records-desk handover gracefully.
- 05Stamp each PDF with its own signature block — the contractor-tier seal on the recommendations memo and the findings map, the municipal-tier seal on the records registry and the long-form summary. The same locator signs both, but the blocks differ because the artefacts they seal differ.
One dataset, two shapes, one segment-ID contract
The contractor-tier PDF carries what the contractor reads (action items). The municipal-tier PDF carries what the municipality reads (records rationale). The same segment ID lives on both — a contractor claim and a municipal review verify against the same evidence.
- Findings map — surface-mark positions, depth estimates, APWA colour-coded utility class on every segment, level stamp on each line.
- Recommendations memo — what to do at each finding (pothole before crossing, re-sweep at a different level, hand off to a different discipline) bound to the findings map by segment ID.
- Field-report summary — short narrative that links the map and the memo together by segment ID, not by page number or paragraph order.
- Calibration appendix — the contractor reads the deliverables tier, not the methodology tier.
- Long-form records-tier summary — replaced by the recommendations memo.
Locator seal on the recommendations memo and the findings map — recognises the action-first deliverable.
- Per-utility registry — the ASCE 38 quality level stamped on every segment, organised by utility class with the segment ID consistent with the contractor tier.
- Bounded-negative annotations — the method stack, sweep length, calibration point, and frequency applied to each negative.
- Calibration evidence — equipment model, serial number, calibration date, calibration log reference next to every geophysical method on a line.
- As-built alignment notes — where the on-site work agrees with or differs from the as-built records the municipality carries.
- Recommendations memo — the municipality does not perform the work; it reads the records that justify the work.
Locator seal on the per-utility registry, the bounded-negative annotations, the calibration evidence, and the as-built alignment notes — recognises the records-first deliverable.
Four rules the closeout package has to ship under
The four rules governing how the closeout package ships: the segment-ID namespace contract that binds the two tiers, the PDF-as-default archival convention, the per-PDF signature-block distinction, and the executive-summary-on-the-front-page orientation.
Bind the contractor tier and the municipal tier by segment ID — same namespace on both, never by page number, never by paragraph order. The segment ID is the contract between the two tiers and the contract has to hold at audit.
Ship the PDF as the default deliverable. PDF carries visual context (maps, sketches, photo grids), is non-editable, and is universal across records systems. CAD overlays are engineering-review tools; they ship as an optional addition for the engineering reviewer only.
Each PDF carries its own signature block. The contractor-tier PDF seals the recommendations memo and the findings map; the municipal-tier PDF seals the records registry and the long-form summary. The same locator signs both, but the blocks differ because the artefacts they seal differ.
Ship a one-page executive summary on the front of both tiers. The summary names the engagement, the site, the segments (count), the level distribution (count of A/B/C/D lines), and the sealed-and-signed signature block. A reader who opens the package and reads the front page alone has the headline.
Six deliverable-shaping mistakes worth flagging
The lesson collects the calls we have flagged on post-closeout debriefs — the kind that quietly turn a defensible twin-pair into a single artefact the audit cannot reproduce. Each has a clear signal on the package and a corrective move the team can run before delivery.
A closeout package ships a single recommendations memo and ships the same memo to both the contractor and the municipality. The municipality does not need the recommendations; it needs the records rationale.
Split the artefact — the contractor-tier PDF carries the recommendations memo; the municipal-tier PDF replaces it with a long-form records-tier summary that names what the records carry, not what to do at each finding.
The report writer renamed some segment IDs when assembling the municipal-tier registry. The contractor tier and the municipal tier share no segment ID namespace, so a co-citation fails.
Bind the two tiers by segment ID — same namespace on both. The segment ID is the contract between the tiers. Renames break the contract and force reconstruction at audit time.
A closeout package is shipped as an editable CAD overlay with no PDF version. A municipal reviewer who needs a PDF for the records desk receives the CAD file and has to convert it.
Ship the PDF as the default deliverable and the CAD overlay as an optional addition. PDF is the long-term archival format; CAD overlays are engineering-review tools.
A draft map colours every segment in APWA red; a legend says "red = electric and confirmed" — the colour carries both utility class and evidentiary weight in one symbol.
Use APWA colour code for utility class on every segment (red electric, blue water, green sewer, etc.). Stamp the ASCE 38 level as a separate annotation in the same legend. Colour and evidentiary weight are two different signals.
A closeout package includes a one-page summary that does not carry segment IDs on it. A reviewer reading the summary alone has to flip back to the body for the segment references.
Stamp the segment ID on the corner of every page that carries an entry — the page header for orientation, the segment ID for the audit. Partial coverage is an audit-time hazard.
A closeout package is shipped without a signature block. The reader has to chase the engagement ID back to the engagement office for authorisation.
Stamp each PDF with its own signature block — the contractor-tier seal on the recommendations memo + findings map, the municipal-tier seal on the records registry + long-form summary. The locator signs both blocks before delivery.
Self-check — four questions on the twin-pair deliverable, reveal as you go
A short authored self-check covering the closeout calls the audit reads against — the contractor-tier shape, the municipal-tier shape, the segment-ID namespace contract, and the per-PDF signature-block distinction.
This is a self-check, not a graded exam. Pick a question, reveal the answer, and use the rationale to decide whether the topic earns another pass before delivery.
0 of 4 answers revealed. State is kept on this device only.
- 01
A contractor on a school campus asks for the closeout package three weeks after the engagement closes. The locator's audit log shows that every line carried an ASCE 38 quality level, every negative was bounded, and every method-stack annotation was reproducible. What shape should the closeout package take for the contractor-reader tier?
- 02
A municipal reviewer asks for the same closeout package the contractor received, six months after the engagement. What is a different shape for that reader?
- 03
A closeout package ships the contractor-tier findings map and the municipal-tier registry, but the segment IDs on the two are different because the report writer renamed them when assembling the registry. What is the deliverable failure here?
- 04
A closeout package was requested in PDF format but the team scheduled the deliverable as an editable CAD overlay file with no PDF version. A municipal reviewer who needs a PDF for the records desk immediately receives the CAD file. What is the deliverable failure here?
Graded deliverable formats practice run
A graded practice exam on this module — 8 multiple-choice questions, 4 options each, instant feedback, score summary with a tier label at the end. The four-question reveal-on-click knowledge check above is for reading; this is for testing.
The Module 04 practice exam covers the contractor-tier shape, the municipal-tier shape, the segment-ID namespace contract, the PDF-default archival convention, and the per-PDF signature-block distinction. Take it after the four-question knowledge check.
Next steps after the deliverable shape
Module 04 stops at the deliverable shape. The track landing page indexes all four lessons; the practice-program hub indexes all four exams; the Advanced Module 03 lesson extends the closeout vocabulary into multi-utility campuses and records at scale.
The four lessons and four exams align one-to-one by topic. Module numbers in this track correspond to the practice-program hub on /training/records-documentation/practice.