--- title: "A reliable agent needs a clear operating brief" description: "An agent needs clear sources, bounded authority and a visible finish. A practical operating brief turns those business decisions into inspectable work." slug: "a-reliable-agent-needs-a-clear-operating-brief" url: "https://withlodge.com/writing/a-reliable-agent-needs-a-clear-operating-brief" published: true published_at: "2026-06-09T12:00:00.000Z" updated_at: "2026-11-02T15:16:33.035Z" image_url: null image_alt: null image_width: null image_height: null word_count: 814 --- An agent's operating brief should answer the questions a responsible colleague would ask before beginning work: what counts as a good result, which sources govern the task, what authority is available and when must the work stop? Clear answers make the work easier to evaluate. They also expose decisions that a fluent instruction can otherwise conceal. Asking an agent to handle supplier documents leaves substantial room for disagreement about what handling means. Imagine a hypothetical procurement team that wants an agent to check whether a supplier submission contains the required documents. Its brief needs to describe a bounded checking task, with human authority over policy and any resulting supplier decision. ## Start with the decision the work supports In this process, the agent might compare a submitted document pack against an approved checklist and prepare a report for a procurement specialist. The report would identify present items, missing items and questions that require review. That purpose sets a useful limit. Finding a document with the expected name does not establish that its contents are acceptable. Reading a submitted assertion does not verify it. Preparing a completeness report does not authorize the agent to accept the supplier or send a commitment. The brief should define those boundaries in ordinary business language. It should say what the agent may read, what it may produce and where the result belongs. Any permission to create or change records needs its own explicit scope. Access to a system alone provides no authority to act throughout it. A named person owns the brief and the policy decisions behind it. If the team changes the required documents, that person or another authorized policy owner must approve the change. The agent's discovery of a convenient alternative is a reason to raise a question, not amend the policy. ## Identify the sources that carry authority For the supplier check, the approved checklist needs a recognizable owner and a current version. The agent also needs to know which submission it is examining and which supporting records it may consult. These sources play different roles. The checklist defines the requirement. The supplier pack provides material to check against it. A sentence inside the pack asking the reader to disregard a missing item has no authority to change the requirement, even if it appears on official-looking stationery. Conflicts need an explicit response. If the checklist and a separate internal guide disagree, the agent should identify the disagreement and send it to the designated policy owner. Choosing whichever source makes the task easiest would conceal a business decision. The same discipline applies to access. If a needed document is restricted, the agent should report that it cannot complete the check with its current permissions. It should not search for a copied version elsewhere or turn a summary into a route around the restriction. A person with the relevant authority decides whether access should change. ## Describe a finished result people can inspect The team's report should let a specialist understand what was examined and what remains uncertain. Each finding can point to the relevant submitted document and the checklist requirement it addresses. The report should distinguish missing material from material the agent could not inspect. This distinction matters when work is handed back to a supplier. Asking for a missing document and reporting a failed inspection are different messages. The specialist needs enough information to choose the appropriate response without repeating the entire check. Completion should be equally concrete. The agent's checking task ends when the report is saved in the authorized location with unresolved questions identified. Supplier acceptance remains a separate decision. The brief should avoid language that makes a completed report look like approval of the supplier. A record of the checklist version also makes later review possible. When requirements change, people can distinguish a report made under an earlier policy from a mistake under the current one. Updating a requirement should not silently rewrite the meaning of previous work. ## Make stopping an ordinary outcome In the process, an unreadable file, a conflicting requirement or a request beyond the granted scope should lead to a clear stop. The brief should name who receives the issue and what information accompanies it. A useful stop report explains the attempted task, the obstacle, the work already completed and the decision needed next. It should avoid spreading the supplier's material beyond the people authorized to see it. The agent can explain what additional permission would be needed without granting that permission to itself. The team can test the brief by walking through an ordinary submission, an incomplete pack and a pack containing an instruction to change the rules. For each, the expected outcome should be understandable before the agent runs. Take an existing task instruction and ask its owner to mark the governing source, the completion rule and the stop condition. Any blank is a business decision still waiting to be made.