You made this decision before. You thought about it, weighed the factors, decided, and then six months later you’re making the same decision again with no memory of how you reasoned through it last time. Worse, you might be making the same type of mistake again without knowing it.
Most freelancers operate from instinct and memory. When a decision doesn’t go well, they feel bad about it and move on. When it does go well, they feel good and move on. Either way, the reasoning that produced the outcome is lost. There’s no record, no review, no learning loop, just accumulated experience with no structure to extract the patterns.
A decision log fixes this. It’s not a journal. It’s not a reflection exercise. It’s a structured record of business decisions, specifically the reasoning behind them, that you review quarterly to find patterns you cannot see any other way.
The 5-Line Format (Every Entry, No Exceptions)
The format must be simple enough that adding an entry takes under three minutes. If it’s longer, you won’t do it. These are the five lines:
Line 1, Date: The date you made the decision. Not when you first thought about it, when you actually decided.
Line 2, Decision made: One clear sentence. “Accepted the Meridian project at $8,500.” “Declined to add social media management to my service offering.” “Hired Carlos as a subcontractor for overflow design work.” No hedging, no caveats in this line.
Line 3, Why (the actual reasoning): This is the most important line. Write your real reasoning, not the reasoning you’d give a client, but the reasoning in your head. “The rate was below my target but I had a slow month and the anxiety of empty pipeline drove the decision.” “I’ve seen three requests for this in six months and turned them all down. I’m concerned it’ll fragment my focus.” This line is where the value lives.
Line 4, Alternatives considered: What else could you have done? List 2-3 options you didn’t choose and why you didn’t choose them. This forces you to confirm you actually considered alternatives instead of defaulting to the first option.
Line 5, Expected outcome: What do you expect to happen as a result of this decision? Be specific. “I expect to deliver this project in 6 weeks, collect $8,500, and have the client ready for a retainer conversation by month 3.” When you review the log quarterly, you can compare what you expected against what actually happened.
That’s it. Five lines. Create a new entry in Notion, fill in the five lines, done.
What Qualifies as a Loggable Decision
Not every choice goes in the log. The filter: would this decision be hard to reverse, or would I regret not knowing my reasoning for it in six months?
Log these:
- Accepting or declining any client worth $2,000+
- Changing your pricing (any service, any amount)
- Adding or dropping a service from your offering
- Hiring or ending a relationship with a subcontractor
- Any investment over $500 (tools, courses, ads, equipment)
- Changing a key operational process
- Responding to a client conflict or complaint in a non-standard way
Don’t log these:
- Which meeting time to pick
- Minor design or copy choices
- Routine task sequencing
- Any decision you can easily reverse in under an hour
A typical solo makes 2-4 loggable decisions per week. That’s 8-16 entries per month, 100-200 per year. Manageable.
The decision log doesn’t make you a better decision-maker immediately. It makes you a better decision-maker over 12 months, because it gives you the data to identify your specific failure modes. Most people think they know their own patterns. They don’t. The log shows you.
The Quarterly Review: 45 Minutes That Change How You Operate
On the last Friday of each quarter, open your decision log and read every entry from the past three months. For each entry, add a brief outcome note: what actually happened versus what you expected.
Then look for these five patterns:
Pattern 1: Urgency-driven decisions. Flag every entry where “anxiety,” “cash,” “fear,” or “urgency” appears in the reasoning line. How did those decisions turn out compared to decisions made without time pressure? Most solos discover that urgency-driven decisions underperform by a significant margin, which is itself a reason to build a cash buffer.
Pattern 2: Decisions made too slowly. Look at the dates, are there decisions you deliberated on for weeks that you should have made in days? Slow decisions have a cost too: the delayed hire, the postponed rate increase, the client conversation you kept avoiding.
Pattern 3: Recurring decisions. If you’re logging the same type of decision multiple times, that’s a sign it should become a standing policy. “Should I take on clients who contact me without a referral?” is a decision you shouldn’t be making case-by-case, it should be a rule. The log surfaces these.
Pattern 4: Outcome vs. reasoning quality. A good decision made for bad reasons is still a dangerous pattern. If you’re getting lucky on decisions based on faulty logic, it’ll catch up with you. The review separates outcome from reasoning quality.
Pattern 5: Avoided decisions. Look at the log and ask: what decisions did I not make this quarter that I should have? The decisions that don’t appear in the log are often more revealing than the ones that do.
What Solos Discover in Their First Review
First-quarter reviews tend to surface three consistent findings:
Finding 1: More emotion-driven decisions than expected. When you read back your reasoning from 90 days ago, the emotional drivers are obvious in a way they weren’t in the moment. “I was afraid of losing the revenue” is visible in retrospect. In the moment, it felt like strategic reasoning.
Finding 2: Several recurring decisions that should be policies. Typical examples: how you handle scope expansion requests, how you decide whether to discount, whether to work with clients in a specific industry you’ve had bad experiences with. These keep coming back because there’s no standing rule. The log makes the pattern undeniable.
Finding 3: Decisions avoided for too long. The pricing increase deferred for six months. The subcontractor relationship that should have ended in January and didn’t end until March. The service you should have dropped in Q1. The log shows you the cost of avoidance in concrete terms.
Converting Patterns Into Policies
The most practical output of the quarterly review is a list of decisions that should become standing policies, rules you apply automatically rather than re-deciding each time.
Example policies that emerge from typical first reviews:
- “I will not accept a new client at a rate below $X/hr, regardless of how slow the pipeline is.”
- “Any scope expansion request gets a written scope addendum and additional quote. No verbal agreements.”
- “I do not offer discounts in response to first-ask objections. If a client asks for a discount, I explain value once. That’s it.”
- “Any client who goes more than 14 days without responding to a pending decision gets an automatic follow-up with a project pause notice.”
Write these policies in your knowledge base under Personal Frameworks. The decision log feeds the knowledge base.
Standing policies are how you stop making the same decision repeatedly. The decision log is what tells you which decisions deserve to become policies. Without the log, you never have the data to know.
The Compounding Value Over Time
A single quarterly review is useful. Four quarterly reviews (one year) are genuinely transformative.
By year one, you know:
- Which client types consistently produce good outcomes
- Which service types have the worst margin after accounting for revision time
- Which decisions you make well under pressure versus poorly
- Which instincts to trust and which to override with deliberation
By year two, your decision-making system is a documented competitive advantage. You have policies for the common decisions, a clear sense of your blind spots, and a running record of what you expected versus what happened, which is the closest thing to a calibration tool a solo operator has.
Start the log today. One entry. Five lines. The value isn’t in the first entry, it’s in the pattern you’ll see 90 days from now.
Ready to send stronger proposals?
Build, send, and track proposals in one place so follow-up is easier.
Start your free trial →
