Scenarios in a Decision Case
In DigitalCore, every meaningful decision lives in a decision case — the single container for AI agent inputs, risks, issues, decisions, follow-ups, and scenarios.
A scenario is the structured option set inside a case. It lays out two to four courses of action with assumptions, projected impact, and a recommended choice. A case can carry several scenarios over its life — an initial set when the case opens, plus refined sets after stakeholder feedback.
Open or find the case
Scenarios are not created on their own. Start from the case:
- A case opened automatically by the agents from a critical signal — already populated with AI agent inputs and linked risks.
- A case promoted from a risk.
- A case you opened manually for a pricing, staffing, scope, or renewal decision.
See Decision Cases for the full case structure.
Generate a scenario
Inside the case, click Generate Scenario. DigitalCore will:
- Read the case context: engagement, linked signals, risks, priorities.
- Pull the relevant data from your portfolio.
- Propose options informed by similar past decisions in your AI Use Cases.
- Stamp each option with assumptions and projected impact.
- Write a short rationale and recommend one option.
Refine
You can ask the assistant to:
- Change assumptions (rates, volume, timing, headcount).
- Drop or add an option.
- Regenerate with a different constraint, for example “keep margin above 30%”.
- Try an angle the agent missed.
Each refinement creates a new version of the scenario on the case.
Compare options
The comparison view stacks options side by side:
- Margin impact
- Capacity impact
- Risk shift
- KPI projection
- Implementation effort
Use the comparison view in stakeholder reviews and renewal conversations.
Approve and apply
| Action | Effect |
|---|---|
| Approve | Marks the chosen option. Status becomes Approved. No data changes yet. |
| Apply | Updates rates, plans, or scope on the engagement. Creates follow-ups on the parent case. Status becomes Applied. |
| Decline | Records the decision and the reason. Status becomes Declined. No data changes. |
Approve and Apply are kept separate on purpose. Approval is a governance moment. Apply is a data moment. Splitting them lets you sign off in advance, then apply on a future date.
Statuses
- Proposed. Generated and under review.
- Approved. Selected as the chosen path.
- Declined. Considered and not chosen.
- Applied. Pushed into the live plan; follow-ups created on the case.