Maintain an evidence-based plan for a complex customer case
Keep documents, decisions and milestones together when a case cannot follow a fixed sequence.
How this works
Keep documents, decisions and milestones together when a case cannot follow a fixed sequence.
Maintain a flexible case plan when the next action depends on evidence and professional judgment. Preserve decisions and prerequisites so a new document can change the plan without erasing why earlier actions were chosen.
Before you start
Defined operating scope
Complex customer cases require evidence and judgment because the next step cannot always follow a fixed sequence.
Required source material
Obtain Case records; Policies; Goal and owners. If connectors are unavailable, use authorized files with the same fields.
Decision and exception rules
New evidence invalidates a planned action. Mark that action superseded and preserve the prior decision record.
Prepare the inputs
- case_id
- Required
Stable customer case reference
Keep scope and permitted participants clear.
- case_evidence
- Required
Documents, events and decisions
Record dates, source and current validity.
- case_goal
- Required
Desired outcome and constraints
Separate customer requests from approved objectives.
- policy_owners
- Required
Applicable rules and decision roles
Define who resolves exceptions.
Implementation, step by step
Establish the working record
- Confirm the selected records, effective versions and responsible owner.
- Check case_id, case_evidence, case_goal, policy_owners before beginning. Record the source version and the selected scope; an unavailable value stays unknown rather than becoming an inferred fact.
Checkpoint: The input record identifies the selected case_id and any missing required fields.
Consolidate relevant evidence
- Consolidate current evidence and identify missing, contradictory or superseded facts without forcing them into a fixed sequence.
- Verify each active action has satisfied or explicitly pending prerequisites.
Checkpoint: A saved intermediate result for: Consolidate relevant evidence.
Draft possible next actions and prerequisites
- Propose possible next actions with their prerequisites, expected evidence and decision owner.
- Check the decision history retains prior choices and explains changes rather than overwriting them.
Checkpoint: A saved intermediate result for: Draft possible next actions and prerequisites.
Let the case owner choose and update milestones
- Let the case owner choose the next milestone, record the reasoning and update dependent actions when new evidence arrives.
- Verify each active action has satisfied or explicitly pending prerequisites.
Checkpoint: A saved intermediate result for: Let the case owner choose and update milestones.
Reconcile the proposed result
- Verify each active action has satisfied or explicitly pending prerequisites.
- Check the decision history retains prior choices and explains changes rather than overwriting them.
Checkpoint: The listed discrepancies have a named reviewer or an explicit unresolved status.
Package the result and unresolved work
- Check authority, completeness and permissions; human judgment governs exceptional decisions.
- Human judgment governs exceptional decisions and customer commitments.
Checkpoint: A current case plan and decision history. Unresolved items remain visible in the review record.
Decisions along the way
New evidence invalidates a planned action.
Mark that action superseded and preserve the prior decision record.
Two next actions require incompatible assumptions.
Present alternatives and ask the owner to resolve the prerequisite.
The case requires a policy exception.
Escalate to the authorized role instead of treating the assistant’s plan as approval.
What you will produce
adaptive-customer-case-plan-result.json
JSONA current case plan and decision history. Label proposed and completed states separately.
Include: case_id · current_evidence · open_questions · action_options · prerequisites · chosen_milestone · decision_history · status · evidence_reference · review_note
adaptive-customer-case-plan-review.md
MarkdownKeep the evidence and unresolved decisions needed to apply this result, including exceptions involving policy_owners.
Include: source_reference · question · owner · next_action
Check the result
- Verify each active action has satisfied or explicitly pending prerequisites.
- Check the decision history retains prior choices and explains changes rather than overwriting them.
- Inspect case_id and case_evidence in both the original and output; confirm that record identity and interpretation survived the transformation.
- Check authority, completeness and permissions; human judgment governs exceptional decisions.
When something goes wrong
New evidence invalidates a planned action.
Mark that action superseded and preserve the prior decision record. Retain the affected evidence and recovery status.
Two next actions require incompatible assumptions.
Present alternatives and ask the owner to resolve the prerequisite. Retain the affected evidence and recovery status.
The case requires a policy exception.
Escalate to the authorized role instead of treating the assistant’s plan as approval. Retain the affected evidence and recovery status.
A worked example
SYNTHETIC EXAMPLE · NOT A REPORTED BUSINESS RESULT
Request
Maintain an evidence-based plan for a complex customer case for the following bounded example; prepare the result for review.
Inputs
Synthetic example: Case C-8 needs proof of delivery before a refund review. A newly uploaded document is for a different order.
Expected result
Synthetic expected result: Keep delivery evidence missing, flag the mismatched document and request the correct proof. Do not advance to refund approval solely because a file arrived.
Run a small pilot
Start small
Trial a representative batch containing the ordinary case and the exception demonstrated above.
Record the baseline
Record current preparation time, review effort and correction types for the same records.
Agree success criteria
Agree acceptable review and error limits; measure owner-approved actions with evidence; missed prerequisites and time to update the case plan.
Stop or revise
The case requires a policy exception. Pause affected records and apply this recovery: Escalate to the authorized role instead of treating the assistant’s plan as approval.
Keep the scope clear
- Human judgment governs exceptional decisions and customer commitments.
- A proposed plan is not permission to access unrelated records or execute every listed action.
Check before using
Check authority, completeness and permissions; human judgment governs exceptional decisions.
Business activities
- Deliver recurring client work
- Resolve customer questions
FROM A RECIPE TO YOUR WORKFLOW
Bring the company context together.
This workflow needs reliable inputs before it needs a better prompt. Moat8 Vault brings working information into a readable archive for the AI tools you use.
For this recipe: Case records · Policies · Goal and owners
Start with one recurring task, agree which sources to use, and review the first result with your team.
Discuss this workflow