Skip to content

The approval matrix template: a free sheet for who approves what

A free, ungated approval matrix template - CSV and printable Markdown, English and Polish - for mapping who approves what before you build it as a workflow.

Updated · 7 min read

In short

  • An approval matrix is a one-page plan of who approves what, in what order, with what evidence, and who covers a step when the usual approver is away - before any of it becomes a workflow in a tool.
  • This page gives you that sheet as a CSV and a printable Markdown file, in English and Polish, pre-filled with ten common request types and no email address required.
  • Every threshold and role in the sheet is a default taken from a shipped DueReason template, not an invented benchmark - edit every number and name to match your own organization.
  • Each row also says exactly which DueReason template it maps to, so filling in the sheet and installing the matching template end up describing the same rule.

A spreadsheet is the right first draft for an approval process, because it forces a decision most organizations have never written down: for each kind of request, who approves it, in what order, past which threshold does a second person need to sign off, what proof do they need to see, and who covers the step if the usual approver is on leave. Answering those five questions on paper is cheap. Discovering the answers were never written down - during an audit, a dispute, or the day the one person who approves vendor payments is unreachable - is not.

Download the template (no email required)

Four files, pre-filled with ten common request types. Nothing is gated behind a form: download, open, edit.

Every threshold, role name and timing in the sheet is an example value - set your own for your organization; none of it is a market figure or a recommendation about how strict your approvals should be.

Five rules for filling it in

  1. Set the threshold before you name the approver. A second approver on a row almost always exists because of a number - an amount, a percentage, a yes/no field - crossing a line, not because of who happens to be free. Decide the number first, then who it routes to.
  2. Fix the order. Write down which approver sees the request first. DueReason enforces this as written: a workflow's steps run in the order you set them, and a step that is not yet open cannot be answered out of turn.
  3. Never let a requester approve their own row. Whoever files the request is disqualified from approving it themselves, whatever role or approver group they also belong to - DueReason refuses the attempt directly, on every request, not just the first one.
  4. Name the evidence, not just the approver. A document (an invoice, a vendor's registration form), a written reason, or nothing at all - decide per step what has to come with the answer, the same way a DueReason workflow step names one of document, text or none.
  5. Write down what happens when an approver is away. A step that needs exactly one approver can be handed to someone else for that one request. A step that needs two or more approvers at once cannot be reassigned to a single stand-in - it needs a second person already sitting in the approver group, not a delegate.

How each row maps to a shipped DueReason template

Settings → Templates installs ten ready-made setups; the sheet's ten rows line up with them one for one. Each template ships with its own default threshold, which is exactly the number printed in the sheet - editing the sheet does not change the product, but editing the installed template's condition does.

RowDueReason template (core/src/approval-templates.ts)What crosses the line
Purchase or payment requestagent-payment ("Payments and refunds")Amount at or above 5,000 adds a Management step after Finance
Vendor onboardingvendor-onboardingEstimated annual spend at or above 10,000 adds a Management step after Procurement
Discount exceptiondiscount-exceptionDiscount at or above 25% adds a Sales leadership step after Sales manager
Hiring offerhiring-offerAn offer outside the pay band adds an Executive step after HR
Expense / policy exceptionpolicy-exceptionAlways two steps: Manager, then the policy's owner
Production deployproduction-deployDeploying to the production environment (staging auto-approves) needs Engineering lead, then Security
Access restriction or suspensionaccess-or-account-actionOne reviewer, no second step
Offboarding (access revocation)access-or-account-actionRevoking access needs two reviewers in parallel (quorum), then Legal
Content / publication sign-offcontent-or-publication-signoffA legal or financial claim adds a Legal step after the content lead
Data access, export or deletiondata-access-exportA deletion request adds a Security step after the data owner

The quorum on the offboarding row - two reviewers who must each independently approve, not one of two interchangeable people - is the same minPerGroup mechanism the workflow engine uses for any step that needs more than one named group to each supply an approval, and it is also why that row has no single-person stand-in: reassignStep only hands off a step that needs exactly one approval.

What this does not do

Filling in the sheet does not create anything in DueReason by itself. It is a planning document: installing the matching template in Settings → Templates, adding people to its approver groups, and editing its conditions is what actually makes a rule enforceable. The "max time to decide" column is a target you set for yourself, not a per-template setting - DueReason lets whoever files a request choose how long it waits for an answer (24 hours, 3 days, 7 days, or a custom number of hours) before it expires unanswered, the same choice for every action.

Questions

Do I need to give an email address to download this?
No. All four files download directly with no form, no account and no newsletter sign-up - the newsletter is a separate, optional opt-in elsewhere on the site, never a condition for this download.
Can I change the thresholds, roles and timings in the sheet?
Yes - it is a plain CSV and Markdown file, not a locked form. Edit every cell to match your organization; the sheet itself does not enforce anything, so changing it has no effect until you also edit the matching workflow in DueReason.
What happens if the approver on a row is away?
For a step that needs exactly one approver, an owner, admin, or another eligible approver can reassign that one open step to someone else. A step that needs two or more approvers at once has no single person's turn to hand off, so it needs a backup person already in the approver group rather than a reassign.
Does filling in the sheet automatically create the workflow?
No. The sheet is a planning document you can use with any tool, including a spreadsheet alone. Installing the matching template (or building your own workflow) in DueReason's Settings is a separate step that actually enforces the order, the approvers and the evidence.

Build this matrix as workflows

Create an account, install the templates that match your rows, and the order, the approvers and the evidence in the sheet become something DueReason actually enforces.

Create your account

Sources

This guide explains the regulation as we read it; it is not legal advice. Check the official text and your national law, which may add obligations.

Start with DueReason

Create a free account, try it live, or talk to us about your workflow.

Get product updates