A notice lands. You have days to answer.
A labour inspection notice or a customer audit letter asks for registers, wage records, attendance and returns for a site and a period - often for your contractors too. Teamnet gathers what the notice asks for, site by site, ready to send, and shows the gaps to close first.
Where the answer breaks today.
Records in many hands
Contractor registers, wage sheets and returns sit with each contractor, in their own formats.
The clock runs while you chase
Days go on phone calls and emails before anyone knows what is missing.
Gaps found while answering
A missing month or an unpaid due shows up in the file you are about to send.
The records the notice asks for, per site, ready to send.
Pick the site and the period on the notice. Teamnet lists every record asked for, from your own staff and every contractor, and marks each one Ready or Needs review with a plain reason.
| Record asked for | From | Status |
|---|---|---|
| Wage register, March | Contractor A, Contractor B | Ready |
| Attendance register, March | All contractors on site | Ready |
| Social security returns, March | Contractor C | Needs review |
| Bank proof of wages, March | Contractor B | Needs review |
Example data. Each Needs review item goes to the contractor or site team that can fix it, on record.
What you get, and how soon.
The list at once
The records the notice names, for that site and period, as soon as you pick them.
Gaps first
What is missing or does not add up is shown first, with who needs to fix it.
A pack you send
The records you choose to send, in one pack. You decide what goes out.
No promise of outcome
The inspector, the authority or the customer auditor decides. Teamnet makes the records ready; it does not answer for you.
What changes when the next notice comes.
- Days spent answering, not chasing.
- Gaps closed before the file goes out.
- The same records ready for the next notice, every month.