Operations SOP: Decision-oriented intelligence brief
Compare approved dated sources with the previous reviewed state and propose decisions only when a verified change matters.
Untested general-purpose draft. All procedure steps, quality checks, and acceptance tests are not run.
The planner preset is an editable starting specification, not an execution of this procedure. Its fields are starting values: replace its owner, approver, trigger, and inputs with this SOP's, and reconcile the rest before use.
These are proposed templates, not actual Belkins SOPs or hands-on test reports. No external actions, sends, model calls, or schedules are performed or configured. No action is preapproved.
Jump to section tap to open
Purpose
Turn verified changes into a short decision brief for an operating team. The planner preset's weekly cadence is an observation window, not an obligation to manufacture an update or a schedule configured by this SOP.
Ownership and trigger
Owner: Research analyst. Named person: not assigned.
Approver: Operations lead. Named person: not assigned.
Proposed trigger: A manually requested observation window closes and its source list is approved. No verified change means skip; no recurring job is created.
Approved inputs
Observation window with start/end dates and time zone, plus a unique run identifier.
Approved dated source material, previous reviewed brief, and frozen evidence register.
Decisions the team can make, excluded topics, and minimum source coverage agreed by the operations lead.
Named analyst/reviewer, approved environment, and any proposed time/spending limits; no sources are fetched by this page.
Proposed procedure (not run)
- Not run
Check the supplied source register for availability, missing material, and stale observations. Distinguish publication date from the date of the underlying event; record gaps rather than treating absence as confirmation.
- Not run
Deduplicate reports describing the same event. Prefer supplied original announcements, documented changes, research artifacts, or first-party observations. Several rewrites of one announcement are not independent evidence.
- Not run
Compare each event with the previous reviewed state. Identify what changed, who it affects, and which operating decision could change. Omit repeated findings without a documented new development.
- Not run
Record evidence, counterevidence, confidence rationale, and unresolved facts. Describe the actual coverage boundary; do not claim a complete-market view from a limited or interrupted source list.
- Not run
Propose an action, bounded future test, explicit watch condition, or no action. Give each proposal an owner and acceptance condition without executing it, subscribing recipients, or creating a monitor.
- Not run
Submit the dated draft for operations-lead review. When nothing verified changes a decision, record a skip reason and no distribution draft. A separate approved process owns any future publication or send.
Proposed outputs
Dated draft brief, or an explicit skip reason when no verified finding qualifies.
Deduplicated evidence register, source-health report, and changed-state list.
Proposed decisions with owner, evidence, acceptance condition, and unknowns.
Empty operations-lead disposition field; no delivery or monitoring job is implied.
Quality checks (not run)
- Not run
Every included signal has an observed event date and a supporting approved source.
- Not run
Source failures, stale observations, and uncertainty remain visible.
- Not run
Each included item changes a decision or records a justified watch condition.
- Not run
No product test, price change, regulation, or performance result is invented.
Acceptance tests (not run)
- Not run
Normal. Proposed fixture: One synthetic verified change with a previous-state record and a relevant team decision. Expected result: The event appears once with its source, date, limitation, and proposed implication.
- Not run
Repetition. Proposed fixture: Five syndicated versions of the same original announcement. Expected result: They remain one event, not five independent confirmations.
- Not run
No change. Proposed fixture: Unchanged sources and the previous reviewed brief. Expected result: The result is a skip reason, without a manufactured update or distribution draft.
- Not run
Outage. Proposed fixture: A required source marked unavailable in the supplied register. Expected result: The coverage gap is explicit; it is not interpreted as no market activity.
Stop and recovery
Hold unsupported items. If critical coverage is unavailable, report the gap to the operations lead rather than issue a complete-market verdict.
Preserve the frozen evidence register and identify the missing observation window.
Resume review after approved source material is available; recheck deduplication and prior-state comparisons. No schedule or notification is created.
Evidence record (empty)
Template version: draft-1 / 2026-11-09. Adapted version and run identifier: not recorded.
Run status: Not run. Fixture/source versions and approved environment: not recorded.
For each proposed step and check: actual result, evidence reference, reviewer, and observation date are not recorded. Expected results above are not observations.
Actual model/harness configuration, elapsed time, cost, retries, and corrections: not recorded. No model call is made here.
Human decision: pending. Approver identity, review date, and scope: not recorded. No response is not approval.
External execution: none performed by this template. Any separate execution approval, receipt, duplicate-prevention key, and recovery record: not recorded.
Keep any future evidence in its approved restricted location. Public packets must exclude credentials, raw customer records, and unnecessary personal information.