A website design brief is approved and signed by the marketing director, scoped by the web project manager, built by content, design, development and SEO in parallel, then tested and launched.
Sign in with your Edesy account; the setup wizard opens on this template.
Category
Type
Business process
Steps
12
Roles
Marketing director, Web project manager, Content writer, UI designer, Web developer, SEO specialist, QA tester
Level
Advanced, about 19 min to set up
Web projects stall when everyone waits on everyone else. After the marketing director approves and signs the brief, the web project manager turns it into a scope and sitemap, and the requester is told the project has started. Four streams then run at the same time: the content writer drafts copy, the UI designer produces mock-ups, the web developer sets up the build, and the SEO specialist prepares keywords and redirects. When all four are done, QA tests across devices, the developer launches, and the requester gets the live link.
Form: Website Design Request
Starts the workflow
Approve & sign website brief
Approve & sign · Marketing director
Deny: E-mail: Website brief not approved · Approve: Scope the project and sitemap
E-mail: Website brief not approved
Scope the project and sitemap
Task · Web project manager
Mark as done: E-mail: Your website project has started
E-mail: Your website project has started
Four streams in parallel
Split
Write page copy
Task · Content writer
Mark as done: Test on devices and browsers
Design mock-ups
Task · UI designer
Mark as done: Test on devices and browsers
Set up the build
Task · Web developer
Mark as done: Test on devices and browsers
SEO plan and redirects
Task · SEO specialist
Mark as done: Test on devices and browsers
Test on devices and browsers
Task · QA tester
Mark as done: Launch the site
Launch the site
Task · Web developer
Mark as done: E-mail: Your website is live
E-mail: Your website is live
Website Design Request
Starts the workflow · 12 questions
You sign in to Edesy Flow with your Edesy account and the template wizard opens: map each role to a person, pick the app connections it needs, and Flow creates the forms and the workflow for you to edit.
Yes. The workflow opens in the visual builder, where you can add, remove or reorder steps, change who approves, edit the e-mails and add branches.
Requests for administrator or privileged accounts are approved and signed by the system owner; the IT administrator then records exactly what was granted and until when, and the record is filed in Drive.
7 steps · 3 rolesEquipment Purchase RequestTeams request new laptops, phones, instruments or tools; the department manager approves and signs, and procurement orders the items and tells the requester the PO and delivery date.
4 steps · 2 rolesHelp Desk Ticket ApprovalHelp desk tickets that need a sign-off are routed by type: purchases to the budget holder, access to the system owner, and every ticket is then approved and signed by the IT support lead.
10 steps · 5 rolesInformation Request ApprovalStaff request a data extract or report; the data owner approves sharing it, a data analyst prepares it with escalation if it stalls, and the data protection officer gets a report.
6 steps · 4 rolesIT Change RequestIT changes are routed by type: standard changes go straight to scheduling, normal changes need the CAB chair's signature and emergency changes the emergency approver's, before the window is booked and implemented.
12 steps · 4 rolesIT Incident ManagementService outages are classified and signed off by the incident manager, resolved by the resolver group, analysed for root cause and formally closed (or reopened) by the service owner.
8 steps · 4 roles