BlogHow-to

Your busywork lives in files too

The exports, workbooks, and note folders on your disk are busywork too. How to hand file work to AI that edits in place and reports back.

The two exports you need to merge are already on your Desktop. The notes that should become a client update are sitting in a folder called notes-final-2. None of this work has a URL, and all of it is still busywork.

Ask people what they would automate and they name the online chores first, the portals, the inbox, the listings. But an honest audit of a working week is heavier on disk than anyone admits: spreadsheets that need reconciling, documents that need assembling, lists that need cleaning, Markdown that needs to grow up into a deliverable. All of it sits on the same machine you do.

The work on disk

It is the same busywork grammar, re-keying, cross-referencing, tidying, merging, just pointed at files. The master workbook that drifts a little further from the export every month. The catalog sheet with four naming conventions and nobody sure which one won. The folder of exports that needs its totals in one place. The meeting notes that contain a status update the way ore contains metal: truly, but not usably.

File work also hides best. No unread badge sits on a messy folder. It just waits, and compounds, and eventually becomes a weekend.

Document assembly is the sneakiest of the bunch. The quarterly review, the onboarding packet, the board update: each is stitched from pieces that already exist, the numbers from one workbook, the narrative from last month's doc, the caveats from a notes file, and the stitching is an evening. Nothing about it needs judgment until the last pass, which is the only pass you want anyway. Hand off the stitching and keep the last pass.

The same handoff

Agent FM works your files the way it works your apps: directly, on your computer, in the folders you point at. It opens the workbook, reads the CSVs, edits the Markdown, assembles the doc. The rules do not change either. It reports what it changed, flags what it could not resolve, and anything meant for someone else's eyes waits for your OK.

Precision helps here the way it does everywhere: name the folder, name the files, name the destination. Files carry none of the ambient context an inbox does, so the ask carries it instead.

Merging messy exports is the cleanest first handoff, because the before and after are so easy to check.

Merge [file A, e.g. badge-scans.csv on my Desktop] and [file B, e.g. the webinar signups export in Downloads] into one tracker. Normalize first: one name format, one phone format, lowercase emails. Dedupe on email, keep the newer row when the same person appears twice, and log every collapsed dupe on a Dupes tab. Save it as [name, e.g. leads-master.xlsx] next to the originals and leave the originals untouched. Tell me the final row count, the dupes collapsed, and flag any rows too broken to place.
Use caseMerge two messy lists into one clean trackerMerge [list A] and [list B] into one deduped tracker with normalized columns.View →

Reconciliation is file work at its most thankless: two sources, one truth, and a variance hunt that eats a Saturday. Name both files and let the hunt happen to something else. You keep the judgment calls; it keeps the eyestrain.

Reconcile [the export, e.g. this month's rent roll export in Downloads] against [the master, e.g. the master workbook in the Properties folder]. Flag every variance: amounts that don't match, rows missing on either side, and anything recorded twice. Put the flags on their own tab with the likely cause next to each, and change nothing outside that tab. Tell me how many rows reconciled clean and how many need a human look.
Use caseReconcile the rent roll and flag every variancePull the rent roll from AppFolio, reconcile it against the master sheet, and flag variances.View →

That grammar also cleans a messy sheet in place: normalizing titles, fixing variant names, filling gaps from the supplier files, and flagging what does not line up instead of guessing. The pattern holds: the sheet changes, nothing else does, and the gaps arrive as a short list.

Use caseClean the product catalog before the season startsClean the catalog sheet: normalize titles and variants, flag gaps against the live Shopify listings.View →

Then there is the quiet one: notes into deliverables. This is where file work brushes up against judgment work, so the draft waits for you by design. What comes back is structured, sourced from your own words, and shorter than the folder it came from.

Turn the Markdown notes in [folder, e.g. the acme-project folder in my Documents] into a client-ready status doc. Structure it as: what shipped, what's in progress, what's blocked, decisions needed. Keep my wording where it's already clear and cut the fragments that were notes to myself. Draft only, nothing goes to the client until I've read it. Tell me which notes you drew from and flag anything you had to interpret.

Watching file work

Nothing here is a black box. Changes are described back to you, flags live on their own tab, dupes get logged rather than silently collapsed, and a draft stays a draft until you have read it. If a run ever surprises you, stop it; the report will say exactly how far it got.

Files do not matter more than apps. Busywork simply does not care where it lives, and the thing that takes it off your plate should not care either. Your work was never just tabs.

See also: How to automate the spreadsheet work between your apps and How to ask an AI assistant for real work.

Pick the folder you have been avoiding, hand it over, and read the flags that come back. Get early access on macOS or Windows; when access opens, make that folder your first handoff.

Related