The One File I Open Every Monday to Decide What to Work On

Every Monday I open one file.

It tells me which deal has gone quiet, which fact about the business is out of date, and what I owe someone this week. I read it for a few minutes, pick the two or three things that matter, and close it. Then I start working.

I stopped trying to hold the whole company in my head. Pipeline, partners, prices, promises, the thing I said I would send someone three weeks ago. That information does not fit in a head, and the parts that do fit are usually the parts that already went stale.

This post is about the file, the ritual around it, and the one rule that keeps it honest. The rule is the whole point, so I will say it early: give every fast-changing fact exactly one home, link to it everywhere else instead of re-typing it, and when it changes, run a pass that finds every place that mentions it. You can copy that into Notion, Obsidian, or a folder of Google Docs this week.

Takeaway

A planning file is only useful if you trust it. It is only trustworthy if it is never out of date in two places at once.

Why a Head Is the Wrong Place to Keep This

The information that decides what to work on is the information that changes the fastest.

A deal moves from quiet to warm to signed. A price gets revised twice in a week. A partner changes what they want built. A check-in date slips. None of that is hard to know on the day it happens. The problem is the week after, when three other things happened and the version in your head is now wrong, and you make a decision off the wrong version.

The most expensive failures in a small business are quiet ones. A deal that needed a nudge and got silence. A partner who was waiting on something you forgot you promised. A fact you acted on that stopped being true a month ago. None of those announce themselves. They just sit there, aging, while attention goes elsewhere.

The Anti-Rot Rule: One Fact, One Home

Here is the failure mode that breaks every notes system I have ever seen, including my own earlier ones.

A fact gets written down in more than one place. The price of a service shows up in a planning note, a proposal draft, and a summary of a call. Then the price changes. You update one of the three. Now you have two stale copies sitting in your own system, and you cannot tell which version is right just by looking. The next decision you make off that note is a coin flip.

The fix is simple to state and takes discipline to hold:

• Every fast-changing fact lives in exactly one place. That place is its home.
• Everywhere else that needs the fact, you link to the home instead of re-typing the value.
• When the fact changes, you change it in the home, and nowhere else has a copy to go stale.

When a Fact Changes, Run a Pass

Links solve most of it. The remaining gap is the place you forgot to link, or the fact you described in your own words on some other page months ago.

So when something material changes, I do one more thing: a reconciliation pass. I find every page that mentions the thing that changed, and I check each one. If a deal moves, I look at every note that names that deal and make sure none of them still describes the old state. Most of the time the links already did the work. The pass catches the one paragraph that did not.

This is the step people skip, and it is the step that matters. It is the difference between a system that drifts a little more every week and a system that gets cleaner every time you touch it. You are not relying on memory to know where a fact is restated. You are searching for it on purpose.

Takeaway

The goal is a system that reconciles itself during normal work, so cleanup becomes a rare structural check instead of a constant rot sweep.

A Read-Only Assistant on Top

Once the facts each have one home and the pages link to each other, something useful becomes possible. You can put a read-only assistant on top of the whole thing and ask it questions.

What is the current state of this deal. What did I agree on with this partner. What have I not followed up on in three weeks. The assistant reads the knowledge base and answers from it. It does not invent the state, because the state is written down in one place. It does not contradict itself, because there are not three versions to choose from.

The assistant is only as good as the structure underneath it. That is the part worth getting right. A clean knowledge base with one home per fact gives a question-answering layer something true to stand on. A pile of contradictory notes gives it nothing, and it will happily make something up to fill the gap.

What the Monday File Actually Surfaces

When the base is clean, the Monday read takes a few minutes and surfaces three kinds of things.

• What went quiet. A deal or a partner with no contact in a while, where silence is a signal worth acting on rather than a settled state.
• What changed. A fact that moved last week, so I can confirm it reconciled everywhere and nothing downstream is still describing the old version.
• What I owe. The thing I said I would send, build, or answer for someone, sitting in one place where I cannot pretend I forgot it.

None of that requires me to remember anything. It requires the system to have written it down at the time it was true, in a place I will look. The Monday ritual is just the habit of looking.

What I Would Build First

You do not need a custom tool to start. You need a folder, a habit, and the discipline to not re-type a fact. Here is the smallest version that works.

1. Pick your tool. A Notion workspace, an Obsidian vault, or a folder of Google Docs all work. The rule is the same in any of them.
2. List your fast-changing facts. Deal states, prices, partner agreements, open promises, next checkpoints. These are the things that rot.
3. Give each fact one home. One page or one section per topic. Write the current value there and nowhere else.
4. Link instead of restating. Anywhere else that needs a fact, link to its home page rather than typing the value again.
5. Run a pass when a fact changes. Search for the thing that changed, open every page that mentions it, and fix any page that still describes the old state.
6. Open it every Monday. Read top to bottom, pick two or three things, and reconcile anything that drifted before you close it.

Start small. One topic with one home beats a whole system you will not maintain. Add the read-only assistant later, once the base is clean enough to trust.

The Bigger Pattern

The Monday file is a thin layer of ritual on top of an operating memory that maintains itself. The ritual is cheap. The structure underneath is what makes it work.

Some people call a system like this a second brain. The name matters less than the rule. One fact, one home, link everywhere else, and reconcile on change. Hold that, and the file you open on Monday will still be telling you the truth in six months.

Start with the facts that rot the fastest. Give each of them a single home this week.

Keep Reading

Next: the Monday scan that matters most for revenue is the one that catches a warm lead before it goes cold.