Workers with Multiple Roles in a Training Matrix

One person, one row, combined assignments

Duplicating a person under two role tabs is how dates diverge. Keep a single worker record and apply every requirement that any active role assigns. If Friday’s work is banksman duties and Monday’s is MEWP operation, both requirement sets must be current before those days. Mark roles that are historical or occasional so templates do not silently drop requirements when the “primary” role label changes in HR.

Setup checklist for multi-role people

• Unique worker ID and a single display name
• Primary role plus additional active roles listed explicitly
• Requirement set calculated as the combination of those roles
• Not-required only where no active role assigns the item
• Project-specific assignments layered on top when a site adds extras
• Review date when roles change (promotion, demotion, acting up)
• Evidence still attached per requirement, not per role nickname

Workflow when someone starts acting up

Acting-up is the most common multi-role event on construction sites. Handle it as a controlled assignment change.

1. Record the new or temporary role on the worker with an effective date.
2. Add any newly assigned requirements (for example SSSTS) immediately.
3. Filter gaps before the person supervises or operates under the new role.
4. Book training or arrange cover if critical requirements are missing.
5. When acting-up ends, remove the temporary role and recompute assignments—do not leave orphan requirements unmarked.
6. Export a fresh named list for the project if the client tracks supervisors separately.

Avoid the “easiest role wins” trap

Spreadsheets often colour a row green based on the role template last applied. That erases plant categories when someone is re-labelled “general operative”, or drops first-aid when they move off a cover roster but still hold the certificate you rely on. Prefer additive assignment with explicit removal. For matrix templates, document how multi-role combination works so every administrator applies the same rule.

Client inductions and site-specific briefings still sit as project requirements on top of portable role assignments. A multi-skilled operative attending three sites needs three induction lines if your process assigns them that way—role combination does not invent a universal induction. Review multi-role people before major mobilisations; they are over-represented in gate failures because someone assumed “they’re skilled so they must be fine”.

Template and system limits

FieldClear tracks the requirements you assign to each person. It does not decide which roles someone may perform or prove competence across those roles. Templates help you structure assignments; they do not guarantee compliance. This guide is not legal advice.