Multi-site operators

How Construction GRC is set up for you

An operator with several sites needs a consistent way to name inspections and compare them over time. Site checks retain the site, inspection date, permit reference and open safety issue count. Assessments add a separate period, business-unit counterparty, owner and scope. The organization relationship lets the team review each record in the correct operating context.

Start with two locations and a single assessment period. Record a check for each site, then plan control tests against the applicable business unit. Submit one check for decision and create one failed test with a finding. Confirm that the review queue and owner views show the right records without combining different sites.

For a multi-site operator, use the same site naming rule at both locations and compare inspection dates before reading the issue counts. Keep each site check linked to its organization and assessment. A failed control test should remain associated with its own assessment period when the team looks across locations.

When the pilot reaches a failed result, record the correction owner and due date. Ask a different person to perform the retest. A passing result can close the finding; a failed or inconclusive result keeps it in follow-up. This is the clearest way to check that the team understands the boundary between doing the correction and verifying it.

Use [implementation](/grc-for-construction/implementation) to plan the rollout and [the data model](/grc-for-construction/data-model) to check the relationships before importing records. Review [roles](/grc-for-construction/roles) with the people who will inspect, test, correct and retest.