Approval Workflow
How approvals protect quality in agency work — client deliverable approval and the live-publish gate.
#Business goal
Ensure nothing reaches the client or the public without the right sign-off.
#When to use this
Throughout every engagement.
#At a glance
| Detail | Value |
|---|---|
| People involved | Delivery lead, developer, client |
| Departments used | Delivery, Marketing |
| Modules used | Projects, Website CMS, Deliverables |
| AI used | Content Writer Agent drafts copy; you review |
| Recommended timeline | Per deliverable / launch |
| Prerequisites | Projects and Website CMS access; A connected WordPress site for publishing |
#Step-by-step process
1
Deliverable approval
Client approves work in the portal.
2
Prepare to publish
Finalize the approved change.
3
Publish-live approval
A person approves live WordPress publishing.
4
Verify
Confirm the published result.
#Decision points
Decisions to make along the way
- Is the deliverable client-approved?
- Who approves the live publish?
#Approval points
Human approval required
- Client deliverable approval in the portal; human publish-live approval for the live site.
#Success metrics
- No unapproved client-facing work
- No accidental live changes
#Best practices
- Keep both gates in place.
- Verify after publishing.
#Common mistakes
- Bypassing the publish gate.
- Publishing before client approval.
#Realistic example
In practice
A homepage change is approved by the client, then a team member approves the publish-live request before it goes public — two gates, zero surprises.
#Related documentation
Approval Review
Keep approvals moving.
Approval Rules
Where gates are.
Business Workflows
Underlying step-by-step flows.
Contact Support
Reach the DevSphere OS team.
Still need help?
Can’t find what you’re looking for? The DevSphere OS team is happy to help.
Was this page helpful?