facebook alt Skip to main content
Support System status Security

Compliance

Self-employed workforce weekly ops checklist (UK)

UK weekly ops checklist for self-employed workforces: one file, rota, pay run and audit trail, with HMRC record-keeping links and how Zerity fits.

12 October 2026 · Zerity editorial team

Self-employed workforce weekly ops checklist (UK)
Compliance

Weekly ops for a self-employed workforce means one live file per person, one rota of who can work, one pay run from days worked, and one closed audit trail. Each week you finish onboarding gaps, review document expiries, publish availability, capture work done, run self-billing where agreed, then file who checked what.

That loop is how UK operators streamline weekly admin. Courier and delivery work is a common example industry, not the definition of the workforce. Zerity is one operating system for compliance and operations across your self-employed workforce. Day-one collection sits on how to onboard delivery drivers in the UK. Expiry depth sits on driver document tracking. Reviewed against primary GOV.UK, HMRC and ICO sources on 12 October 2026. This is general information, not legal advice.

The weekly cycle

Run the same six steps every week. Skip a step and the next one invents work: a rota without an expiry review puts the wrong people on shift; a pay run without a work record rebuilds days by hand.

  1. Onboarding gaps closed — every new starter has a live file before the first shift: agreement, identity evidence, licence and vehicle documents where needed, plus any network or client pack items. See onboarding tips and the onboarding checklist.
  2. Document-expiry review — walk photocard and entitlement dates, hire-and-reward insurance, MOT, tax, contract review dates, and any other time-limited item. Time-limited right-to-work permission is one diary row, not a separate weekly project. Depth: re-check checklist.
  3. Rota / availability — publish who can work, where, and on which day. Only people with an in-date file should be offered shifts.
  4. Work record — capture days (and any agreed units) actually worked. That record must match what finance will bill.
  5. Self-bill / pay run — where you raise the supplier invoice, do it from the agreed rate and work record, and, if the contractor is VAT-registered, against a written self-billing agreement put in place before you start, with a start and end date no longer than 12 months or the contract term. Process notes: HMRC self-billing for couriers (same rules for subcontractors more widely).
  6. Audit file closed — file who checked what, which documents were in force, and which invoices went out. Then stop editing last week's numbers.

Multi-site operators should use the same cycle at every location: start at depots.

Who owns each step

Name an owner. A shared inbox is not an owner.

Step Ops lead Admin Self-employed contractor
Onboarding gaps closed Sets the required file for the engagement Chases missing uploads and records clearances Uploads documents and signs the agreement
Document-expiry review Decides who may work when a date is close or overdue Runs the diary and logs reviews Renews and re-supplies evidence before the date
Rota / availability Publishes the week and blocks unsafe assignments Updates availability and depot tags Confirms or declines shifts
Work record Signs off disputed days Reconciles rota to worked days Flags missing or wrong days early
Self-bill / pay run Approves the rate card and the run Raises invoices and keeps agreements Checks the self-bill and reports errors
Audit file closed Owns the pack for carrier or HMRC questions Stores exports and access logs Keeps personal Self Assessment records

Time reality: estimate with your own volumes

Do not adopt someone else's "hours saved" figure. Build a week model from your headcount and sites: minutes to chase one missing document × overdue count; minutes to rebuild one person's days when rota and pay disagree × disputed count; minutes to find last week's check log × ask count. Use the compliance cost calculator as a worksheet for those inputs. It is a planning aid, not a promise of savings.

What to keep, and for how long

Record-keeping depends on whose records they are and which regime applies. Do not invent one statutory number for every depot file.

Limited company accounting records. GOV.UK company and accounting records says limited companies must keep accounting records (money received and spent, assets, debts and the other items listed there) for 6 years from the end of the last company financial year they relate to, or longer in the cases that page sets out.

Self-employed business records. What records to keep covers sales, income, expenses and VAT records where relevant. How long to keep your records says keep them for at least 5 years after the 31 January submission deadline of the relevant tax year (longer if the return is very late).

Self Assessment pay and tax records. How long to keep your records covers people who are not self-employed: keep records for at least 22 months after the end of the tax year if the return is sent on time, or 15 months after sending it if late.

PAYE payroll records. Where you run PAYE for employees, PAYE keeping records requires pay and deduction records for 3 years from the end of the tax year they relate to, and notes separate rules for minimum wage and holiday pay records.

Self-billing. VAT Notice 700/62 requires a written self-billing agreement in place before you start, with a start and end date no longer than 12 months or the contract term. Each invoice must meet HMRC's rules, including the 'SELF-BILLING' marking. You must keep the names, addresses and VAT registration numbers of suppliers you self-bill, and be able to show them to HMRC.

UK GDPR. The ICO storage limitation principle says not to keep personal data longer than you need it. Collecting and keeping employment records adds that UK GDPR does not set fixed retention periods for workers' information: justify the period, then erase or anonymise. Zerity does not publish a default retention interval for operator records.

Spreadsheet vs system thresholds

A shared sheet fails when volume or sites break the audit trail: missed expiries across tabs, days rebuilt from chat because the rota never fed pay, a date with no who-checked owner, or the same contractor under two rates at two sites. When any of those is weekly, compare what the sheet costs you each week with a shared system. Modules: product, operations hub, scheduling, compliance and invoicing.

Employment status stays fact-specific

Weekly ops assumes you already decided how each person is engaged. GOV.UK employment status explains that status in employment law helps determine rights and responsibilities, and that tax status may differ. Courts and tribunals can decide. HMRC's CEST tool gives HMRC's view for tax from the information you provide. Use those as tools, not as a conclusion that someone is "definitely self-employed."

How Zerity fits

  1. Collect documents and agreements through onboarding so gaps are visible before the first shift.
  2. Store each expiry on compliance, with a warning before a licence, policy or other tracked document lapses.
  3. Publish the week on scheduling; days worked feed the self-bill.
  4. Raise self-billed invoices from agreed rates and days worked on invoicing, with the self-billing agreement stored on the file. The software does not make the arrangement compliant on its own.
  5. See the same people across sites in operations hub, tagged by depot and by the network or client each site works for.

Zerity stores the driving licence record, the date it was checked and the expiry, and alerts you before it lapses. The operator remains responsible for the DVLA licence check, using the DVLA check code service or a licence-checking provider their insurer accepts, and for the prescribed right-to-work check, following the Home Office employer's guide. It is an offence to cause or permit someone to drive a vehicle they are not licensed to drive. Zerity records right-to-work evidence, the date it was reviewed and the follow-up date; the prescribed check, and the decision, stay with the operator. Pricing is from £6 per active driver — see pricing.

See Zerity on your own operation: book a demo or open the demo page.

Frequently asked questions

Is a weekly ops checklist the same as deciding employment status?

No. Status is fact-specific and can differ for rights and for tax. Use GOV.UK employment status and CEST as tools. The weekly checklist assumes you already know how each person is engaged and focuses on file, rota, pay and audit.

What belongs in the weekly review?

Onboarding gaps for new starters, document dates that can stop someone working, the published rota, the work record for the week, the self-bill or pay run where you use one, and a closed audit file of who checked what.

When does a time-limited document follow-up sit in the weekly cycle?

Inside the document-expiry review. If permission or another document is time-limited, the follow-up date is one diary row beside licence, insurance and MOT. It is not a separate weekly lead topic. Since 1 October 2026 right-to-work checks also apply to workers and individual subcontractors, and can reach substitutes and businesses further up a contracting chain. Check before work starts, by a manual document check, a Home Office share code beginning with 'W', or a registered right to work digital verification service provider. Keep the record for the engagement plus two years, and follow up before time-limited permission expires, as set out in the Home Office employer's guide to right to work checks (1 October 2026). Zerity stores the evidence, the review date and the follow-up date, and alerts you before it lapses; the operator remains responsible for the prescribed right-to-work check.

How should multi-site operators roll this up?

Use one file shape and one weekly cycle at every site. Tag people by depot and by network or client. Roll up overdue expiries, unfilled shifts and unpaid days to one ops view rather than reconciling separate sheets after the fact. Depots and operations hub describe that pattern.

What must be true before a VAT self-billing pay run?

A written self-billing agreement must be in place first, with a start and end date no longer than 12 months or the contract term, and the invoices must meet HMRC's rules in VAT Notice 700/62, including the 'SELF-BILLING' marking. Keep copies of agreements and supplier VAT details.

When is a spreadsheet no longer enough?

When missed expiries, duplicate pay, or missing who-checked logs are weekly events, or when two or more sites cannot agree on one person's file. That is an ops threshold, not a ranking of software brands.

Sources

Zerity

Written by

Zerity editorial team

The Zerity team writes about fleet management, compliance, and scaling logistics businesses, drawing from hands-on experience helping UK courier companies streamline operations.

See this on your own fleet.

Book a 20-minute demo. A product specialist walks through your depots, contracts and the work this article describes.

See Zerity on your own depot

From £6 per active driver

Book a 20-minute demo