UNLEASHX FIELD NOTES · TEMPLATES

AI responsibility brief

The AI responsibility brief is a UnleashX template for workflow sponsors and implementation teams that produces a draft scope ready for joint review. A copyable worksheet for scope, system access, authority and completion evidence.

For Workflow sponsors and implementation teamsA draft scope ready for joint review

How to use this worksheet

Complete one brief per responsibility, not one per channel. Start with an actual customer or internal request and follow it to the business record that should change. Use the fields below to record decisions and unanswered questions. A blank field is a review item, not permission for the employee to improvise.

Make the boundary concrete

Write actions as permitted operations against specific records. ‘Manage accounts’ is too broad; ‘update the agreed contact field after the approved identity check’ is testable. Name exclusions such as pricing exceptions or permission changes. Confirm the proposed scope with the business owner and the owner of each connected system.

Describe the evidence

Specify what establishes completion and where a reviewer can find it. A transcript alone is insufficient for a destination write. Record expected references, source state and any separate confirmation requirement. Also define the evidence for a failed or pending action so those cases remain visible rather than being omitted.

Review before configuration

Walk through a routine case, a request outside authority and a system failure using the completed brief. If reviewers disagree about the next step, revise the brief before implementation. Confirm credentials, data handling and supported operations separately. This planning template is not an executable workflow or a compliance certification.

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.

Responsibility name: [one bounded job]

Eligible input: [trigger, identity and prerequisites]

Excluded requests: [explicit limits]

Permitted reads and writes: [system, operation, fields]

Completion evidence: [record and verified state]

Human owner: [queue, decision, fallback]

Evaluation cases: [routine, ambiguous, failed]

Release decision: [reviewer and open issues]

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.

Pilot evidence scorecard

A case-level worksheet that keeps verified outcomes, exceptions and unknown results distinct.