ORBITxi×UNTAPPED AI
DESIGNED / A · REVIEW ONLY · NOT IMPLEMENTED
INTERNAL DELIVERY CONTROL SYSTEM · 19 AUG 2026

Client lifecycle.
Every node. Every exit.

A top-to-bottom operating map from discovery booking through qualification, internal approval, onboarding, build, client sign-off, go-live, value and closure.

33 nodes8 gates141 explicit routes21 human decisions
READ TOP → BOTTOM

The branch is part of the process—not an exception hidden in a note.

ContinueRevise / retryHold / escalateStop / close33 nodes visible
NON-NEGOTIABLE APPROVAL CHAIN
Internal feasibilityScope / price / timelineClient contract + paymentInternal spec + QAClient UAT / go-liveProduction evidence
DC-00

Discovery call booked

Did a valid discovery happen, or must the booking route change?

Owner → approverAE / SalesSales lead
SLA / escalationReminders before call; no-show action same day
Mandatory evidenceCalendar booking · Client/contact identity · Direct or reseller route · Consent/recording notice
Required proof / proposed source of truthA — booking assertion · GHL calendar + Opportunity
BOUNDARYDirect: Untapped sales owner. Reseller: record the certified reseller and end-client identity separately.
ContinueHeld — evidence review required

→ SD-10 Discovery evidence received

Revise / retryRescheduled

↺ Update booking; preserve source opportunity

Hold / escalateNo-show

⏸ Rebook sequence; escalate after repeated miss

Stop / closeCancelled / invalid

⊘ Dated nurture or close with reason

GATE EXITA held discovery with usable evidence—or an explicit non-proceed route.
SD-10

Discovery evidence received

Does an authorized held-meeting or written route have valid evidence, a human-reviewed Discovery Summary and a gate record?

Owner → approverAESales lead
SLA / escalationSame day; missing evidence escalates after 1–2 days
Mandatory evidenceHeld-meeting link or accepted written evidence · Human-reviewed Discovery Summary · Named reviewer · Discovery gate record
Required proof / proposed source of truthB — evidence and human gate read back · GHL Opportunity + governed evidence pointer
ContinueValidated and reviewed

→ SD-20 Sales Deal Brief

Revise / retryEvidence or summary missing

↺ AE obtains authorized evidence and a reviewed summary

Hold / escalateAmbiguous / wrong match

⏸ Quarantine for human reconciliation; no stage advance

Stop / closeCancelled / no-show / non-sales

⊘ Rebook, nurture or close; no discovery-completion claim

SD-20

Sales Deal Brief submitted

Is the brief complete, factual and explicit about assumptions?

Owner → approverAESales lead
SLA / escalation1 business day; incomplete return once; overdue 2 days escalates
Mandatory evidenceLegal/client identity · Products and outcomes · Users, volumes, integrations and data · Budget, timeline and every promise made
Required proof / proposed source of truthB — validated structured record · GHL form + Opportunity
BOUNDARYThe direct/reseller route is mandatory; reseller identity never replaces end-client identity.
ContinueComplete

→ SD-30 Qualification decision

Revise / retryIncomplete

↺ Return to AE with missing-field list

Hold / escalateContradictory promise

⏸ Sales lead + SA review before qualification

Stop / closeUnrecoverable identity / fit

⊘ Disqualify with durable reason

SD-30
HUMAN DECISION

Qualified / nurture / disqualified

Should Untapped invest in technical and commercial preflight?

Owner → approverAESales lead
SLA / escalation1 business day
Mandatory evidenceProblem and authority · Urgency and budget range · Strategic and delivery fit · Data/security risk signal
Required proof / proposed source of truthB — recorded human decision · GHL Opportunity
ContinueQualified

→ PF-10 Technical feasibility

Revise / retryRequalify later

↺ Dated nurture with owner and trigger

Hold / escalateAmbiguous high-value / high-risk

⏸ CA + SA triage

Stop / closeDisqualified

⊘ Closed with reason; no live delivery stage

GATE EXITQualified opportunity routed to preflight, or a dated nurture/disqualification outcome.
PF-10
HUMAN DECISION

Technical feasibility reviewed

Is each promised capability supported, conditional, excluded or impossible?

Owner → approverSolution ArchitectTechnical approver
SLA / escalationSimple 2 days; complex 5 days
Mandatory evidenceCapability map · Integration/API facts · Tenant and identity assumptions · Volumes and non-functional needs
Required proof / proposed source of truthB–C — doc readback / prototype · DCL + Drive feasibility record
ContinueSupported

→ PF-20 Security/data review

Revise / retryConditional / prototype

↺ Research or bounded prototype; update promise

Hold / escalateVendor/API fact missing

⏸ CONDITIONAL; never silently approve

Stop / closeUnsupported

⊘ Exclude/redesign, or disqualify if outcome depends on it

PF-20
HUMAN DECISION

Compliance, data & security reviewed

Can the engagement proceed safely, and under which controls?

Owner → approverSEC / Information delegateInformation Officer delegate
SLA / escalationLow risk 2 days; medium/high 5 days
Mandatory evidenceData categories and subjects · Channel/recording/automation map · Geography and subprocessors · Retention, access and regulated-sector flags
Required proof / proposed source of truthB — recorded risk decision · DCL + approved Drive record
ContinueApproved

→ PF-30 Capacity reservation

Revise / retryConditional controls

↺ Add minimisation, retention, DPA or human-review controls

Hold / escalateHigh risk unresolved

⏸ Counsel / Information Officer escalation

Stop / closeDeclined

⊘ No proposal; disqualify or redesign

PF-30
HUMAN DECISION

Capacity reserved

Can named people deliver the approved shape without hidden overload?

Owner → approverDelivery ManagerDelivery leadership
SLA / escalation2 days; reservation expires at approved validity date
Mandatory evidenceWorkstreams and skills · Weighted load and support demand · Named PM/WLs/QA/backups · Start date, buffer and reservation expiry
Required proof / proposed source of truthB — named reservation · DCL capacity board
ContinueReserved

→ PF-40 Specialist preflight or PF-50 design

Revise / retryAlternative plan

↺ Change sequence, staffing, scope or start date

Hold / escalateNo capacity

⏸ Waitlist or client-approved replan

Stop / closeEconomics / delivery fit fails

⊘ Decline or materially redesign

PF-40
HUMAN DECISION

Specialist / subcontractor preflight

Is the specialist approved, replaceable and safe for this exact task?

Owner → approverPMDM + SEC where needed
SLA / escalation3 days
Mandatory evidenceBounded deliverable and SLA · Rate/commercial boundary · NDA/DPA and data class · Availability, least privilege and backup
Required proof / proposed source of truthB — approved specialist packet · DCL + restricted Drive folder
BOUNDARYNo direct client contact or access unless the packet explicitly allows it.
ContinueApproved specialist

→ PF-50 Solution design

Revise / retryInternal alternative

↺ Reassign to qualified internal owner

Hold / escalateNo backup / unavailable

⏸ Replan; do not commit the timeline

Stop / closeNDA, security or fit fails

⊘ Reject specialist and remove access path

PF-50

Solution designed

Is there a coherent solution whose scope traces to evidence?

Owner → approverSolution ArchitectPM
SLA / escalation3–7 days by complexity
Mandatory evidenceTarget state and workstreams · Architecture and data flows · Dependencies and assumptions · Rollout, rollback and measurable outcomes
Required proof / proposed source of truthB–C — reviewed design / prototype evidence · Versioned Drive design
ContinueDesign ready

→ PF-60 Internal scope/pricing/timeline approval

Revise / retryDesign changes

↺ Return to affected feasibility/security/capacity review

Hold / escalateCritical assumption open

⏸ Conditional design or paid discovery phase

Stop / closeOutcome infeasible

⊘ Exclude, redesign or disqualify

PF-60
HUMAN DECISIONFORMAL APPROVAL

Internal scope, price & timeline approved

May this exact offer be promised to the client?

Owner → approverCommercial ApproverAuthorised commercial approver
SLA / escalation2 days; material change restarts affected concurrence
Mandatory evidenceExact design version · Estimate and unit economics · Capacity and risk concurrences · Acceptance, exclusions, responsibilities and change rule
Required proof / proposed source of truthE-internal — attributable approval · DCL approval + restricted commercial record
BOUNDARYResellers may propose context; they cannot approve feasibility, scope, price or production authority.
FORMAL APPROVAL 1 — internal commercial/design release
ContinueApproved

→ SD-40 Issue exact proposal/SOW

Revise / retryRevise

↺ PF-50 and any affected concurrence

Hold / escalateDecision incomplete

⏸ Proposal remains locked

Stop / closeDeclined

⊘ Nurture, close or redesign

GATE EXITOne exact, internally approved solution, price, timeline and acceptance baseline.
SD-40

Proposal / SOW issued

Is the correct approved version ready for the correct recipient?

Owner → approverAECommercial release approver
SLA / escalationWithin 1 day of internal approval
Mandatory evidencePF-60 exact version · Authorised recipient · Deliverables and acceptance · Responsibilities, exclusions, change control and validity
Required proof / proposed source of truthB — sent version and delivery evidence · GHL + e-sign platform + Drive
BOUNDARYClient-facing brand is Untapped AI unless a written exception authorises ORBITxi visibility.
ContinueClient accepts

→ SD-50/60 Commitment verification

Revise / retryClient requests change

↺ PF-50/PF-60 re-design and reapproval

Hold / escalateAwaiting decision

⏸ Controlled follow-up until validity expires

Stop / closeRejected / expired

⊘ Close, nurture or requalify

SD-50 / SD-60
HUMAN DECISION

Client acceptance & payment verified

Is there a valid commercial commitment that delivery can still honour?

Owner → approverAE + FinanceCA + Delivery Manager
SLA / escalation1 day after evidence arrives
Mandatory evidenceAuthorised signature · Exact signed version · Cleared payment or approved exception · Capacity and planned start revalidated
Required proof / proposed source of truthE — authorised commercial acceptance · Signed document + finance record + GHL
ContinueVerified

→ IM-10 Sales-to-Delivery handoff

Revise / retryVersion / authority mismatch

↺ Correct signature or commercial record

Hold / escalateUnpaid / exception pending

⏸ Finance hold; no onboarding

Hold / escalateCapacity lapsed

⏸ Controlled replan and new start acceptance

Stop / closeWithdrawn / disputed

⊘ Commercial/legal hold or closure

IM-10
HUMAN DECISION

Sales-to-Delivery handoff accepted

Can delivery accept this engagement without guessing?

Owner → approverAEPM / Delivery
SLA / escalation1 day; two failed returns escalate Sales/Delivery leadership
Mandatory evidenceStakeholder and communication history · Promises, risks and tenant · Scope, payment, dates and success metrics · Every open client input has an owner
Required proof / proposed source of truthB — delivery acceptance record · Engagement in GHL + DCL
BOUNDARYReseller sees only client-safe handoff facts; internal margin, subcontractor terms and delivery constraints remain restricted.
ContinueAccepted

→ IM-20 Welcome and onboarding

Revise / retryReturned

↺ Sales corrects named gaps

Hold / escalateConflict / unowned risk

⏸ Decision log and owner assignment

Stop / closeMaterial contradiction

⊘ Reopen commercial approval or terminate commitment per terms

GATE EXITDelivery accepts a complete engagement record with payment/capacity rechecked.
IM-20

Welcome & onboarding launched

Will the correct people receive the correct branded onboarding pack?

Owner → approverPMEngagement owner
SLA / escalationSame day as accepted handoff
Mandatory evidenceCorrect brand/audience · Client contacts and route · Controlled folders/templates · Intake, access and kickoff tasks
Required proof / proposed source of truthB–C — delivery receipt / form access test · GHL + Drive/DCL links
BOUNDARYDirect/reseller visibility and sender identity are resolved before any automated message runs.
ContinueDelivered & tested

→ IM-30 Intake + IM-40 Access + IM-50 Kickoff prep

Revise / retryDelivery failed

↺ Correct recipient/template and retry once

Hold / escalateRoute / identity unclear

⏸ Suppress all messages until resolved

Stop / closeWrong recipient / brand leak

⊘ Stop sequence, contain and correct evidence

IM-30

Client intake completed

Is the operational baseline complete and reconciled?

Owner → approverClient PMUntapped PM
SLA / escalationTarget 3 days; sponsor escalation day 5; replan day 7
Mandatory evidenceBusiness intake · Product/workstream modules · Requested source documents · Conflicts against proposal logged
Required proof / proposed source of truthB — validated intake baseline · Form/DCL + Drive files
ContinueComplete

→ IM-50 Kickoff readiness

Revise / retryPartial

↺ Targeted reminders for missing modules

Hold / escalateClient delay

⏸ Sponsor escalation and schedule/capacity impact notice

Stop / closeMaterial scope conflict

⊘ Controlled change/commercial route before build

IM-40
HUMAN DECISION

Secure access verified

Is each critical access item lawful, least-privileged and tested?

Owner → approverClient system owner + Access coordinatorPM / SEC
SLA / escalationRequested day 0; verified by kickoff or agreed build date
Mandatory evidenceExact tenant/account/environment · Owner and permission level · Invite/OAuth/vault method · Readback, MFA, expiry and revocation owner
Required proof / proposed source of truthB–C — permission readback / safe test · DCL access register
BOUNDARYResellers and clients never send passwords, API keys or recovery codes through forms, email or WhatsApp.
ContinueVerified

→ IM-50 / IM-80 as required

Revise / retryWrong permission / tenant

↺ Reissue named invite and retest

Hold / escalateCritical access late

⏸ Block affected work and replan dates

Hold / escalateStaged exception

⏸ Proceed only with explicitly limited work

Stop / closeSecret sent insecurely

⊘ Incident: quarantine exposure; rotate/revoke

IM-50 / IM-60

Kickoff ready & completed

Are the right people aligned on how delivery and decisions will work?

Owner → approverPMClient sponsor
SLA / escalationReady 1 day before; actions issued 1 day after
Mandatory evidenceAgenda and attendee authority · Scope, decisions and risks · Communication and change rules · UAT, go-live, cadence and baseline metrics
Required proof / proposed source of truthB — attendance, decisions and actions · GHL appointment + Fireflies + DCL
ContinueCompleted

→ IM-70 Confirmed requirements

Revise / retryScope / process correction

↺ Update decision/conflict log

Hold / escalateNo-show / missing approver

⏸ Rebook and escalate to CPM/sponsor

Stop / closeFundamental conflict

⊘ Return to commercial/change route

IM-70
HUMAN DECISION

Confirmed requirements issued

Does the client-readable baseline accurately reflect the agreed requirement?

Owner → approverPMClient sponsor / Client PM
SLA / escalation2–3 days after kickoff; escalate after 3 days without response
Mandatory evidenceKickoff and intake reconciliation · Process maps · Decision/conflict log · Success baseline and open assumptions
Required proof / proposed source of truthE — written acknowledgement · Controlled Drive document
ContinueAcknowledged

→ IM-80 Internal solution specification

Revise / retryCorrections

↺ Reconcile and reissue exact version

Hold / escalateNo response

⏸ Escalate; silence is not approval

Stop / closeNew material requirement

⊘ Change/commercial reapproval route

IM-80
HUMAN DECISION

Solution specification internally approved

Is the specification buildable, testable, safe and traceable?

Owner → approverSA / Workstream LeadPM + QA + SEC as required
SLA / escalation2–5 days
Mandatory evidenceArchitecture and data mappings · Prompts/actions and environments · NFRs, tests and monitoring · Rollback and access model
Required proof / proposed source of truthB — approval on exact version · Drive + DCL
ContinueApproved

→ IM-90 Build plan

Revise / retryRejected

↺ Add missing acceptance, rollback, monitoring or security

Hold / escalateOpen access / decision

⏸ Specification cannot advance

Stop / closeMaterial scope impact

⊘ Client/change approval before build

IM-90

Build plan & SLA assigned

Can the approved spec be executed with every task and dependency owned?

Owner → approverPMDelivery Manager
SLA / escalation1–2 days
Mandatory evidenceWork breakdown and estimates · Owners and dependencies · Critical path, buffer and environments · QA plan, cadence and client-input dates
Required proof / proposed source of truthB — baselined plan · DCL / task system
ContinuePlan approved

→ IM-100 Build

Revise / retryOverload / sequence issue

↺ Replan capacity, scope or dates

Hold / escalateUnowned dependency

⏸ Assign owner or block start

Stop / closeSpecialist unavailable

⊘ Replace or reapprove timeline before start

GATE EXITOwned build plan based on acknowledged requirements and approved specification.
IM-100

Build in progress

Is the build still within the approved specification and plan?

Owner → approverWorkstream LeadPM
SLA / escalationPer baseline; weekly status minimum
Mandatory evidenceSafe environment and verified access · Version control and rollback boundary · Decision/deviation log · Progress, dependency and build evidence
Required proof / proposed source of truthB–D — readback through controlled execution · Build platform/repository + DCL
ContinueBuild complete

→ IM-110 Internal QA / red team

Revise / retryIn-scope defect

↺ Fix within build stage

Hold / escalateClient input / dependency late

⏸ Document blocker, owner, due date and impact

Hold / escalateVariance above threshold

⏸ Reforecast or change review

Stop / closeTechnical premise fails

⊘ Return to design/feasibility

IM-110
HUMAN DECISION

Internal QA / red team complete

Is the candidate safe enough for client UAT?

Owner → approverQA / Release leadIndependent release approver
SLA / escalation2–5 days
Mandatory evidenceTraceable test cases · Failure, permissions and security tests · Idempotency, retry and observability tests · Rollback rehearsal and defect disposition
Required proof / proposed source of truthC–D — synthetic and end-to-end execution · DCL + QA report in Drive
ContinuePass

→ IM-120 Demo/UAT Round 1

Revise / retryP0/P1 or rollback fail

↺ IM-100 Build and retest

Hold / escalateHigh-risk security fail

⏸ SEC review; no UAT promotion

Stop / closeUnacceptable residual risk

⊘ Redesign or terminate affected scope

IM-120
HUMAN DECISION

Demo / UAT Round 1

Which findings are defects, changes, questions or training gaps?

Owner → approverPM + QAClient UAT approver
SLA / escalation3–5 day UAT window
Mandatory evidenceQA-approved exact version · Named testers and representative cases · Expected results and defect rules · Demo/UAT evidence
Required proof / proposed source of truthD–E — controlled client execution · DCL UAT/defects + Drive
ContinueCases executed

→ IM-130 Controlled change round

Revise / retryDefects found

↺ Classify and route through IM-130

Hold / escalateSilent / incomplete UAT

⏸ Two reminders, sponsor escalation, schedule hold

Stop / closeWrong environment/version

⊘ Invalidate evidence; reset UAT on correct candidate

IM-130
HUMAN DECISION

Controlled change round

Fix, approve, defer or reject each item—without silent scope absorption.

Owner → approverPMCA + Client sponsor/UAT approver
SLA / escalationTriage 1 day; estimate 2 days
Mandatory evidenceUAT1 item list · Approved baseline · Impact on cost, time and risk · CR ID and disposition
Required proof / proposed source of truthB/E — attributable decision · DCL change record + signed change evidence
ContinueDefects fixed

→ Regression then IM-140 UAT Round 2

Revise / retryChange approved

↺ Rebaseline → build → QA → IM-140

ContinueDeferred / rejected

→ Record backlog/boundary; IM-140 on baseline

Hold / escalateNo decision

⏸ Defer; do not build

Stop / closeCommercial change refused

⊘ Preserve original scope or controlled closure

IM-140
HUMAN DECISION

Demo / UAT Round 2

Does the release candidate now meet the agreed acceptance baseline?

Owner → approverQA + PMClient UAT approver
SLA / escalation2–4 days
Mandatory evidenceExact revised release candidate · Regression pass · Updated UAT plan · Fix/change-set evidence
Required proof / proposed source of truthD–E — client verification · DCL + Drive
ContinueAccepted criteria

→ IM-150 Go-live readiness

Revise / retryValid defect rejection

↺ Build/QA and contractual triage

Hold / escalateIncomplete / silent

⏸ Escalate; silence is not acceptance

Stop / closeNew change / unclear baseline

⊘ New CR or revisit requirements/specification

GATE EXITA release candidate that meets acceptance criteria or has an approved exception path.
IM-150
HUMAN DECISION

Go-live readiness approved

Is the exact production release ready to be authorised?

Owner → approverPM / Release leadSA + QA + SEC + Client sponsor as applicable
SLA / escalation1–2 days before launch
Mandatory evidenceUAT2 and known issues · Deployment/rollback and backups · Monitoring, support and incident runbook · Production tenant/asset ownership and payment milestone
Required proof / proposed source of truthD — rehearsed readiness evidence · DCL approval + Drive runbook
ContinueGo

→ IM-160 UAT / Go-live acceptance

Revise / retryNo-go

↺ Build, QA, UAT or readiness remediation

Hold / escalateConditional go

⏸ Named, signed exception within tolerance

Stop / closeWrong tenant / ownership / rollback

⊘ Block launch until corrected

IM-160
HUMAN DECISIONFORMAL APPROVAL

UAT / Go-live acceptance

Does the authorised client accept this exact release for production?

Owner → approverClient UAT approver + SponsorUntapped authorised release approver
SLA / escalationTarget 1 day; silence never equals acceptance
Mandatory evidenceExact version and environment · UAT/readiness evidence · Known issues and conditions · Authorised signers, support and rollback terms
Required proof / proposed source of truthE — authorised client acceptance · E-sign record + Drive + DCL
BOUNDARYA reseller cannot sign for the end client or authorise production unless the contract explicitly grants that authority.
FORMAL APPROVAL 2 — client UAT and production release
ContinueAccepted

→ IM-170 Controlled go-live

ContinueConditionally accepted

→ Go-live only if conditions fit approved tolerance

Revise / retryRejected

↺ Change/UAT remediation route

Hold / escalateDeferred / authority mismatch

⏸ Resolve signer, scope or launch window

Stop / closeNo valid acceptance

⊘ Production remains Off

IM-170
HUMAN DECISION

Go-live & hypercare started

Continue, contain, forward-fix or roll back based on production evidence?

Owner → approverRelease leadPM / Incident commander
SLA / escalationInside controlled launch window
Mandatory evidenceSigned acceptance · Approved window and runbook · Production readback and smoke tests · Monitoring, correlation log and rollback owner
Required proof / proposed source of truthF — monitored production outcome · Production readback + deploy/incident record
BOUNDARYNeither reseller nor automated workflow may activate production autonomously.
ContinueStable

→ IM-180 Four-week hypercare

Revise / retryMinor partial failure

↺ Contain and approved forward-fix

Hold / escalateMonitoring unknown

⏸ Remain in launch observation; no success claim

Stop / closeP0 / readiness breach

⊘ Rollback or kill switch; incident command

Stop / closeWrong tenant/sender/brand

⊘ Immediate stop, contain and investigate

GATE EXITProduction is verified, monitored and inside hypercare—or safely rolled back.
IM-180
HUMAN DECISION

Four-week hypercare complete

Is production stable enough to leave hypercare?

Owner → approverCSM + PMClient sponsor
SLA / escalationWeekly for four weeks
Mandatory evidenceWeekly Week 1–4 records · Incidents, defects and workarounds · Training/adoption signal · Support handoff and residual risks
Required proof / proposed source of truthF — monitored service outcome · DCL + GHL meetings
ContinueExit approved

→ CS-20 Month 2 check-ins

Revise / retryExtend hypercare

↺ Continue weekly with defined exit criteria

Hold / escalateClient unavailable

⏸ Rebook and sponsor escalation

Stop / closeRecurring critical issue

⊘ Incident/build track; no stable-state claim

CS-20

Month 2 check-ins

Is adoption and service health progressing after hypercare?

Owner → approverCSMClient sponsor
SLA / escalationTwo reviews roughly two weeks apart
Mandatory evidenceTwo check-in records · Metric snapshots · Residual backlog · Actions and owners
Required proof / proposed source of truthF — current service evidence · GHL + DCL
ContinueHealthy

→ CS-30 Monthly success

Revise / retryRed health

↺ Recovery plan with owners and dates

Hold / escalateRepeated missed contact

⏸ Sponsor escalation

ContinueExpansion signal

→ New Deal Brief / preflight; do not absorb scope

CS-30

Monthly success / maintenance

What must continue, recover, change or expand this month?

Owner → approverCSMClient sponsor
SLA / escalationMonthly; red health recovery plan within 2 days
Mandatory evidenceHealth score and success metrics · Incidents/utilisation · Compliance/access expiries · Optimisation and change backlog
Required proof / proposed source of truthF — recurring production/value evidence · GHL Success pipeline + DCL metrics
ContinueHealthy

→ Continue monthly and prepare 90-day review

Revise / retryRed health

↺ Recovery plan / incident / training

Hold / escalateMetric unavailable

⏸ Fix data owner/source before value claim

ContinueChange / expansion

→ CR or new commercial preflight

Stop / closeCancellation request

⊘ CS-50 Controlled closure

CS-40
HUMAN DECISION

90-day outcome / value review

Are outcomes achieved, trending, blocked or unmeasurable?

Owner → approverCSMClient sponsor
SLA / escalationPrepare day 75; review by day 95
Mandatory evidenceBaseline, target and source · Cost/adoption/quality data · Stakeholder feedback · Variance and recommendation
Required proof / proposed source of truthF — measured outcome · DCL Success Metric + Drive review
ContinueAchieved

→ Renew, expand or steady-state

ContinueTrending

→ Continue plan with next measurement date

Revise / retryBlocked

↺ Recovery owner and improvement plan

Hold / escalateUnmeasurable

⏸ Redesign metric/source; no invented value

Stop / closeNegative outcome

⊘ Commercial/service recovery or closure

CS-50
HUMAN DECISION

Renew, expand, steady-state or close

What is the authorised next lifecycle state?

Owner → approverCSM + Commercial ApproverClient sponsor + SEC/PM for closure
SLA / escalationBegin 60–90 days before term end
Mandatory evidenceValue and account health · Contract dates and support state · Access/data inventory · Open risks, liabilities and retention
Required proof / proposed source of truthE/F — commercial decision and closure evidence · GHL + signed docs + DCL
BOUNDARYThe contracting party determines the commercial route; end-client data and tenant boundaries remain isolated through renewal or closure.
ContinueRenew

→ Signed renewal; continue success lifecycle

ContinueExpand

→ New Deal Brief / feasibility / approved change SOW

ContinueSteady-state

→ Support SLA + monthly success

Stop / closeClose

⊘ Offboard, revoke access, export and schedule retention

Hold / escalateDispute / refund

⏸ Commercial/legal hold; no destructive deletion

GATE EXITA recorded commercial/service outcome with access, data and obligations controlled.
THE SYSTEM NEVER ENDS AT “DONE”

Every engagement ends in one controlled state.

RENEW

Signed commercial continuation and current success baseline.

EXPAND

New Deal Brief, feasibility and scope approval—never absorbed work.

STEADY-STATE

Named support owner, SLA, access review and monthly success cadence.

CLOSE

Revocation, export, retention, obligations and closure evidence.