The Evidence Log System
Replace impressions with proof. The Evidence Log is a two-minute daily record of what you committed to, what actually happened and what it tells you. It is the raw material for every weekly review, every reframe and every 90-day decision.
Where this fits: after you fill in the Personal PAL worksheet, log the evidence here every evening. Once you have a week of entries, follow the 90-Day Transformation Roadmap to plan the quarter.
What the Evidence Log is (and is not)
An Evidence Log is not a journal. It does not ask how you feel about the week. It asks what someone else could have observed: what was scheduled, what was completed, what moved and what got in the way.
Leaders rarely fail for lack of effort. They fail because their read on progress is built from memory, mood and the last crisis. A Tuesday that felt chaotic gets remembered as a lost week. A week of steady pipeline work gets forgotten because nothing dramatic happened. The Evidence Log corrects that distortion so decisions are made on facts.
- Record observable facts, not interpretations
- Tie every entry to a commitment from your Personal PAL
- Capture obstacles the moment they happen, while the cause is still clear
- Review the log weekly to decide what to keep, change or stop
- Use 90 days of entries to choose your next outcome
What counts as evidence
Use one test: could a neutral observer confirm it? If yes, it belongs in the log. If it is a feeling, a judgment or a story about yourself, note the fact underneath it instead.
Evidence
- “Blocked 8:00–9:30 for proposals. Sent 2 of 3.”
- “Held the leadership huddle in 15 minutes. 3 decisions logged.”
- “Pipeline moved from 18 to 21 active opportunities.”
- “Reopened email at 8:40. Lost the first focus block.”
Not evidence
- “Felt productive today.”
- “Team seems more aligned.”
- “I always get distracted.”
- “Bad week. Nothing worked.”
The Evidence Log loop
Commit
Start from the one to three actions you scheduled for today. Each one should trace back to a priority in your Personal PAL.
Record
At the end of the day, log what happened against each commitment in two minutes or less. Facts, numbers and times only.
Read
Once a week, read the entries as a set. Patterns that are invisible day to day become obvious across five entries.
The daily entry format
Use five fields. Keep each one to a single line. A paper planner, a notes app or a spreadsheet all work; consistency matters more than the tool.
| Field | What to write | Example |
|---|---|---|
| Commitment | The scheduled action, copied from today's plan | Call five past clients, 9:00–10:00 |
| Result | Done, partial or missed, with the number | Partial: 3 of 5 calls |
| Evidence | The observable output or measure | 2 conversations, 1 meeting booked for Thursday |
| Friction | What interrupted or slowed the action, stated as a fact | Took an unscheduled staff question at 9:20 |
| Adjustment | One small change for tomorrow, or “none” | Door closed and phone on Do Not Disturb until 10:00 |
How it connects to the rest of the system
The Evidence Log is the connective tissue of Focused Systems. Each practice either feeds it or reads from it.
Personal PAL sets what you log
Your Personal PAL names the priority and installs the actions. The Evidence Log records whether those actions happened and what they produced. Without PAL, the log becomes a diary of busywork. Without the log, PAL becomes a wish list.
The weekly review reads the log
Spend 30 minutes at the end of each week reading your entries. Count completed commitments, note the friction that appeared more than once and choose next week's one to three priorities. The weekly review for leaders and the owner's weekly review walk through the full agenda.
Reframing fixes repeating friction
When the same friction shows up three or more times in a few weeks, it is not bad luck. It is a habit doing a job for you. Take that pattern into the Six-Step Reframing process and design a replacement behavior. Then use the log to confirm whether the new behavior is holding.
Time blocking protects the actions
Many friction entries trace back to unprotected time. If the log shows focus blocks being lost, tighten your calendar with time blocking for leaders.
The 90-day roadmap is built on accumulated evidence
The 90-Day Transformation Roadmap asks you to establish a baseline in week two and choose your next outcome based on evidence rather than momentum. Twelve weeks of log entries give you exactly that: real numbers, real constraints and a clear record of what worked.
A week of evidence, read in five minutes
Priority (from Personal PAL): Book eight qualified discovery meetings by month end.
Mon: Outreach block held. 10 messages sent, 1 meeting booked.
Tue: Outreach block lost to an unscheduled operations issue at 8:15. 0 sent.
Wed: Block held. 12 sent, 2 meetings booked.
Thu: Block shortened to 20 minutes after reopening email. 4 sent.
Fri: Block held. 9 sent, 1 meeting booked.
Weekly read: 4 meetings booked; on pace. Output tracks directly to whether the first block of the day is protected. Two of five blocks were lost to the same pattern: reacting before the block starts.
Decision: Move outreach to 7:30, before email opens. If the pattern repeats next week, run it through Six-Step Reframing.
Notice what the log does not say: “I need more discipline.” It shows exactly which condition produces results and which one breaks them. That is something you can change on Monday.
Start your Evidence Log this week
Pick one priority
Choose a single 30 to 90 day result. Use the worksheet in the Starter Kit to define it and the evidence that will prove it.
Log for five days
At the same time each day, fill in the five fields for each commitment. Stop at two minutes.
Run one review
On Friday, read the five entries, name one pattern and make one adjustment for next week.
Need a structured first seven days? Follow the first-week plan.
Common mistakes to avoid
- Writing paragraphs. If an entry takes more than two minutes, it will not survive a busy week. One line per field.
- Logging only wins. Missed commitments are the most useful entries. They show where the system needs work.
- Judging instead of recording. Replace “lazy morning” with “started first block at 9:40 instead of 8:00.”
- Skipping the weekly read. Daily entries create awareness. The weekly review is where they become decisions.
Prefer a bound format? The Individual Planner and Executive Planner each include a structured weekly review, so your log entries have a place to become decisions. Teams can run a shared version through the Team Operating System.
Evidence Log FAQ
How is this different from journaling?
A journal explores thoughts and feelings. The Evidence Log records observable outcomes against specific commitments. You can do both, but they serve different purposes, and only the log is designed to drive planning decisions.
How long does it take each day?
Two minutes for the daily entry and about 30 minutes for the weekly review. If it takes longer, reduce the number of commitments you are tracking.
What if I miss a day?
Log the next day and note the gap. A missing entry is evidence too; if gaps cluster on certain days, that tells you something about your schedule.
Should I track everything I do?
No. Track only the one to three commitments tied to your current priority. The point is signal, not a full activity record.
Can a leadership team use an Evidence Log?
Yes. Each owner logs against their committed priorities, and the team reads the evidence together in a weekly huddle. See the leadership huddle agenda and the Team Operating System.
Make progress you can prove
Start with the free Starter Kit, or work through your evidence with a coach in a strategy session.