The route is defined once, not for every document
Every company has its own rules: an incoming invoice is checked by the person who placed the order, then by the finance department; a request for approval above a certain threshold goes up to management; an internal personnel note passes through HR. These rules already exist, but usually only in the heads of a few people. In 4docs.net you write them once, as routes automatically triggered by the type of document, the department that initiates it, or its value. From then on, the system routes correctly every time, even when the person who "knew how it's done" is on leave or has left the company.
Parallel or sequential approval, according to what reality requires
Not every document needs to go through a chain. Often you want two departments to look at it at the same time, to save days — that's the case with independent checks that don't depend on one another. Other times the order matters: the technical review first, only then the financial one, because the second relies on the first. The platform supports both models and combinations of them, with optional steps and conditional steps. Every approver sees the document, the attachments and the notes left by others, and records their decision directly in the platform, with nothing to download and resend.
Deadlines, reminders and escalation
A route without deadlines quickly turns into the same forgotten email, just with a different interface. That's why every step has its own deadline, and the person in charge gets a reminder before it expires. If the deadline passes, the escalation rule can automatically move the decision up to a superior or notify the initiator. The practical effect isn't punishing whoever is late, but visibility: management sees on a single screen where delays are piling up and can address the cause — an understaffed department, a route that's too long, a step that wasn't actually necessary.
What remains once a document has been approved
At the end of the route, the document doesn't vanish into a folder: it moves into the electronic archive, under the records-schedule category that matches, with its retention period and the entire approval history attached. That means that, two years on, in a review, you can show not just the document but its journey: who initiated it, who approved it, when and with what notes. If the document also needs to be signed with legal effect, signing happens outside 4docs — for contracts and digital signing, see the sister platform 4mycontracts.net.
