Before we begin
Your signed service order records the scope, fees, timing, dependencies and acceptance process. Keep it beside the working plan so everyone is using the same commitments.
- Name one day-to-day contact and one person who gives consolidated approval.
- Gather the existing brand guide, approved assets, current offer and relevant business facts.
- Agree how access will be granted. Use invitations or a secure credential process; do not put passwords in an enquiry form.
- Confirm the first deliverable, the inputs it requires and the next review date.
Prepare a useful brief
For each request, explain the audience, the business problem, the intended action and how the output will be used. Add the approved sources, relevant examples, mandatory details and a reviewer. If something is an assumption, mark it as one.
For an AI or systems project, also identify the workflow owner, data sources, permitted actions and what should happen when the workflow cannot complete a task.
Give feedback the team can act on
- Send one consolidated set of feedback through the agreed project channel.
- Connect the comment to the brief: accuracy, audience, message, usability or missing information.
- Separate corrections within scope from a new direction, additional page or different offer.
- Identify the final approver and confirm when the revision can be reviewed.
Understand the monthly rhythm
The monthly plan names the active workstreams, selected outputs, owners and review dates. Weekly working updates or monthly strategy reviews follow your engagement. Scope or priority changes are agreed before additional work begins.
Reports distinguish completed deliverables, operational adoption and commercial observations. Bring customer feedback and sales outcomes to the review, alongside channel metrics. Read the monthly planning details.
Acceptance and handoff
Review a deliverable against its agreed checklist and provide feedback within the period in your service order. Before launch or handoff, confirm who owns publishing, ongoing updates, access, maintenance and issue reporting.
For a workflow, request the runbook and exception process. For a website, confirm form routing and who updates the content. For a content kit, check editable files, approved claims and the publishing responsibilities.
