Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/juanmatz/inspection-form-euroautos/llms.txt

Use this file to discover all available pages before exploring further.

The Euroautos Inspection Form is divided into logical sections that mirror the sequence a trained mechanic follows when physically walking around and examining a vehicle. This structure ensures the inspection is comprehensive, consistent between different inspectors, and easy to audit — every finding is tied to a named section, a specific checklist item, and the inspector who assessed it.

Top-level sections

Each section groups related checklist items and can be completed independently, allowing the inspector to work through the vehicle in whatever physical order suits the job — for example, starting with the tyres while the vehicle is on the lift, then moving to the interior.

Vehicle Information

Captures the vehicle’s identity and current condition baseline: registration plate, make, model, year of manufacture, odometer reading, VIN, colour, and any customer-declared pre-existing damage. This section is completed by the service advisor before the inspector begins.

Exterior Condition

Documents the condition of all external panels, glass, lights, and body trim. Inspectors assess paintwork, panel alignment, chips, scratches, dents, and the condition of all exterior lighting — headlights, indicators, brake lights, and reversing lights.

Interior Condition

Covers the cabin environment: seat condition and upholstery, dashboard and trim, seatbelts, mirrors, infotainment and controls, carpets, and the condition of the boot or load area. Odours and signs of water ingress are also noted here.

Engine & Mechanical

Assesses the engine bay and drivetrain: fluid levels (oil, coolant, brake fluid, power steering fluid, washer fluid), belts and hoses, battery condition, transmission behaviour, exhaust condition, and visible leaks or corrosion.

Electrical Systems

Checks all electrical functions: central locking, windows, wipers, horn, air conditioning, heating, interior lighting, and any warning lights active on the dashboard. OBDII fault code readings can be attached as a note or photo.

Tyres & Wheels

Records tread depth and condition for all four tyres (and spare if applicable), tyre pressure, sidewall condition, wheel condition (alloy or steel), and wheel nut security. Uneven wear patterns are flagged and photographed.

Brakes

Inspects brake pad thickness, disc condition (scoring, warping), brake fluid level and colour, handbrake operation, and brake line condition. This section has the most branching logic — critical findings prompt additional detail fields.

Final Checklist

A summary section confirming that the vehicle has been fully inspected, all critical findings have been communicated to the service advisor, any recommended work has been noted, and the inspector is satisfied with the completeness of the record before signing off.

Section anatomy

Every section in the inspection form shares a consistent layout so inspectors know exactly where to look for information regardless of which section they are working in. Section header At the top of each section, the form displays the section name, the name of the inspector assigned to that section (on multi-inspector jobs, different sections can be owned by different technicians), and a timestamp recording when the section was last saved. This header is read-only and populated automatically. Checklist items Below the header, each section contains a list of specific inspection points. Every checklist item presents the inspector with three mutually exclusive status options — ok, attention, or critical — rendered as a button group. The inspector must select one of these options for each mandatory item before the section can be marked complete. Notes field Each checklist item has an associated free-text notes field. This field is optional for items marked ok, but becomes a required field for any item marked attention or critical. Notes are plain text, support up to 500 characters, and appear verbatim in the generated PDF report beneath the relevant finding. Photo attachment Every checklist item supports the attachment of photographic evidence via a dedicated upload control. The inspector can capture a new photo using the device camera or select an existing image from the device gallery. Multiple photos can be attached to a single item. Photos are stored as Base64-encoded strings and displayed as thumbnails in the form; they are embedded directly in the PDF report.

Checklist item states

Each checklist item must be assigned one of the following status values before the containing section can be submitted. The status drives both the visual styling within the form and the prominence of the finding in the generated report.
StatusDisplay colourMeaningNotes field requiredPhoto required
okGreenNo issues found. The item is in satisfactory condition and requires no further action.NoNo
attentionAmberA minor issue has been identified. The vehicle can be returned to the customer but the finding should be monitored and addressed at the next service.YesRecommended
criticalRedAn issue requiring immediate action has been found. The vehicle should not be returned to the customer until this finding has been addressed or formally acknowledged.YesRequired (in default configuration)
Checklist items that have not yet been assessed are displayed with a grey background and a null status in the data model. The form tracks completion progress per-section using a progress indicator at the top of each section card, showing how many items remain unassessed. The inspector cannot submit the form while any mandatory item still has a null status.

Validation

The Euroautos Inspection Form enforces two layers of validation to maintain data quality. Mandatory items are defined at the workshop configuration level by an Admin. These items must be assessed (assigned a non-null status) before the section they belong to can be marked complete, and the form submission button remains disabled until all sections containing mandatory items are complete. Mandatory items are visually indicated with a red asterisk next to their label. Optional items may be left unassessed without blocking form submission. They are typically used for features that are not present on all vehicles inspected at the workshop (for example, a tow bar condition check, or a panoramic sunroof inspection item). When the inspector attempts to submit the form, a pre-submission validation summary lists any remaining mandatory items that have not been assessed, grouped by section, so they can be quickly located and completed.

Branching logic

Some checklist items reveal additional input fields when they are marked critical. This branching logic is designed to capture the specific detail needed for safety-critical findings without cluttering the form for routine checks. For example:
  • Marking Brake Pads as critical expands inline fields for pad thickness (mm) on each axle and a recommended action dropdown (monitor / replace soon / replace immediately).
  • Marking Brake Discs as critical reveals fields for disc scoring depth and disc warping observed (yes/no).
  • Marking Tyres as critical expands fields for tread depth (mm) per wheel position and a replacement urgency selector.
  • Marking Engine Oil Level as critical expands a field for observed level on dipstick and a top-up performed checkbox.
Branching fields are mandatory once their parent item is marked critical — they must be completed before the section can be submitted. Admins can configure which items have branching logic and define the additional fields through the form configuration panel.

Build docs developers (and LLMs) love