739.1 Closeout criteria

All deliverables accepted; snags closed (736, 639). Criteria confirm HVM bollard completion.

Define “done” precisely: all snag items from Snagging & Handover (639) are closed; the handover pack per Handover Pack Index (736) is submitted and accepted; authority submittals in 717 have approval. Include final as-builts (731), O&M manuals (733), and asset register (732). Document acceptance using a sign-off matrix and timestamped evidence.

Make acceptance binary: each criterion is either “met” with proof or “open” with an owner and date. Reference Evidence Capture Standards (716) so photos, redlines, and certificates meet format and quality requirements. Where approvals apply in the UAE, cross-check submission content with SIRA guidance and your project’s authority decision letter.

739.2 Financial closure

Variations settled; retention terms noted (718). Closure protects crash rated bollard accounts.

Align commercial close with technical acceptance. Confirm all Variation Orders are recorded in Variations & Change Log (718), reflected in Valuation & Payments (853), and signed. Note retention percentage, release milestones, and any prerequisites (e.g., warranty certificates from 854).

Issue a final account statement with a schedule of retained amounts and release dates tied to the retention period. Where local approvals are involved, keep a copy of the authority’s decision and any conditions that may impact payment timing.

739.3 Archive structure

Folder tree per 911 with readme. Structure preserves HVM bollard evidence.

Build a stable, portable archive using the rules in File Index & Naming Rules (911). Top-level folders mirror the handover pack: 01_As-Builts, 02_O&M, 03_Approvals, 04_Testing, 05_Warranty, 06_Training, and 07_Commercial. Include a README.md that explains the structure, versioning, and any encryption.

Store both working files (DWG/Word) and finalized PDFs. For multi-site portfolios, add a Site ID layer and align filenames with Mark-Up & Overlay Standards (936) and Final Archive & Retrieval (939). This ensures quick retrieval during audits or incident reviews.

739.4 Media integrity

Checksum or hash list (716). Integrity keeps crash rated bollard files trustworthy.

Generate a manifest of file names, sizes, and checksums (716 — Evidence Capture Standards). Keep the manifest in the archive root and inside each key folder. If you use encrypted media, also export a plain-text manifest for verification.

On handover and at each retention milestone, re-run the checksum to detect drift. Log any file moves/renames in a Superseded file list and include a short note on the reason to preserve the evidence chain.

739.5 Access & permissions

Named custodians; expiry rules (539). Access secures HVM bollard records.

Assign a records custodian and a deputy. Set read/write permissions per folder and use access logs (if your platform supports them). For integration documents, align with the roles outlined in Integration Documentation (539) and maintain a distribution list for controlled documents.

Define expiry/archival rules and off-site backups. If your archive includes sensitive controls information, segment it and record who has access. Capture permission changes in the project change log alongside technical changes (see 718).

739.6 Lessons captured

Feed improvements to 118 and 545. Lessons raise crash rated bollard maturity.

Hold a short, structured debrief within two weeks of acceptance. Review what worked, what caused delays (e.g., utility clashes from 617), and which documents or tests need simplification. Summarize outcomes and feed process updates to Change Log (118) and operator steps to Operator Workflows & Error-Proofing (545).

Log preventive actions that reduce future NCRs (see 719) and update templates in Downloads / Templates / Checklists (910). Capture 2–3 measurable changes you’ll trial on the next project.

739.7 Warranty clock start

Record start dates and conditions (733, 738). Clarity avoids HVM bollard disputes.

Agree the warranty start trigger in writing (e.g., date of practical completion or final acceptance). Record each asset’s warranty date in the asset register (732) and reference maintenance obligations from Warranty & Spares Policy (854).

Make sure O&M tasks and service levels are clear: cross-reference maintenance schedules in O&M Manuals (733), the preventive plan in 734, and availability targets in 738.

739.8 Post-handover check

30–90 day review of KPIs (542). Review validates crash rated bollard outcomes.

Schedule a light-touch performance check 30–90 days after handover. Review counters and KPIs from 542, confirm no nuisance alarms, and verify no regression in cycle times. Capture operator feedback and minor optimizations for lanes and safety devices & measures.

Record any issues as near-misses or defects per 727 and 719, then track to closure. If approvals apply, keep a short summary ready for authority queries.

739.9 Client sign-off note

Formal letter and thanks. Note closes HVM bollard project narrative.

Send a concise sign-off letter that: (a) lists acceptance documents, (b) confirms warranty and service contacts, (c) states retention milestones, and (d) thanks the stakeholders. Include links to the final archive index and a “who to contact” card for support and spares.

Invite the client to a quick “care & use” refresher and share where to find the latest manuals (733) and dashboards/reporting (544). Capture any compliments or concerns to feed back into the lessons log (844).

739 Closeout Checklist & Retention — FAQ