Free agency briefing template
Agency WordPress Brief
A cleaner technical brief without turning it into a wall of jargon.
Use this checklist to brief WordPress, WooCommerce, integration and custom-code work while protecting the relationship, review route and client deadline.
- Built for inherited WordPress work
- Client roles made clear
- Print, save or copy
Make it your own: use the prompts that suit the job and remove anything you do not need. It is a helpful handover structure, not a promise that every item is included in every package.
The agency relationship
Set the role, approval route and confidentiality expectations before technical detail takes over.
- Agency project reference and likely service
- Client-facing deadline and internal review date
- Who approves scope and deployment
- Behind-the-scenes or agreed client-facing role
- Confidentiality, NDA and portfolio permissions
The website setup
Share what is known and say what is missing—an inherited site rarely arrives perfectly documented.
- Public and staging URLs
- Known WordPress and PHP versions
- Hosting provider, theme or builder
- WooCommerce and major extensions
- Repository, backup and error-log status
What needs to change
Lead with the visible problem or result your agency needs, then add the evidence available.
- Visible symptom or requested outcome
- Steps to reproduce and expected result
- Affected roles, devices or browsers
- When it began and relevant recent changes
- Commercial impact and known workarounds
What is available to work with
- Repository or source files
- Designs and API documentation
- Test data and console or network evidence
- Server or PHP logs
- Existing tickets and previous supplier notes
Review, sign-off and handover
Make the finish line clear enough for your team to review before communicating with the client.
- What must work and what must remain unchanged?
- Required browsers and devices
- Who tests and signs off?
- Evidence required in the handover
- Who deploys?