Website Project SOP
The standard operating procedure for delivering a website from kickoff to approved launch.
#Business goal
Deliver websites consistently, on time, and with clear client approval.
#When to use this
For every website build.
#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 project |
| Prerequisites | Projects and Website CMS access; A connected WordPress site for publishing |
#Step-by-step process
1
Kick off
Create the project, tasks, and milestones; confirm scope.
2
Build
Develop the site and draft content (AI can assist).
3
Review internally
Quality-check before showing the client.
4
Client review and publish
Share via the portal, then publish live through the approval gate.
#Decision points
Decisions to make along the way
- Is the build ready for client review?
- Is it ready to publish live?
#Approval points
Human approval required
- Client approves deliverables in the portal; publishing to the live WordPress site requires a human publish-live approval.
#Success metrics
- On-time launches
- First-pass client approval
#Best practices
- Quality-check before client review.
- Use the publish-approval gate every time.
#Common mistakes
- Publishing without the approval gate.
- Skipping internal QA.
#Realistic example
In practice
A build finishes, passes internal QA, the client approves it in the portal, and it goes live only after the publish-live approval — no accidental early launches.
#Related documentation
Launch Checklist
Before go-live.
Website Publishing
Underlying flow.
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?