FIELD GUIDE / 01

The register behind every next move.

A contractor document register only helps when it separates what you asked for, what arrived, what a person approved, and what happens next.

Download the CSV template Includes two clearly fictional example rows. Remove them before adding your own data.
SITENOD / FIELD NOTE01—04
One record.
Four different facts.
  1. 01RequestedThe ask is recorded.
  2. 02ReceivedA file has arrived.
  3. 03ReviewedA person decides.
  4. 04Next actionFollow up or renew.
A file arriving never means it was approved.

01 / WHAT TO RECORD

A useful register tracks the next action.

Names and dates are only the start. A team also needs to know whether a replacement has arrived, whether someone reviewed it, and who owns the next step.

Fields included in the downloadable register
FieldHow to use it
Business and contactWho the request is for and where to send it. Check the address before sending anything.
Document requiredThe exact document your team has decided to request. Keep separate rows for separate requirements.
Recorded expiry dateThe date shown on the accepted document, if one exists. Leave it blank for a missing document.
Review stateUse missing, awaiting_review, approved or rejected. An upload alone is not approval.
Responsible ownerThe person or team expected to make the next decision or follow up.
Last request and next follow-upRecord what was actually sent and the next planned contact date. Leave a date blank when it has not been decided.
NotesA short factual explanation. Do not put passwords, bank details or unnecessary personal data here.

02 / WORKED EXAMPLE

Missing, received and approved are different.

Harbourline Services has no accepted public liability insurance document. The recorded expiry stays blank and the state is missing. The office team owns the follow-up.

Summit Air Solutions has a trade licence replacement awaiting review. Keep the previous accepted expiry visible until a person decides on the replacement. If the team rejects it, record the reason and the next action.

Both rows are fictional. The template records your team’s information; it does not verify coverage, authenticity or permission to work.

03 / A SIMPLE ROUTINE

Keep the register current.

  1. Assign an owner. Decide who checks new documents and who follows up on missing ones.
  2. Record the request. Note the date sent and the document requested; do not mark it received yet.
  3. Review the replacement. Check it against your own requirement and record the person’s decision. Preserve the previous version elsewhere if history matters.
  4. Set the next action. Use a follow-up date for a missing or rejected document and a reminder date for an approved expiry.
  5. Check the list regularly. A spreadsheet cannot prove that a message was delivered or that a document is valid. Reconcile the rows with the source files and decisions.

TURN THE REGISTER INTO A ROUTINE

Make the next date visible.

Check the template in your browser to find rows needing a request, a review or a renewal plan. Then use the planner to work back from an accepted expiry.

The exact columns the checker reads

Keep one requirement per row, even when one contractor supplies several documents. The CSV template has ten columns. Map its six assessment fields or use your own headings. Site/policy context and a record identifier can also be mapped to keep distinct requirements separate. Contact and historical notes remain outside this check.

CSV field dictionaryScroll sideways to see every column. When the table is focused, use the left and right arrow keys.
HeadingChecker useExample or rule
business_nameRequired heading and valueFictional Harbourline; the business for this requirement
document_requiredRequired heading and valueExact requirement chosen by your team
recorded_expiry_dateRequired heading; value may be blank2026-11-01; real YYYY-MM-DD date, not a guessed date
review_stateRequired heading and valuemissing, awaiting_review, approved or rejected
responsible_ownerOptional headingOffice team; a blank adds an assignment prompt
next_follow_up_onOptional heading2026-10-05; real YYYY-MM-DD date or blank
site_context, record_idOptional mapping fieldsDistinguish sites/policies; use a unique requirement identifier, not a shared business identifier
date_purpose, date_basisOptional mapping fieldsexpiry (default), review, action or none; no recorded expiry needs a stated basis and blank date
source_referenceOptional source pointerA user-maintained reference; not a verified or immutable audit trail
contact_name, contact_emailNot read by the checkerCheck your own contact record before sending
last_requested_on, notesNot read by the checkerRecord actual requests and factual review context yourself

Save as UTF-8, comma-separated CSV. The import preview recognises template headings and asks you to map other headings explicitly. Confirm unfamiliar review-state meanings and date conventions. Possible matching business/document/context rows are flagged for a manual decision; nothing is automatically deleted. Keep original source evidence under your organisation’s own rules.

Give each state a precise meaning

Four recorded review statesScroll sideways to see every column. When the table is focused, use the left and right arrow keys.
StateUse it whenNext human action
missingThe requirement still needs a fileCheck the request history and ask for the document
awaiting_reviewA replacement arrived and awaits a decisionReview it; keep the previous accepted expiry distinct
approvedYour reviewer recorded acceptancePlan around the recorded expiry; acceptance is not a coverage or site-access guarantee
rejectedYour reviewer decided a correction is neededRecord the reason and request the specific correction

Do not enter “approved” just to remove a warning. An approved row with no expiry is flagged for you to confirm the date rule. If your own requirement has no recorded expiry, choose that date purpose in the editor, clear the date and enter its basis. Administrative review and next-action purposes do not become document expiry claims. None of these choices proves legal compliance.

A weekly review someone else can take over

A weekly check is a suggested office routine. Increase or reduce its frequency for your own workload and requirements.

  1. Check new receipts against the review queue before sending another chase.
  2. Give each pending decision or request an owner. Record the actual send and reply, not merely the planned date.
  3. Review near and passed expiries against source evidence. Keep old evidence and the replacement distinct until the decision is recorded.
  4. Set the next follow-up, then leave a handover note: what is waiting, who owns it, which source to check and the next action date.
  5. At handover, confirm the receiving person can access your approved source records. SiteNod’s public tools provide no shared storage or audit trail.

A plain CSV sends no reminders. Spreadsheet products can support notifications when separately configured; this template and checker do not configure them.

Work through a messy register before and after →