UNLEASHX FIELD NOTES · TEMPLATES

Pilot evidence scorecard

The Pilot evidence scorecard is a UnleashX template for pilot reviewers and business owners that produces a reusable evidence review record. A case-level worksheet that keeps verified outcomes, exceptions and unknown results distinct.

For Pilot reviewers and business ownersA reusable evidence review record

Fix the evaluation rules first

Write the intended outcome, unit of evaluation, eligible cohort and observation window before running the pilot. Define exclusions up front. Agree which failures block release and who can accept residual issues. Do not change the success definition after seeing the results without preserving the original evaluation.

Complete one record per case

Use the fields below for routine, failed and exceptional cases. Link the destination evidence and capture the observed state as completed, pending or handed off. Add the reason when the result differs from expectation. Avoid copying sensitive customer data into the worksheet when a controlled record reference is sufficient.

Review disagreement

Have an accountable reviewer inspect uncertain cases. Preserve disagreement between the conversation and destination state instead of averaging it away. A well-routed exception can pass the boundary check while remaining unresolved as a business outcome. Record those dimensions separately so the release decision has a clear basis.

Summarize without hiding failures

Aggregate comparable cases only after the case-level review. Report denominators, exclusions and unknowns beside the result. Separate operational completion from downstream business impact. Retest changes against the failed examples and keep the configuration version with the scorecard so evidence is not detached from what was tested.

Apply it to a real case

Consider a claims-intake employee. Write the responsibility as preparing a referenced packet, not approving a claim. Record document receipt separately from validation. A case with missing evidence can still be handled correctly while remaining incomplete as a business outcome.

Review question: Which record proves the next step is allowed, and who owns the case if that evidence is unavailable?

Test before release: Run the normal case, a duplicate request and a missing-source case. Compare the actual destination record with the expected state and retain the reviewer’s decision.

TAKE THIS INTO YOUR NEXT REVIEW

Copy and complete the worksheet.

Use the prompts below with the accountable owners. Record unresolved questions explicitly and verify the proposed scope against your systems.

Case reference and configuration version: [ ]

Expected outcome and authority boundary: [ ]

Observed state: [completed / pending / handed off]

Destination evidence reference: [ ]

Action correctness: [pass / fail / unresolved]

Handoff owner and remaining decision: [ ]

Reviewer notes and failure category: [ ]

Release decision and retest reference: [ ]

Planning guidance only. Confirm supported capabilities and review data handling, permissions and applicable requirements for the actual deployment.

CONTINUE THE WORK

Connect the brief to a real responsibility.

AI responsibility brief

A copyable worksheet for scope, system access, authority and completion evidence.