Why should your client records be plain text files?
Written for agents, brokers, lenders, contractors, home services.
The short answer
A plain text file is readable by you, by any editor on any machine, by any AI assistant you point at it, and by whoever opens it in fifteen years. A record inside a product is readable by that product.
Markdown is plain text with a handful of punctuation marks that mean heading, bold and list. Nothing else is hidden in the file.
Text files can be kept under version control, which means every draft is recoverable. Photos, scans and recordings sitting beside them are not, and your laptop backup is the safety net for those.
The format has no required fields and no validation, so it will let you spell one client three ways. Whatever writes into the folder has to enforce the naming.
Verdict: plain text for what a human writes and reads. The live numbers stay in the system that produces them, and the file says where to look.
Most conversations about getting organized are about which app to buy. Underneath that is a smaller question almost nobody asks, and it is the one that decides what you still have in ten years. What format are your records written in, and who besides the vendor can read them.
We keep client records in plain text files. The reason shows up on the days a business gets tested: the day you change brokerage, the day a platform gets acquired, the day somebody asks what you promised a seller in March of a year you barely remember.
What is a plain text record?
A plain text record is a file containing only characters, with no hidden formatting and no particular application required to open it, so any text editor on any computer can display exactly what is in it.
Markdown is the version worth using. It is plain text with a few punctuation marks that carry meaning: a hash mark starts a heading, two asterisks make bold, a hyphen starts a list item. The file ends in .md. Open it in Notepad or TextEdit and you see your words plus that punctuation, which is the whole story of the file.
Compare that to a record inside a product. Your notes about a past client live in a database on somebody else's server, in a shape designed for their software. You can read it through their screens, at their prices, for as long as they keep the account open and keep the feature. Every one of those is a condition somebody else controls.
What do you own when the vendor changes?
Three things happen to software businesses, and all three have happened to tools this industry uses. Pricing changes. The company gets acquired and the roadmap changes with it. Or the product gets shut down and you get ninety days notice and an export button.
The export button is where the damage shows. An export usually hands you a spreadsheet of the fields the product was built around: name, email, phone, stage, a date or two. What it tends to lose is the part that took years to accumulate. The sentence about which parent is really making the decision. The note that this buyer walked from a deal over a retaining wall. The reason you stopped referring one inspector.
There is a version of this specific to real estate that catches people at the worst moment. Some of the tools you use every day were provided by your brokerage rather than bought by you. Access to a brokerage platform typically ends when the affiliation ends. Find out what happens to your files on the day you leave, on a day when you are not leaving.
A folder of text files has no such day. There is no account, no seat, no renewal and no export. The records are already in the form you would have exported them to.
Who can read a plain text file?
- You, in any editor, on any machine, with no software to install. Mac, PC, a phone, a borrowed laptop at a title company.
- Any AI assistant you point at the folder. This is the one that changed recently and it matters more than people realize. An assistant can read a thousand of your own notes and answer from them only when it can open the files. Records locked inside a product are reachable only if that product built a way in and you are paying for it.
- Search tools you already have. The search built into your operating system finds text in these files without anything being indexed by a vendor first.
- Whoever opens the folder in fifteen years. A partner, an assistant, a buyer of your book of business, your estate. Plain text is the only format on this list with a track record that long.
What does version history protect, and what does it leave out?
Text files can be kept under version control. Git is the common tool for it, and the behavior worth understanding is simple: every time a change is saved, the previous state of every text file is kept. Delete a file by mistake, or let an assistant mangle one, and the earlier version comes back word for word.
Here is the part that gets left out of every article recommending this, and we made it a written rule on 2026-08-09 so nobody would forget it.
Where should a document sit, next to the record or in a documents folder?
Where should a signed document live?
A file sits in the same folder as the record it belongs to. One tree, no mirror. The signed disclosure for a past client lives in that client's folder, next to the note about them.
The alternative, a separate documents tree that mirrors the shape of your records, sounds tidier and fails the same way every time. Now every record needs a pointer to a document, every document needs a pointer back, and the first time anyone renames a folder half those pointers rot silently. You also get the question nobody can answer: which half holds this.
The exception is size. Large media stays in whatever system already handles it. Listing photo sets, walkthrough video, call recordings. Those do not belong in a records folder, and the record names the system and the folder where they live.
Where large files live gets recorded once, by service and named folder, and never by file path. "Listing photos, Dropbox, folder named Listings by address" survives moving between a Mac and a PC and survives being read by somebody else. A path starting with /Users does not. Writing "unknown" or "scattered" is a legitimate answer for a kind of file, and it is more useful than a guess made to fill in the blank.
What conventions does a text system need?
The format gives you nothing for free, so a small number of rules do the work a database schema would have done. These are the ones we enforce, and they are enforced silently by whatever writes into the folder rather than by asking the owner to remember them.
| Rule | What it looks like | What it prevents |
|---|---|---|
| One file per person, forever | Maria-Ortega.md, created once, referenced from every deal she appears in | The same human existing as a lead, a client and a referral source in three places, with three different phone numbers |
| Filenames in kebab-case | listing-appointment-notes.md, never Listing Appointment Notes FINAL v2.md | Broken links, and files that sort differently on different machines |
| Dates in ISO format | 2026-07-15, never 7/15/26 | Files sorting into the right order by name, and no argument about whether that is July or the fifteenth month |
| Frontmatter at the top of every file | A few lines carrying at least what kind of record it is and when it was last touched | A folder where nothing can be filtered or listed without opening every file |
| Cross-references as links | A deal file links to the person file. It does not copy her details in. | Two copies of one fact, one of which is already wrong |
What should never go in a text file?
Should you write live numbers into your notes?
No. A live fact belongs in the system that produces it, and the file says where to look. Prices live in the billing system, loan status lives with the lender, what is scheduled lives in the calendar, listing status lives in the MLS.
A note reading "under contract, closing on the fourteenth" is a sentence somebody typed on a Tuesday. It does not know when the appraisal came back low and the date moved. Nothing in the file will ever tell you it went stale, so it will be quoted to a client with total confidence six weeks after it stopped being true.
Where a number genuinely has to be written down, it carries the date it was checked and the system it was checked against. That way a reader can see the number is four months old and go look, rather than reading it as current.
The same discipline applies out loud. If somebody asks the status of a file and you are reading from a note, say when it was last checked before you say the number.
And nothing sensitive goes in these files at all. No passwords, no account numbers, no social security numbers, no lockbox codes. A text file has no lock on it. If something like that arrives inside material you are filing, take it out, file the rest, and say what you removed.
What does this look like for a working business?
Three folders. People, Assets, Deals. One file per person, one folder per transaction, and things that appreciate or decay in the middle folder. Plus one plain text file at the top, named CLAUDE.md, that tells an AI assistant how to work inside them: where to file what, how to name it, what it may never do, and when to stop and ask.
That operating file is the piece that makes the format pay off. It is written in ordinary English, you can read it, you can change a rule in it, and nothing is compiled or hidden. The rules in this article are literally lines in that file. When a rule turns out to be wrong, you edit a sentence.
The whole thing sits in a folder on your own computer. A markdown editor reads it, a version control tool keeps the history of the text, and your existing backup covers the documents beside it. Every piece is replaceable except the folder, which is the point.
The four boxes
Filled in for plain text as the format for client records in a real estate, lending or trades business, as of 2026-07-15.
There, and should be
Durable knowledge about people, written by a human, read by a human and by an assistant, in a format neither of them needs permission to open.
- Notes on past clients, referral partners, subs and vendors. The material that took years to gather and would take years to gather again.
- A record of what happened in a transaction and why, kept after the platform that produced it is gone.
- Decisions with a date and a name on them, which is the only thing that stops the same argument being had twice a year.
Missing, and should be there
Something that enforces the naming convention, because the format never will.
- The convention is the schema here. Check the folder for the existing spelling of a name before writing it, every time, without being asked.
- A weekly pass that surfaces links pointing at files that do not exist, files nothing links to, and numbers with an old checked date on them.
- A rule about what happens on arrival: an email, a call summary or a signed document turns up, and something routes it to the person or the deal it belongs to.
There, and should not be
Live numbers written into files, and a second copy of any record.
- A price, a rate, a stage, a closing date or an inventory count typed into a note. The note should name the system to check.
- A duplicate person file created because somebody typed the name differently. Merge it, and keep the older filename.
- Anything sensitive. Codes, account numbers, government identifiers. Take them out and say what you took out.
Missing, and correctly missing
No field validation, no required fields, and nothing enforcing that a link points at something real.
- For records a human writes and reads, this is correct. Required fields produce empty records filled with placeholder text, because the person filing at ten at night will type anything to get past the form.
- Real knowledge about a person arrives in an odd shape. She is afraid of a second flood, her brother is the one with the money, the deal died over a fence line. There is no field for any of that, and a format that demands one loses the sentence.
- The cost is exact: nothing stops you writing one person's name two ways, and the moment you do, you have two people. Nothing stops a link pointing at a file that was renamed. Nothing marks a required piece of information as missing.
- Which means the discipline has to live in whatever writes into the folder, and in a weekly pass that reads the whole thing looking for drift. Choose plain text and you have chosen to pay for the convention somewhere else.
When is plain text the wrong answer?
Common questions
- What is a markdown file?
- A markdown file is a plain text file, ending in .md, that uses a few punctuation marks to mean formatting. A hash mark starts a heading, two asterisks make text bold, a hyphen starts a list. It opens in any text editor on any computer, and nothing is hidden inside it.
- Why not just keep client notes in my CRM?
- Keep working the CRM for what it does on a schedule: sending, reminders, routing, reporting. The risk is holding the durable knowledge only there. Access to a brokerage-provided platform typically ends when the affiliation ends, and an export usually returns names, emails, phones and stages while the notes come back truncated or not at all. Keeping the knowledge in files you own removes that day from your calendar.
- Does version control protect all my client files?
- No. It protects text. Every draft of every text file is kept, so a deleted or mangled note comes back word for word. Binary files sitting beside them, signed PDFs, scans, photos, are excluded by file extension and have no version history at all. Your laptop backup is the safety net for those, and this distinction was written down as a rule on 2026-08-09 exactly because it is easy to assume otherwise.
- Should signed documents sit next to the client notes or in a separate folder?
- Next to them. A file sits in the same folder as the record it belongs to, so a signed disclosure lives in the client folder beside the client file. One tree with no mirror. Large media, listing photo sets, video and call recordings, stays in its own system, and the record names the service and folder where to find it.
- Can an AI assistant read plain text client records?
- Yes, that is one of the main reasons to use the format. An assistant with access to the folder can read every file directly, with no integration to build and no vendor to grant permission. Records held inside a product are reachable only through whatever access that product chose to offer.
- What stops plain text records from becoming a mess?
- A short list of conventions, enforced by whatever writes into the folder rather than by the person: one file per person forever, filenames in kebab-case, dates in ISO format, a few lines of frontmatter at the top of every file, and cross-references written as links instead of copied details. The format enforces none of that on its own, which is the tradeoff you accept when you choose it.
Worth passing along
This one serves an agent and a lender, because both of them carry a book of relationships across employers at least once. The agent changes brokerage and the CRM stays behind. The loan officer changes lenders and the loan origination system goes with the old badge. What survives either move is the folder of files about people, which is the only asset in both businesses that nobody can switch off.
Written by Brett K Moore. We build the PAD System, a records structure for people, assets and deals that lives as plain text files on your own computer. Read what it is.
Read next
What is Obsidian, and should a real estate business run on it?
Obsidian is a reader and editor for a folder of plain text files on your own computer. What that is good for in a brokerage, a loan branch or a crew, what it will never do for you, and the four box verdict. Written for agents, brokers, lenders and the trades.
How do you decide whether a tool belongs in your business?
A four box audit for a software stack: what is there and should be, what is missing and should be there, what is there and should go, and what is missing for good reason. Written for real estate agents, brokers, mortgage lenders and the trades who work alongside them.
Should Notion be where your business keeps its records?
Notion is very good at shared pages a team reads together. The question is whether it holds your records or shows them. The rule we adopted, the stale page that produced it, and the one case where content is allowed to arrive in Notion first.