Practical AI · 3-minute read
Somewhere in your shared drive are three final proposals, two approved price lists and a folder called OLD_DO_NOT_USE that someone used yesterday. The filing system has developed a rich inner life.
AI can help organize that mess. It cannot reliably decide which document has authority from the filename, the newest timestamp or how confidently the first paragraph introduces itself.
Start with one document family
Consider Sandridge Buildworks, a fictional construction company. Its office has four versions of a standard subcontractor welcome packet. The newest file contains an unapproved payment-term edit. The approved packet is older. Sorting by ‘last modified’ would confidently promote the wrong one.
Start with those four files, using an approved system. Ask AI to compare their contents and surface differences. Give each file a stable reference so someone can find it again. The output should describe what changed and where, leaving approval decisions to the responsible person.
Then create a small document register. Each entry needs a purpose, accountable owner, approval status, approved version or effective date, authoritative location and next review trigger. The register tells people where to go; it does not require copying every document into another folder.
Give the tool a sorting job
Using these approved document descriptions or files, draft a register with title, purpose, owner if stated, stated approval status, version, effective date and source location. Group possible duplicates and identify material differences with page or section references. Mark missing details ‘Unconfirmed.’ Do not infer approval from filenames or timestamps. Do not rename, move, merge or delete anything.
A useful comparison might say, ‘File C changes payment timing in section 4; approval not supplied.’ It should not say, ‘File C is the current policy.’ That second sentence needs evidence and a person with authority.
Confirm before cleaning up
Have the document owner inspect every material difference and confirm the version people should use. Label drafts and superseded copies clearly. Check applicable retention requirements before archiving or deleting anything, especially signed documents and records connected to active work.
Use your existing platform’s version history where appropriate. Microsoft documents version history for files stored in OneDrive or SharePoint. It helps trace changes and recover earlier versions; it does not decide which change your business approved. [1]
Finally, ask a coworker to find the approved packet using their own access. If they still ask which ‘final’ is final, the cleanup is unfinished. Check that the register does not expose restricted file names or locations to the wrong audience.
Begin with one document family people use every week. Once its owner, approval and location are clear, repeat. You are building a habit the next upload can survive.
Your turn: Which document in your workplace currently has more than one version claiming to be in charge?
Source [1]: Microsoft Support: View previous versions of Office files. The document register, prompt and construction scenario are original editorial guidance.
