859.1 Report cadence

Weekly status; monthly executive (845). Keep HVM bollard stakeholders aligned.

Use a clear weekly rhythm (site-level) and a monthly executive snapshot to prevent drift between teams. Weekly updates focus on progress, blockers, and actions; the monthly roll-up highlights milestones, decisions, and variances in scope, cost, and time. Define the publication cadence in your kick-off so everyone knows when to expect what.

Align the cadence with the approved programme in 855 Programme & Phasing and the site’s daily record in 729 Daily Progress & Site Diary. For UAE jobs involving approvals, note any SIRA reporting checkpoints in the plan and reference SIRA Bollards (UAE).

Keep the format lean: 1 page for weekly status, 2–3 slides for the monthly. Use consistent section headers and stable order so readers can scan quickly. If you change the structure, log it in your Change Log (718) for traceability.

859.2 KPI dashboard

Availability, cycle time, defects (542, 544). Data-led decisions.

Dashboards should present a minimal, stable set of measures: Availability, Ops/hour, cycle time, and defect/NCR counts. Add a simple RAG status and trend arrows. Each KPI must have a definition, a data source, and an alert threshold.

Ensure the KPI list mirrors operational sources in 542 KPI Set and reporting patterns in 544 Operational Dashboards. For availability, state the calculation window and exclusions (e.g., pre-agreed shutdowns). Use sparklines for lane KPIs and a monthly executive snapshot view for leadership.

859.3 EV/percent complete

Earned value for civils/controls/commissioning (855). Predicts outcomes.

Apply earned value (EV) to the three big workstreams: civils, electrical/controls, and commissioning. Baseline against the approved schedule in 855 Programme & Phasing. Track Planned Value (PV), Earned Value (EV), and Actual Cost (AC) to calculate cost and schedule variance and forecast an Estimate at Completion (EAC).

Be explicit about measurement rules for witness points, hold points, materials on site, and partially complete activities. For commissioning, tie EV to objective evidence from 630 Commissioning & Safety Tests and related subpages (e.g., 634 Interlock Matrix Verification).

859.4 Risk & issues list

Live linkage to 846 and 718. No hidden blockers.

Maintain a single live risk register with clear owners, triggers, and thresholds. Mirror governance guidance in 846 Risk Register & Governance, and connect day-to-day issues to 718 Variations & Change Log so scope or design changes are never “off-ledger.”

Use short, action-oriented entries: cause, impact, owner, due date, and status. Add a weekly “top-5 risks” panel to the report and a list of critical rating-critical dependencies (e.g., foundation class, utilities clearances) with links to the relevant design pages (e.g., 421).

859.5 Change log snapshot

Approved variations and impacts (718). Avoid scope creep on crash rated bollard work.

Show a compact monthly snapshot of approved variations, pending Change Requests (CRs), and their cost/time impact. Link each variation to source evidence (RFI, drawing, calculation pack) and to the authoritative list in 718 Variations & Change Log. Record effective dates and the downstream updates made (programme, BOQ, drawings, testing).

Call out any impact on crash-rating assumptions (e.g., foundation depth class or ducting route) and reference 435 Anti-Downgrade / Equivalence Clauses to protect specification intent.

859.6 HSE summary

Incidents, near misses, actions (727). Safety trend visible.

Summarize incidents, near-misses, and close-out actions. Show a rolling 4-week trend and any high-risk activities scheduled next period (lifting, confined-space, energization). Cross-reference the underlying records in 727 Incident / Near-Miss Reporting and site permits/toolbox talks where applicable.

Keep the language factual and blame-free; focus on prevention and the hierarchy of controls. For the UAE context, include any regulatory notifications or SIRA-specific requirements if the project falls under that jurisdiction.

859.7 Quality summary

NCRs, audits, closures (858, 719). Quality stays on track.

Report open/closed NCRs, audit findings, and due dates for corrective actions. Connect this section to 858 Quality Audits & Surveillance for surveillance cadence and to 719 Nonconformance & Defects for definitions and evidence standards.

Highlight rating-critical checks (e.g., acceptance bands on clear-gap, embedment, cable specs). Where any concession is proposed, include a risk summary and tie back to the 431 Documentation & Certificates needed to maintain compliance.

859.8 Look-ahead & dependencies

Next two weeks, holds, permits (134). Clear asks.

Share a two-week look-ahead with explicit holds, permit needs, and decisions required. Tie inspections/permits to the 134 Permit & Inspection Timeline and list any hold points that will stop work without timely approval.

Make dependencies visible: utilities NOCs, shop drawing approvals, material deliveries, witness bookings, and coordination with other trades (247 Trade Coordination). Use brief, actionable bullet points and name the accountable owner for each item.

859.9 Distribution & archive

Recipients, portal link, file rules (911, 739). Reports remain accessible.

Publish reports to a single controlled space with a stable URL and a clear distribution list. Include links to source evidence (drawings, photos, NCRs) using consistent filenames per 911 File Index & Naming Rules. Attach a one-page snapshot PDF for quick sharing when required.

At closeout, confirm the full set is archived per 939 Final Archive & Retrieval and cross-check against 739 Closeout Checklist & Retention. Name a records custodian and a retention period.

859 Progress Reporting & Controls — FAQ