Client-Record Inventory Template for a Small Business
How can a small business inventory client records before setting retention rules?
Create one register row for each meaningful client-record category, not every individual document. Capture the category name, examples, business purpose, client or matter relationship, sensitivity, systems and paper locations, duplicate copies, responsible owner, likely retention trigger, applicable requirements to verify, hold status and next review point. Interview the people who create and use the records, inspect actual systems and shared drives, and mark unknowns explicitly. Consolidate duplicate categories only after confirming that their purpose, obligations and disposal treatment are genuinely the same.
Set the inventory boundary
A record can be information created, received and maintained as evidence of obligations or business transactions. Use that broad concept to include client-related material the business controls, while keeping the inventory manageable through category-level rows.
Sources: Records management and retention and disposal policy - GOV.UK.
- Include evidence of client work, obligations and transactions.
- Limit scope to categories the business creates, receives or controls.
- Avoid deciding retention periods during discovery.
Find records across people, paper and systems
Find client records by following the work, not only by searching a shared drive. Ask each role where information arrives, where it is changed, which systems send copies and where completed work is stored. Check paper files, email, shared drives, line-of-business systems, devices, archives and outsourced services, then mark locations that still need confirmation.
- Interview people who create, use and file client information.
- Walk through processes from intake to closure.
- Inspect active, archived and outsourced locations.
Complete the client-record register
A useful client-record register gives each meaningful category one visible home for ownership, locations and unanswered questions. Include category name, examples, business purpose, client or matter relationship, sensitivity, locations, authoritative copy, duplicates, owner, likely trigger, requirements to verify, hold status and next review point. Write plainly enough that a colleague can locate the record and understand what remains to be checked.
- Record categories rather than individual files.
- Separate authoritative copies from convenience copies.
- Add a verification action for every unknown field.
Resolve duplicates, unknowns and ownership gaps
Duplicates, unknowns and missing ownership should become explicit work items before retention rules are designed. Treat one copy as authoritative only after confirming that it is complete, controlled and suitable for the category’s obligations. Group categories only when their purpose, requirements, trigger and disposal treatment genuinely match.
- Do not merge categories solely because files look similar.
- Assign an owner to every uncertainty.
- Keep convenience copies visible until their treatment is confirmed.
Hand the register into policy design
The inventory is ready for policy design when it represents material locations and makes uncertainty visible rather than claiming completeness. Before approving any retention rule, ensure every important category has an owner and every open question has a named follow-up action. Use the broader client-record retention policy process to verify rules, define controls and operate approved disposal.
- Confirm material locations are represented.
- Name owners for categories and open questions.
- Hand unresolved requirements to the policy decision process.
Client-record register template
Use one row for each meaningful client-record category. The register supports discovery and verification; it does not itself determine a retention period or authorise disposal.
| Register field | What to enter | Why it matters |
|---|---|---|
| Category and examples | A plain-language category name and representative examples. | Prevents a row from becoming an unhelpful catch-all. |
| Purpose and relationship | Why the information is held and its client, matter or transaction connection. | Supports later classification and rule verification. |
| Sensitivity and locations | Sensitivity considerations plus systems, paper stores, devices, archives and providers. | Shows where access, holds and reviews may need to reach. |
| Authoritative and duplicate copies | The controlling copy and known convenience or synchronised copies. | Avoids treating every copy as the same record without checking. |
| Owner and likely trigger | Accountable owner and the event likely to matter for future rule design. | Creates a clear handoff into policy work. |
| Requirements and unknowns | Requirements to verify, current hold status, unanswered questions and next action. | Turns uncertainty into managed follow-up work. |
Mark unknown information clearly and assign a follow-up owner. Do not infer completeness from a software-generated file list alone.
Related guidance
What follow-up questions matter most?
- Should every document have its own register row?
- Create a row for each meaningful category with the same purpose, obligations and expected treatment. Do not create a separate row for every individual document unless it needs a distinct decision.
- How do we find records outside shared drives?
- Inspect actual work practices as well as folders. Use staff interviews, process walkthroughs and checks of email, systems, paper storage and outsourced services.
- What if the requirement or owner is unknown?
- Mark the uncertainty, assign an owner and state the follow-up action. An unresolved field is safer than an unsupported assumption.
What steps does this workflow follow?
Build a client-record inventory
- Set the boundary: Include client-related information the business creates, receives or controls as evidence of work, obligations or transactions.
- Inspect real locations: Walk through business processes and inspect paper storage, inboxes, shared drives, applications, devices, archives and providers.
- Group into categories: Create one row per meaningful category whose purpose, likely obligations and treatment are expected to match.
- Name ownership and gaps: Identify the authoritative copy, accountable owner, duplicate locations and any question requiring verification.
- Prepare handoff: Move to policy design only when material locations are represented and unresolved items have an owner and action.