1 to 2 · Weak
A personal observation or one informal signal. Useful as a lead, not as a confident renewal claim.
Qubit
Free consultant tool
Capture defensible value while the engagement is happening. Keep outcomes, improved decisions, prevented risks, transferred capability, and client confirmation separate from task history.
A value evidence ledger records what changed for the client, how you contributed, and how well the claim is supported. A completed task alone is not value evidence.
Private workspace
Entries stay in this browser. Nothing in the form is sent to Qubit. Export before clearing browser data or changing devices.
Saved locally
Add a changed state above. Your entries will remain in this browser.
| Record | What it proves | Ledger treatment |
|---|---|---|
| Task completed | Work happened | Not qualified until the client-relevant change is named |
| Asset delivered | An output exists | Qualifies when adoption, decision use, or changed capability is evidenced |
| Outcome movement | A relevant state changed | Record baseline, movement, evidence source, and contribution boundary |
| Risk prevented | A credible downside was reduced | Record the risk, intervention, counterfactual uncertainty, and client recognition |
| Client confirmation | The client recognizes value | Strong supporting evidence, especially when paired with an observable change |
A personal observation or one informal signal. Useful as a lead, not as a confident renewal claim.
A dated dashboard, approved decision, artifact adoption, or other traceable source supports the changed state.
Multiple sources point to the same change, with plausible alternative contributors recorded.
The client explicitly confirms the value and a documented source supports it. Confirmation does not automatically prove sole causation.
Use directly delivered for an output or intervention you controlled, materially influenced when your work changed a shared outcome, supported when your role was one input, and observed only when the result is relevant but your contribution is unproven.
These are fictional examples showing evidence structure. They are not Qubit customer results.
Change: Leadership moved from channel opinions to one approved pipeline allocation. Contribution: materially influenced. Evidence: signed budget decision and planning deck.
Change: Weekly fulfillment exceptions fell after ownership and escalation thresholds were adopted. Contribution: supported. Evidence: eight-week exception log plus operations lead confirmation.
Change: The team stopped two low-evidence roadmap bets before engineering commitment. Contribution: directly delivered the decision process. Evidence: decision records and revised roadmap.
Entry: completed 12 stakeholder interviews. This records activity. Add the decision, risk, capability, or changed state those interviews produced.
This ledger adapts benefits-management and contribution-analysis principles into a lightweight operating record for independent consultants. It asks for ongoing evidence, explicit sources, alternative contributors, and confidence instead of treating correlation as proof.
Method limit: the strength labels organize judgment. They are not a statistical validation of impact, and they cannot establish causation by themselves.
Track a changed client state, a better decision, a prevented risk, a transferred capability, a useful system, or value the client explicitly confirmed. Record your contribution and the evidence source separately.
No. Completion is activity or output. It becomes value evidence only when you name what changed for the client and support that change with an appropriate source.
Record the risk or decision that existed, the intervention, the observable evidence, who else contributed, and what remains uncertain. Avoid claiming a counterfactual as fact.
Only with an honest contribution boundary. Use language such as materially influenced or supported unless the evidence can isolate direct causation.
Add evidence when it appears and review it monthly. Waiting until renewal makes sources harder to recover and increases hindsight bias.
No. Ledger entries are stored only in local browser storage on this device. Clearing site data or resetting the ledger removes them.