Skip to content

Approvals in email, Slack or a spreadsheet: where they break, what a workflow adds

Where approvals tracked in email, Slack threads or a spreadsheet break down, and what an approval workflow adds without leaving Slack, Teams or email.

Updated · 8 min read

In short

  • Email threads, Slack DMs and a spreadsheet column all work for the first few approvals - the trouble starts with who was actually supposed to approve, whether they approved the exact thing that shipped, and whether anyone can still show that later.
  • A workflow tool does not replace the channel: it still notifies people by email, in Slack or in Teams, and an approver can act from a link in that message - it replaces what happens after someone clicks approve.
  • DueReason shows the exact payload being approved, refuses a request nobody's workflow covers, never lets a requester approve their own request, and keeps an append-only record a person can produce later without reconstructing a thread.
  • None of this is required to run a small, low-stakes approval - a sheet or a Slack message is often still the right tool when there is little to get wrong and nothing to prove afterwards.

Most organizations do not set out to build an approval process in email, Slack and a spreadsheet - it accumulates. A payment needs a second pair of eyes, so someone starts a thread - a purchase request goes through the same thread, which is exactly what the purchase request approval guide replaces with an amount-based path instead of a reply buried in the thread. A deploy needs sign-off, so it becomes a Slack ritual. Someone wants a record of who approved what, so a column gets added to a sheet. A one-off exception - waiving a cap, approving over a limit - usually starts the same way, which is exactly the path the policy-exception workflow guide covers moving into a workflow. Each piece works on its own. The trouble shows up later, in five specific ways, and it shows up the same way whether the thread lives in Gmail, Outlook or Slack.

Who was supposed to approve, and in which order

An email thread or a Slack DM gets forwarded to whoever answers fastest, not necessarily whoever the policy says should decide, and a policy that says "Finance, then management" is not enforced by the tool - it is enforced by whoever remembers to forward it in the right order. A spreadsheet can have an "Approver" column, but nothing stops a row from being marked approved out of order or by the wrong name.

DueReason routes a request through a workflow defined once: steps run in a fixed order, conditions on the payload decide who the step asks, and a request that no workflow covers is refused rather than waved through. Only the currently open step can answer; a person counts once across the whole request, even if they sit in more than one approver group for it.

Approving your own request

Nothing in an email client or a Slack channel stops someone from approving a request they wrote themselves - forwarding it to your own second account, or just replying "approved" to your own message, is not something either tool checks for. A spreadsheet is no different: nothing stops the requester from writing their own name in the Approved column.

DueReason refuses this directly: a person who requested an action can never be the one who approves it, whatever their role or group membership. The check runs on every answer, not just the first one.

"Approved" without the exact amount, payee or version

Approving over email or Slack usually means approving whatever was pasted into the message - a summary, a screenshot, a rounded number - not the record a system will later act on. If the real amount or the attached file changes after that message was sent, nothing in the thread catches it. A spreadsheet cell that says "approved" carries even less: no link to which version of anything was approved.

DueReason shows the approver the exact payload as it will run, and the grant issued on approval is signed and bound to that payload's hash. If the amount, payee or document changes before anything executes, the grant no longer matches and is refused - approval was for one exact thing, not a description of it.

The record can be edited, or just disappears

Anyone can delete an email. Slack lets the author of a message edit or delete it after the fact, which is reasonable for a typo and a problem for an approval record - see Slack's own help article on editing and deleting messages. A spreadsheet cell can be overwritten with no history of what it said before, by anyone with edit access to the sheet.

DueReason keeps an append-only, hash-chained ledger: each event carries the hash of the one before it and the sha256 of every evidence file, and a scheduled check re-verifies the whole chain and raises an alert on any break. Every decided request can produce a record (JSON or CSV, including while still pending) and, once decided, a signed receipt that anyone can verify without a DueReason account.

Nobody notices a request that stalled

A request sitting in an unread email or a Slack thread that scrolled past does not announce that it is stuck - someone has to remember to check. A spreadsheet row waits exactly as long as it takes for someone to look at the sheet again, which for a low-traffic approval can be weeks.

A DueReason request has an expiry chosen when it was filed - 24 hours, 3 days or 7 days, or a custom number of hours - and if nobody answers in that window, it stops waiting and is recorded as expired rather than left open indefinitely with no sign that it needs attention.

Where each option actually stands

ConcernEmail / Slack threadSpreadsheet logDueReason
Who approves, in what orderWhoever replies, in whatever order the thread happens to goAn "Approver" column; nothing enforces itWorkflow steps run in order; only the open step can answer
Approving your own requestNothing stops itNothing stops itRefused: a requester cannot answer their own request
Exact amount, payee or version approvedWhatever was pasted into the messageA cell that says "approved", with no link to a versionThe exact payload shown, and the grant is bound to its hash
Can the record be edited or disappearA message can be edited or deleted after the factA cell can be overwritten with no historyAppend-only, hash-chained ledger, re-verified on a schedule
Noticing a stalled requestSits unread until someone checksWaits until someone reviews the sheetExpires automatically after the chosen window and is recorded as expired

Keep Slack, Teams and email - this is not about leaving them

Adopting a workflow tool does not mean asking anyone to stop using the channels they already check. DueReason notifies approvers by email (per person), in a Slack or Microsoft Teams channel, and with a browser or phone push notification, exactly where they already look for things that need them. By default a chat or push message carries only the request's title, its action and the step or outcome - never the payload, the reason, comments or evidence - so approvers still sign in to see the rest.

An organization can turn on Approve/Decline links inside those notifications (off by default). This does not mean a link alone approves anything: clicking it opens an authenticated confirmation page, which still requires signing in as an eligible approver before anything is recorded. The channel changes; what counts as an answer does not.

A channel can also turn on showing the request's own fields - amounts, payees, links, whatever the action's schema carries - and, once a request is decided, the approver's written reason. This is a separate, per-channel setting, off by default for every channel: even an organization that wants the convenience chooses it one channel at a time, since a Slack or Teams channel usually has more members than the approvers it was set up for.

If you are still working out who should approve what before picking a tool, the approval matrix template is a free, ungated sheet for writing that down first.

When you don't need a tool for this

Not every approval needs any of this. If there are very few approvals, one person always decides, and nobody will ever need to show later that a specific decision happened a specific way, a Slack message or a line in a sheet is a perfectly reasonable way to track it - the cost of a dedicated workflow is not worth paying until getting the order, the exact payload or the record wrong would actually cost something.

Questions

Do we have to stop using Slack or Teams to use DueReason?
No. DueReason posts to the same Slack or Microsoft Teams channels and sends the same emails approvers already watch; what changes is that answering a request opens an authenticated page rather than being a reply anyone could write.
Can we import our existing spreadsheet of past approvals?
Not today - there is no import tool for past spreadsheet or email history. DueReason starts recording from the first request you file going forward; older decisions stay wherever they already are.
Does rejecting a request still need a written reason?
Yes. A rejection always requires a comment, because the requester is owed the reason - the only evidence kind that is ever optional is a plain approval with nothing further required.
Can an approver just reply to the notification email instead of opening the app?
No. The email tells an approver a request is waiting and can carry an approve or decline link if the organization turned that on, but acting on it opens an authenticated confirmation page - replying to the email itself does not record an answer.

See what a real approval record looks like

Create an account, install a template, and file a request the same way your team already approves things today - just with a record you can still produce later.

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