North build
Correspondence / 18 files
✓ Matched identifierGoogle-first property records
Property Project Tracker turns long-running Gmail threads and attachments into an organised, searchable record across Drive and Sheets, without asking AI to guess where anything belongs.
Fictional filing plan · no property data
Correspondence / 18 files
✓ Matched identifierCorrespondence / 11 files
✓ Matched identifier1 ambiguous message
! No guessingThe operating principle
Known addresses, lot references and project terms route mail. A message that matches none or more than one project goes to a clearly labelled review queue.
A traceable filing route
The workflow is deliberately boring where property evidence matters: bounded searches, exact fingerprints and a visible fallback.
Configured project identifiers find relevant correspondence without scanning the entire mailbox each run.
Deterministic terms produce a single route. Zero or multiple matches go to review.
Normalised body text and exact attachment hashes collapse copied thread deliveries.
A readable HTML record and each unique attachment land in the project’s Correspondence folder.
A tracker row retains received date, route, sender, subject and direct Gmail and Drive links.
One malformed message cannot stop the batch, and uncommitted items remain available for the next run.
The tracker Sheet
Every processed message gets an index row, so a document can be found by project, date, sender or subject without hunting through folders.
Safety by design
Folder IDs stay in private Script Properties. The automation creates new correspondence records and tracker rows, but does not move or delete pre-existing property documents.
A Drew’s Digest project