interventiontech

The work is finished, the equipment is in place. It still has to be formally accepted — and that is often where everything is decided. Without a signed acceptance report, the handover is argued over months later: what worked, what was missing, what had been pointed out.

The module produces that document, has it signed, and keeps it.

A report is created from a sales order, a quotation, a customer record, a service job or a project — where the deal was made, or where the site is being tracked. It carries over the customer reference, the date, the title and the lines concerned.

Three kinds of document, because a construction job, a delivery and equipment being made available are not accepted in the same way.

Acceptance rarely happens without reservations. Each one is described, numbered, and followed until it is cleared — with its date, its author and its state.

If the Technical Interventions module is installed, a reservation can directly generate the job that will clear it, and the two records appear in each other's linked objects. The two modules remain fully independent: each works on its own.

The report is produced as a PDF on your letterhead. The customer receives a link, opens it on their phone, and signs with a finger. No registration, no app.

Several signing parties can be declared — client, project manager, contractor — each with their own box. The final PDF is sealed with a SHA-256 fingerprint, making it possible to demonstrate years later that the document presented is the one that was signed.

Manuals, certificates, as-built drawings, attestations: the list of what you handed to the customer appears on the report and forms part of what they sign. The signed service report from the Technical Interventions module can be added automatically.

A report is closed with a note, or abandoned. Either way the reason is recorded: a document that vanishes without explanation leaves a hole in the file, and that hole is exactly what gets looked for on the day of a dispute.

The module has its own cockpit, and it answers one question: what needs attention today?

Four figures at the top — drafts, sent for signature, reports with open reservations, signed this month — and each one opens the list already filtered on it.

Then what is stalling: the files nobody is handling any more, oldest first, with the reason spelled out. *Awaiting signature for 26 days.* *Three reservations still open, deadline missed by 12 days.* The two costly oversights — a signature that never came back, a reservation nobody followed up — sit in the same table, and you can see which is which.

Finally, the last twelve months of activity, and breakdowns by decision, type, customer and site.

The list carries ten columns, including the site, the order and the reservations still open. Eight are sortable, and sorting covers the whole history, not just the page on screen.

The site uses the Dolibarr project when the Projects module is active: it is the site in your ERP's own terms, already tied to your quotations, orders, invoices and time spent. Otherwise a free-text field takes over.

The order can also be searched by the customer's own reference — often the only one they will quote to you on the phone.

A compact one-line filter bar, an adjustable page size, and a CSV export of everything the filter leaves visible: not the page on screen, which would produce a file named after your filter and containing a fiftieth of it.

"Acceptance report" tabs on customer, quotation, sales order and service job records; a "Linked objects" block on each record; a REST API to read and write reports from another tool; configurable module colours; built-in online help; a complete user guide in French and English.

Updating means replacing the folder, with no SQL to run and no module to disable: it adds its own columns and puts its menu back in place the first time one of its screens is opened.