Step 1: Set lifecycle routing
Open Configuration, choose Communications, and under Lifecycle Routing and Reminders choose the TPRM Office and Supply Chain user groups. Offboarding approvals and the executed contract task go to these groups, each following the group’s own assignment rule (round robin gives one person the task, assign to all gives everyone one).- With no TPRM Office group, offboarding approval goes to the vendor’s first risk analyst, then the requester.
- Supply Chain approval is required only once its group is named. Left unset, the TPRM Office approves offboarding alone.
- The approvals a request needs are fixed when it is filed. Changing routing later does not change requests already filed.
Start offboarding automatically
Under Automatic Offboarding on the same page, Coverbase can file an offboarding request for you. A daily check files the request; the approvals in step 3 still apply.
Automatic Offboarding under Lifecycle Routing and Reminders.
Complete the contract handoff
The Contract tab lists the engagement’s Contracts and its Execution Handoff.
The Contract tab with an execution handoff waiting for the executed contract.
- Signed through e-signature: nothing to do. The handoff completes when the envelope is executed.
- Signed on paper: under Signed on paper, choose the Contract, drop the executed copy, and click File executed contract. If the contract is not listed, link it from About Engagement on the Overview tab first.
Write a continuity plan
An engagement whose inherent risk is the highest level of its scale is critical, whatever you call that level. When it reaches that level, a draft Third-Party Continuity Plan opens on the Exit tab and its Transaction Owner gets a task. Any other engagement can have a plan too. Fill in the Owner, Backup Suppliers (with readiness notes), the Exit Strategy, the Recovery Time Objective (Hours), Resiliency Notes and Transition Steps, one per line. Save draft keeps your work. Submit plan needs an exit strategy and a recovery time objective. Reopen plan makes a submitted plan editable again. If the engagement is offboarded, each transition step becomes an exit plan step.Step 2: Request offboarding
On the Exit tab, under Request Offboarding, choose a Reason (Consolidation, Contract ending, No longer needed, Performance, Risk, Cost or Other), write the Business Justification, optionally pick a Requested Date, and click Request offboarding. An engagement has at most one open request. One also opens automatically when:- an owner answers Start offboarding on a monitoring plan attestation, or
- someone marks the engagement not in use (a canceled status, or a status labeled Inactive or Not in use), or marks every service it uses not in use, or
- a contract end date or a period without spend triggers it (see Start offboarding automatically).
Step 3: Approve it
The Offboarding Request card shows Waiting for TPRM Office and, if required, Waiting for Supply Chain. A member of each group, or an admin, clicks Approve. The last approval starts the request: Coverbase generates the exit plan and runs the start of the cascade. From the moment the request is filed, the engagement’s tracker shows Exit as the current stage, reading Exit under way. See The engagement record. Cancel offboarding, with a Cancel Reason, closes every open step and task, and the tracker goes back to Active. Anything already stopped stays stopped.Step 4: Work the exit plan

The Exit tab with the exit plan, the offboarding request and what stops automatically.
Submit evidence
Approve or return
- Submit evidence for N steps sends one file, one note or both to every selected step. Each step still has to pass its own gate, so a document step without a file or a sign-off step without a note is listed with what it needs, and the rest go through. A certificate step goes through only once the vendor has signed.
- Approve N steps approves the selected steps that wait on you. Each closes with the evidence it has; a step you cannot approve is skipped and listed with the reason.
Required steps, exceptions and closing the exit
A step is required when its kind is one of your Required step types, and the AI data deletion step is always required. Every other step shows Optional. While any required step is open, the plan says how many are open and Close exit is unavailable.
An exit plan with two required steps open. One required step closed with an exception; optional steps are labeled.
- Record exception closes a required step without its evidence. Write Why this step will not be done and click Record exception. The step shows Exception and Exception by the person, with the reason. With Exceptions to required steps need the TPRM Office on, only a TPRM Office member or an admin can do this.
- Skip takes an optional step off the plan. The step shows Skipped. A required step cannot be skipped.
- Close exit closes the exit once every required step is done or has an exception. Optional steps still open are skipped, and everything under What Stops Automatically takes effect. If a required step is still open, Coverbase names it and refuses.
AI data deletion
When the engagement brings AI in, the plan adds a required data step: Confirm deletion of our data from AI training, fine-tuning, embeddings, retrieval indexes and logs, labeled AI. Coverbase adds it when a service on the engagement is marked as an AI system, the vendor’s AI bill of materials lists a machine-learning model, or a fourth party is recorded as an AI model provider. Its evidence is a second certificate the vendor signs, requested the same way as the destruction certificate below. It asks what entered training, fine-tuning, embeddings, retrieval indexes and logs, whether any model still retains the data, and ends with an attestation that covers the vendor’s AI model providers.Get the vendor’s destruction certificate
The data step closes on a certificate the vendor signs. Click Request certificate on the step. The vendor gets an informational request in the supplier portal with a data destruction certificate to sign; Copy portal link gives you the link to send. When they sign, the step shows Signed by, with their title and the date, and Vendor Attestation shows a digest of the certificate. Submitting the step records that digest. If the signed certificate changes afterwards, approval is refused, so the approver always approves the certificate they saw. If the engagement held no data on record, the data step is instead an owner sign-off that no data is held.What stops automatically
What Stops Automatically lists what the offboarding will change, and keeps a line for anything another live engagement still needs (Kept).Work offboarding from MCP or the API
You can file offboarding, write continuity plans and work the exit plan from an MCP client, and file and plan with an API key. An MCP client reads withquery_engagements_contracts(kind="engagement_lifecycle"). It writes with mutate(entity="offboarding", action=...) (file, approve, cancel, regenerate, remind), mutate(entity="exit_item", action=...), mutate(entity="continuity_plan", action="save") and mutate(entity="contract_handoff", action="update").
With an API key, use GET and POST /v1/engagement-records/{engagement_id}/offboarding and the /v1/engagement-records/{engagement_id}/continuity-plan routes. See Read and file offboarding and Continuity plan.
Before an MCP client sends a write, it shows you the change and waits for you to confirm it. The MCP tool reference lists every field.
The API has no route to approve offboarding or work exit steps. Those approvals are decisions for the people they route to.