Run a project through two signed gates: the sponsor approves the start, the project manager plans and the delivery lead builds, and the client signs acceptance before closing.
Sign in with your Edesy account; the setup wizard opens on this template.
Category
Type
Business process
Steps
7
Roles
Project sponsor, Project manager, Delivery lead, Client representative
Level
Intermediate, about 15 min to set up
A simple stage-gate model for client or internal projects. Gate 1: the sponsor approves and signs the proposal so planning can start. The project manager then submits a plan (milestones and resourcing) through a task form, and the delivery lead executes and marks delivery complete. Gate 2: the client representative reviews the result and signs acceptance, or asks for rework, which sends the work back to the delivery lead. When accepted, the requester is told and a flow report records both gates.
Form: Project Proposal
Starts the workflow
Gate 1 — approve & sign start: {{trigger.body.projectName}}
Approve & sign · Project sponsor
Deny: E-mail: Gate 1 not passed: … · Approve: Plan the project
E-mail: Gate 1 not passed: …
Plan the project
Task · Project manager
Mark as done: Deliver the work
Deliver the work
Task · Delivery lead
Mark as done: Gate 2 — sign acceptance: {{trigger.body.projectName}}
Gate 2 — sign acceptance: {{trigger.body.projectName}}
Approve & sign · Client representative
Accept & sign: Flow report · Needs rework: Deliver the work
Flow report
Flow report
E-mail: Accepted and closed: …
Project Proposal
Starts the workflow · 10 questions
Project Plan
Task form · 4 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.
Authors upload a policy, specification or report; the document owner approves and signs it or asks for changes, and the signed version is filed in Google Drive.
7 steps · 2 rolesCampaign Approval ProcessMarketers submit a campaign brief with creatives; the marketing head approves it, the launch date goes on the team calendar, creatives are filed in Drive and the campaign manager schedules it.
7 steps · 2 rolesChange Request ApprovalA change to a project's scope, schedule or budget is signed off first by the project manager and then by the change board chair before anyone acts on it.
7 steps · 3 rolesCustomer Service Request ApprovalCustomers ask for an on-site service visit through a contact form; support checks the account and approves, a field technician confirms the job, and the customer is told when to expect them.
6 steps · 3 rolesEvent Invitation ApprovalGuests RSVP to an invitation-only event; the host approves and signs off each guest, the guest is added to Zoho CRM, and the event coordinator prepares their badge.
6 steps · 2 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 roles