Document Approval Process

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.

A document approval workflow template is a ready-made sign-off process in which an author submits a document with its version number, a named owner approves and signs it, asks for changes or rejects it, and the approved version is filed in one controlled place.

Sign in with your Edesy account; the setup wizard opens on this template.

Category

Project Management

Type

Business process

Steps

7

Roles

Document owner, Document controller

Apps

Google Drive

Level

Intermediate, about 12 min to set up

Updated

2026-11-19

How the workflow runs

Documents that change hands over e-mail end up with five "final" versions. Here the author uploads the file with its version number and audience, gets an acknowledgement, and the document owner reviews it. The owner can approve and sign, send it back with specific changes (the author revises and it returns to the same owner), or reject it outright. Approved documents are uploaded to a shared Google Drive folder and a flow report records who signed which version and when. Point the Drive step at your controlled-documents folder before you switch it on.

Request changesRejectApproveMark as doneFormForm: Document UploadE-mailE-mail: request receivedApprove & sign · Document ownerReview: documentTask · SubmitterMake the requested changesE-mailE-mail: rejectedApp action · Google DriveGoogle Drive: file approveddocumentE-mailE-mail: approvedFlow reportFlow report

Steps in order

  1. 1

    Form: Document Upload

    Starts the workflow

  2. 2

    E-mail: request received

    E-mail

  3. 3

    Review: document

    Approve & sign · Document owner

    Request changes: Make the requested changes · Reject: E-mail: rejected · Approve: Google Drive: file approved document

  4. 4

    Make the requested changes

    Task · Submitter

    Mark as done: Review: document

  5. 5

    E-mail: rejected

    E-mail

  6. 6

    Google Drive: file approved document

    App action · Google Drive

  7. 7

    E-mail: approved

    E-mail

  8. 8

    Flow report

    Flow report

Forms

  • Document Upload

    Starts the workflow · 10 questions

    Full name · E-mail address · Document title · Document type · Version · Document file · Who will use it? · Approval needed by · Is this new or a revision? · What changed since the last version?

Who takes part

  • Document owner: Accountable for the content; approves and signs each version.
  • Document controller: Keeps the register of controlled documents and receives the report.

Apps it connects

  • Google Drive

Why each step is there

Document Upload form (trigger)

Version and Is this new or a revision? are required, so every run is tied to one specific version. What changed since the last version? gives the owner a change summary instead of a side-by-side read of two files.

E-mail: request received

Confirms the title and version to the author and tells them that any change requests will arrive as a task, so they do not chase the owner on chat.

Review: document (Document owner approval with signature)

The core of the process: Approve, Request changes or Reject, due in 3 days with daily reminders. Approval captures the owner's signature, the owner can reassign the review or ask for more information, and a comment is required for changes or rejection.

Make the requested changes (task for the author)

Quotes the owner's comment and who asked for it. Marking it done returns the document to Review: document, so the revise and review loop can repeat until the owner approves or rejects.

E-mail: rejected

Ends the run with the owner's reason and asks the author to submit a fresh draft as a new document, keeping rejected versions out of the register.

Google Drive: file approved document

Files only approved versions in the shared folder, which becomes the single source of truth. Point it at your controlled-documents folder before you switch the workflow on.

E-mail: approved and Flow report to the Document controller

The author is told who signed which version, with the owner's note, and the document controller receives a report of the run to update the document register.

About the Document Approval Process template

The workflow starts with the Document Upload form: Full name, E-mail address, Document title, Document type (Policy, Standard operating procedure, Technical specification, Report, Contract template or Training material), Version, the Document file, Who will use it? (All staff, Managers, A single team, Customers, Suppliers), an optional Approval needed by date, Is this new or a revision? and What changed since the last version?. The author gets a request received e-mail naming the title and version with a link to follow the run. The Document owner then has the approval step Review: document, due in 3 days with a reminder every day up to 3 times, and three outcomes. Approve is signed: the step asks for the owner's signature. Request changes needs a comment and creates a Make the requested changes task for the author, who updates the document and marks it done to send it back to the same owner. Reject also needs a comment, which is quoted in the rejection e-mail before the run ends. An approved document is uploaded by the Google Drive: file approved document step, the author receives a Signed off e-mail naming who signed which version, and the Document controller gets a Flow report.

Who it is for

It is for any organisation where policies, SOPs and specifications are still passed around as e-mail attachments until nobody knows which file is final: manufacturers and pharma units keeping controlled documents for audits, IT and services companies maintaining ISO-style procedures, schools and hospitals updating staff policies, and finance teams approving contract templates. In Indian companies where the managing director or a department head signs off most documents, it gives that one owner a single queue and leaves a dated record of each signed version for the document controller.

How to use it

  1. 1

    Click Use this template and sign in with your Edesy account; the setup wizard maps the Document owner and Document controller roles to people, connects Google Drive and creates the Document Upload form.

  2. 2

    Edit the Document type and Who will use it? options to match your document register, and make Approval needed by required if your owners work to deadlines.

  3. 3

    Before switching the workflow on, point the Google Drive step at your controlled-documents folder so signed versions are filed in the right place.

  4. 4

    If different documents have different owners, add an If / else decision on Document type in the builder and send each type to its own approval step.

  5. 5

    Share the upload form link with your authors and tell them to share the Drive link, not attachments, once a version is signed off.

Connected templates in other Edesy apps

Document Approval Process: frequently asked questions

The Review: document approval step asks for a signature when the owner approves, so the record shows who signed off which version. If you need a counterparty or several people to sign the file itself, you can add a Sign document step, which sends it through Edesy Sign.

They must write what to change. The author gets the Make the requested changes task with that comment, updates the document and marks it done, and it goes back to the same owner for another review.

The template has one approval by the Document owner. You can add further approval steps in the visual builder, for example a compliance review before the owner signs.

In the Google Drive folder you choose in the Google Drive: file approved document step. Rejected documents and drafts that need changes are not filed.

Yes. Review: document is due in 3 days, with a reminder every day up to 3 times. The revision task for the author has the same settings.

Not as shipped, but you can add an Edesy Voice Agent step so an AI voice agent calls the approver now or at a set time. It needs an Edesy voice agent account.

About the app

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.

Related templates