Operate & Automate · Prompt
Wrap up a client relationship cleanly: export what they're owed and document the hand-off.
Needs an LLM client connected to ScalePad MCP — Claude Desktop, Cursor, Windsurf or similar. Without it the assistant cannot call the recipe's tools.
[CLIENT NAME] is ending their compliance program with [MSP NAME]. Using ControlMap, prepare: 1. A summary of their program: frameworks, compliance %, open risks, open action items 2. A list of what they should receive: policies, procedures, governance documents, evidence, risk register 3. Open items they need to take over, with context for whoever picks them up 4. A hand-off checklist for us: access to remove, data retention, final report Read-only. Don't delete anything. How to work with the ControlMap API (ScalePad MCP): - Find the client with GET /controlmap/v1/clients/health and use its tenant ID (for example "dundmif") in every request. Some clients have no UUID. - Send the header Content-Type: application/json on every POST, PUT and PATCH, including searches. - Use page_size of 50 or less and follow next_cursor. The "fields" parameter is ignored, so responses are large. - Judge controls by "status", not the "compliant" flag. Objective lists include sub-objectives, so take totals from objective_summary. - Use framework-level scores and labels. The overall score_label on client health can be wrong. - Older policy sections may be URL-encoded twice: decode them and use the highest version of each section. - If a call returns 502 or fails to connect, wait a few seconds and retry once. If it still fails, tell me exactly which data is missing.
# Client offboarding checklist
Hook: Wrap up a client relationship cleanly: export what they're owed and document the hand-off.
A client leaves or moves the program in-house.
An export list, a hand-off summary and a checklist. Nothing is deleted.
Tested against the ControlMap API on October 16, 2026. Only asks for what the API supports.
