Statement of work draft

Draft a statement of work for [MSP NAME]'s compliance service for [CLIENT NAME] covering [FRAMEWORK]. Use their ControlMap scope and the services we deliver ([SERVICES]).

Include: scope, what [MSP NAME] does, what the client does, deliverables and their frequency, assumptions, and what's excluded (for example remediation projects or the audit fee). Plain language. Mark it as a draft for review, not a final contract.

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.