What Does an Evidence Log for Worthiness Work Actually Look Like?

Q: I’ve heard about keeping an evidence log for worthiness work. What exactly goes in it and how do I use it effectively?

The evidence log is a written record of claiming experiments and their actual outcomes. It’s the primary mechanism by which behavioral evidence accumulates into an update of the conditional belonging template.

The Purpose of the Evidence Log

The conditional belonging template runs on predictions about relational consequences of claiming acts. These predictions are generated automatically and feel like accurate reads of the situation — “they’re going to think I’m too expensive,” “this will change how my community sees me.”

The evidence log creates a direct record of what actually happened, in specific claiming situations, when the prediction ran. Over time, it becomes a body of contradicting evidence the template can accumulate against its own predictions.

Without a written log, the template’s predictions are easy to maintain even in the face of contradicting experience. The practitioner names the rate, the client enrolls without issue, and the template dismisses the outcome as “that client was unusually easy” or “this one doesn’t count.” Written, specific, dated entries are harder to dismiss.

The Format

An evidence log entry has three parts:

1. The anticipated relational outcome (before the claiming act)
What specific relational consequence did you imagine would follow? Not the business outcome (“they won’t enroll”) — the relational one. “They’ll think I’ve become money-focused.” “My professional community will see me differently.” “This client will pull back from our relationship.”

2. The actual relational outcome (after the claiming act)
What actually happened, specifically, in the relationship? Not a general sense of how it went — the specific words or behaviors that showed the relational response. “Client said ‘that sounds fair’ and asked how to pay.” “Prospect said they needed to think about it and thanked me warmly for my time.” “Long-term client said the increase made sense and renewed.”

3. The gap between prediction and outcome
This can be brief. “Predicted: relationship would change. Actual: enrolled immediately, warm tone throughout, no mention of the rate after the conversation.”

An Example Entry

Date: [date]
Claiming act: Named new rate of $165 to a new prospect on the introductory call.
Anticipated relational outcome: She’ll think the rate is high relative to what she expected, pull back from the conversation, and decide I’m too commercially oriented. I’ll feel like I’ve lost the connection we had in the first half of the call.
Actual relational outcome: She said “okay, that makes sense” and asked about my availability. We scheduled the start date at the end of the call. The tone of the conversation remained warm throughout. She sent a follow-up email thanking me for my time.
Gap: Anticipated social distance and judgment. Actual: warm enrollment, no comment on the rate.

How to Use It

Review the log when the template’s alarm is running at high intensity — before a difficult enrollment conversation, during a reassertion period, when considering whether to discount a prospect who hasn’t asked.

The log’s function is not to provide inspiration. It’s to provide specific, written evidence that the template’s predictions have not reliably materialized. The entries are data. Reading three or four entries from past experiments before a new claiming context gives the nervous system something concrete to work with.

The log also shows the trajectory over time. An early entry’s anticipated catastrophe compared to a later entry’s matter-of-fact outcome reflects the template’s gradual update.

The Minimum Viable Version

If the full format feels like too much, the minimum viable version is two sentences per claiming event:

“What I thought would happen: [relational consequence]. What actually happened: [specific outcome].”

Even this minimal version, done consistently over months, builds the body of contradicting evidence that the template requires to update.

The Abundance GPS Skool community provides accountability for maintaining the evidence log as a consistent practice rather than an occasional one. Come take a look.