CBM CoachesOFFICE SETUP

ONE-TIME NETLIFY SETUP

Connect your reports.

Complete these steps before giving the app to drivers.

Email is not switched on by uploading the ZIP alone.Netlify must detect the report form and have an email notification configured. No email password needs to be put into this app.

1. Upload the app

Unzip cbm-walkaround-site.zip. Upload the extracted website folder to Netlify Drop, or drag it into the Deploys page of your existing Netlify site. The folder you upload must contain index.html at its top level.

Do not upload the unextracted ZIP or just index.html. Keep the JavaScript, icons and other files together.

2. Enable report handling

Open your site in Netlify. Go to Forms → Enable form detection. If detection is already enabled, leave it enabled.

Upload the same folder again to trigger a new deploy. Then open Forms and confirm active forms called cbm-walkaround and cbm-defect-action are listed. On the app, the “Report sending is not connected” banner should disappear and the “Submit report” button should return an accepted submission receipt. If it stays visible, form processing has not completed.

3. Set the office email

In your Netlify site, go to Forms → Submission notifications → Add notification → Email notification. Choose notifications for all forms, or create one notification for cbm-walkaround and another for cbm-defect-action. Use this address:

reports@cbmcoaches.ie

Leave the notification subject at its default. The report’s subject field and reference are included in the submission. Save the notification. Netlify sends the notification; the driver does not need an email app or email login.

4. Prove it reaches the inbox

Submit a clearly labelled SETUP TEST — NOT AN OPERATIONAL INSPECTION using a test registration. Check all three places: the app receipt, the record in Netlify Forms, and the message in reports@cbmcoaches.ie. Check junk/spam and the Forms spam list if needed. Do not assume a receipt means the email was delivered.

Test a normal report, a defect report, an offline-then-online report and an office follow-up record. Confirm the reference matches the email. Only then give the app link to your drivers.

5. Put the operating process in place

The driver form follows the operator-supplied RSA Bus/PSV sample: items 1–20 before driving, with the original wording and numbering. The two On-the-Road items, 21–22, are shown for reference and completed in a separate road follow-up only after observing normal travel and stopping safely. Other defect details records an additional concern without duplicating a required check.

Have the transport manager approve vehicle-specific checks and train drivers before rollout. A defect entry records what was found, when it was discovered, and any temporary action (or an explicit None). A reported defect stays awaiting assessment; the app does not clear it for road use.

Nominate the person who reviews reports and the suitably qualified person who assesses faults. Use Office records to link the assessment, work, completion date and responsible person to the original defect. Record the reason if no repair is needed. Keep the supporting job sheets and invoices. Do not use an unsafe vehicle pending appropriate inspection and action.

Keep inspection, maintenance and repair records for a minimum of two years from their creation. The office must maintain a backed-up vehicle file, retrievable by registration, containing driver reports, defect follow-up, original maintenance documents and relevant test records. Device history is only a convenience copy. Netlify retention, exports, backup and access must be configured by the office; this ZIP does not enforce a two-year archive.

Tell drivers how to contact the office immediately about a dangerous defect. A submission receipt or email does not confirm that anyone has reviewed the fault. The app is a reporting aid and is not RSA approval or a substitute for the wider vehicle maintenance system.

Day-to-day use

Drivers: Open the link in Safari or Chrome and add it to the home screen. At the start of every shift, before driving, complete every item, describe faults, confirm vehicle status, sign and press Submit report. If offline or not connected, the draft stays open; reconnect and submit it. A local report has not reached the office.

Office: Review faults promptly, monitor pending or spam submissions and export reports from Netlify for your records. Email is a notification channel; retain and manage the underlying inspection records. My reports only shows copies on that device, including up to 20 submitted reports and all unsent reports.

Access: This version has no individual driver accounts or verified electronic signatures. A typed name records the driver declaration. Use nominated staff for the office form and restrict access using suitable hosting controls. The app does not authenticate staff or verify qualifications. Keep devices locked; choose access, record-retention and vehicle-release procedures before use.

Checklist: Approve this checklist for the specific vehicle and operation. The app supports daily reporting and maintenance follow-up; it does not certify legal compliance, cover all operator duties or determine roadworthiness automatically.

Service: Check the Forms allowance and limits in your Netlify account for the number of daily checks. Keep email notifications enabled. No paid add-on or subscription has been ordered as part of this app.

Official references

Netlify form detection and setup
Netlify email notifications
Stored submissions and exports

RSA Bus/PSV sample checklist
RSA/CVRT daily checks and defect reporting
RSA/CVRT record keeping

Guidance checked 20 October 2026.

Back to driver checks →