2026-10-12 · Fleet Upkeep

How Should Long-Term Corporate Vehicles in Shanghai Be Maintained and Inspected? Logs, Insurance Continuity and Replacement Arrangements

The part of long-term corporate vehicle use that causes trouble is not signing the contract; it is the year that follows. Who arranges the servicing, whether the inspection date is being tracked, whether the insurance renewal left a gap, and how quickly a breakdown is replaced - none of it makes a sound day to day, but any of it lands directly on airport pickups and shuttle runs when it goes wrong. Ten questions and answers set out a system that can actually run: fix responsibility first, covering who arranges servicing, inspection and insurance, who pays and how quickly it must be done; then the operating rules, covering servicing intervals, a validity register and insurance continuity; then the exceptions, covering replacement vehicles, vehicle class and everyday repairs; and finally record keeping, the decision to replace a vehicle, and the four things that make the system hold. General principles and management method only; your own policy and contract terms govern the specifics.

1. Who Is Responsible for Servicing, Inspection and Insurance

Q1: Who is responsible for servicing, inspection and insurance on long-term corporate vehicles?

Three things belong in the contract: who does it, who pays for it, and how quickly it must be done. In practice the provider usually handles routine servicing, daily pre-departure checks, and arranging and tracking annual inspection and insurance, while the user company cooperates as agreed - scheduling time in the workshop, supplying what the inspection needs, and reporting an incident immediately. Disputes usually start with a single contract line saying the provider maintains the vehicles: when major repairs, accident damage or wear parts arise, each side reads maintain differently. A maintenance schedule attached to the contract, listing routine servicing, wear parts, accident repairs, annual inspection and insurance with the responsible party and settlement basis against each, keeps every job tied back to a clause.

Q2: How should the servicing interval be set - by distance or by time?

Whichever comes first: the vehicle goes in when either the recommended mileage or the time interval is reached. Long-term corporate use also needs to be banded by intensity. Low-mileage urban hospitality work can run mainly on time; long intercity runs and commuter shuttles cover far more distance and should run mainly on mileage. For shuttles and commuter routes that operate continuously, servicing has to be scheduled outside peak hours or at weekends so morning and evening runs are not affected, which means building the window into the rostering in advance. The log should record the date, the odometer reading, the work done and the next due point for each service; recording time alone lets high-mileage vehicles run overdue.

2. Tracking Certificates and Keeping Cover Continuous

Q3: How do you track annual inspection and emissions testing without letting them fall overdue?

The core is a single validity register covering every vehicle: registration date, the month annual inspection falls due, the emissions testing cycle and the insurance expiry date, with an alert one or two months ahead so the inspection can be booked into a quieter period. Falling overdue is not only about a penalty - a vehicle past its inspection date creates complications if there is an incident, an internal review or a later registration step, and it disrupts the company's transport plan. Under a long-term arrangement the contract can place arranging inspection with the provider, with the completion record returned to the company, which then checks it against the register rather than assuming someone else is handling it.

Q4: How is insurance kept continuous, with no gap in cover?

Three points. First, the right cover: compulsory motor insurance and commercial cover in place to the agreed level, with policy details matching the vehicles actually in use. Second, continuity of time: the new policy must take effect no later than the expiry of the old one, so renewal starts before the expiry date rather than on it. Third, archiving: policies and endorsements kept with the vehicle or on file so the company can check them at any time. Vehicles added, replaced or returned must be endorsed promptly, otherwise cover drifts away from the fleet actually in use. The incident reporting and claims process, and who to contact on each side, are also worth writing into the contract so it is clear who reports, who follows up and who supplies the documents.

3. Exceptions: Replacement Vehicles and Vehicle Class

Q5: If a vehicle breaks down mid-term, how quickly can a replacement be provided?

It depends on how the fault is graded and on the provider's standby capacity. Three bands work well: anything affecting safety - brakes, steering, tyres, failed lights - is stopped and replaced immediately; faults that affect comfort but not safety, such as air conditioning, audio or seat mechanisms, can be handled by a nearby repair or a swap; anything that does not affect the day's use can wait until the next day. Whether a like-for-like vehicle can be produced the same day depends on the size of the provider's own fleet and its stock of the same model - a more concentrated model pool and a larger owned fleet make it easier. The contract can set a response time, such as arrival or replacement within a given number of hours, together with how force majeure is handled, turning a verbal promise into a clause that can be checked.

Q6: How do you make sure a replacement vehicle does not disrupt a hospitality or conference task?

Two practices. First, like-for-like substitution: state in the contract schedule that a replacement will be no lower in class than the original vehicle, so an important reception or conference is never covered by a vehicle a grade down. Second, advance notice: when a substitution happens, send the model, plate number and driver details to the company contact, and confirm before dispatch where the task is a significant one. It also helps to set different rules by use - vehicles for receiving guests should match the original in class and configuration, while everyday commuter transport only needs to match seating and safety requirements. That protects the experience where it matters without making substitution unworkable.

4. Record Keeping and the Decision to Replace

Q7: What maintenance records should be kept, and what are they actually used for?

Four groups are worth keeping: servicing and repair records, covering date, mileage, work performed and parts replaced; certificates and policies, covering annual inspection, emissions testing and insurance documents with endorsements; daily check records, covering the pre-departure inspection of brakes, tyres, lights, fluids and cleanliness; and exception records, covering when a fault was reported, how it was handled and what the recheck showed. They serve three purposes. They allow the vehicle condition to be verified at handover or return, reducing dispute. They show in an annual review which vehicles generate the most faults, which informs the model mix. And they demonstrate, in any internal or external review, that the fleet really was under control rather than reconstructed after an incident.

Q8: How do you decide when a vehicle should be replaced?

Look at four indicators together: age, cumulative mileage, fault frequency and repair cost per kilometre. The general pattern is that once age and mileage move into the higher range, fault frequency and repair cost rise together and the risk of unplanned downtime increases. A company can set an internal threshold - for example, a vehicle enters the replacement list at a certain age, or after a defined number of faults within a given number of months - and build it into the annual discussion with the provider. Under a long-term arrangement replacement can follow the contract cycle: concentrating replacements at contract renewal is easier in both cost and coordination than swapping individual vehicles mid-term. The right threshold depends on your own usage intensity and budget rather than someone else's standard.

5. The Repair Loop and Making the System Run

Q9: Which everyday issues must be reported for repair immediately?

Anything affecting safety is stopped and reported at once: abnormal braking, heavy or pulling steering, a bulging or incorrectly inflated tyre, failed lights, or a warning on the instrument panel. Other items can be reported the same day: air conditioning that is not cooling or smells, door or seat mechanisms that misbehave, interior noises, and audio or charging points that fail. So that reporting does not depend on memory, give drivers a daily pre-departure card covering five fixed checks - brakes, tyres, lights, fluids and cleanliness - with anything found written down and escalated immediately, forming a loop of find, report, resolve and recheck that stops small faults turning into downtime.

Q10: How do you make this system actually run?

Four things. One register, not several: vehicles, certificates, insurance, maintenance and exceptions held in five registers maintained by a named owner. One contact on each side: a single interface within the company and a single interface at the provider, so information does not go missing between parallel conversations. A fixed rhythm: monthly reconciliation of registers against settlement statements, quarterly review of faults and maintenance data, and an annual assessment of vehicle replacement and provider performance. And the terms in writing: scope of servicing, responsibility for inspection and insurance, substitution rules and response times all set out in the contract schedule. With those four in place, fleet upkeep moves from reacting when something breaks to running on a defined system.