Modelos de inspeção

You write the checklist once for "elevator" and it applies to all the elevators in the installed base. If the checklist belonged to the work order, each visit would start from scratch and nothing would be comparable between one inspection and the next.

The check scripts per equipment type, grouped by area and with a response type: compliant, measurement with range, photo or choice. It is the template reused on all equipment of the same type. — this is the role of the "Inspection templates" screen within the platform.

A regulatory inspection has more than a hundred items. A hundred items in a single scroll on the phone is how the technician loses their place and answers the wrong item. The groups — machine room, car, shaft — are the unit of navigation in the field.

The platform comes with factory checklists for elevators, fire extinguishers, lightning rods and air conditioning, with the standard reference in each item. You can use them as they are or copy and adapt them to your company's way of working.

The list accepts slicing by parameter: ?q=extintor opens already searching for "extintor", and ?fd_tipoAtivo=Elevador filters by asset type using the field key in the screen's dictionary. This mechanism is what makes a link coming from another screen open the list exactly on the set that the source number showed — the slice arrives via the URL and is applied before the first rendering, without you having to redo the filter by hand.

In each checklist item, three columns have direct consequences: the standard reference appears to the technician on the phone next to the item (and backs up the report); the severity defines the weight of the nonconformity that arises when the item fails — it is what orders the pending queue and the deadline; and mandatory locks the completion of the inspection on the phone until it is answered. The range (min/max and unit) applies only to measurement items: it is what fails the item, not the opinion of whoever measures.

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.

A measurement item with no minimum or maximum value silently accepts any number. The warning in the footer points out these items before you save, because afterwards they don't give any error - they just stop catching the defect.

When the template already has recorded answers, the screen locks editing and shows the warning with the "New version" button. The reason: editing a checklist that has already been answered would retroactively change the report signed last month. The new version is born editable and the number in the Version field goes up; old inspections keep pointing to the version they were done with. Always adjust the checklist going forward, never on top of what has already been answered.

In the record's activity panel, each note has "Turn into request". The click creates a ticket with the note's text, who wrote it and the link to this record — nothing is retyped. Use it when the note is a request for action ("someone needs to review this"); the note stays where it was. The button only appears once the record has been saved; a read-only session (demo) doesn't create one.

Not directly, and that is deliberate. Changing the checklist would change the meaning of reports already issued. The screen offers to create a new version - old inspections keep pointing to the version that was actually used, and new ones use the current version.

"What does my technician need to check on each type of equipment?" — when this question comes up, this is the screen that answers it.

This list runs on the platform's standard engine: the export buttons generate Excel, PDF and CSV of the whole set of checklists, not just the page on screen. You can save views with the filters and columns your way (they are per user) and recover deleted templates from the recycle bin by adding ?excluidas=1 to the URL. Column preferences are also yours — changing the order here does not change anyone else's screen.

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?".

"Compliant" is the technician's check mark. "Measurement" asks for a number and fails on its own when it falls outside the range you defined - what fails the item is the range, not the opinion of whoever measured. "Text" and "Choice" record information. "Photo" requires the image as proof.