Small businesses make consequential calls constantly: raise a price, drop a channel, hire ahead of demand, match a promo. Almost none of them get written down, which means almost none of them get graded, which means the same judgment errors get repeated with fresh confidence each season.
The record is not bureaucracy. It is four lines that take ninety seconds at the moment of deciding, and it pays out twice: once when writing the expectation forces you to say what success would look like in a number, and again when the check-back date arrives and the business gets to learn something on purpose.
Use the guide from the role you actually hold.
- Owner-operator
- Log the calls that commit money, capacity, or reputation. Skip the trivial ones; the bar is 'would I want to remember why'.
- Partners
- A shared record turns 'I told you so' into 'the record shows we both expected this to work'. Cheaper than the argument.
- Owner with a manager
- Managers log their own calls the same way. Reading each other's records is the fastest trust-builder there is.
- Anyone about to make a big call
- Write the entry before deciding. If you cannot fill in the expected-outcome line, you are not ready to decide.
The ad budget question, three months later.
In April you increased the ad budget by 30%. It is now July. Was it the right call? Without a record, the answer depends on last week's mood. With one, it is arithmetic: the entry says you expected qualified leads up 15% by end of June at roughly flat cost per lead. Leads are up 18% and cost per lead held within 4%. The call was right, the reasoning was right, and the next budget decision starts from evidence instead of vibes.
- What exactly did we decide, and when?
- What did we expect to happen, in a number, by a date?
- What actually happened, measured the same way?
- What does the gap between the two teach the next decision?
Record to keep: The decision, the date, the reasoning, the expected outcome with its check date, what happened, and the lesson.
The six parts of an entry that grades itself.
Each part exists to make the future check-back possible. Skip one and the entry becomes a diary line instead of an instrument.
The call
One sentence, stated as the action taken: 'Raised install pricing 6% effective August 1.' Deciding not to act counts; write 'decided to hold' with the same care.
The reasoning
Why this, why now, in two or three sentences. Include the alternative you rejected; future-you will want to know what it lost to.
The expectation
A number and a date: 'close rate holds above 40% through September.' This line is the whole trick. Vague expectations cannot be graded.
The check-back
A calendar date when you will measure the expectation. Entries without check-backs are wishes.
What happened
Filled in on the check-back date, measured the same way the expectation was written. Met, missed, or mixed, with the number.
The lesson
One sentence the next decision can use: 'price moves under 8% did not dent close rate' travels forward; 'it worked out' does not.
Three useful stopping points.
- 10 minutes
Backfill the big three
Write entries for the three biggest calls of the past year, from memory, including what you expected at the time. Notice how hard the expectation line is to reconstruct. That difficulty is the argument for the record.
- 15 minutes
Set up the log
Copy the template below into whatever your team already uses. One table, one row per decision. No new software.
- 90 seconds per decision
Log at the moment of deciding
The entry gets written when the call is made, not at the end of the week. Memory starts editing immediately.
Running the record, month over month.
- 01
Set the logging bar
Money, capacity, pricing, people, reputation. If the call commits any of them for more than a month, it gets an entry.
- 02
Write the expectation before acting
If you cannot name the number that would count as success, the decision is not ready. This step catches half-formed calls before they ship.
- 03
Put the check-back on the calendar
The record fails silently without this. The calendar, not your discipline, does the remembering.
- 04
Grade honestly on the date
Met, missed, or mixed, with the measured number. A missed expectation graded honestly is worth more than a met one, because it changes what you do next.
- 05
Read the record quarterly
Ten minutes over the last quarter's entries. Patterns appear: maybe your pricing calls run right and your hiring calls run optimistic. That is self-knowledge with receipts.
The decision log
Copy the starter log and replace the examples with your own calls. The expectation column is the one that earns its keep.
| Decision | Date | Why | Expected outcome | Check on | What happened | Lesson |
|---|---|---|---|---|---|---|
| Raised install pricing 6% | Aug 1 | Costs up, calendar full, rivals higher | Close rate holds above 40% through Sep | Oct 1 | Held at 43% | Small moves inside cover are safe |
| Added Friday dispatch coverage | Jul 25 | Two missed windows became one-star reviews | Zero missed Friday windows for a month | Aug 25 | One miss, weather day | Coverage fixed the pattern, not the weather |
| Declined to match rival's $89 promo | Jul 21 | Their promo is a plan funnel, not a price war | Tune-up volume dips under 10%, recovers by Sep | Sep 15 | ||
| Increased ad budget 30% | Apr 12 | Season starting, capacity to absorb wins | Qualified leads up 15% by end of June, flat cost per lead | Jun 30 | Leads up 18%, cost within 4% | Season timing beat the raw budget size |
What useful documentation looks like.
Useful and maintainable
Expectations are numbers with dates
Every entry can be graded by someone who was not in the room, because success was defined before the outcome existed.
Misses stay in the record
The wrong calls are the curriculum. A record with only wins in it is a scrapbook.
Lessons show up in later entries
You can trace a June decision citing a lesson from February. That trace is the record earning compound interest.
Common mistakes
Logging after the outcome is known
Backfilled reasoning is a story, not a record. The entry's value comes from being written while the future was still uncertain.
Expectations without numbers
'We expect this to help' cannot be missed, which means it cannot teach. Name the metric or do not bother.
Grading generously
Calling a miss 'basically met' converts the record from an instrument back into a mood. Mixed is an honest grade; use it.
This guide describes a record-keeping habit, not an evaluation standard. What to decide, and what any outcome means for your business, stays with you and the qualified advisors you bring into the big calls.
- 01
Harvard Business Review: Performing a Project Premortem. Gary Klein's method for surfacing failure modes before a decision ships; pairs naturally with writing the expectation line
Business press. A single-method article aimed at project decisions; adapted here for small-business calls. Supporting location: Full article. Reviewed July 21, 2026.
- 02
U.S. Small Business Administration: Manage your business. Baseline guidance on reviewing business performance over time
Government guidance. General small-business guidance; it does not prescribe a decision-logging method. Supporting location: Business guide, Manage your business section. Reviewed July 21, 2026.
Prepared by Index8 Research.
- Jul 21, 2026First edition published.
Published July 21, 2026. Last reviewed July 21, 2026.