File history
A document that tells its own story
Every event lands on the document's timeline the moment it happens. There is nothing to reconstruct from email threads or from what people remember.
- Author and owner of the document at every stage
- Content changes with a diff between versions
- Statuses and transitions between process steps
- Versioning with the binding version clearly marked
- Initials tied to the specific version they apply to
- Signatures together with the identity verification method
Document timeline
Every event recorded at the moment it happened
This is not a report generated for the audit. It is a record that builds itself, next to the document, during normal work - together with events scheduled for the future.
Description: Check whether the payment terms match what was agreed at financial sign-off.
Today
Description: Last moment to decide whether the agreement is renewed for another term.
The same record drives reviews and deadline reminders - an event dated in the future waits on the timeline and watches the deadline for you.
Control
Proof you can put in front of an auditor
Audit trail and logs
A non-repudiable record of system events: sign-ins, permission grants, downloads and deletions.
Metadata and search
Parties, values, deadlines and statuses as fields you can filter on - not just text inside a PDF.
Retention and backup
Storage and deletion rules set once and enforced automatically. Backups held in a separate instance per client.
Reports and analytics
Breakdowns by status, deadline and cycle time. Ready-made summaries instead of counting by hand.
GDPR and eIDAS compliance
Legal bases, consents and accountability built into the process. Signatures compliant with the eIDAS regulation.
Metadata and search
Search by contract data, not by file name
Parties, the CRM number, author, date and tags are fields you can filter by. The view below works - type a phrase or click the tags.
The same fields power reports and audit summaries - there is no separate contract register to maintain in a spreadsheet.
Other solutions
The two remaining pillars
Contract workflow and approvals
Document generation, approval paths and initials, process automation - instead of versions circulating over email.
See the solutionSignature and identity verification
SES, AES and QES built into the process, with an identity check matched to the type of document.
See the solutionDPT
One platform. Three pillars.
Audit is the Proof pillar - but proof only exists when the decision and the signature happen in the same system.
Decision
Create. Negotiate. Automate.
The document is created inside the process, so its history starts at the first draft, not at archiving.
Proof
Track. Audit. Comply.
Author, changes, statuses, versions, initials and signatures - a complete record on the document, ready for an audit.
Trust
Identify. Sign. Verify.
The signature also records the identity verification method and the moment it was applied.