Workflow Template
Project Approval Workflow
End-to-end project approval process covering proposal submission, business case review, stakeholder input, funding/management approval, decision recording, and project initiation.
Someone submits a project idea, and suddenly you're juggling email threads, chasing reviewers, and trying to remember who still needs to sign off. The Project Approval Workflow handles every stage automatically — from proposal submission and business case review through stakeholder input, funding approval, and project initiation. Your team always knows where a proposal stands, and nothing slips through the cracks while you're focused on other priorities.
Business Outcomes
- Reduce average project approval cycle time by eliminating manual follow-up and status chasing
- Ensure every proposal reaches the right reviewers and approvers in the correct sequence
- Create a complete, auditable record of every approval decision and revision request
- Give submitters real-time visibility into their proposal status without needing to ask
- Standardise approval quality by ensuring business cases and stakeholder input are captured before funding decisions are made
Workflow Steps
Steps
- 1Create Project Proposal Recordcreate record
Registers the submitted project proposal as a record in the system.
- 2Set Review Due Dateset due date
Sets a 10-business-day SLA target for completing the approval process.
- 3Set Status: Receivedupdate record
Marks the proposal as Received upon submission.
- 4Send Submission Confirmationsend email
Notifies the submitter that their project proposal has been received and is under review.
- 5Business Case Reviewcreate task
Assigned reviewer assesses the business case including objectives, benefits, scope, cost, resources, risks, and dependencies.
- 6Set Status: Under Reviewupdate record
Updates the proposal status to Under Review after the business case assessment is complete.
- 7Route on Reviewer Recommendation
Routes the workflow based on the business case reviewer's recommendation.
reviewer_recommendation: "Proceed to Stakeholder Review"→Collect Stakeholder Inputreviewer_recommendation: "Requires Revision"→Notify Submitter: Revision Requiredreviewer_recommendation: "Recommend Rejection"→Set Status: RejectedDefault→Collect Stakeholder Input - 8Notify Submitter: Revision Requiredsend email
Emails the submitter that their proposal requires revision before it can proceed.
- 9Proposal Revision Taskcreate task
Assigns a task to the submitter's coordinator to facilitate proposal revision and resubmission.
- 10Route on Revision Outcome
Routes to re-review if revised, or closes the proposal if withdrawn.
revision_ready: "Yes"→Restart from Business Case Reviewrevision_ready: "No — Withdraw Proposal"→Set Status: WithdrawnDefault→Restart from Business Case Review - 11Restart from Business Case Reviewrestart from step
Restarts the workflow from the business case review step with the revised proposal.
- 12Set Status: Withdrawnupdate record
Marks the proposal as Withdrawn at the submitter's request.
- 13Notify Submitter: Proposal Withdrawnsend email
Confirms to the submitter that their proposal has been withdrawn.
- 14Collect Stakeholder Inputrequest external input
Sends an external form to key stakeholders to gather their input and endorsement before the approval decision.
- 15Set Status: Stakeholder Reviewupdate record
Updates the proposal status to Stakeholder Review after input is received.
- 16Funding / Management Approvalrequest approvalrequires approval
Requests formal approval from the approving authority (funding committee or senior management) to proceed with the project.
- 17Route on Approval Decision
Routes the workflow based on the funding/management approval outcome.
approval_status: "approved"→Set Status: Approvedapproval_status: "rejected"→Set Status: RejectedDefault→Set Status: Approved - 18Set Status: Approvedupdate record
Records the approval decision on the proposal record.
- 19Notify Submitter: Proposal Approvedsend email
Emails the submitter to confirm their project proposal has been approved and initiation can begin.
- 20Project Initiationcreate task
Assigns a project initiation task to the project coordinator to set up the project, assign resources, and confirm the kick-off plan.
- 21Set Status: Initiatedupdate record
Marks the proposal record as Initiated, completing the approval workflow.
- 22Notify Submitter: Project Initiatedsend email
Sends a final confirmation to the submitter that the project has been formally initiated.
- 23Set Status: Rejectedupdate record
Records the rejection decision on the proposal record.
- 24Notify Submitter: Proposal Rejectedsend email
Emails the submitter to inform them that their project proposal has not been approved.
Fields
- Project Title*
- Submitter Name*
- Submitter Email*
- Department / Business Unit*
- Project Priority*
- Project Objectives*
- +10 more fields
Forms
Project Proposal Submission
14 fields
Data Views
All Project Proposals
project_title, submitter_name, department, project_priority +2 more
Active Proposals — Awaiting Decision
project_title, submitter_name, department, project_priority +1 more
Dashboard Widgets
Recommended integrations
Setup the following integrations to extend workflow capability.
Send email in the workflow
AWS SES
Similar Categories
FAQs
Do I need technical skills or a developer to set this up?
No technical skills are needed at all. The Project Approval Workflow is a ready-to-use template inside assess.one — you publish it and it's live within minutes. All steps, roles, notifications, and approval logic are configured directly in the platform without writing a single line of code.
How long does it take before my team can start using this workflow?
You can publish the template and run your first live approval process in minutes, not weeks. There's no implementation project, no external software to install, and no waiting on a vendor. Once published, your team submits proposals and the workflow kicks off immediately.
Can my team customise the approval steps to match how we actually work?
Absolutely. You can add, remove, or reorder steps, adjust who is responsible for each stage, and change the approval logic to reflect your organisation's structure. If your funding approval involves multiple sign-off tiers, for example, you can configure that routing directly inside assess.one.
Who needs access to the workflow, and can different people have different roles?
Yes — you assign roles within assess.one so that submitters, reviewers, stakeholders, and approvers each only see and action what's relevant to them. A project submitter can track their proposal's progress without having access to the funding approval stage, for instance. Role-based access keeps the process clean and secure.
What happens if a business case needs revision — does the process restart from scratch?
No, it's smarter than that. If the reviewer recommends a revision, the workflow automatically notifies the submitter, creates a revision task, and routes the updated proposal back to the business case review stage once changes are submitted. If the submitter doesn't proceed, the proposal can be marked as withdrawn and all parties are notified automatically.
Is this suitable for organisations that need a clear audit trail for compliance purposes?
Yes. Every decision, status change, and approval action is recorded within assess.one as the workflow progresses. This gives you a timestamped, end-to-end record of who reviewed what, when decisions were made, and what the outcome was — which is exactly what internal audit and governance teams typically need.
Can stakeholders provide input without being involved in every stage of the approval?
Yes. The workflow includes a dedicated stakeholder input stage that sits between the business case review and the funding or management approval decision. Stakeholders are brought in at the right moment, complete their input, and the process moves forward — they're not pulled into stages that don't require them.
Will submitters know what's happening with their proposal without having to chase anyone?
Yes — automated notifications keep submitters informed at every key milestone. They receive a confirmation when their proposal is received, a notification if revisions are needed, and a clear approved or withdrawn outcome message once a decision is made. No chasing, no ambiguity.
Can we connect this workflow to our email or Slack so notifications go to the right places?
Yes. Email and Slack integrations are configured inside assess.one — there's no third-party development work involved. You set up where notifications go as part of your workflow configuration, so approvers get pinged in the tools they already use.
What triggers the project initiation stage, and can we control what happens at that point?
Project initiation is triggered automatically once the funding or management approval decision is recorded as approved. You can customise what the initiation step involves — whether that's assigning a project lead, sending a kick-off notification, or creating a follow-on task — all configured within the workflow in assess.one.
Ready to use this workflow?
Create a free account and customise this workflow for your business.
