The problem
Versions in email, decisions in the hallway
As long as a contract travels as an attachment, nobody owns the whole of it. Versions drift apart, approvals get lost in threads, and only the person running the case knows its status.
- The same contract exists in several versions and nobody knows which one applies.
- Approvals happen in emails and conversations - away from the document.
- Nobody but the owner knows what stage the case is at.
- Print, sign, scan - and the document returns to the workflow as a file with no history.
How it works
Document, path and process in one system
Document generation
The contract is built from an approved template, with fields pulled from your systems and public registers. No copying from the previous contract.
Approval paths and initials
Flexible paths with an owner and a deadline at every step. An initial stays attached to the exact version it refers to.
Business process automation
Conditions, branches and reminders instead of manual chasing. The process moves the document to the next step on its own.
Examples
The processes most companies start with
This is what an approval path looks like in the system: every step has an owner, a status and a deadline, and the current task is visible without asking anyone for an update.
From the initial request, through legal review and financial sign-off, to routing for signature.
You define the steps, conditions and deadlines yourselves - no code required. See process modelling in BPMS
Other solutions
The two remaining pillars
DPT
One platform. Three pillars.
Contract workflow is the Decision pillar - but proof and signature travel with it, inside the same process.
Decision
Create. Negotiate. Automate.
A standard route from request to decision, with an owner and a deadline at every step.
Proof
Track. Audit. Comply.
Every approval, initial and version stays with the document - along with its date and author.
Trust
Identify. Sign. Verify.
An approved document goes to signature inside the same process, with no export and no email.