Assign every research exception to a responsible owner — what should the operator record?
An exception column full of check later does not support a reliable handoff. Each issue needs a specific failure, an accountable owner and a safe next action. This operational structure helps teams resolve problems without broadening access or treating an unresolved row as automatically acceptable evidence.
Turn vague unresolved notes into bounded work items with evidence references and stop conditions.
Use exception_key, row_reference, problem_type, owner_role, next_action and state, keeping sensitive excerpts out of the general queue. A useful issue reads row-reference A17, invalid timestamp, check original receipt, not something looks wrong; precise wording prevents unbounded reinterpretation of the research task.
If ownership changes, preserve the prior next action and the new owner's acceptance so unresolved work cannot disappear between teams. A reassignment should include accepted_by_role and transferred_at, making it possible to distinguish a completed transfer from an issue merely moved to another queue.Create the issue schema
Use exception_key, row_reference, problem_type, owner_role, next_action and state, keeping sensitive excerpts out of the general queue. A useful issue reads row-reference A17, invalid timestamp, check original receipt, not something looks wrong; precise wording prevents unbounded reinterpretation of the research task.
Define the evidence boundary
Point to the authorized receipt or manifest needed for review and say which details the assigned owner may inspect. The queue can carry a restricted manifest pointer while source passages remain in the authorized artifact, minimizing unnecessary duplication across team task systems.
Check owner capability
Confirm the assigned role can perform the proposed read-only check; an inaccessible source should become an access blocker, not an impossible deadline. If the owner lacks source access, assign a permitted schema-only check or mark access-blocked; do not send another person's login or a copied private payload.
Review closure evidence
Require a concrete result such as validated-identifier or source-still-unavailable rather than accepting a generic reviewed status. Closure evidence can be a validation output reference or corrected table revision, providing a checkable result without restating sensitive source content in the ticket.
Transfer outstanding issues
If ownership changes, preserve the prior next action and the new owner's acceptance so unresolved work cannot disappear between teams. A reassignment should include accepted_by_role and transferred_at, making it possible to distinguish a completed transfer from an issue merely moved to another queue.
Keep the boundaries clear.
- Turn vague unresolved notes into bounded work items with evidence references and stop conditions.
- Operational record: Create the issue schema. Context badges do not certify access.
Start with a read-only check: ask your agent to report actual source coverage before collecting records or exporting an audience.
Primary references
Documentation reviewed 2026-11-15. Product capabilities, client availability and plans can change. Third-party marks identify their products, not an affiliation.