A live fact is anything that can change without your file knowing it changed. A price, a loan rate, a deal stage, a job status, a schedule, an account balance, a commission split, or what is currently listed and at what number. The test is whether something outside your note can change the fact while the note sits there.

What should a file say instead of the number?

Where to look. One line naming the system that owns the fact and the record inside it, specific enough that somebody who is not you could open it. Prices live in the billing system, what is scheduled lives in the calendar, listing status lives in the MLS, and the closing date lives in the transaction system.

What if a number has to appear in a proposal or a bid?

Then it carries the date it was checked and the name of the system it was checked against, on the line itself rather than at the top of the document. When it changes, the old line stays with a mark on it and the new line goes underneath, so the record shows how the number arrived and not only where it landed.

Should records update themselves from the systems that own the numbers?

No, and the absence of that connection is deliberate. A record that refreshed its own numbers would rewrite history on every run, erasing the evidence that a date or a price ever moved. The cost is that a person has to go and look, and nothing in the folder announces that a note is old, which is why a weekly pass over checked dates belongs in any working setup.

Library

Why should a price never be written into your notes?

Brett K Moore25 July 20269 min readHow the system works

Written for agents, brokers, lenders, contractors, home services.

The short answer

Because a price changes and your note does not. A live fact is anything that can change without your file knowing it changed, and the file should say where to look instead of holding a copy.

Prices live in the billing system. What is scheduled lives in the calendar. Open work lives wherever the work is tracked. What is published lives at the host. Listing status lives in the MLS.

Two records of one fact means two answers, and neither one carries a mark saying it lost.

The half people skip: the same rule holds when you say it out loud. Say when a number was last checked and against what, in the same breath you state it. If you have not checked it, say that first, before the number.

Where a number has to be written down anyway, it carries the date it was checked and the name of the system it was checked against. Superseded material gets marked and never deleted.

A buyer asks a loan officer what rate he can get. The loan officer says a number, because that is the number he gave the last three people and it was right on Monday. It is Thursday. Nothing in his head told him the number moved, and the note he typed on Monday did not tell him either.

One rule sits at the center of every records system we build, and it is the rule people argue with before they use it and defend afterwards. Never write a live fact into a file.

What is a live fact?

A live fact is anything that can change without your file knowing it changed: a price, a loan rate, a deal stage, a job status, a schedule, an account balance, a commission split, a medication dose, or what is currently listed and at what number.

The test takes a second. Ask whether something outside your note can change this while the note sits there doing nothing. If the answer is yes, the fact is live, and it belongs in the system that changes it.

The opposite kind of fact is settled. A birthday. The words somebody used in a driveway. The date a contract was signed. The reason a deal died. The name of the inspector you stopped referring. Those do not move once they happen, so a file is the right home for them and there is nothing to keep in step with anything else.

Almost everything people want from a client record is the settled kind. Almost everything people write into one is the live kind, because the live kind is what somebody asked about this morning.

Why a copy goes stale without saying so

When you copy a number out of the system that owns it, you have made a second record of one fact. From that moment the two can disagree, and the copy has no way to tell you it lost. It looks identical on the day it is right and on the day it is wrong. That is the entire problem in one sentence.

The harm is rarely the number by itself. The harm is the confidence. Nobody quotes a figure they doubt. You quote the one written in front of you, in your own file, in your own words, and you say it to a client without hedging, because why would you hedge about something you wrote down.

Then two people compare answers and there is no way to settle it, because neither record carries a mark saying it is the older one. It gets settled by opening the system that owns the fact, which is what should have happened before anybody spoke.

Where does each live fact live?

The fact	The system that owns it	What the file holds instead
A commission split	The brokerage agreement, and whatever accounting pays off it	A line naming the agreement and where the signed copy sits
A rate quote	The pricing engine, on the day and at the hour	A record that a quote was given, with the date and who gave it
A closing date	The transaction management system	A pointer to the transaction, and the last date anybody checked
A subcontractor day rate	The current bid, or the current agreement with that sub	The name of the sub and where the current numbers live
A client headcount	The client, who is the only one who knows	A line saying to ask, with the date it was last asked
Listing status and price	The MLS	The listing identifier, and nothing else
What is scheduled	The calendar	The name of the calendar, never a copied time

Read down the middle column. Every one of those systems already exists in your business, you already pay for most of them, and every one is more current than your note by definition, because it is the place where the change gets made.

What does a file say instead of the number?

The file says where to look. One line naming the system that owns the fact, specific enough that somebody who is not you could open it: the system, the record inside it, and who to ask if it cannot be reached.

"Closing date: see the transaction file in the transaction system" is a better sentence than "closing 15 September", because the first one is still true in November and the second one is a small trap laid for whoever reads it next.

Writing it that way feels like a downgrade the first time. It is a trade. You give up the convenience of reading the number in your own note, and you get a record that never claims to know something it cannot know. Any system built on copies eventually claims exactly that, quietly, on a day nobody chooses.

The half of the rule that people skip

Everything above is about writing. The extension matters more, and almost every system misses it, because a rule about files feels like it stops at the edge of the file.

Does the rule apply when you say a number out loud?

Yes. Reporting a stage, a date, a price or a status carries the same obligation as writing one down. Say when it was last checked and against what, in the same breath you state it. If you have not checked it, say that first, before the number.

The two versions sound almost identical and they do completely different work. "We close on the fifteenth" is a claim about today. "The transaction system said the fifteenth when we looked on Tuesday" is a claim about Tuesday, and it hands the listener what they need in order to decide whether to go and check.

For an assistant reading your records this is a hard requirement rather than a courtesy. An assistant will read a stage out of a file written in March and report it in the present tense, in clean prose, with no hesitation anywhere in the sentence. The rule that prevents it has to be written into the operating file: state the checked date and the system in the same breath, or say plainly that you have not checked.

The habit costs nothing and it changes how people hear you. A number with a date on it invites a check. A number with no date on it invites a decision.

When a number has to be written down anyway

Sometimes there is no way around it. A proposal carries a price. A scope of work carries a rate. A monthly report carries a balance. The rule bends the same way every time, and it bends in three places.

A checked date on the line itself. Never only at the top of the file, where it appears to cover everything and therefore covers nothing.
The system it was checked against, named. "Checked in the billing system" and "the client said so on the phone" are different grades of evidence, and the reader deserves to know which grade they are holding.
Superseded material marked, never deleted. When the number changes, the old line stays with a mark on it and the new line goes underneath. A record that overwrites itself cannot tell you when something changed, or how many times, or who was quoted the old figure.

That third one is what separates a record from a whiteboard. A whiteboard shows the current state. A record shows the current state and how it arrived, which is the only version that survives somebody disputing it a year later.

What this looks like in a real estate business

Five copies we run into constantly. Every one of them starts as a convenience and ends as a wrong answer delivered with total confidence.

A commission split typed into a note. The split lives in the brokerage agreement and in whatever pays off it. A note holding the number will be quoted a year after a plan change, to somebody who has no reason to doubt it.
A rate quoted from memory. Pricing moves during the day. A figure that was right at breakfast is a different conversation by lunch, and the borrower did not hear an estimate.
"Closing 15 September" written into a person file. The transaction system holds the real date and moves it the week the appraisal comes back low. The person file will still say the fifteenth next spring.
A subcontractor day rate in a bid template from eighteen months ago. Templates are where old numbers go to look official. The rate went up, the template did not, and the bid leaves under your name.
A team headcount written into a scope of work. People join and leave and nobody sends you a notice when they do.

That last one has a case behind it. In one engagement, a scope of work stated a client team size as fourteen, in three separate places in the same document. On the same day, another document in the same set of records gave a different number. Both numbers in the records turned out to be about a week stale, so the correct move was neither of them. The correct move was to ask her. Nobody had asked, because the number was written down, and a written number looks like a checked number.

Source of truth is the reason a fact lives elsewhere. Risk never is.

This distinction does real work, and getting it wrong produces a system that keeps things from you for reasons it will not state.

A current medication dose for a dog lives at the veterinary practice. The reason is that the practice is where changing the record changes the fact. Write the dose into a file at home and you have made a copy that goes wrong the next time the vet adjusts it, and the copy will look authoritative on exactly the day it is wrong.

That reasoning stands on its own and has nothing to do with sensitivity, liability or what might be awkward later. The name of the practice goes in the file. The dog's name, breed and birthday go in the file too, because none of those change. Only the live number stays where it lives.

Watch for the other version of this argument, because it wears reasonable clothes. Any rule saying something should not be written down because writing it down might cause a problem later is a rule about what you are allowed to know. Constraints on knowing belong at the moment something is sent, or nowhere. What you know about the people in your business is the thing a records system exists to hold.

The four boxes

The four boxes applied to the live fact rule in a real estate, lending or trades business, as of 2026-07-25. The fourth box carries the argument.

There, and should be

Pointers. Every file names the system that owns each live fact it touches.

One line per fact, specific enough that somebody who is not you could open the right thing.
A checked date beside any number that had to be written down at all.
Settled facts written in full: spellings, birthdays, what somebody said, what you promised, why a deal went the way it went.

Missing, and should be there

A weekly pass that reads the whole set of records looking for numbers carrying an old checked date.

Copies get made under pressure, at the end of a long day, by people who know the rule. The rule fails silently, so something has to go looking for the failures on a schedule.
The pass surfaces the stale line and names the system to check. It fixes nothing, because fixing means a person opening that system and looking.
Anything with no checked date at all is the first pile. A number nobody dated is a number nobody checked.

There, and should not be

Every copied live number sitting in a note, a template or a proposal with no date beside it.

Templates first, because a bid template or a listing presentation carries old numbers into new deals under your name and nobody reads a template closely.
Second, any place two systems hold the same status. Decide which one owns it, write that down once, and make the other point at it.
Third, the habit of reporting a status out loud without saying when you checked. That one costs nothing to fix and it is the one that reaches clients.

Missing, and correctly missing

A plain text record has no live connection to your billing system, your calendar, your transaction system or the MLS, and it cannot refresh itself.

This absence is correct, and the reason is worth stating slowly. A record that reached out and updated its own numbers would be rewriting history every time it ran. The line saying the closing date was the fifteenth when you looked on Tuesday is the record. Silently changing it to the twenty-second destroys the only evidence that the date ever moved.
A record exists to hold what was true and when it was true. Anything that edits itself is a dashboard wearing a record's clothes, and the two get confused constantly because they look the same on screen.
Name the cost, because it is real and it is daily. Every live number in your business requires a person to go and look, and nothing in the folder will tell you the note is old. The pointer moves the work rather than removing it.
What you get in exchange is a file that never claims to know something it cannot know. A stale copy makes that claim every single time somebody reads it.

What this rule does not do

The short version fits on one line, and it is worth putting somewhere you will see it. If it can change without your file knowing, your file does not get to hold it. Your file gets to say where to look.

Common questions

What is a live fact?: A live fact is anything that can change without your file knowing it changed. A price, a loan rate, a deal stage, a job status, a schedule, an account balance, a commission split, or what is currently listed and at what number. The test is whether something outside your note can change the fact while the note sits there.
Why should a price never be written into your notes?: Because the price changes and the note does not, and the note gives no signal on the day it goes wrong. Two records of one fact produce two answers, and neither one carries a mark saying it is the older one. The note ends up quoted with confidence long after it stopped being true.
What should a file say instead of the number?: Where to look. One line naming the system that owns the fact and the record inside it, specific enough that somebody who is not you could open it. Prices live in the billing system, what is scheduled lives in the calendar, listing status lives in the MLS, and the closing date lives in the transaction system.
Does this rule apply when you say a status out loud?: Yes, and this is the half most systems miss. Reporting a stage, a date, a price or a status carries the same obligation as writing one down. Say when it was last checked and against what, in the same breath you state it. If you have not checked it, say that first, before the number.
What if a number has to appear in a proposal or a bid?: Then it carries the date it was checked and the name of the system it was checked against, on the line itself rather than at the top of the document. When it changes, the old line stays with a mark on it and the new line goes underneath, so the record shows how the number arrived and not only where it landed.
Should records update themselves from the systems that own the numbers?: No, and the absence of that connection is deliberate. A record that refreshed its own numbers would rewrite history on every run, erasing the evidence that a date or a price ever moved. The cost is that a person has to go and look, and nothing in the folder announces that a note is old, which is why a weekly pass over checked dates belongs in any working setup.

Worth passing along

This one serves the loan officer and the general contractor. The loan officer states figures that move during the day, to people who hear them as commitments. The contractor carries figures forward in templates, where a day rate from eighteen months ago goes out under his name to a homeowner who will hold him to it. One rule, two completely different ways of getting caught by it, which is why it travels well across a referral sphere.

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.

Reach us directly

Follow us