How to Find and Document Lost or Undocumented Policies
Every organisation runs on some rules nobody wrote down, and others that were written once and then lost. This is a practical sweep plan for finding them, deciding which ones matter, and putting the right ones on record.
In short
Policy archaeology is a structured search for the rules an organisation actually follows but has never documented, or documented and lost. Collect evidence from old files, email, onboarding material, signage, contracts and regulator correspondence; interview the people who apply the rules; sort each find into obligation, policy, procedure or habit; then formalise, merge or retire it, with a named owner and a recorded approval.
Related guides: if your library has the opposite problem, see how to consolidate a bloated policy library. Many lost rules began as spoken instructions, so it is also worth reading how to document verbal policy changes.
Where unwritten and lost rules hide
Undocumented rules leave traces. Gather the paper trail before interviewing anyone, so you have specific things to ask about.
Old shared drives
Search folders like “HR” or “Ops” and files named “rules” or “guidelines”. Note each file’s date and author.
Email and announcements
All-staff emails that begin “Going forward…” or “Reminder that…” are often policy decisions that never made it into a document.
Onboarding decks
Compare every rule the training slides state with the policy library. Mismatches are prime finds.
Posters and signage
Break-room notices and signs by the till or loading dock. Photograph them by location; they often differ.
Manager habits
How approvals, overtime, refunds or discipline are actually handled. Consistent behaviour across managers usually points to an inherited rule.
Contracts and leases
Customer, vendor, insurance and lease agreements often commit you to practices no internal policy mentions.
Regulator and inspector letters
Inspection reports and licence conditions often hold commitments nobody turned into policy.
Forms and checklists
A required field on a form, or a box on a closing checklist, is a rule in disguise. Ask why it is there and who decided.
Interview the people who carry the rules
Documents show what was once decided; people tell you what still happens. Prioritise long-serving staff, site supervisors and trainers, plus recent joiners, who remember which unwritten rules surprised them.
Keep the tone curious: you are looking for gaps in the library, not individual mistakes. Useful questions:
- “What do you tell a new starter that isn’t in any document?”
- “What would get someone in trouble here, even though it’s not written down?”
- “When you’re unsure, who do you ask, and what do they usually say?”
- “Is anything done differently here than at other locations?”
- “Where did that rule come from?” If the answer is a regulator, a customer or an incident, mark it as high priority.
Record each find in a simple inventory: the rule in one sentence, where you found it, who applies it, which locations, and any evidence of where it came from.
Telling a real policy from a habit
Not every find deserves a policy. Sort each into one of four categories. The test: what goes wrong, and for whom, if people stop doing it?
Obligation
Required from outside
Comes from a law, licence, contract, insurer or regulator. It must be written down. Confirm the source and the current wording with counsel.
Policy
A decision about conduct
Leadership chose it, it applies broadly, and breaking it has consequences. Formalise it in the policy library.
Procedure
How a task gets done
Steps for a specific job or site. Document it as an SOP or checklist rather than inflating it into a policy.
Habit
Preference or legacy
Nobody can say why it exists and nothing goes wrong without it. Leave it informal, or say openly that it no longer applies.
Watch for conflicts. If a find contradicts a written policy, you have two rules for one situation. Escalate it to the policy owner rather than choosing between them yourself; the written version may be out of date, or the practice may be a compliance problem.
The sweep plan, step by step
Run the sweep as a time-boxed project with one coordinator. Piloting on one department or location shows how much there is to find.
- 1
Set scope and sponsor
Pick the departments and locations in scope, name a coordinator, and get a senior sponsor who can resolve disputes about whether a rule should exist.
- 2
Gather the paper trail
Work through the eight sources above. Log every candidate rule in the inventory with its evidence, even if it looks trivial.
- 3
Interview and observe
Ask specific questions from the inventory, and watch tasks being done; people skip steps they think too obvious to mention.
- 4
Compare with the library
Mark each find as missing, lost (an old document exists but is not in the current library), conflicting, or already covered.
- 5
Classify and decide
Apply the four categories, then choose: formalise, merge into an existing policy, document as a procedure, or retire. Record the reason for each decision.
- 6
Write up, approve and communicate
Draft the documents, route them through approval, and tell affected staff what is now official and what has been dropped.
Writing it up with an owner and approval
Each rediscovered rule needs a named owner, a clear scope, a note of its source (the contract clause, inspection letter or decision it came from) and formal approval by someone with authority. Record retirements too: a short note that the practice was reviewed and no longer applies stops it resurfacing.
When a lost document turns up as an old PDF, avoid retyping it. Policy management software can shorten the path from find to approved policy. In PolicyTrak:
Policy management
Import a PDF and AI extracts its content into a draft, or generate a first draft from a description. Drafts still need human review before approval.
Approval workflows
Approval chains can be set by category, department or sensitivity, with status tracking and reminders for approvers. Status changes are recorded in the audit log.
Version control
Every save creates a numbered version with the author’s name and date. Earlier versions can be compared side by side or restored, and nothing is overwritten.
NoteSoftware does not find unwritten rules for you. The sweep itself, including interviews, evidence gathering and the decisions about what to keep, is people work; the tools help once you know what to write down.
Preventing it happening again
Rules go undocumented through decisions made by email, managers leaving without handover, and commitments accepted in contracts or inspections that never reach the policy owner. Close those routes:
- One route for new rules. Agree that a rule is not in force until it is in the library and approved. Instructions given in email or verbally should point to the document.
- Contract and inspection hand-off. Whoever signs a contract or receives a regulator letter sends any new commitments to the policy owner.
- Exit handovers. Ask departing managers and long-serving staff the interview questions above before they leave.
- A lighter repeat sweep. Repeat a smaller version after reorganisations, acquisitions or high turnover.
Give Every Rediscovered Rule a Proper Home
Import old PDFs into drafts, route them through approval and keep every version on record. Sign up and see plans without booking a call.
