Guide · Updated 2026-10-02
Can One Training Matrix Cover Multiple Sites?
One training matrix can cover multiple sites when it is built around named people and portable requirements, with site-specific items (inductions, permits, local briefings) added as separate columns or filters. What fails is one spreadsheet per site that drifts out of sync — or one blob of columns nobody can filter by Monday morning.
Quick answer
Keep a single source of truth for worker identity, CSCS, plant tickets and other portable cards. Add site or project tags and site-only requirements beside them. Filter to the crew for Site A without maintaining a second “truth” file for Site B.
What belongs once versus per site
| Record type | Usually |
|---|---|
| CSCS, IPAF, first aid, SMSTS | Once per person — portable |
| Company induction / role baseline | Once (or by role), not per site |
| PC / client induction | Per site or project |
| Local permit or brief | Per site — time-bound |
Avoid the multi-file trap
- Do not email “Site B matrix.xlsx” as a fork of Site A
- Use project or site fields so filters answer gate questions
- Archive finished-site columns instead of deleting history
- Give one owner for the live file and clear deputies
- List portable requirements that follow the worker.
- List site-only requirements for each live contract.
- Tag workers to current sites or gangs.
- Test a Monday filter for one site before you scale.
Honest limits
FieldClear can hold one workforce view with filters and evidence. It does not decide which site rules apply or replace principal-contractor systems. Multi-site structure is your operational model. Not legal advice.
Already have a spreadsheet?
Upload your existing matrix and see who’s current, what’s expiring and what’s missing.
14-day free trial. No card required.