Six phases. One accountable path to production.

The technical build and the control model move together. Each phase has a decision, a client input, and a deliverable that can be reviewed.

A reviewable output at every phase.

The sequence is stable; the calendar is not. Clean integrations can move quickly, while legacy systems, sensitive data, or complex approvals require more discovery and testing.

  1. 01

    Discover

    What work are we changing?

    Client provides

    Process walkthrough, systems, stakeholders, service constraints, and current failure points.

    DecarbDesk delivers

    Workflow map, integration inventory, stakeholder map, and an initial fit decision.

  2. 02

    Assess

    Where should the system stop?

    Client provides

    Policies, risk tolerance, approval expectations, known exceptions, and subject-matter review.

    DecarbDesk delivers

    Risk framing, decision boundaries, oversight model, and evidence gaps.

  3. 03

    Design

    How will the workflow behave?

    Client provides

    Access decisions, role mapping, thresholds, test cases, and sign-off on requirements.

    DecarbDesk delivers

    Integration plan, data contracts, approval logic, audit fields, and exception paths.

  4. 04

    Deploy

    Does it work under real conditions?

    Client provides

    Access to a test environment, feedback during a parallel run, and production-readiness sign-off.

    DecarbDesk delivers

    Configured workflow, reference-case results, monitoring, alerts, and an operating runbook.

  5. 05

    Govern

    Is behaviour staying inside the agreed boundary?

    Client provides

    Reviewer decisions, incident context, and approval for material control changes.

    DecarbDesk delivers

    Evaluation results, regression review, exception reporting, and recommended adjustments.

    Review DSPy evaluation →
  6. 06

    Handover

    Can the client operate and review it?

    Client provides

    Operators, reviewers, and administrators available for training and acceptance.

    DecarbDesk delivers

    Documentation, training, administrative access, support terms, and the installed system.

A seven-day path for a clean integration.

This schedule applies when APIs are documented, data is consistent, and approval rules are already understood. Discovery expands when those conditions are not present.

  1. 01 Day 1 Process mapping and tool connection
  2. 02 Day 2 Automation logic and approval gate design
  3. 03 Day 3 Exception handling and edge case configuration
  4. 04 Day 4 Integration testing and cap configuration
  5. 05 Day 5 Monitoring setup and alert configuration
  6. 06 Day 6 Parallel run, automated alongside manual
  7. 07 Day 7 Go-live with full monitoring active

Production is an acceptance state, not a demo date.

The workflow is ready only when its behaviour, controls, records, and operators have all been tested.

  • The approved workflow runs in its target environment.
  • Access roles, approval gates, and stop conditions have been tested.
  • Reference cases meet the agreed evaluation thresholds.
  • Audit records, monitoring, alerts, and exception paths are active.
  • Operators and reviewers can complete their assigned tasks.
  • The client has the implementation record and administrative handover.