An account operations statement of work translates the agency's commercial promise into a delivery specification. It should identify accounts, platforms, approved inputs, operating tasks, acceptance evidence, dependencies, and the process for changes that affect effort or timing.
What is the minimum useful scope description?
Name the campaign, authorized accounts, platforms, content source, included tasks, and responsible parties. Define what a complete publishing instruction contains. Avoid relying on phrases such as full account management without explaining the actual work. The statement should let a delivery person determine whether a request is included before accepting it into the operating queue.
How should deliverables be accepted?
Define completion using evidence appropriate to the task: a published URL, an account setup record, or a documented exception. Distinguish submission, acceptance, execution, and review. An uploaded file is an input, not proof of completed distribution. Acceptance criteria should also explain how the agency raises an error and how the provider records the correction.
Which exclusions deserve explicit wording?
List work that clients could reasonably assume is included, such as filming, editing, rights clearance, community replies, paid advertising, or custom analytics. State who supplies those functions when they are dependencies. An exclusion is useful when it prevents an ambiguous handoff; it should not be buried where sales or delivery staff will overlook it.
How should changes be approved?
Require an authorized person to approve changes that affect scope, cost, timing, or account access. Keep the original request, impact assessment, and accepted instruction together. Operators can flag the impact, but should not negotiate a new client promise through informal messages. The statement of work should name the route that converts a request into accepted work.
What does the research help you decide?
Adobe 2025 marketer survey reports: 89% reported at least three approval stages; 58% spent over 40% of their time managing reviews and approvals. The approval burden in this marketer survey makes input readiness a useful scope boundary. It does not prescribe how many approval stages a client should have or how quickly a provider can deliver.
What would this look like in a real workflow?
The following is a hypothetical operating example, not a Conbersa customer result. A client buys account operations for approved videos, then asks the provider to rewrite scripts and source additional footage. The statement of work identifies production as a separate responsibility, so the agency can quote that work or obtain it elsewhere. Meanwhile, existing approved assets continue through delivery. Clear scope lets the team resolve the new request without treating the entire campaign as either unlimited or blocked.
Use a record that someone outside the original conversation can act on:
| Record field | What to write down |
|---|---|
| Deliverable | Specific operating task, destination, and evidence of completion. |
| Dependency | Asset, permission, or decision required before that task can begin. |
| Change control | Authorized requester, impact on scope, and the accepted revised instruction. |
Review the document against the sales proposal and provider agreement. The same task should not be promised in one document, excluded in another, and unassigned in the delivery brief. Resolve those mismatches before kickoff, then give operators a concise working version of the accepted scope.
How does this connect to the wider workflow?
Continue with What Should White-Label Distribution Contracts Define and What Should Sales Hand Off for an Account Operations Campaign for the related decisions. Keep the accepted instructions connected to the same campaign record. When scope, permission, or destination changes, the responsible team should be able to identify what must be reviewed and which publishing work is affected.
How Conbersa fits into the workflow
Keep the agency responsible for the client promise and name the provider responsibilities inside the delivery agreement. Conbersa offers managed account infrastructure for teams supplying content. Discuss platforms, account access, posting work, reporting needs, and escalation expectations before incorporating that service into a client retainer.