Laudos

The customer does not buy the visit, they buy the document that proves they are compliant. The report comes out of the answered inspection and carries the technical lead, the validity and the result item by item.

The document is born from ISSUANCE, based on an answered inspection: the "Completed inspections awaiting report" queue, at the top of the list, is the only way to create one. This page exists for what changes afterwards: the ART number and date, the delivery recipients and the internal note.

Each row in the list has the PDF icon at the far right. It opens the report assembled on the spot from the answers of that inspection — it is not a stored file, it is the document generated from the current data. That is why it never becomes outdated, and that is why the rule that a checklist with recorded answers cannot be edited matters so much: it is what freezes the meaning.

Since 09/13/2026 the number and title of each row open the report record, where the ART, the recipients and the note are kept. Before, they reloaded the list itself — the screen used the standard list and had nowhere to take you.

The list of e-mails, separated by commas, that the "Send to customer with PDF" button uses. Filling it in is what avoids the usual path — someone downloading the PDF and forwarding it by hand, with no record that the customer received it and when.

When the equipment type requires a technical lead, issuance is refused without one. Issuing a regulatory report without the qualified professional is not a registration detail - it is a worthless document, and the one answerable for it is your company.

APPROVED, APPROVED WITH RESERVATIONS or FAILED comes from what failed in the inspection: any critical or high non-conformity fails the report, medium or low becomes a reservation, nothing failed is a clean approval. No one chooses the outcome on the screen — if they could choose, the report would become an opinion, and a piece of equipment with a serious defect would come out "approved with remarks" on a rushed day. Only the open issues from that visit count. An old non-conformity, still open on another item, is a debt of the installed base and not a result of this inspection — adding it would fail forever a piece of equipment that has already been repaired.

When you save a view with the Views button, it stores four things: the search text, the applied filters, which columns appear (and in what order) and which column the list is sorted by. Applying the view restores everything at once — including resetting the sort and the page you were on, so the result is exactly what the view describes. Views saved before this version remain valid: whatever they didn't store simply doesn't change when applied.

Nas fichas, sair de um campo já dispara a conferência do que dá para conferir na hora: campo obrigatório deixado em branco e e-mail mal formado. O aviso aparece embaixo do campo e desaparece quando você começa a corrigir. Campo numérico não precisa de aviso: ele simplesmente não aceita letra enquanto você digita. Isso é conforto, não a validação final: ao salvar, o sistema confere tudo de novo do lado do servidor.

And not for lack of a field: changing them here would change the meaning of a document that has already been delivered to the customer and that they keep to show to inspectors. A wrong report is corrected by issuing another one from the inspection — in the same way that an invoice is not erased.

Because it is what makes the contract renew. An expired report halts the customer's operation, and warning in advance is what separates the supplier from the partner. The radar at the top shows what expires in the next 90 days.

Open the record and look at the Timeline on the right: it shows each change as "from one value to another", with the person and the date. When there are many changes, use the two filters at the top of the timeline — one by field, the other by person. The search runs in the database, so old changes show up just the same. You can also ask Tenkai: "who changed contract 482?".