Mission oversight
A shared view of missions and the decisions they need
A team runs several agent workflows for a client. One mission is waiting for approval, another has sent a request whose outcome is still unknown, and a third is ready to hand over to the business team. To organise the next steps, knowing which tools are in use is not enough: the team needs to find the work in progress and the person who can help move each situation forward.
A useful shared view brings together mission state, applicable authorisations and available records. This guide sets out the information needed to decide who should act and on what basis, within an explicitly defined scope.
In brief
The question and the useful result.
- Question
- Which missions need an intervention, from whom and based on which records?
- Useful result
- A six-field mission record and a framework for directing interventions without confusing visibility, authorisation and outcome.
Mission oversight
Start with missions that need a decision
The unit of work is the mission: an assignment given to an agent, with an objective and an expected outcome. The same workflow may support several missions, each at a different stage.
The team needs to distinguish work in preparation, pending approval, an attempted action and a confirmed outcome. One step within a mission may have completed while another remains uncertain. A single ‘complete’ status would hide the work still outstanding.
The view helps direct an intervention: provide information, review an action, check an outcome or hand over the record. It does not, by itself, authorise the next action.
Mission oversight
What a mission record should bring together
| Information | What it should help the team understand |
|---|---|
| Mission and scope | The intended outcome, the workflow involved and the steps actually covered. |
| Person or team coordinating the work | Who to contact about the next step and who can take over if needed. |
| Mission state | What is prepared, waiting, attempted or complete, and what remains unknown. |
| Authorisation and pending decision | The permitted action, its conditions, any approval required and who has authority to decide. |
| Available records | References supporting the displayed state, their sources and the date of the latest observation. |
| Next question to resolve | The information, check or decision needed before the following step. |
The person coordinating the mission and the person authorising an action may be different. Identifying both prevents every question being sent to the same contact. This allocation of operational roles does not automatically assign legal liability.
Mission oversight
Example: three missions needing different interventions
These fictional situations illustrate the framework. They do not describe an available product screen or qualified DUBSAR integrations.
| Mission | What the team knows | Intervention to arrange |
|---|---|---|
| Prepare a commercial proposal | The draft is ready. Sending it requires a human decision. No sending attempt has been established. | Present the content and intended recipients to the person authorised to approve them. |
| Reschedule an appointment | The action was authorised. An attempt and a request acknowledgement have been recorded; the new time has not been confirmed. | Assign an outcome check to the team that can consult the relevant calendar. |
| Complete a customer follow-up task | A record from the business system confirms the expected update. Subsequent manual changes are outside the observed scope. | Hand the result and this coverage limit over to the client team. |
The acknowledgement in the second case establishes that the request was received. It does not establish that the appointment changed. The shared view therefore keeps that uncertainty visible, rather than turning missing confirmation into success or definite failure.
Mission oversight
Make coverage clear to the team running the workflows
A declared mission may appear in an inventory without its actions being technically observed. A connection may provide events without enforcing an authorisation. The view should state what each scope covers and identify information that is old, unavailable or contradictory.
This view complements business tools and their own records. It should point to what is needed to examine a mission, without indiscriminately copying conversations or content. An individual's identity helps direct a decision; the purpose of the view is not employee surveillance or productivity measurement.
Mission oversight
DUBSAR’s intended role
DUBSAR is developing a foundation to connect durable mission state with authorisations, human decisions and execution evidence. A shared view of these elements is intended to help the team running the workflows find pending decisions and outcomes that still need to be established. Business systems remain necessary to perform operations and examine the results they hold.
Mission oversight
Frequently asked questions
Is every visible mission necessarily controlled?
No. The team needs to know where the information came from, which actions are integrated and where authorisation is actually enforced. A row in a shared view does not establish any of those facts on its own.
How should the team use the view during day-to-day operations?
At each review, identify decisions with no assigned reviewer, outcomes still unknown and information that is too old to support a decision. Assign each check and agree when its result will be reviewed.
Should the view include an overall control score?
Partial coverage and an unknown outcome call for different decisions. Showing them separately gives the team more useful information than a score from which those distinctions cannot be recovered.
Mission oversight
Current project status
DUBSAR is in development. Selected workflows have been tested; full B2B integration and validation are still underway. Pilots are not currently open.
Mission oversight