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.

Once an inspection is marked as complete and submitted, the Euroautos Inspection Form generates a structured, print-ready report suitable for customer handover. The report consolidates all findings from the eight inspection sections into a clear, professional document that can be downloaded as a PDF, printed at the workshop, or shared digitally with the customer — all without requiring a backend connection.

Report contents

Every generated report contains the following elements:
  • Workshop header — workshop name, logo, address, and contact details (configured via environment variables)
  • Vehicle details — registration plate, make, model, year, mileage, VIN, and exterior colour
  • Inspection metadata — date and time of inspection, inspector name, inspection ID
  • Section summaries — for each of the eight sections, a count of OK / Attention / Critical items displayed as a colour-coded summary row
  • Detailed findings — each checklist item that was marked Attention or Critical is listed with its status, the inspector’s notes, and any attached photos
  • Photos of critical items — full-width embedded images for every item marked Critical, with captions
  • Overall recommendation — Pass, Advisory, or Fail, displayed prominently with a colour badge
  • Inspector notes to customer — the free-text summary message written in the Final Checklist section
  • Inspector signature — the digital signature captured on-screen, rendered as an image
  • Customer signature — included if captured during the inspection

Generating a report

1

Open the completed inspection

From the Dashboard, locate the inspection in the list. Completed inspections show a green status badge. Tap or click the inspection row to open the detail view.
2

Click Generar Informe

In the top-right action area of the inspection detail screen, click the Generar Informe button. The app assembles the report data and renders a preview — this typically takes one to three seconds depending on the number of photos.
3

Preview the report

A modal opens displaying a paginated preview of the full report. Scroll through all pages to verify the content before exporting. If you spot an error, close the modal, edit the inspection, and regenerate.
4

Export or share the report

At the bottom of the preview modal, choose one of the available export actions:
  • Descargar PDF — saves the report as a PDF file to the device’s default download location.
  • Compartir — opens the native device share sheet (on supported browsers) to send via email, WhatsApp, or any other installed sharing app.
  • Imprimir — opens the browser’s print dialogue with the report pre-loaded.
Report generation runs entirely in the browser using client-side PDF rendering. No inspection data is sent to an external server during this process. The report will generate correctly even when the device is offline.

Report formats

FormatDescriptionConnection required
PDF (A4, print-ready)Fully formatted A4 document with workshop branding, all findings, photos, and signatures. Suitable for printing and archiving.No — generated locally
Digital summary linkA shareable URL that opens a web view of the report. Allows interactive browsing of findings and full-resolution photos.Yes — requires backend
Print viewBrowser-native print layout derived from the PDF preview. Use if the customer is present and a printer is connected.No — generated locally
For customer handover, the PDF download combined with a WhatsApp share covers the majority of use cases in workshop environments. The digital summary link is intended for workshops with a connected backend that want to provide a richer, interactive report experience.

Customising report branding

The PDF report header is populated from environment variables set in the project’s .env file. Configure these before building or deploying the app for your workshop:
# .env
VITE_WORKSHOP_NAME="Euroautos Madrid"
VITE_WORKSHOP_LOGO_URL="https://your-cdn.example.com/logo/euroautos-logo.png"
VITE_WORKSHOP_ADDRESS="Calle de Ejemplo 42, 28001 Madrid"
VITE_WORKSHOP_PHONE="+34 91 000 0000"
VITE_WORKSHOP_EMAIL="taller@euroautos.es"
  • VITE_WORKSHOP_NAME — displayed as the main heading in the report header.
  • VITE_WORKSHOP_LOGO_URL — must be a publicly accessible URL or a base64-encoded data URL. The logo is rendered at a maximum height of 60 px in the header. PNG or SVG formats are recommended.
  • VITE_WORKSHOP_ADDRESS, VITE_WORKSHOP_PHONE, VITE_WORKSHOP_EMAIL — displayed in smaller text beneath the logo and name.
If VITE_WORKSHOP_LOGO_URL is not set, the header will display the workshop name as text only. The report is still fully functional without a logo.

Sharing reports

Reports can be shared with the customer immediately after generation using the following methods:
  • Email — tapping Compartir and selecting the device mail client attaches the PDF automatically. The subject line is pre-filled with the vehicle registration plate and inspection date.
  • WhatsApp — on mobile devices, the native share sheet includes WhatsApp if it is installed. The PDF is shared as a file attachment. This is the most commonly used sharing method in workshop environments.
  • Direct download — the customer can receive the PDF file via USB, AirDrop, or any other file transfer method after it is saved to the device.
  • Digital link (backend required) — if a backend is connected and the inspection has been synced, a unique shareable URL is displayed in the share modal. The customer can open the link on any device without needing the app.

Report language

Reports are generated in Spanish by default, matching the primary language of the inspection form UI. All section headings, status labels, recommendation text, and footer notes appear in Spanish.
Internationalisation (i18n) support for additional report languages — including English and Portuguese — is planned for a future release. When i18n is implemented, the report language will follow the language selected in the app settings.

Build docs developers (and LLMs) love