Preparing a Vehicle Special Order for a self-driving pilot

The order answers a specific non-compliance problem

A company wants to run a passenger shuttle without a safety driver on a public road. The vehicle is designed to travel without a person in the driving seat. The team has evidence that its automated system can complete the route. That does not mean the vehicle can simply be used under ordinary construction and use rules. The applicant must identify every rule the vehicle cannot meet and seek a lawful exemption where one is available, while showing how safety will be maintained. A Vehicle Special Order is one possible legal instrument for that task.

The Road Traffic Act 1988 section 44 gives the Secretary of State power to authorise use on roads of certain special vehicles, subject to restrictions and conditions. The current DfT pilot applicant guidance describes how a Vehicle Special Order, or VSO, fits into the Great Britain self-driving pilot without a safety driver. The Vehicle Certification Agency assesses and issues an order on behalf of the Secretary of State after a successful application. The order identifies vehicles and grants only the relevant exemptions, with tailored conditions. It is not a general certificate that the company may run any self-driving service anywhere.

This page owns the exemption and order application problem. The pilot overview explains the broader applicant route. Listing under the Automated and Electric Vehicles Act 2018 is a different decision, even if the assessments run together. An APS permit concerns a passenger service, not the vehicle's construction exemption. Full authorisation under the Automated Vehicles Act 2024 is a future framework and should not be substituted for today's pilot order.

First identify the rules the vehicle cannot meet

The pilot guidance expects applicants to set out the case for a VSO where the vehicle cannot comply with certain legal requirements and to identify the exemption sought. It gives regulation 107 of the Road Vehicles Construction and Use Regulations 1986, concerning unattended vehicles, as an expected issue for pilot designs. That example is not an invitation to ask for a blanket waiver. The applicant should create a rule-by-rule schedule: the provision, the vehicle feature or operating model that conflicts with it, why compliance cannot be achieved, the safety consequence, the alternative control and the evidence that the control works.

Review the actual vehicle rather than starting from a stock exemption list. A conventional vehicle with an unusual automated function may present different issues from a purpose-built shuttle without ordinary driving controls. Registration, approval, construction, equipment and service law may each require separate analysis. The DfT code for vehicle authorisations and exemptions in complex trials says an applicant should make a reasoned case for the requirements it cannot meet. The same principle is useful for a pilot, while the pilot applicant guidance remains the primary route document.

The question is not simply whether an exemption is convenient. A VSO can carry restrictions that are essential to the safety case. A vehicle might be allowed only in a defined area, at certain speeds or under particular operating arrangements. A successful order can therefore impose duties that must be reflected in dispatch, maintenance, remote support and change control. The exact conditions are in the issued order. Do not assume an example from another applicant's project applies to yours.

Separate approval, registration, VSO and listing

The pilot guidance identifies vehicle approval and registration alongside the VSO and vehicle listing. Vehicle approval may involve type approval or individual vehicle approval, with a different route for certain prototypes under restrictions. Registration details may need updating when a vehicle is listed as self-driving. None of these steps should be treated as a synonym for the other. A team can be advanced in technical assessment and still lack a permission needed for road use. A registration record also does not prove that the planned automated function is allowed under an order.

Listing under section 1 of the Automated and Electric Vehicles Act 2018 addresses whether, in the Secretary of State's opinion, the vehicle is capable of safely and lawfully driving itself in at least some circumstances. The guidance says a successful VSO application can lead to a recommendation for listing. The listing decision has its own test and should be tracked separately. The pilot overview covers the sequence. A buyer or operator should ask for the issued order, proof of listing, vehicle registration and any approval documentation rather than accept a single phrase such as “pilot approved”.

If the service carries passengers, an APS permit may also be relevant. Its scope, local consent and service conditions require their own assessment. The 2026 APS instrument and DVSA application service should be read alongside the pilot guidance. A VSO cannot disapply passenger licensing merely because the vehicle is automated. Nor can an APS permit repair a vehicle's unresolved construction or equipment issue. Separate records make these boundaries visible.

Begin with pre-application engagement

The pilot guidance expects significant early engagement with the Vehicle Certification Agency, Driver and Vehicle Standards Agency and Centre for Connected and Autonomous Vehicles. Applicants are asked to describe the vehicle and automated system, supporting organisations, proposed deployment, commercial plans and stakeholder engagement. This is a chance to identify the real exemption and evidence questions before a formal pack is assembled. It is not a grant and should not be marketed as approval.

Prepare a concise concept note for those conversations. State the applicant entity, vehicle identification and design, automated feature, operating domain, area, intended start and service model. List the legal provisions that appear problematic, the proposed mitigations and the evidence already available. Identify suppliers who control the software, maintenance or remote functions. Record authority feedback, action owners and which source or assumption changed. If the proposal evolves, version the concept note so later reviewers can tell what was discussed.

Early engagement should also test whether the organisation has chosen the right route. The June 2026 trialling code addresses supervised trials with a driver ready to take over. The no-driver pilot guidance expressly excludes deployments that require a safety driver during automated operation. A team should not use a VSO application merely to relabel a conventional supervised trial, or use the supervised code when its driverless plan needs pilot assessment.

Build the application around each requested exemption

The guidance lists information an applicant should provide: organisations and contacts, the purpose and dates of deployment, vehicles and modifications, the automated system and its operating domain, supporting operations, personnel and physical security, remote functions, incident response, maintenance, and details of every exemption sought. A complete pack should show how these pieces support each other. A technical safety case about the driving system is not enough if the operator cannot explain how the vehicle will be maintained or what happens when it stops in traffic.

For each exemption, describe the ordinary rule and why the vehicle cannot comply. Explain the risk that the rule normally addresses. Then show the alternate measure, test evidence and monitoring that would maintain an appropriate level of safety. If the vehicle has no conventional driver, a claim that the automated system will “handle it” needs much more detail about remote support, fallback, passengers, emergency responders and conditions of use. A competent road-law and engineering team should review that connection. The applicant should not invent a legal equivalence test from a blog template.

Cross-reference the evidence by vehicle and software version. The authority needs to know which hardware and automated-driving system it is assessing. An updated perception model, steering controller or sensor arrangement may change the answer. Put the operating-domain map, test reports, maintenance plan and incident procedures under version control. If a supplier owns a critical component, the applicant must have a way to obtain necessary evidence and implement a condition in live operations. A contract name in a table does not prove the control works.

Make the operating limits operational

The application should state where the vehicle may run, under what weather, speed and traffic conditions, and how those limits will be monitored. An order condition is useful only if the operator can implement it. Show who checks the route before deployment, who can stop a trip when roadworks appear, what the automated system detects and what remote staff may do. The organisation should not promise a limit that its dispatch system or people cannot observe. A technical specialist must confirm that the proposed fallback and support arrangements are safe for the actual vehicle.

The guidance indicates that assessment can include automated-system capability, behavioural competencies, modelling and simulation, and an on-site pre-deployment assessment. It also says VCA may request further information and may accept alternative means of showing compliance in appropriate cases. Those are assessment routes, not a checklist that guarantees success. Submission begins a review; the Secretary of State retains discretion and each application is assessed on its merits.

Read the issued order as an operating control

If granted, the VSO identifies the vehicle by vehicle identification or registration details and sets the recognised non-compliances, exemptions, restrictions and conditions. Create a controlled copy and extract each operational condition into a register with an owner, evidence and review trigger. The extraction must be checked against the actual legal text. A dashboard summary should never replace the order itself. The order may be narrower than the business plan originally proposed, so the launch team must reconcile the two before a public journey.

Do not infer that a VSO makes a vehicle generally roadworthy. The operator must maintain the vehicle in a condition fit for lawful use and meet the order's terms. The pilot guidance says conditions may address notification of hardware or software modifications. It describes notifiable modifications as case-specific, with the VCA considering their safety and security impact. Set up a change process that asks whether a new build affects the order, listing or other permission before installing it. A patch labelled “minor” by a supplier may still affect the automated system's behaviour.

Keep the order connected to each vehicle. A fleet might have several builds, serial numbers and update states. The team should not assign a new vehicle to a route just because another vehicle in the project has a VSO. Check the actual identifiers and conditions. If a vehicle is sold, rebuilt or taken out of service, review the permission and record the decision. The same discipline applies when a vehicle moves to another operating area or service model.

A change example before a vehicle is released

Suppose the pilot applicant replaces a camera and installs new automated-driving software after a VSO has been granted. The new camera improves night performance, but the evidence used for the original order was collected on an earlier build. The engineering team should identify which safety and exemption claims are affected. The legal or regulatory owner should check the actual order for notification and approval conditions. Operations should keep the vehicle outside the changed automated use until the necessary testing, VCA contact and internal approval are complete. A positive internal test does not amend the order by itself.

The same reasoning applies to a new route. A VSO may define an operating area and restrictions. An APS permit for passengers may have a separate geography and consent route. Moving a shuttle to a neighbouring area can therefore affect more than one permission. Assign each instrument a holder and source, then record which authority has to decide what. A supplier may handle engineering evidence while the permit holder handles service variation, but the project needs one reconciled launch decision.

This is why an application file should include future change control, not just evidence for day one. A condition that cannot be monitored after grant creates a continuing compliance risk. Ask the applicant to demonstrate how it will find relevant modifications, evaluate their effect and preserve both the old and new configuration. A review process must remain workable when the person who wrote the original application leaves the project.

Avoid five common misunderstandings

“Every automated trial needs a VSO.” The DfT supervised trialling code says ordinary trials under existing law do not need a general AV trial permit. A particular vehicle may require an exemption, and the no-driver pilot has its own applicant route. Identify the actual non-compliance before making a blanket statement.

“The VSO is the self-driving listing.” The order can authorise use despite specified construction or equipment non-compliance. Listing under the 2018 Act is a distinct assessment of the vehicle's ability to drive itself safely and lawfully in some circumstances. The two decisions may be linked, but they are not the same document.

“The VSO is the passenger permit.” A passenger service may need an APS permit and local consent. The order concerns the vehicle. The service's bookings, accessibility, support and geographic conditions need separate attention.

“Any software update is covered.” The guidance describes case-specific modification notifications and order conditions. Review the actual VSO before changing hardware or software. A generic exemption is not a permanent approval of all future versions.

“Applying means launch can begin.” VCA assessment, listing, vehicle approval, registration and any passenger service permission must be resolved. A draft application or pre-engagement note is not authority to operate a no-driver service.

A useful evidence and permission register

This is a project register, not a VCA form. Its purpose is to stop one positive decision being mistaken for all others. Keep the issued legal documents and current government guidance as the source of truth.

Where Complys may fit

Complys could be assessed for controlled documents, condition owners, vehicle records and review dates if its current product demonstrates those functions. The noindex AV workspace preview is not proof of a released VSO module. This page does not claim that Complys prepares a technical VCA application, checks legal exemptions, grants orders, submits to VCA or monitors an automated vehicle. Product-owner demonstration and sign-off are required before publication of any specific feature promise.

In a demonstration, give the product team a sample VSO condition, two vehicle identifiers and a proposed software change. Ask how they would link the condition to the affected build, assign the VCA notification review, prevent a pending change from appearing approved and retrieve the earlier order for an incident investigation. If engineering records remain in another system, state that boundary. The AV software overview gives a broader buying script. The AV checker is only a nonbinding regime pointer.

The practical next step is a rule-by-rule exemption schedule and early engagement with VCA, DVSA and CCAV. A competent legal and engineering team should decide what the actual vehicle needs and whether the proposed operating model belongs in the current pilot route. No web article can determine an applicant's eligibility or guarantee an order.