Answer first: document the vehicle before work, describe the proposed change without claiming an outcome, record which current official guidance applies, and keep design, parts, work and correspondence records in separate linked sections. The map helps a qualified person or authority find evidence; it cannot approve a modification.
Define the proposed change and baseline
Record the registration, VIN or chassis number, make, model, year, body type and existing configuration shown by the documents you hold. Describe what is proposed, which systems or structural areas may be affected, intended use and the date the proposal was written. Include baseline photographs and manufacturer information where available.
Use neutral states: proposed, under review, work started, work recorded, queried or closed. Avoid āapprovedā, ācertifiedā or ācompliantā unless the relevant document and issuing party support that exact statement.
Create an authority and source map
| Question | Possible official source | Record |
|---|---|---|
| Does RSA modification guidance apply? | RSA vehicle-modification page and current forms | URL, access date and advice received |
| Is vehicle classification relevant? | RSA guidance for the vehicle category; Revenue or motor-tax authority where applicable | Question asked and written response |
| Are test documents requested? | RSA/NCTS current instructions | Form/version and submission correspondence |
| Could insurance information change? | The vehicleās regulated insurance provider or broker | Facts disclosed and written response |
The correct route depends on the vehicle and the change. The RSA also publishes specific information for special-purpose vehicles and light commercial vehicles. Listing a source here does not mean it applies to a particular camper.
Build the technical file
Keep the proposal, drawings, measurements, calculations, manufacturer information, component specifications, instructions and risk or engineering records provided by the relevant people. Where the current process calls for a suitably qualified individual or a specific report, retain the personās details, scope, dated document and version. The RSAās current modifications report form is a useful official reference, but only the responsible authority or qualified person can determine its use in a case.
Link each component to the parts provenance log, including markings, source documents and the vehicle information used when selecting it.
Preserve work and inspection evidence
Use dated before, during and after photographs. Record who performed work as stated on the evidence, the method or instruction referenced, parts used, departures from the proposal and the reason recorded. File invoices, reports and correspondence without rewriting them into broader conclusions.
Keep any inspection, measurement or test report with its scope, date, vehicle identity and limitations. A report about one component is not evidence about the whole vehicle. A restoration project record pack can preserve the chronological link between these documents.
Close with a status index, not a verdict
List the current configuration, superseded documents, outstanding questions, documents supplied to each authority or professional, responses received and the next recorded action. Keep changes to registration particulars, testing correspondence and insurance disclosures in separate sections. If there is no written response, mark the point open rather than assuming acceptance.
Checked 25 July 2026 against RSA guidance on vehicle modifications, special-purpose vehicles, light commercial vehicles and the current modifications report form. RSA notes that its web information is general. This document map is not legal or technical advice and does not determine safety, certification, test, tax, registration, insurance or roadworthiness outcomes.