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 a web application designed to digitise the vehicle inspection process at automotive workshops. Instead of relying on paper checklists that can be lost, misread, or inconsistently filled out, the app gives every inspector a structured, section-by-section digital form that captures vehicle data, inspection findings, photographs, and signatures — then produces a polished PDF report that can be handed to the customer or archived. It is built for day-to-day use by the people who perform and oversee inspections at Euroautos workshop locations.

​
Who Should Use This

The Euroautos Inspection Form is intended for workshop staff who create, review, or act on vehicle inspection records. It does not require any technical background to operate.
  • Workshop Inspectors & Mechanics — The primary users of the form. Inspectors open a new inspection for each vehicle, work through every checklist section, flag items that need attention, and attach photos as evidence before signing off on their findings.
  • Service Advisors — Service advisors use completed inspection reports to communicate findings to customers, quote repair work, and prioritise jobs on the workshop floor.
  • Workshop Managers — Managers review completed inspections to track inspection quality, monitor recurring issues across vehicles, and maintain a searchable archive of all past reports.

​
How It Works

A typical inspection follows a straightforward, linear flow inside the application:
  1. Open a new inspection — The inspector taps or clicks Nueva Inspección from the dashboard. A new inspection record is created immediately in local storage so work is never lost.
  2. Enter vehicle details — The inspector fills in the vehicle’s registration plate, make, model, year of manufacture, current mileage, and the name of the vehicle’s owner. These details appear in the header of the final PDF report.
  3. Work through each section — The form is divided into logical inspection sections (engine, brakes, tyres, bodywork, interior, lights, and so on). Within each section, every checklist item is rated — for example OK, Requires Attention, or Urgent — and free-text notes can be added to any item.
  4. Attach photos — For any item flagged as requiring attention or urgent, the inspector can attach one or more photographs directly from the device camera or file system. Photos are stored locally alongside the inspection record.
  5. Sign off — Once all sections are complete, the inspector provides a digital signature and confirms the inspection is finalised. At this point the record is locked against accidental edits.
  6. Generate a PDF report — A single click on Generar Informe produces a formatted PDF containing the vehicle details, all section results, embedded photos, and the inspector’s signature. The PDF can be downloaded, printed, or shared directly with the customer.
The entire flow from step 1 to step 6 can be completed without an internet connection. The app stores all data locally and syncs to the backend when connectivity is restored — see Offline Support for details.

​
Key Capabilities

Inspection Sections

Configurable checklists organised into vehicle systems — engine, brakes, tyres, bodywork, interior, electrics, and more. Every item supports pass/attention/urgent ratings and free-text notes.

Photo Capture

Attach photographic evidence to any checklist item directly from your device camera or gallery. Photos are compressed and stored locally, then embedded in the final PDF report.

Report Generation

Produce professional, branded PDF inspection reports at the tap of a button. Reports include vehicle details, all findings, photos, and the inspector’s digital signature.

Offline Support

The application is fully functional without an internet connection once loaded. Inspections are saved to IndexedDB and automatically synchronised to the backend API when the device comes back online.

​
Architecture Overview

The Euroautos Inspection Form is a frontend web application built with modern web technologies. There is no mandatory backend dependency — the app is self-contained enough to run entirely in the browser.
  • Frontend — A single-page application (SPA) served as static assets. All UI rendering, form logic, and report generation happen client-side.
  • Local storage — Inspection records, photos, and application state are persisted in the browser using IndexedDB (with a localStorage fallback). This is what makes offline operation possible; data survives page refreshes and browser restarts.
  • Optional backend sync — When a VITE_API_URL environment variable is configured, the app will synchronise completed inspections to a remote backend over a REST API. This enables cross-device access, centralised reporting, and long-term archiving. Sync is non-blocking — the app continues to function normally if the backend is unreachable.
For workshop deployments that only need a local, single-device workflow, the backend sync layer is entirely optional and can be left unconfigured.

Build docs developers (and LLMs) love

Get started for freeTalk to us