One page per job.

Every naming convention works for about three weeks. Then someone saves "Copy of Untitled document", someone else uses underscores instead of dashes, and the person who wrote the convention leaves.

Google Drive has no bulk rename. You can rename files one at a time, or you can write an Apps Script that does find-and-replace on names that were meaningless to begin with.

A scanner names a file by the order it came off the glass. Scan_0043.pdf tells you it was the forty-third thing scanned, which is the one fact about it you will never need.

The best explanation of the whole topic happened on a whiteboard, and it exists as IMG_3312.jpg between a photo of a parking sign and a picture of somebody's lunch.

You remember a 2019 paper, something about attention, a figure on page four. Your folder holds two hundred PDFs named things like 1-s2.0-S0022314X19301234-main.pdf.

Six accounts, twelve months, two years. Every file downloaded from every bank is called something like eStmt_0831.pdf, and the reconciliation needs the one from March on the account ending 4471.

One household holds a joint account at one custodian, two IRAs at another and a trust account at a third. Every statement cycle produces three files named three different ways, none of which contain the family's name.

Every return starts by finding last year's. It is in a folder named after the season it was prepared in, under a filename that says "final", next to two other files that also say final.

The merge itself takes a minute. Collecting the six documents from four places, putting them in the right order, and remembering to do it every month is the part that costs you.

You put eleven invoices through the sheet feeder and got one PDF back. The scanner treated a stack of separate documents as a single document, because as far as it knows a stack is what it is.

The contract is in an email from March. So is the invoice, the signed W-9, and the revised statement of work. Your inbox has become a filing cabinet that only opens with a search box.

Every receipt you need in April arrived in your inbox between January and December, and you will look for all of them in the same frantic week.

Somebody posted the signed contract in #clients about four months ago. You know it exists, you know roughly who posted it, and you are scrolling.

Teams does not have a file store of its own. Every document posted in it is really sitting in SharePoint or OneDrive, and which one depends on where it was posted — which is why they are so hard to find again.

The plumber sends one PDF for the month: three call-outs, two buildings, one total. It arrives as a reply to a text-message thread forwarded into email, and month-end is in four days.

A return needs eleven documents. The client sends four in one email, one as a photo taken at an angle, two more a fortnight later replying to the wrong thread, and then asks whether you got everything.

Six forms go out to a new starter on Monday. Four come back over the following fortnight, in three separate email threads, and on their first day nobody can say which two are missing.

Three months later the client says they never approved that headline. The approval exists — in a Slack thread, in a channel that has since been archived, from an account manager who has left.

Onboarding one household means statements from three custodians, two forms of identification, a trust deed, a signed agreement and a risk questionnaire — arriving over three weeks, several of them as photographs taken in poor light.

Six forms went home with four hundred students. They come back over a fortnight — some in backpacks, some as photographs texted at 11pm, some not at all — and the trip is on Friday.

The rate confirmation comes from the broker on Monday, the signed bill of lading is a photo your driver sends on Wednesday, and the proof of delivery arrives as a scan from the receiver on Friday. All three belong to load 7842 and all three are called something else.

The final report is due Friday and needs participant numbers from one person, receipts from another, and three photographs with signed releases from a program that ended in March.

The borrower has sent one paystub, a photograph of a W-2 taken on a kitchen table, and page one of a five page bank statement. Underwriting needs all five pages and the second paystub, and it is Thursday.

Outlook rules can file the message, flag it, categorise it and forward it. What they cannot do is take the attachment out and put it somewhere useful, which is the only part anybody wanted.

Most file automation starts the day you switch it on. The four thousand documents already in the folder — the ones that sent you looking for automation in the first place — are exactly the ones it will not touch.

Most retention policies are a document describing what should happen to other documents. Nothing reads it, so nothing happens, and the drive keeps everything forever — which is its own kind of exposure.

The document gets filed correctly and then somebody opens it, reads four fields off it, and types them into something else. That second job is the one nobody counts.

Two people forward the same invoice. One replies to the thread with it attached, the other uploads it. Nothing is wrong with any of them and you now have three.

Full automation is easy to build and hard to trust. Most teams do not want the workflow to stop — they want to be asked before the one step that would be awkward to undo.

Power Automate can move a file when a column changes. It cannot tell you what the document is, which is the part you actually needed.

Every document belongs to a matter, and every matter has the same six folders. The filing is entirely predictable, which is exactly why nobody wants to be the one doing it.

One auto claim arrives as fourteen separate things: the loss notice, six photos from the insured’s phone, a police report, two estimates, the adjuster’s notes and a signed release — each from a different person, on a different day, named whatever their device called it.

The COI spreadsheet is accurate on the day somebody builds it. Then a vendor renews, sends a fresh certificate to whoever asked for the last one, and the spreadsheet quietly describes a policy that no longer exists.

A submittal arrives as a reply to a forwarded email, from a subcontractor who called it "shop dwgs rev2.pdf", to a project engineer who is on site and will open it tonight.

Nobody looks at a jobsite photo until eighteen months later, when an owner claims the block-outs were never formed and the only proof is somewhere in a superintendent’s camera roll from a Tuesday in March.

A credentialing spreadsheet is correct on the day it is built. Then one physician renews a DEA registration, emails the certificate to whoever asked last time, and the spreadsheet quietly describes a registration number that no longer applies.

A billing question about a claim from March is really a question about which fee schedule was in force in March — and the answer is in an email attachment from two years ago called "amendment final".

The deposit dispute arrives in November about a move-out in July. The inspection form is filed. The forty photographs that prove the carpet was already stained are in a phone belonging to someone who left in September.

It is week eleven. The Downloads folder holds four hundred items, thirty of which are called lecture.pdf, and the midterm is on Thursday.

The production arrives as one PDF of four thousand scanned pages with no text layer, a filename of PROD0001.pdf, and a deposition in nine days.

The photographer delivers 120 images per property in a folder called exports_final, and by the third price reduction there are three sets for the same house and no obvious way to tell which one is current.

The question arrives three years later, usually from a lawyer, about a deal nobody at the brokerage worked on, filed by an agent who left in the meantime.

Forty employees, eleven kinds of certificate, all renewing on their own schedules. The tracking spreadsheet was accurate the day it was made, which was fourteen months ago.

Somebody asks whether the household ever signed the updated agreement. There is a signed copy, an unsigned draft, and a scan of a page with a signature on it, and no obvious way to tell which one governs.

Enrollment closes and the scanner has produced four hundred files named scan0001.pdf through scan0400.pdf. Each one belongs to a different family, and the only thing distinguishing them is handwriting.

A request arrives for everything held on a student who enrolled six years ago, moved between two schools in the district, and whose paperwork spans a paper era and a scanned one.

Three years later somebody asks what the depreciation figure was based on. The folder holds the client's documents, the preparer's working schedules and the delivered return, in one list, sorted by name.

An auditor asks for the file on a driver hired three years ago. The medical card is in a filing cabinet, the motor vehicle record is in somebody's email, and nobody is certain the annual review was ever done.

A new board member asks what was decided about the building lease. The answer is in minutes that were emailed as a draft, approved at the following meeting, and never saved anywhere in their approved form.

The file was ready in July. The appraisal came in low, the borrower disputed it, and now it is September and half the documents in the folder are too old to close on.

Your retention schedule is written in record series: employment records, financial source documents, contracts, student records. Your shared drive stores a filename, a date and a size. Nothing in the second tells you the first, so a person has to decide, and they decide three years late from a filename.

Somebody leaves, and the folders they leave behind are organized around how they personally thought about the job. Nobody else can read it, the person who could is gone, and the clock on reassigning their storage is already running.

The folder is not the problem. The problem is that six months later nobody can tell which of logo-final-v3-APPROVED-b.ai was the one the client actually signed off, including the person who made it.

Filing one contract takes ten seconds. The problem is doing it consistently for twelve clients across three years, while the work that actually pays is always more urgent.

Every agency has a filing system. Most of them exist as an agreement between the two people who have been there longest, and neither of them can say what happens to a certificate for a policyholder who is also a claimant on somebody else’s claim.

ABC Plumbing is on four of your jobs. They have one insurance certificate, one licence, four contracts and a lien waiver for every draw — and the certificate is currently filed in whichever job needed it most recently.

An inspector asks for the calibration history of one centrifuge. The purchase paperwork is in a folder named after the year it was bought, the service reports are in three different inboxes, and the warranty is in a drawer.

A tenant asks whether they are allowed a second cat. The answer is in an addendum signed eleven months ago, attached to a renewal that replaced the original lease, in a folder holding four documents all called "lease signed".

A client calls about a letter from the IRS concerning 2023. The preparer who handled 2023 left in the spring, and their filing convention left with them.

Month close is not hard because the ledger is hard. It is hard because the source documents for it are in an inbox, a phone camera roll, a Slack channel and a folder of scans called IMG_4829.jpg.

Someone asks which of your vendor agreements contain a non-compete. There are ninety of them, in four folders, and about a third are scans.

A deal produces about thirty documents from eight different people over six weeks, and roughly a third of them arrive as a photograph of a signed page taken in a car.

Somebody asks for an employee's file. What comes back is a folder holding their offer letter, their reviews, a doctor's note and a copy of their passport — three of which several jurisdictions say should not have been in there.

The client asks for the banner you delivered in March. There are five files with almost the same name, two of them say FINAL, and the newest one was edited a week after delivery by someone trying something out.

A truck goes down in another state and the shop asks what was done to it last. The answer is in a repair invoice from a different shop, filed under the month somebody paid it.

The renewal application asks what you told this funder last year. The proposal is in a shared drive, the award letter is in the executive director's email, and the final report is on somebody's desktop.

The appraisal is in the inbox, the title commitment is in a portal, the initial disclosures are in the origination system, and the borrower documents are spread across four email threads.