Document approval system
A document moves along a route set in advance: who approves it, in what order and by when. Every edit stays as a version with its author.
- Buildfrom $2,850
- Timeline4–7 weeks
- Supportfrom $570/mo
Who this suits: Companies where a document is approved by mail and in a chat, the current version sits in somebody's downloads, and who approved it is answered from memory.
What is in the first version
- routes per type
- deadlines per step
- version history
- approval log
The figures above are the package this sits on: CRM or client portal. Anything past its edges the calculator adds before the work starts, not after.
How the path goes
- 01
The document enters a route
The type decides who approves and in what order, in sequence or branching by amount, and the system picks it.
- 02
Every step carries its own deadline
A reminder arrives while the window is open; when it runs out, the step goes to a manager or stand-in.
- 03
A remark produces a version
The author uploads the next version, earlier ones stay, and only the steps the edit touches are approved again.
What decides whether this works or annoys people
A late edit restarts the route
The re-approval rule is set per section and by how material the edit is, before launch rather than on the first argument.
One approver on holiday stops everything
A route built from names lasts until the first sick day, so steps go to a role with a stand-in.
The wrong version gets approved
Only the version held in the system is approved, and a downloaded file carries a mark of its version and status.
What to measure once it is live
- time a document spends in a route
- steps past their deadline
- approval rounds per document
- documents approved outside the system
Why this comes out faster
The shape of this one is known: the states, the edge cases and the things that usually go wrong have been decided before. Nothing here is a template, and the saving is not in your half of the work. It goes into your process, your content and the systems this has to talk to, which is the part nobody can have solved in advance.
A likely stack for this
Picked against the task when we scope it, not decided in advance. This is the shelf it usually comes off.
- InterfaceTypeScriptReactNext.js
- Documents, routes and serverNode.jsPostgreSQLPrismaTemporalS3
- Notifications and operationsTelegram Bot APIn8nRedisDockerGrafana
Price it yourself, right here
Five steps, and you can see the number without leaving a contact. The estimate accounts for the kind of work, what you already have and what it will need inside.
These bills do not come from us
- the qualified electronic signature and its provider
- storage for files and all versions
- mail delivery for notifications
- scan recognition and AI model calls
Asked before the first call
- Does an approval like this hold up legally?
- An internal approval is a company decision, and the log with its versions shows who takes it and when. A qualified electronic signature is separate: we connect your provider, and it signs a specific version.
- Can we change the routes ourselves?
- Steps, roles, deadlines and branching conditions are edited from a settings screen without us. A new document type with its own fields and checks is code and goes through us, priced before the work.
- What if an approver is not our employee?
- An outside participant gets a link to one document and one step, with no account and no access to anything else. Their answer lands in the same log, against a version.