Solution · Operations
Documents that write themselves when the job is done.
Every delivery or completed job comes with paperwork: a DDT when goods leave, a verbale di collaudo and a dichiarazione di conformità when the installer finishes, a rapportino d'intervento after a call-out, a handover pack at the end. Today each one is rebuilt from a template by hand. We generate it from the job or delivery record the moment it's ready, get it signed, send it, and file it where it can be found.
Free, 30 minutes, no obligation.
What gets automated
- Generating the document the moment a job is marked complete in your CRM or job system
- Filling in customer, site, serials, numbering, dates, signatures and branding
- Sending for e-signature where a signature is required, then delivering to the customer
- Archiving the final PDF with a reference back to the job record
The problem
A Word template, a PDF export, an email, and a folder called 'Documenti'.
The technician finishes on site, the office marks the job done, and then somebody opens last month's document, changes the names and dates, hopes the numbering is right, exports it and sends it. It works until a customer asks for a copy, or an auditor asks which version was actually signed.
Today
- 1A job is finished on site and marked complete in the CRM or job system
- 2Someone opens a Word template — or the last document that looked similar — and retypes the details
- 3Numbering, dates and the signature block are filled in by hand and checked by eye
- 4It's exported to PDF, attached to an email and sent to the customer
- 5The file is filed somewhere under a name that made sense that day; the signed copy comes back later, or doesn't
With Reviamo
- 1The document is generated from the job record the moment the job is marked complete — the same template, always the current version
- 2Customer, site, serial numbers, sequence number, dates and branding are filled in from the data; anything the template requires and the record lacks is flagged for a person before anything goes out
- 3It's sent for e-signature where needed, delivered to the customer, and archived with a link back to the job — with a record of when it went and to whom
The document doesn't change. What changes is that nobody has to assemble it, chase it, or search for it afterwards.
How it works
Generate, sign, deliver, archive — with one flag for a person to clear.
-
1
Trigger
We watch the system where a job is closed — the CRM, the job or field-service tool, a status column in a spreadsheet. The status change to complete is the trigger; nobody has to remember to start anything.
-
2
Assemble
Your existing templates are turned into proper document templates once, with the fields marked. Each document — DDT, verbale di collaudo, dichiarazione di conformità, rapportino, handover pack — is filled from the job record, the customer record and the parts or serials attached to the job.
-
3
Check
Before anything is produced, the required fields are checked. A missing serial number, a customer with no delivery address, a certificate whose reference number would repeat — each one stops the document and goes to a person with the reason spelled out.
-
4
Sign and send
Documents that need a signature go to DocuSign or Yousign, to the customer, the technician or both. Everything else is sent straight to the customer by email, with the covering text written once and reused.
-
5
Archive and link
The final PDF — signed where it was signed — is stored in SharePoint, Google Drive or Dropbox under a consistent name, and the job record gets a link to it. The next person to open the job sees the document; nobody has to search for it.
Illustrative run. The verbale goes out the moment the job is closed; the flagged line is a document whose template needs a field the job record could not fill, and it waits for a person.
Plugs into
Where job data comes from, and where documents go
- CRM & job systems
- HubSpot, Pipedrive, Zoho, Salesforce, Odoo — or the spreadsheet where jobs are tracked today
- E-signature
- DocuSign, Yousign
- Files & documents
- SharePoint, Google Drive, Dropbox, your existing Word and Excel templates
- Mail & messaging
- Microsoft 365, Google Workspace, WhatsApp Business for delivery to the customer
Not on the list? If it exports CSV or has an API, it is almost certainly fine. The one exception is SAP — we don't integrate with it, and we say so up front.
Who it's for
-
Installers and maintenance companies
Every intervention ends in a rapportino, a collaudo or a certificate, and the office is the bottleneck between the technician finishing and the customer receiving it.
-
Manufacturers shipping to order
A DDT and a dichiarazione di conformità for every delivery, numbered in sequence, with the serials on the document matching the serials in the crate.
-
Engineering and technical studios
Handover packs assembled from drawings, test reports and declarations that already exist as files — collected and bound instead of rebuilt.
-
Anyone who has been asked 'which version did we send?'
One template, one number sequence, one archive. The answer becomes a link on the job record instead of a search through mailboxes.
Questions
The questions people ask about document automation.
Do we have to redesign our documents?
No. We take the Word or Excel templates you already use, mark the fields that change from job to job, and keep the layout, wording and branding as they are. If a template has drifted into several versions over the years, we agree on one with you before it goes live — that is usually the only design decision.
What happens when the job record is missing something the document needs?
The document isn't produced. A dichiarazione di conformità without a serial number, a DDT without a delivery address, a collaudo with no technician assigned — each stops and goes to a person with the missing field named. Once the record is completed, the document is generated from the same trigger. Nothing goes to a customer half-filled.
Which documents can it generate?
Invoices are a separate process because they go through SdI. The invoice side of the same idea — supplier invoices read and matched automatically — has its own page. This page covers the documents you produce: DDT, verbale di collaudo, dichiarazione di conformità, rapportino d'intervento and handover packs.
How does the signature work?
Where a signature is required, the document is sent through DocuSign or Yousign to the people who need to sign — the customer, the technician, or both, in the order you specify. The signed copy comes back automatically and replaces the unsigned draft in the archive. Documents that don't need a signature skip this step entirely.
Where do the documents end up, and can we still find them by hand?
In your own storage — SharePoint, Google Drive or Dropbox — under a naming pattern you choose, in folders you can browse as you do now. In addition, the job record in your CRM or job system gets a link to the file, so the usual route is to open the job and click through rather than to search.
How long does it take to set up?
We start with a free consultation, then a paid process audit that ends in a fixed price. A first document template is usually live within a few weeks of the audit, running alongside the manual process until you trust it — the steps are set out on how we work.
Related solutions
The documents you send, and the ones you need to find again.
Sales
B2B orders from email and PDFs
Every document on this page is generated from a record. This is where that record gets created without anyone typing it.
Read moreKnowledge
Your company's internal brain
Producing the paperwork is half the problem. The other half is finding the contract, procedure or certificate two years later.
Read moreAll solutions
See everything we automate
Six of the processes we're asked for most, each compared before and after.
Back to services
Free consultation
Tell us which document you produce most often, and what it's made from.
Tell us which documents follow a job and where they live today, and thirty minutes online is enough to say whether generating them is worth it. No preparation needed.