Track contractor workforce evidence by site and period

Start with a matrix prepared by the responsible HR, compliance and legal specialists. Each row needs the requirement, its source, the facts used to assess applicability, the responsible party, the coverage period and the evidence expected. Include contract requirements as such; do not label every client-requested document a statutory obligation.

Current rules and jurisdiction matter. The Ministry of Labour's central OSH rules notification of 2026 is one primary source to assess where applicable. It does not justify using one universal checklist for every state, establishment or contracting arrangement. Have the qualified owner resolve the appropriate-government and coverage questions and record the dated conclusion.

Use plain names for the resulting evidence requests. A contractor should understand which site and period a request concerns and why an earlier submission has not satisfied it. Repeatedly asking for a vaguely named compliance certificate creates work without improving assurance.

In this fictional example, a contractor serves Site A and Site B. The register asks for evidence covering Site B for the current period. The contractor submits a document that is current but names Site A. The reviewer records received, scope unresolved, and asks for evidence or a qualified explanation of coverage.

Do not conclude from the site name alone that the contractor is non-compliant. Some requirements may operate at a different level. Equally, do not assume coverage because the company name matches. The reviewer needs the actual requirement and its applicability decision before accepting the document.

If a later review establishes that the evidence covers both sites, save that conclusion, its basis and the reviewer's authority. If separate evidence is needed, preserve the first submission and link the replacement. This makes the history understandable without forcing a future reviewer to reconstruct an email chain.

An expiry date says when a document ceases to be current under its terms. A coverage period says which activity or reporting period it evidences. These dates can differ. A document uploaded this month might concern a previous period, and an unexpired document may not cover a changed arrangement.

Give the register separate fields for issue date, validity where relevant, coverage start and end, receipt date, review date and the next required action. Allow not applicable or not stated where those are legitimate states, with a reason. Inventing an expiry date to satisfy a mandatory field can create false reminders and false confidence.

Worker transfers need the same care. When a crew moves between sites or contractors, retain the effective dates and the relevant evidence associations. A person identifier can help prevent duplicate records, but it should not imply that an old authorisation or obligation automatically transfers with the person.

Use states such as requested, received, under review, accepted for the stated scope, clarification required and superseded. Each state should carry an owner and the evidence needed for the next transition. Accepted should always have a scope; it should not mean that every aspect of the contractor's compliance has been certified.

A configurable approval engine can support this design. ERPNext Workflows describes role-based states and transitions. The actual authority matrix and documentary requirements must come from your organisation. A software administrator should not become the substantive reviewer merely because they can configure the form.

Escalations should follow the approved risk and contract process. A reminder email can chase a missing document; it cannot decide whether work must stop, a payment may be held or an exception is permissible. Route such decisions to the responsible authority and record the outcome separately from the upload history.

An operations dashboard usually needs coverage status, the exception and the next owner. It seldom needs unrestricted access to identity scans, individual bank information or complete employment files. Keep sensitive attachments in a restricted evidence store and expose only the fields necessary for each role.

Record why each personal field is collected, who can view it, who can export it and when it should be deleted or retained under an approved requirement. Include downloaded copies and contractor portal access in the design. Removing access to a dashboard does not recall spreadsheets already emailed around the project.

Set up a correction route. A worker's record or contractor association may be wrong. The responsible team should be able to investigate and correct it while retaining the minimum necessary history. Do not let an unresolved identity mismatch automatically become an adverse decision about the person.

Use a current document for the wrong site, an expired document for the correct site, a submission covering the wrong period and a worker transferred midway through the period. Add a reviewer who loses authority before completing the task. Ask the team to show the resulting status and escalation without editing the underlying history.

For management reporting, show accepted coverage, unresolved applicability and overdue evidence separately. A single completion percentage can hide the very issues that need attention. Track the age of unresolved questions and repeated rejection reasons so the team can fix the request process as well as chase contractors.

The register succeeds when a new reviewer can explain why a requirement was considered satisfied for a specific scope. It does not succeed merely because every row has an attachment.

1. Have the qualified owner approve the site and period obligation matrix.
2. Rework evidence requests so the required scope and acceptable proof are clear.
3. Test wrong-site, wrong-period and transfer cases through review and escalation.
4. Publish a minimal operational view while restricting the underlying personal documents.