Site compliance checks

A Site Inspector records where the check took place, when it was inspected, the permit reference and the number of open safety issues. The check belongs to an organization and can be connected to an assessment. For example, a permit reference for a concrete pour is useful only when the team can tell which site was inspected and which open issues were still present at that visit. The Compliance Manager can then review a submitted check in context.

The submitted state lets the Compliance Manager find checks awaiting a decision. After examining the permit reference and open issues, the manager records approved or rejected on the check. Completion is a separate state for later site follow-up. The team should retain the inspection details from the original visit when recording another check.

• Site identity. Agree how inspectors name a site so repeat checks can be compared without combining different locations.
• Permit reference. Decide which reference identifies the permit in the authority or document source used by the team.
• Open issues. Agree who updates the open safety issue count after a reinspection and what evidence is needed.

The Site Inspector and Compliance Manager should rehearse how this work is assigned and reviewed. Agree which organization and business unit own the first case, who may update it, and where its supporting evidence lives. Set a clear handoff when the person preparing the record is different from the person checking its outcome. Use the same rule for routine work and exceptions so an urgent item does not lose its owner or history.

For the pilot, use a site with a permit reference and an open issue. Agree how the inspector records the date and issue count, who examines a submitted check, and how the manager records the result. Keep an earlier rejected visit available when a later check shows the issue resolved.

Use a site with a permit reference and an unresolved safety observation. The Site Inspector records the visit and submits it. The Compliance Manager checks the permit reference and issue count, then records the decision. On the next visit, compare the new check with the earlier record. A rejected check should stay visible; a later approved check should not silently rewrite the first observation.

Open Site checks awaiting decision and compare the submitted check’s site, inspection date, permit reference and issue count. Then use Site compliance board to distinguish that visit from later checks. An approved later visit should leave the earlier rejected status visible.

• Site checks awaiting decision — Submitted inspections with permit and safety context for the manager.
• Site compliance board — Checks grouped by their current review and completion state.

See the related process for the stage-by-stage handoff. Use the data model to inspect the record relationships and implementation to plan the first rehearsal.