Start with your register.
Download the free template or export your own UTF-8 CSV and map its headings. Keep one document requirement per row. Remove the fictional sample rows before using the template for real work.
Understand the registerMap your CSV columns, resolve possible matching records and keep an editable working register. Prepare owner handovers and document request drafts from honest recorded states.
Choose your CSV, map its columns and preview the records. This check runs in your browser; the file is not uploaded or saved.
Nothing is saved automatically. A working copy contains the original mapped records, edits and decisions. Keep your source CSV separately: omitted columns and raw date/state labels are not retained in this copy. A CSV contains active rows only, with formula-like cells prefixed for spreadsheet safety. Downloads may contain personal or business information.
Optional: save on this device. This is shared-browser storage, not a private account, backup or cloud sync. Anyone using this browser may reopen it. Save again after edits; clearing the page does not remove a saved copy.
The checker reads the business, document requirement, review state, recorded expiry and follow-up date from each CSV row. After checking required fields, recognised states and date formats, it separates missing, awaiting_review, rejected and approved records before applying approved-expiry planning rules.
A received replacement stays in the review queue. The date on a previously accepted record remains visible until someone reviews the new file; a spreadsheet cell cannot approve it for you.
Approved rows with an expiry inside your chosen window become renewal planning work. Invalid dates and uncertain states are flagged for correction instead of being counted as current.
Download the free template or export your own UTF-8 CSV and map its headings. Keep one document requirement per row. Remove the fictional sample rows before using the template for real work.
Understand the registerRun the check locally in this browser. Review every flagged row against the actual document, request and decision history. Keep corrections and original rows in a portable working copy. Device saving is optional; the tool cannot tell you whether a contractor may work.
Edit the responsible owner, prepare a grouped handover or draft one request for several document requirements. Use the renewal planner to work backwards from an accepted document’s expiry. A calendar reminder still needs a person to follow through.
Use the renewal planner Adapt a request emailThe results use only the values in your CSV and your selected assessment date, initially set from your device’s local date. They cannot verify a document’s authenticity, policy terms, licence status, coverage, or whether the right contractor sent it. A blank expiry may be intentional for a non-expiring item; confirm that with your team.
Register data stays in the browser session unless you explicitly download a working copy or choose to save on this device. Clearing the page removes the session data; use “Remove device copy” to remove an explicitly saved browser copy. Downloads and handovers may contain contractor or contact information. Preview the included fields and handle copies under your organisation’s rules.
See the fictional review workflowMap your headings to the four required fields, or use the template headings: business_name, document_required, recorded_expiry_date and review_state. Optional assessed fields are responsible_owner and next_follow_up_on. Context, a unique requirement identifier, date purpose/basis and a source reference can also be mapped. See the full field dictionary.
Upload UTF-8, comma-separated CSV up to 1,000 records and 1 MB. Pasted CSV is limited to one million characters. Double-quote a cell containing a comma; use two quotes for an embedded quotation mark. Dates must be real calendar dates in YYYY-MM-DD format. For numeric dates such as 01/11/2026, explicitly choose day/month or month/day with a four-digit year. ISO dates stay unchanged; the tool never guesses an ambiguous convention.
Duplicate or blank column names, unmapped required fields and malformed quotes prevent import. Review the preview and columns left out. Possible matching records require a reasoned decision before active exports. Edit records against your source, keep original mapped records in a portable working copy and retain the raw source CSV separately, and explicitly choose whether to save a copy in this browser.
| Queue | Trigger | What to do |
|---|---|---|
| Check data | Missing business/requirement, unknown state or invalid date | Correct against the source; do not guess |
| Review | awaiting_review, even if the prior expiry has passed | Ask the reviewer to decide on the received file |
| Request | missing or rejected | Check receipt and request history; request the file or correction |
| Check data | approved with a blank expiry | Confirm the expiry rule, or explicitly record a no-expiry purpose and its basis |
| Expiry | approved expiry is today or earlier | Recheck source evidence and decide the next action |
| Plan | approved expiry inside the selected window, or recorded follow-up due | Plan request and review dates; confirm a due follow-up still applies |
| Keep on register | approved expiry beyond the window and no due follow-up | Revisit later; this is not a verified compliance status |
Results are ordered Check data, Expiry, Review, Request, Plan, then Keep on register. An unassigned owner adds a prompt; it does not by itself create a data-error queue. Your assessment date starts with your device date and can be changed. The renewal window includes its final day.
If your spreadsheet has separate insurance and licence columns, choose “Separate columns for each document” in the import preview. Name each requirement and explicitly map its dates and review states. The converter creates one requirement per row while keeping a reference to the original wide CSV record.
Set each date’s purpose: document expiry, administrative review, next action or no recorded expiry with a documented basis. Prepare a handover by owner, or draft a request covering several requirements for one business and context. Each requested document gets its own chosen deadline. These drafts send no email.
For approved recorded expiries, select a batch calendar plan and inspect four all-day entries per requirement. Generic titles are the default; business and document names are optional. Reimporting can duplicate events in some calendar clients, and no alarms are configured. The weekly date view separates expiry signals from recorded action dates and follows your selected planning window; its counts do not estimate staff hours.
Compare another mapped CSV snapshot to see changed, unmatched and ambiguous recorded fields. This comparison does not reconstruct past events. A user-defined requirement matrix adds missing, undated requirements for your chosen work categories without supplying legal defaults. The manual evidence-check worksheet records your own issuer or regulator observations; it neither visits the source nor approves a document. Download a portable working copy to retain edits, decisions and observations, or explicitly save one copy on this device.
Our worked lesson uses four fictional rows: an ambiguous date, a replacement waiting for review, an unsupported state and an unassigned owner. It explains what a person must confirm before changing any field, with downloadable original and corrected files.
Follow the complete register cleanup lesson →