Scope
This guide covers daily operation for Decision History & Audit Log. Availability depends on your tenant package, role and configured providers.
Purpose
Explain what changed, who acted and what advice was used.
Search actions, automation changes and advice decisions.
Before you start
Correct tenant and project selected
Required source or provider is available
An accountable owner is identified
Test data can be separated from live activity
Procedure
- State the operating objective and the record, audience, campaign or project in scope.
- Search actions, automation changes and advice decisions.
- Inspect the current status and supporting context before changing anything.
- Account for system behaviour: Record supported system and operator events automatically.
- Resolve failures, missing data or approval requirements before continuing.
- Close the loop: Review change frequency, declined advice and incident context.
Verify the result
Review change frequency, declined advice and incident context. Confirm that the intended record, state, run or report is visible to another authorised operator and that its next owner is clear.
Completion checkpoint
The capability is in the intended state, evidence is current, exceptions are owned and the next action can be understood without a separate status message.
Controls and limitations
Keep decision records tamper-resistant and strictly tenant-scoped. Predictive, attribution and recommendation outputs support operator judgement; provider and data limitations remain relevant.