Worksheet

How to trace agent decisions A guide to finding where rules behind agent decisions live.

How to use this worksheet

An agent decision rests on rules. Some sit in systems, some in documents, and some in one person's head. This worksheet traces every rule behind one decision, so you can see which ones an agent can reach. It is the first of four checks in the guide how to handle structured, unstructured, and institutional knowledge for AI agents.

Before you start

Fill it in on this page, or print the PDF and work on paper.

  • One workflow where an agent makes a decision
  • One person who owns that process
  • About 30 minutes

Five steps

  1. Step 10/2Name the decisionOne sentence that says what the agent decides.
  2. Step 20/3List every rule that touches itWhere each rule lives, who owns it, and when it ends.
  3. Step 30/3Find a conflictTwo rules that can disagree, and who picks the winner.
  4. Step 40/3Check the exceptionsWhich ones expire, and which nobody is tracking.
  5. Step 50/2Read the resultCount the rules no agent can reach today.
Step 1 of 5

Name the decision

One sentence that says what the agent decides.

Write the decision in one sentence. Say who asks, what they ask for, and what the agent decides.

Step 2 of 5

List every rule that touches it

Where each rule lives, who owns it, and when it ends.

Ask the process owner what they check before they say yes. Write down every rule, including the ones nobody wrote down.

For each rule, mark where it lives: a system, a document, or someone's judgment. Then name its owner and note any end date.

NumberThe ruleWhere it livesWho owns itEnd date
1
2
3
4
5
6
7
8
Step 3 of 5

Find a conflict

Two rules that can disagree, and who picks the winner.

Pick two rules from your grid that can disagree on the same request. Then ask who decides which one wins, and whether that is written down anywhere.

Step 4 of 5

Check the exceptions

Which ones expire, and which nobody is tracking.

Exceptions are rules too. List each one that applies to this decision. Note which ones expire, and which are still in force with nobody tracking them.

NumberThe exceptionEnds onStill in force?Who tracks it
1
2
3
Step 5 of 5

Read the result

Count the rules no agent can reach today.

Count the rules in your grid that live in no queryable system. Those are the ones an agent cannot reach today.

Rules listed
0
In a system
0
In a document
0
In someone’s judgment
0

Fill in the grid in step 2 and your count appears here.

Worked example

Worked example: a contractor asks for warehouse access

A data engineer placed by an outside contracting firm asks for read access to the customer data warehouse. The access agent has to decide whether the contractor gets it.

Step 1 · The decision

Approve a contractor's read access to the customer data warehouse.

Step 2 · Every rule that touches it

NumberThe ruleWhere it livesWho owns itEnd date
1The engineer is a contractor, based in the EU, leaving in JuneA systemHR systemHRJune
2One group grants read access to customer tables, and the engineer is not in itA systemIAM systemITNone
3Contractors may read customer data only with a named employee sponsorA documentData-handling policy, a PDFNot namedNone
4The security team reviews every new grant of warehouse accessA documentSecurity standard, on the wikiCISONone
5EU-based contractors also need the privacy officer's sign-offSomeone's judgmentOutcome of last year's auditPrivacy officerNone
6The firm's people are pre-approved for warehouse read accessSomeone's judgmentAn email from the CISOCISOMarch

Step 3 · The conflict

Rule A
The CISO's pre-approval for the firm's people
Rule B
EU-based contractors need the privacy officer's sign-off
Who decides which one wins?
Each rule's owner. The CISO can waive the security review, because the CISO owns it. The CISO cannot waive the privacy sign-off, which the privacy officer owns.
Is that written down?
No. It sits with the people involved, so precedence has to be recorded somewhere an agent can read.

Step 4 · The exceptions

NumberThe exceptionEnds onStill in force?Who tracks it
1Pre-approval for the firm's peopleMarchYesNobody. It lives in one email.

Step 5 · The result

Two of the six rules live in a system. The other four live in documents or in someone's judgment, so an agent cannot reach them today.

A careful access administrator would say yes once the engineer has a named sponsor and the privacy officer's sign-off.

What the grid tells you

The grid shows where an agent's view of this decision ends.

Rules in a system are within reach, if the agent can query that system. Rules in documents need someone to turn them into rules an agent can read. Rules in someone's judgment need writing down first.

A conflict with no recorded winner leaves the choice to the model. An exception with no tracked end date can outlive the reason it was granted. Each gap is worth closing before you hand this decision to an agent.

Trail is the company brain for AI, and its context graph is the layer your agents run on. It holds rules, exceptions, dependencies, and the reasoning behind them as a graph any agent can follow, including which rule governs when two apply. When a conflict turns up that nobody has ruled on, Trail asks the owner instead of leaving the choice to the model. See it on your own policy documents.

Read the full guide

PDF

Download the PDF

The worksheet as a three-page PDF, with blank grids to print and fill in with your process owner.

Loading the form…