Varying and renewing an APS permit

A permit covers a defined service, not every future plan

An operator receives an automated passenger service permit for a small driverless shuttle. Six months later it wants more vehicles, a new route and longer hours. The vehicle team says the technology works. That does not show that the existing passenger permit covers the changed service. A permit specifies a service, area, vehicles and conditions. Change management has to compare the proposed operation with that legal permission before bookings or dispatch are expanded.

The Automated Vehicles Act 2024 provides the permit framework. The 2026 APS regulations set important rules on validity, renewal, variation, suspension, withdrawal and review. The DfT pilot applicant guidance advises permit holders to notify changes in advance where a variation may be needed and to engage with DVSA if uncertain. The issued permit is the starting point for a particular operator. An internal plan or supplier release note cannot amend it.

This guide owns the permit lifecycle after the initial grant. The APS overview explains who may apply and what a permit does. Local consent has its own mapped owner. Vehicle listing, a Vehicle Special Order, registration and insurance remain separate. A permit variation cannot silently change a vehicle permission, and a vehicle approval cannot silently change the passenger service area.

The regulations apply in the current national scheme to bus-like services in England, Scotland and Wales and to taxi-like or private-hire-like services in England. An unusual service or proposal in a devolved jurisdiction needs a specialist to check the appropriate authority and current implementing route. This page is not a determination of whether a named service qualifies or whether a proposed change is material.

Read the issued permit before classifying a change

Create a controlled summary of the permit's holder, service type, permitted area, vehicle details, conditions, start and expiry dates and any referenced schedule. Keep the signed permit as the source of truth. A summary is useful for operations, but it cannot expand an ambiguous clause. If an applicant proposes a new route, first ask whether that route lies inside the permitted area and whether the permit also restricts particular stops, times or vehicles. If any answer is unclear, raise it with DVSA and a transport lawyer before operating the change.

The DfT guidance treats a change that would have materially affected the original grant decision as one that may require variation. Examples can include a new area, service model, vehicle or supplier arrangement. A change to a booking screen may also matter if it changes accessibility or passenger support. The label minor in a project plan does not settle the regulatory question. Record what the permit says, what the original application represented and how the proposed operation differs.

Use a change assessment with separate tracks. The passenger permit track asks whether the area, vehicle, holder or conditions change. The local track asks whether another consenting authority, traffic authority or emergency service is affected. The vehicle track asks whether listing, a VSO, approval or registration changes. The safety track asks whether evidence and operating controls still support the route. The insurance track asks whether policy cover matches the new use. One track can be clear while another blocks launch.

Give a named person authority to hold the proposed service. Booking and dispatch should not make a new route available while the legal team is still asking whether a variation is needed. A software switch can produce a real-world operation before the paperwork catches up. Test the practical hold in the booking system, not only in a meeting minute. If the service already operated outside scope, the operator needs a separate incident and legal assessment rather than merely filing a retrospective variation request.

Voluntary variation needs a formal decision

Regulation 5 of the 2026 instrument allows the Secretary of State to vary, suspend or withdraw a permit with the permit holder's consent. A holder may therefore seek a variation, but its request does not change the permit by itself. The authority must make the decision through the applicable process. The DfT's local-authority guidance gives adding vehicles as an example of a requested variation. Whether another proposed change needs the same route depends on the actual permit and effect.

Regulation 6 addresses consenting authorities. Where the original grant required local consent under the Act, the Secretary of State cannot make a voluntary variation without the relevant consenting authority's consent under the regulation. The regulation includes a written request and six-week deemed-consent mechanism. This is not a clock that starts when the holder emails a council informally. DVSA or the appropriate national authority manages the formal request. A holder should map the service version and relevant authorities before proposing the variation.

A change can also affect section 87 consultation with traffic and emergency bodies. For example, a route extension may alter road interactions, pickup points and responder access. The local consultation owner explains the bodies' different roles. The variation file should show which local decisions need revisiting and which safety evidence has changed. Do not reuse an old consent letter for a materially different service without checking its scope.

Build the submission around the difference from the existing permit. Include the current condition, proposed wording, reason for change, vehicles and area affected, safety and passenger impact, updated local engagement, accessibility effects, contractor changes and launch date. A concise comparison helps the authority understand what is changing. A large set of unlabelled documents can hide the key issue. Retain the authority's response and the final varied permit before operations switch to the new service.

Plan renewal from the actual expiry date

Regulation 3 sets a maximum permit validity of five years. That is a ceiling, not a promise that every pilot permit lasts five years. Read the issued expiry date. Regulation 4 permits the holder to apply for renewal during the period beginning six months before expiry and ending two months before expiry. An internal reminder should be set early enough to assemble evidence, obtain reviews and file within that window. Waiting until the last week before expiry can leave the application outside the statutory renewal period.

If the holder has applied to renew but the Secretary of State has not determined the application, regulation 4 can keep the existing permit valid after its expiry date, subject to the five-year maximum. The effect depends on a valid application and the statutory conditions. An operator should obtain legal confirmation rather than tell dispatch that all pending renewals extend permission indefinitely. It should also check whether any separate Vehicle Special Order, insurance policy or other permission expires earlier. Renewal of one instrument cannot extend another.

A renewal pack should update the original application rather than simply attach last year's files. Show current service area, vehicles, passenger support, incidents, complaints, accessibility learning, local concerns, safety management, supplier roles, insurance and compliance with existing conditions. Explain changes and unresolved findings. The authority must be able to assess the service it is being asked to permit next, not a historic pilot concept. An operator should demonstrate what it learned during the first permit period.

Keep a renewal timeline with evidence owners and decision gates. One team may hold the permit, another the vehicle order and a third the support contract. Each must provide current evidence. A near-expiry software update or route extension can complicate the application. Decide whether it belongs in the renewal request, a separate variation or a later proposal after specialist advice. Do not assume a renewal application authorises changes that the current permit does not cover.

Understand regulator-initiated action

Regulation 5 also identifies circumstances in which the Secretary of State may vary, suspend or withdraw a permit without the holder's consent. They include permit-condition breaches, serious or repeated traffic infractions, failure to fulfil an undertaking, a material false statement in an application, a material change in circumstances, serious vehicle safety concerns, serious disruption to traffic, unacceptable delay to emergency workers and use of an unroadworthy vehicle. These are statutory grounds for possible action, not an automatic result from every small defect. The facts and decision process matter.

Regulation 7 provides an ordinary procedure with notice and an opportunity for the holder and consenting authority to make representations before a final decision. Regulation 8 allows urgent suspension or temporary variation first when the Secretary of State considers the need too urgent for the ordinary procedure, followed by reasons and consideration of representations. An operator should have an internal response plan for both. It needs to locate the permit, affected vehicles, supporting evidence and contact people quickly. It should not continue a suspended or restricted operation because a review is being considered.

A serious event may also require an immediate operational hold independent of a regulator's action. If several vehicles show the same unsafe behaviour, the operator should not wait for a formal notice before stopping the affected service. Its safety management system should identify who can act, how passengers are informed and what evidence is preserved. The permit holder can then respond coherently to the authority. A regulator notice, an internal safety hold and a technical repair are different records and may have different release criteria.

Read the reason in any official notice closely. An emergency restriction may apply to a specific vehicle, route, time or service. A summary sent to staff should preserve those limits accurately. Do not convert a narrow condition into permission for everything else without legal review. Equally, do not assume a company-wide shutdown is legally required if the instrument clearly identifies a narrower scope. Operations and legal specialists must reconcile the actual notice with the service plan.

Use the internal review route carefully

Regulation 9 creates an internal review mechanism for specified decisions, including refusal to grant or renew, imposition or variation of certain conditions, refusal to vary or remove a condition, suspension or withdrawal and some permit details. A request must be made within the 28-day period defined by the regulation, beginning the day after the decision was sent, and must include written representations. The relevant decision and dates should be checked by a lawyer; a general dissatisfaction with an informal email is not necessarily a reviewable decision.

An internal review request does not automatically authorise operation under a refused or suspended service. Regulation 9 contains a narrow rule about an existing permit remaining valid during review where a new permit has been sought and the stated conditions are met, subject to the maximum validity period. The holder must check whether that rule applies to its facts. A review of one condition cannot be assumed to suspend every other part of the decision. Operations should work from the written legal position and seek urgent advice if service continuity is uncertain.

Preserve the decision notice, date sent, review deadline, grounds, evidence and authorised sign-off. A permit holder should state precisely what decision it asks to be reviewed and why. If a local consenting authority refused consent, that is a different decision from the national authority's review mechanism. The local-consent guide explains the distinction. A company should not rely on the 28-day national review route as a general appeal against every local objection.

A review process is a reason to maintain a clean evidence trail throughout the permit's life. An operator that can show versioned route maps, incident actions, condition monitoring and correspondence can respond to a disputed decision more clearly than one that reconstructs its case after receiving a notice. The register should still label legal advice separately from operational records and protect confidential material.

Test changes against local and vehicle permissions

Suppose the permit holder wants to add three vehicles of the same model. The DfT local-authority guidance gives adding vehicles as a variation example and indicates consenting authorities may be asked again. The holder should check whether each vehicle is within the permit terms and whether its listing, VSO, registration and insurance records match the intended service. Same model does not guarantee same assessed configuration. The permit variation and vehicle technical checks should proceed as distinct workstreams.

Suppose a bus-like service adds a second town. The operator should check whether the new area lies in a franchising scheme, whether another consenting body must be involved and whether traffic or emergency consultation is needed. It should review passenger support, accessibility, recovery distance and depot arrangements. The route may be technically straightforward but legally outside the existing permit. The launch date belongs after the formal decisions, not merely after a successful test drive.

Suppose a support supplier changes but vehicles and routes do not. The DfT pilot guidance says material changes in third-party arrangements may require variation. Ask whether the new contract changes passenger communication, incident response, data access or the authority's basis for grant. If uncertain, engage with DVSA before changing live operations. A procurement signature does not alter a permit condition. A short transition plan should show how current service obligations remain met during the handover.

Build a lifecycle register that can survive staff turnover

The register is an internal control, not a permit. Store the official documents and their dates. The person entering a reminder should not be the only person who can see that an authority changed a condition. Test whether dispatch, passenger support and engineering receive the same current status. An old route map or vehicle list can turn a valid permit into an out-of-scope service in practice.

Where Complys could support a permit holder

A team may wish to track permit documents, conditions, review owners, renewal dates and evidence of authority correspondence. Complys can be assessed for those administrative tasks in a product demonstration. This page does not claim that it files a renewal, varies a permit, obtains local consent, validates vehicle listing or automatically stops a non-compliant service. The product owner must verify any exact feature before publication.

In a demonstration, provide a permit with an expiry date, a proposed new route and a changed support supplier. Ask how the product would distinguish current permission from pending variation, assign each review, preserve the original permit and alert owners before the renewal window closes. If the actual permit application and dispatch controls sit elsewhere, state those handoffs. The AV software overview supports the broader procurement discussion. The AV checker is a nonbinding regime pointer, not a renewal calculator or legal decision tool.

The next step is to read the issued permit, set its renewal timeline and create a change-control decision for every material proposal. A transport lawyer should confirm the statutory route and any local consent, while the operator keeps passengers and vehicles within the current permission until a formal change takes effect. This is how a pilot can grow without letting the operational plan run ahead of its permit.