Document control
The procedure in force
is the one somebody signed.
Procedures, manuals, project documents: each carries a structured code, a revision history, and an approval that is a workflow — issued, checked, approved — with a named person on every step. The version people work from is the version that passed, and the versions before it are still there.
Editing a document creates a revision.
Editing a document creates a revision. The one in force is obvious, the ones before it are still there, and what changed between two of them is a question with an answer.
Approval has three roles and a route.
A revision is issued, checked and approved by three named roles, or sent back with a comment that stays attached to it — and only then does it become the one in force. Which means the version people are working from is the version somebody signed off.
A revision waiting for approval, with who has to approve it.
The code says what the document is.
Origin, company, department, type, serial: the code is structured and generated, so a document's identity is readable before it is opened. The format is configured per company, and bulk import brings an existing archive in without renaming a thing.
It is filed where the work is.
A document belongs to the company or to the commessa and activity it serves, and is found from either. A drawing lives with the job it is for, a procedure with the company that follows it.
The documents attached to one commessa, alongside its activities.
Everything it does
- Numbered document revisionsDraft, check, approval: only the latest revision is in force, and its source locks once draft ends.
- Multi-role approvalName who issues, checks and approves: an incomplete step is refused, and comments replace outright rejection.
- Signature at every workflow stepEach step needs the acting person's signature; a file swap after voids it, and the result is a signed PDF.
- Document registerProcedures, manuals and project documents in one register, browsable by origin or customer, viewable in-app.
- Documents tied to the projectA document links to its commessa, activity and customer, and starts pre-filled from where it's created.
- Signatures and acknowledgementsSend a PDF to named people: each signs on the page or confirms reading, with reminders.
- PDF from Office sourcesWord and Excel converted to the PDF that circulates, previewed before confirming.
Questions we actually get asked.
- Do documents have their own numbering?
- Yes, per company, on a template you configure — the same mechanism the other entity codes use, so the format is yours and the sequence is ours.
- Can we comment on a revision?
- Comments belong to the revision, so the discussion that produced a change is attached to the change rather than to a thread.
- Who is notified, and when?
- The step's own person: submission for check notifies the verifier, submission for approval the approver, and a rejection goes back to whoever issued the revision, comment attached. The trigger is a notification like any other in the platform.
- Is this a full document management system?
- It is company documents with codes, revisions and approval. Papers that expire — DURC, certifications, policies — have their own register in the corporate documents module, and fiscal preservation of invoices and receipts runs through the compliant preservation service, from the invoicing modules.
Works with
- Corporate documentsDURC, certifications, policies and filings, each with its expiry and a reminder that arrives before it.
- CredentialsCompany passwords in shared lists, encrypted in a dedicated vault, with every reveal on the security log.
- Car poolThe company fleet with its bookings: who has which vehicle, when it comes back, and never two people on the same van.
Tell us how you work today.
There is nothing to prepare. Half an hour on how your company runs — who tracks the hours, how an invoice comes together, when you find out whether a commessa made money — and we tell you which modules would fix it and what a quote looks like.