736.1 Pack checklist

As-builts, O&M, certificates, SAT report (731, 733, 431, 638). Checklist speeds HVM bollard closure.

A tight checklist prevents gaps and rework. Include: approved As-built drawings, signed test certificates, the SAT/witness report, the indexed O&M manual, a consolidated asset register & serials, training sign-offs, and warranty/spares documentation. Align the order with authority expectations and your submission-pack guidance so reviewers can find everything quickly.

Make the list self-checking: add a “received/verified” column, a link to the file location, and a “latest version” flag. Where terms may be unfamiliar, add short tooltips and map each item to your file naming rules to avoid duplicates or wrong versions reaching the client.

736.2 Evidence index

One master index with links (716, 938). Index helps crash rated bollard reviewers.

Create a single evidence index that lists every photo set, video, certificate, and signed form. Each row should include: document title, ID/filename, date, responsible owner, approval status, and a live link (portal path or cloud URL). This “map” is the reviewer’s compass; keep it at the front of the pack.

Use a short “reader sequence” note: the order a reviewer should open items. Pair it with a submission index & cover and a transmittal log for formal deliveries. In the UAE, reference any SIRA-specific folders or forms where applicable and point directly to the signed copies in the portal.

736.3 Training records

Attendance, competency, assessments (737). Records prove HVM bollard readiness.

Include the training plan & sign-offs, attendance sheets, and competency assessments. Note the roles trained (operators, FM, security) and the exact configuration (e.g., modes of operation, HPU basics, emergency procedures). Link each module to the relevant O&M section and include a short “RTS” (return-to-service) checklist signed by the trainer and client lead.

736.4 Spares & tools

Deliver list and custody notes (854, 529). Spares sustain crash rated bollard uptime.

Document the initial spares kit and any commissioning tools handed over: part numbers, quantities, storage location, and custody. Tie spares to preventive maintenance intervals and the asset register so replacements are traceable. If spares are shared across sites (common spares policy), state the response window and where the pool is kept.

736.5 Warranty & SLAs

Terms, contacts, response windows (738). Terms clarify HVM bollard support.

Summarize warranty start/end, inclusions/exclusions, and claim steps. Add service levels & availability with clear response windows, escalation paths, and the maintenance window policy. Include a “who to call” card with 24/7 numbers, and link to the client portal process for creating tickets. Map any SLA KPIs (e.g., availability) to the counters/health pings if deployed.

736.6 Acceptance certificates

Signed forms and conditions (717). Certificates finalize crash rated bollard approvals.

Collect final SAT sign-off, punch-list closure, and authority acceptance letters. Cross-reference SAT / witness procedure evidence and the authority submittals thread so every signature is traceable. Where conditions apply (e.g., “monitor settlement for 90 days”), list them and assign owners/dates.

736.7 Final snag list

Closed items with evidence (639). Closure secures HVM bollard quality.

Attach the final snag register with photo evidence, closure dates, and approver initials. If a concession or NCR was raised, include the NCR close-out and the as-built delta markers that show the agreed change. Keep this near the acceptance certificates so reviewers see “issues found → actions taken → proof of closure” in one flow.

736.8 Distribution & access

Recipients, portals, permissions (539). Access keeps crash rated bollard data usable.

List named recipients, their roles, and how they will access the pack: hard copy, USB drive, or portal. State the document control rules (who can upload, who approves), retention period, and how superseded versions are handled. For portals, add screenshots or a “how to find it” note. In the UAE, specify the SIRA submission folder path (if applicable).

736.9 Archive handoff

Long-term storage path (911, 115). Archive preserves HVM bollard history.

Define the permanent archive: folder path, naming rules, and who owns stewardship. Include a manifest (“one-page index”) listing every final file with checksums and dates. Add a brief “how to retrieve” note for future projects and make sure the archive mirrors the pack structure, with an obvious place for later addenda (e.g., post-incident updates or upgrades).

736 Handover Pack Index — FAQ