A playbook describes the goals and steps for a repeatable type of work. Make each step clear about its objective, needed context and the evidence that should come back.
Before you start
You need permission to manage playbooks and access to the associated task type or records.
Scout Agent configuration follows the Train, Test, Deploy and Analyze areas.
Write and review a playbook
Open Scout → Train → Playbooks and select the relevant playbook or creation control.
Define the business goal and the records the procedure applies to. Break the work into steps that a reviewer can follow.
Write the inputs, action and expected result for each step. Include what to do when information is missing or the requested outcome cannot be achieved.
Use the editor’s capability references where useful to name records, communications or connected systems a step may use.
Review the playbook state. Drafts need publishing; task-type-managed playbooks have their live/pause state controlled from the task type.
Test representative situations and review the resulting task activity before relying on the procedure.
Check the result
The intended playbook is in the correct state and the test follows a coherent procedure with verifiable outcomes. Review changes against both ordinary and exception cases.
Use capability references accurately
A capability reference is a suggestion about what a step can use. It does not pin a data source, grant permission or guarantee a connection is healthy. Workspace tool permissions and connection access remain the authority.
Name the business evidence explicitly: the confirmed date and quantity, a shipment status, a supplier response or the approved record change.
Maintain the procedure
When the process changes, update the relevant steps and retest the affected situations. Keep old and new procedures from competing for the same work.
If something does not look right
What you see | What to check |
The playbook is not running | Check Draft, Live or Paused status and whether its state is managed through a task type. |
A referenced system cannot be used | Review the connection and tool permission; the capability reference itself does not authorize the action. |
Should every exception become a step?
Should every exception become a step?
Keep common recovery paths in the procedure. Use escalation rules or guidance for decisions that should return to people.
Continue your work
Open the relevant area in Cartograph to continue with your workspace data.