How to Create an Approval Process and Workflow

By Kate Eby | September 18, 2017

Approval processes and workflows help to automate simple, repeatable tasks, so that you can focus on the work that matters most. Many organizations create specific approval processes to manage budgets and invoices, as well as creative and marketing initiatives. 

Included on this page, you’ll learn what to include in an approval process,  and how to create an approval process for a variety of needs, including content approval processes, invoice submission, and purchase order approvals.

What Is an Approval Process?

Organizations create approval processes to have a clear, routine way of approving documents, invoices, budgets, purchase orders, and more. Approval processes standardize an organization’s internal processes by creating a reliable, repeatable system. 

Approval processes are a type of workflow, which is any series of ordered steps that you create to ensure you complete work the same way every time.

Creating an approval process can simply mean defining the procedures that you will follow to approve work. You can choose to create a manual approval process where employees follow specified steps and have a manual record of completion, or no record at all. Manual approval processes can be extremely tedious and time-consuming, which can lead to delayed delivery of goods, missed payments, poor document management, and a non-uniform approval process. Additionally, manual processes tend to be less transparent, so some employees might not be aware of the processes and therefore less compliant. 

As a result, many organizations have transitioned to automated approval processes and workflows. Companies can use software to create a tailored approval process, which then guides users through that process to ensure work is completed and approved the same way every time. The main benefits of automated approval processes include saving time, maximizing efficiency, and standardizing processes. 

Additionally, automated approval processes improve transparency and compliance within an organization, since everyone is forced to complete work according to predefined criteria. They also improve decision making, such as whether or not to adopt a project, because the process you define will help you more clearly identify costs and benefits of any work proposal. However, some people struggle with the lack of flexibility that hard-coded automation can inflict upon processes. 

What Is a Project Approval Process?

A project approval process is the process an organization creates to determine which new projects to take on. A project approval team reviews proposed projects and chooses projects based on predefined selection criteria, to help the organization meet its goals.

See how Smartsheet can help you be more effective

Watch the demo to see how you can more effectively manage your team, projects, and processes with real-time work management in Smartsheet.


Watch a free demo

Elements of an Approval Process

While each approval process will differ based on its purpose or the organization’s specific requirements, there are some general tasks that you will likely include when designing your own. These include:

  • Submission: An approval process usually begins with someone submitting something (a document, invoice, purchase order, etc.). You’ll need to create a submission portal where users go to submit their work. Think about including a submission receipt option, so submitters have a record of their activity. 
  • Assign Approvers: The approval process hinges on someone else (not the submitter) approving the work, so you’ll need to identify the person or people who have the final say. If your process has multiple approval levels, define who will approve which aspects of work at each level. 
  • Set Permission Levels: Define the level of authority each user should have. Most systems have features to delineate among viewer, editor, and administrator permissions, so you can control who edits, rejects, or approves submissions. 
  • Set Due Dates: As with any project, it’s important to set deadlines to keep your workflows moving and prevent work backlogs.
  • Automatic Alerts and Notifications: A program that automatically sends alerts and notifications about the status of a submission can help expedite workflow. Automatic alerts may be approval or rejection notifications, update requests (where the approver requests that the submitter makes changes to the original submission), or a simple status update alerting users that work is advancing to the next step in the process. Submissions may have to go through multiple rounds of edits before they are approved, so automatic alerts and notifications can ensure that items are accomplished quickly and that everyone is aware of the current status. 
  • Create a Record or Log: Having a record of every step in the approval process is one of its greatest benefits for increasing transparency and ensuring consistency. If you plan on using an automated solution, look for a program that offers the following capabilities:
    • View User History: See who has made changes, to what, and when. 
    • Lock Record: This will make the record uneditable, so that no user can change the log of actions. 
    • Edit Record: In some cases, you might want the record to be kept editable - for instance, if you made a mistake or need to keep certain information private from other parties. 

While we’re on the topic of automated workflows, it’s important to note that some programs also offer additional functionality that can create a more customized feel, or help disrupt some of the inflexibility that can come with automation. Some of these functions include the following:

  • Email Templates: Some platforms have built-in email templates for notifications. This functionality adds a personalized touch and also provides a space for enhanced communication. 
  • Edit Requests: Similar to update requests, edit requests specifically notify a submitter when the submission has been (temporarily) rejected and that it requires changes before it can be approved. 
  • Task Lists: It can be helpful to build task assignment into the approval process, allowing each employee to clearly see their responsibilities, and informing management of resource allocation. 

Many of these elements will be present in the approval process you design, regardless of the specific project or type or organization. In the next section, we’ll discuss the software programs that allow you to build approval processes and workflows, and additional features to consider. 

Read about the process of creating workflows and automating workflows.


3 Productivity Killers Your Employees Want You to Automate [INFOGRAPHIC]


Software Systems That Support Creating Approval Processes

There are a variety of software tools that you can use to design and build custom approval processes and workflows using the elements defined in the previous section. Regardless of which system you choose, look for a program that supports the following functionality (note that some of these items are named differently in certain products, so make sure you understand the utility of the feature):

  • Create Discrete Steps: An approval process is only effective if there are clear, defined, and repeatable steps. Choose a program that allows you to write discrete steps that users can easily follow and repeat an infinite number of times. 
  • Templates Built-In Workflows: Pre-built templates are helpful if you’ll be creating multiple workflows for a variety of specific use cases. This way, you won’t have to start from scratch every time, or hard-code any parameters. Check out the free downloadable workflow templates and process mapping templates
  • Customization: Although built-in workflows can help you get started, you may want to retain some flexibility. Choose a program with customization options so you can tailor your process; if it doesn’t fit your needs, there’s no benefit. 
  • Edit Capabilities: Once you build your workflow and start using it, you might need to make changes to the procedures you initially put in place. Systems that allow editing will save time. 
  • Mobile Features: Solutions that offer mobile capabilities enable your team to submit work, receive notifications, make requests, and approve work from their phone or tablet. 
  • Signature Collection: If you’re approving sensitive or highly important documents and information, you may require a signature. Some programs offer signature collection so that you can verify approvals. 
  • Feedback Collection: Perhaps you want to create a workflow that elicits feedback, rather than approves work. In this case, look for a program with qualitative collection capabilities. This might be a template option within a larger system (as in Sharepoint, for example). 
  • Notification Templates: You might also want to send notifications in a specific way, such as an in-app notification, email, or push notification on another device. If you want to control the way a user receives notifications, choose a platform with this function.

How to Design an Approval Process

You can design an approval process by defining processes for submission, supporting documentation, review steps, who will give approval, who will edit submissions, and how you will reject certain submissions.

These steps are as follows:

  • Submission: Define how the work will be submitted.
  • Supporting Documentation: Set any additional documents that are required to be included along with a submission.
  • Steps: Define all the steps in the review process.
  • Approvers: Set criteria for who will review each submission.
  • Editing: Decide who (if anyone) can edit submissions.
  • Rejection: Define the criteria for rejecting submissions.

You can think of approval processes as a series of pathways and positive feedback loops. There are often only two possible end-points: reject or approve the submission. However, there are multiple steps and pathways that occur before reaching a conclusion. 

The importance of pre-planning cannot be understated, as this underlying logic will create the structure from which you can build an actual approval workflow. (When we use the term logic here, we are not referring to business logic, which is the part of a software program that encodes the real-world business rules about how workflows can function. Instead, we mean the theoretical logic that will guide the structure of the approval processes you design.)

There are a number of questions that can guide your structural design:

  • How should requests be submitted? Decide how submitters should submit their work, including when, how/where (for example, an online form or portal), to whom, and what to include in the initial proposal.
  • What documentation should you include? Decide if any supporting documentation must be part of the original submission, or if editors and approvers need to send documentation along with their approval or rejection. If so, make sure the software platform can support document storage.
  • How many steps are there, and what are they? The decisions made at this point are the meat of your design process. Here you create the pathways from initial submission to final approval or rejection. For each stage, define the criteria that must be met for a submission to move to the next stage. 
  • Who approves each step? Identify approvers for each stage of the approval process.
  • Who should edit submissions, and at which steps? If your process requires edits at certain stages, who will edit the submission (for example, it could be the original submitter, a designated editor, or the approver)? Deciding who is responsible for editing may change your sequencing.
  • Under what criteria should requests be automatically approved or rejected? There might be instances where an automatic approval or rejection is permissible. Be sure to define these parameters in your logic so you can apply it to the program when you build your process.
  • What actions happen when a request is approved or rejected? Your approval process should not exist in a silo, so consider how it is connected to the execution processes, once a submission is approved or rejected. Consider linking notifications to kick off a project or pull the next submission.

What Is a Project Approval Workflow?

A project approval workflow is a sequence of steps that a project goes through during its lifecycle. At each milestone, the progress of the project is reviewed to determine if it’s ready to begin the next phase.

How to Create an Approval Process

Approval processes can benefit organizations of any type or size, across all industries. You can create an approval process for any repeatable system that can be broken down into discrete steps to formally approve a submitted piece of work. Some of the most common types of approval processes include invoice submissions, documents and creative assets, purchase orders, projected budgets, project plans, college applications and admission, or Food and Drug Administration (FDA) drug approval. 

Below we show you the essential aspects of each of these approval processes, and how to design the process itself. While the specific steps you take to build an approval process will vary based on the system you choose to build it in, these logic maps will help you define the workflow that works best for the situation and your specific requirements.

How to Create a Content or Document Approval Process

Content and documents should be reviewed and approved before being posted or released. At a minimum, this process will include task assignment, writer notifications, one or multiple rounds of drafts and edits, content approval, and content publish.

Content approvals are ubiquitous across all industries and types of organizations. They include any creative asset, written work such as an article or social media copy, or any other documentation that needs approval prior to publication. 

To create a content approval process, follow this outline of steps:

  • Content Manager Assigns Tasks: The editor creates a schedule of tasks and assigns specific work items to each content producer (in this example, a writer).  
  • Writer Receives Email Notification: Institute a standardized way to notify writers of their tasks. Email notifications are easy to use and provide a record of assignment.
  • Writer Reviews Tasks: The writer reviews the assignment and, if necessary, seeks clarification on tasks from the editor. 
  • Writer Submits First Draft to Editor: This is the initial submission step where the writer submits the first draft of their work for editor reviews. 
  • Editor Returns Comments: In most content approval processes, there will be at least one round of edits. So, build in a step where the editor makes edits and returns the submission to the writer to make additional changes if needed. 
  • Writer Submits Final Draft: Once the necessary edits are made, they return the content to the editor for a second review. 
  • Editor Approves or Rejects Content: Here the editor has the option to either approve or reject the content.  
    • Approve: The content is formally approved. 
    • Reject: The writer must make more edits. This cycle of edits can continue until the editor is satisfied and the content is officially approved. 
  • Producer Publishes Content: Once all edits are finalized, the content is published.

How to Create an Invoice Approval Process

In an invoice approval process, vendors, contractors, and employees need to submit invoices to be paid or reimbursed.  This process, at minimum, will include submission, review, and support documentation.

Invoice submission is another common practice that a standardized approval process can improve. On a monthly basis, you might receive invoices from vendors, contractors, or even internal employees seeking reimbursement, so creating a repeatable, reliable approval process will help ensure that everyone is correctly paid on time.

To create an invoice approval process, follow this outline of steps:

  1. Vendor Mails or Submits Invoice Through an Online Portal to Accounts Payable: The vendor submits their invoice to the correct department or single approver (typically accounting or accounts payable). If using an online portal, the invoice is automatically routed to the correct person or department.
  2. Review Invoice for Compliance: This is the initial review made by the approving body. Compliance will differ based on the specific organization, but in general, the invoice should be checked for accuracy and include any necessary support documentation. There are two options here:
    • Invoice Meets Requirements: The invoice can move on to the next stage in the approval process. 
    • Invoice Does Not Meet Requirements: The invoice is returned to the vendor, who will update and resubmit the invoice.
  3. Internal Department Has Required Information from Vendor: In order for an invoice to be processed and payment sent, the approving body often must include supporting information or documentation about how and why they approved the invoice. So, build a step into your process to verify that the required support documentation is included.
    • Support Material Included: The invoice is placed in the payment queue, processed, and sent to the submitter. 
    • Support Material Not Included: The invoice is placed on hold until the approving body compiles all necessary documentation. Once this happens, the invoice returns to the final review stage and if approved, is placed in the payment queue and then processed.

How to Create a Purchase Order Approval Process

Purchase orders (PO) are a key part of many businesses. To ensure they are correct, a PO approval process includes buyer submission, seller approval or rejection, and, if approved, order processing. 

A purchase order (PO) is a document sent from a buyer to a seller to request a certain amount of goods or services at an agreed upon price. Creating an approval process for purchase orders can help you monitor the pace of incoming requests, manage inventory and resources, and provide a log of your external business.

To create a purchase order approval process, follow this outline of steps:

  1. Purchase Order Is Received: The buyer formally submits the initial request for goods or services from the seller. Again, consider creating an online submission portal. From here, the route of approval may differ depending on if the PO is from an existing or new customer. Here are both possible scenarios: 
    • PO from Existing Customer: If the PO is from an existing customer, it is processed one of two ways: 
      • Approved: If everything is correct and the customer has no outstanding balance, the PO is approved and the order is processed. 
      • Outstanding Still Due: If the customer has an outstanding balance, it is sent to another party for review and approval (Step 2 below). 
    • PO from New Customer: The new customer may have to complete a credit application to ensure that they are equipped to pay for the goods or services requested in the PO.
  2. Submitted to Controller for Approval: The approving body reviews the PO and any supporting documents (credit application, payment history, etc.) and either approves or rejects the PO.  
    • Approved: The purchase order has been approved and the order is processed. 
    • Not Approved: The purchase order has failed to meet requirements and is rejected. The buyer will sometimes request another payment form, or the seller might revise the PO and resubmit it to the controller for approval.

How to Create an Annual Projected Budget Approval Process

To create a budget review process, follow these steps: request a budget; set up a system; develop a proposed budget; review; modify and distribute the proposal; modify and submit the updated proposal.

Most companies have to propose an annual or quarterly budget before they can formally adopt projects and allocate funds. Since most - if not all - of an organization’s operations depend on having a pre-approved budget, it’s essential to have an approval process in place. 

To create a budget approval process, follow these steps:

  1. Request Budget: The executive board submits their proposed budget. 
  2. Set Up Budget System: If you don’t already have a system in place to manage and allocate budget, you can build this into your approval process. Complete this step early, as it will inform the rest of your budget review and fund allocation process. 
  3. Develop Base Budget and Distribute: The budget coordinator defines the base annual budget from which you will measure the proposed budgetary needs. 
  4. Review, Refine Rules, and Distribute: This is the initial review, usually performed by an analyst. 
  5. Modify and Submit Budget: Internal budget preparers modify the proposed budget based on the reviewer’s (analyst’s) feedback and resubmits it. In some cases, the original submitter (in this case, the executive board) can also be responsible for modifying and resubmitting the budget.
  6. Review Budget: A designated budget reviewer now reviews the most recent draft of the budget.  
    • Approved: If approved, the budget reviewer submits the final version of the budget back to the analyst for another round of reviews. 
    • Rejected: The budget goes back to the budget preparer for another round of edits, and is then resubmitted to the budget reviewer. This process may require multiple attempts before the budget is approved.
  7. Review Submitted Budget: The analyst performs another review on the submitted budget, which has now been approved by the budget reviewer.
  8. Consolidate Budgets and Present: Now that the budget has been approved by all analyst and review levels, the budget coordinator compiles the information and presents it to the executive board for final sign off. 
  9. Conduct Budget Deliberations: The executive board reviews the changes made by the approving bodies, and either approves or rejects the budget.  
    • Approved: The budget is now officially approved and is adopted into the organization’s yearly planning. Funds are allocated. 
    • Rejected: The executive board resubmits their proposed budget (perhaps with modifications) to the budget coordinator; the cycle begins again at Step 3.

How to Create a Project Plan and Budget Approval Process

Every project that an organization adopts must first pass through a series of approvals. With so many competing projects, budgets, and departments, an approval process helps organize and prioritize projects. 

To create a project plan and budget approval process, follow this outline of steps:

  1. Submit Project Proposal: This is the initial submission, where teams define and request the project they want to take on. You can find a project plan template here
  2. Estimate Baseline Costs and Schedules and Prioritize Projects: In these phases, draft a budget and timeline based on your project proposal, and roughly prioritize projects. There may be some back and forth between these two steps before advancing to the next step. 
  3. Evaluate Funding Alternatives and Scenarios: It’s important to consider alternatives - both to your project specifications and budget - in the event that your proposal is rejected. Build in a step to draft other options, or aspects of your initial plan. 
  4. Approve or Reject Projects: The proposal is reviewed by the approving body and either approved or rejected.  
    • Approved: If approved, funding is allocated for your project and you can hold a project kickoff.
    • Rejected: If rejected, the proposal is terminated. However, you can also build a step for submitters to revise the project plan and resubmit for approval.

How to Create a College Acceptance and Admission Process

The college admission process today involves, at a high level, applications, interviews, conditional offers, and admission.

Colleges and universities receive a high volume of applicants and as such, must create an automated, consistent approval process for admitting and enrolling students. While the steps listed below are what academic institutions might follow, you can also edit the process outline for admission to other programs. 

To create a college acceptance and admission process, follow this outline of steps:

  1. College Application Received and Routed to College Registrar for Initial Approval: The application is submitted (typically through a portal such as the Common App or a university website). The registrar, or any other administrative approving body, performs an initial screening and either approves or rejects the application. 
    • Approved: The application passes the initial screening and next-step information is sent to the student applying. 
    • Rejected: The student’s application is terminated and information is sent to the applicant.
  2. Conduct One-on-One Interviews: Many academic institutions require interviews as part of the application process. However, some don’t, so this step is optional.  
    • Interview Successful: If the interview is successful, the college or university issues a conditional offer to the applicant and moves onto the next stage. 
    • Interview Unsuccessful: The student’s application is rejected.
  3. Conditional Offer Issued to the Student: The university formally offers the applicant admission. The student can accept or refuse the offer. 
    • Students Accepts Offer: Student accepts the conditions of the university’s offer and pays tuition to the school. 
    • Student Refuses Offer: The application is dropped. At this point, the university might also solicit feedback from the applicant to use for future application cycles. 
    • College Issues Admission to the Student: Once the college receives the tuition, the student is enrolled in the university.

How to Create a Food and Drug Administration (FDA) Drug Approval Process

Getting a drug approved involves the following stages: pre-clinical, or drug discovery or screening; clinical, which involves three phases of clinical trial; review by the FDA; and post-marketing, when the healthcare industry sells and markets the drug.

Every pharmaceutical drug on the market today in the U.S. has to pass through a lengthy approval process, as enforced by the Food and Drug Administration (FDA). The following outline is taken directly from the FDA's website.

Stage One: Pre-Clinical: In this stage, the person or body sponsoring the drug (drug sponsor) discovers and screens the drug. 

  1. Drug Developed and Animals Tested: Once the sponsor has developed a new drug and wants to have it approved by the FDA, they perform animal testing to gain information on the safety and efficacy of the drug compound.
  2. Investigational New Drug (IND) Application: The drug sponsor submits an IND application to the FDA to seek approval. This application includes information on the results of the animal tests, as well as on the composition and manufacturing of the drug.

Stage Two: Clinical: This stage consists of the drug sponsor’s clinical studies and trials of the proposed drug. 

  1. Phase 1 (20-80 volunteers): This testing phase is primarily concerned with identifying the most common side effects, and how the drug is processed within the human body. It emphasizes safety. 
  2. Phase 2 (hundreds of volunteers): This phase emphasizes effectiveness, and tests how the drug affects a certain disease or illness. 
  3. Phase 3 (thousands of volunteers): In this phase, testers gather more information about both the safety and effectiveness of the proposed drug. They also test it in combination with other drugs, different dosages, and different populations to understand the effects.

Stage Three: New Drug Application (NDA) Review: The FDA performs a comprehensive review on the new drug to ensure it meets requirements and is safe to approve.

  1. Review Meeting: The FDA meets with the drug sponsor to discuss the findings of the testing.
  2. NDA Application: The sponsor submits a formal application, and includes all data from the tests they’ve completed on both animals and humans.
  3. Application Review: The FDA has 60 days to review the NDA application and decide whether or not to file it.  
    • Filed: If the FDA files the NDA, it moves on to the next review step. 
    • Not Filed: The FDA can also choose not to file the NDA. At this point, the drug proposal is terminated.
  4. Application Reviewed: If the FDA decides to file the NDA, they perform a review of the application to evaluate the sponsor’s research and the drug itself.  
    • Approved: If approved, the drug moves on to the next step. 
    • Rejected: If rejected, the proposal is terminated.
  5. Drug Labeling: The FDA reviews the official drug labeling and edits it to ensure the proper messaging and communication to health care professionals and consumers.
  6. Facility Inspection: The FDA performs an inspection of the facilities where the drug will be manufactured to ensure safety. 
  7. FDA Drug Approval: The drug is formally approved by the FDA.

Stage Four: Post-Marketing: Ongoing efforts by healthcare industries to appropriately market the drug to the public.

Streamline Approval Processes with Real-Time Work Management in Smartsheet

Empower your people to go above and beyond with a flexible platform designed to match the needs of your team — and adapt as those needs change. 

The Smartsheet platform makes it easy to plan, capture, manage, and report on work from anywhere, helping your team be more effective and get more done. Report on key metrics and get real-time visibility into work as it happens with roll-up reports, dashboards, and automated workflows built to keep your team connected and informed. 

When teams have clarity into the work getting done, there’s no telling how much more they can accomplish in the same amount of time. Try Smartsheet for free, today.



Discover why over 90% of Fortune 100 companies trust Smartsheet to get work done.

Learn More About Automating Approval Processes with Smartsheet