A workable vehicle trip sheet format for an event has one row per completed movement and nine columns: movement ID from the plan, vehicle and registration, driver, passenger lead and head count, from and to, four timestamps (on site, picked up, dropped, released), odometer or GPS kilometres, waiting minutes with a reason code, and a completion confirmation. Add a separate one-page incident note for anything that went wrong. With those two records filled in on the day, the post-event reconciliation becomes a matching exercise rather than an argument, because every line on the invoice either points to a row on the sheet or it does not.
What follows is written for whoever holds the event together afterwards: the family member who booked the baraat convoy, or the coordinator explaining to finance why the walima shuttle ran extra loops.
The vehicle trip sheet format, column by column
Finance reconciliation fails when it starts with the bill: the bill is a claim, the trip sheet is the evidence. Keep it as a shared spreadsheet or printed grid filled in at each stop. The columns below are the minimum; drivers skip crowded forms, and if a field is missing for a row, mark it unverified rather than guessing.
| Column | What to write | Why reconciliation needs it |
|---|---|---|
| Movement ID | The reference from the movement plan, e.g. MEHNDI-03 | Links the row to what was ordered, so extras and omissions show up instantly |
| Vehicle and registration | Model, colour, plate number | Confirms the vehicle class charged is the class that turned up |
| Driver | Name and mobile number | Lets you ask the right person about a discrepancy a week later |
| Passengers | Lead passenger name and head count | Separates a no-show from a half-empty run; shows over-capacity requests |
| From / to | Named address or venue, not “hotel” | Events often use several hotels and two venues; ambiguity breeds disputes |
| Timestamps | On site, pickup, drop, released | Waiting and hours are calculated from these, not from the plan |
| Kilometres | Odometer start and end, or GPS trip distance | Checks distance allowances and requested detours |
| Waiting and code | Minutes beyond the agreed grace, plus a reason code | Turns “we waited ages” into a number someone can approve or reject |
| Completion | Signature, named confirmer, or app confirmation time | Evidence that the client side accepted the movement as done |
Four timestamps, not two
Most improvised sheets record “start” and “finish”. That is not enough for an event, because the expensive minutes sit between the vehicle arriving and the passengers getting in, and between the drop and the moment the driver is actually released. Record all four:
- On site — the vehicle is at the agreed pickup point and the driver has told the contact.
- Picked up — the lead passenger is in and the vehicle moves off.
- Dropped — passengers are out at the destination.
- Released — the coordinator tells the driver the job is finished, or hands them the next movement.
The gap between 1 and 2 is waiting at pickup. The gap between 3 and 4 is holding time, common at weddings when a driver is asked to stay “just in case”. Both vanish from the record if nobody writes them down.
Kilometres: record what you can prove
Note the odometer when the vehicle reports on site and again at release, or use GPS trip distance; pick one method per sheet so the rows are comparable. For intercity legs, compare the recorded figure against the published route; the M-2 between Islamabad and Lahore, for example, is listed at 375 km in Wikipedia’s M-2 motorway entry, so a leg claiming, say, 460 km needs an explanation such as a detour to a guest’s village.
Trip sheet or vehicle log book format: which one you need
People searching for a vehicle log book format are often after the same thing, but the two documents do different jobs. A log book follows the vehicle across days and clients; a trip sheet follows the event across vehicles. For an event you want the trip sheet; ask for log book extracts only if one vehicle’s day is disputed.
| Question | Event trip sheet | Vehicle log book |
|---|---|---|
| Organised around | The event’s movement plan | One vehicle over time |
| Kept by | Event coordinator or driver, for the client | Fleet owner or driver, for the operator |
| Typical span | One event, often one to three days | Weeks or months |
| Main use afterwards | Matching movements to the invoice | Maintenance, fuel, the operator’s own accounts |
| Shows waiting and no-shows | Yes, by design | Rarely, unless the operator adds it |
| Who should see it | Client, operator, finance | Mainly the operator |
If you only have the energy for one document, keep the trip sheet. It is the one that belongs to you.
The no show and waiting record
Waiting and no-shows generate more post-event friction than anything else, mostly because each side remembers the evening differently. A dedicated no show and waiting record, even if it is just three extra columns on the trip sheet, removes the memory contest.
Waiting: minutes beyond the grace period, with a reason
Agree the free waiting allowance before the event and write it at the top of the sheet. Then only log minutes beyond it. Pair each entry with a short code so the approver can see at a glance whose delay it was:
- W1 – Client delay: passengers not ready, ceremony running late, photographs outside the venue.
- W2 – Venue or access: gate closed, parking marshal holding vehicles, security check at a hotel porch.
- W3 – Road conditions: closures, diversions, a motorway section shut. Record the source, for instance the National Highways and Motorway Police travel advisory or FM 95 announcement.
- W4 – Operator side: vehicle late, wrong vehicle, driver lost. These should normally not be charged to the client.
The code matters more than the minutes. Forty minutes of W1 is a reasonable charge to discuss; forty minutes of W4 is a service issue to raise.
No-shows: prove the vehicle was there
A no-show is a movement where the vehicle reported on site and nobody travelled. To mark one, the sheet needs the on-site timestamp, the number of call attempts to the passenger lead, the time the coordinator authorised release, and the name of the person who authorised it. A photo of the vehicle at the pickup point with a visible landmark is useful, but only if the family or company is comfortable with drivers taking photos at a residence.
Separate a no-show from a cancellation. If the booking was cancelled before the vehicle was dispatched, it is a cancellation and belongs in a different column; how it is charged depends on the terms you accepted. iDrive’s refund policy sets out how cancellations and refunds are handled for bookings made through the platform, so read it alongside your sheet rather than relying on anyone’s recollection of what was said on the phone.
A transportation incident report template that people will actually fill in
An incident is anything that changes the movement in a way someone might question later: a minor collision, a breakdown, a passenger taken ill, a driver swap, a vehicle refused entry at a venue, a complaint about driving. UK guidance on work-related road safety from the Health and Safety Executive advises employers to implement a reporting system for work-related road incidents and near misses and to investigate the causes. The same habit suits an event: write it down while it is fresh, even if nothing seems serious.
Keep the note to one page. A transportation incident report template for an event needs only these fields:
- Reference: movement ID plus a letter, e.g. BARAAT-02-A.
- Date, time and location: as precise as possible, with the nearest interchange, junction or landmark.
- Vehicle and driver: registration and name.
- Passengers affected: head count and the lead’s name.
- What happened: three or four plain sentences. Facts only, no blame.
- Immediate action taken: replacement vehicle requested, passengers moved, police or motorway police called, first aid.
- Effect on the plan: minutes lost, movements cancelled or merged, vehicles substituted.
- Evidence: photos, reference numbers from police or insurers, message screenshots.
- Reported by and to: names and times.
- Open questions: anything that still needs an answer before the account can close.
Injury, collision or damage go to the operator and, where relevant, police immediately; the note is only the event’s own record.
Matching the sheets to the movement plan
Reconciliation is a comparison between two lists: what was planned and what the sheets say happened. Do it within a day or two of the event, while drivers and coordinators still remember the evening. If you booked through iDrive, the movements you requested sit in your iDrive customer account, which gives you the planned side of the comparison without digging through message threads.
- Freeze the final plan. Use the last agreed version, including changes confirmed on the day. Number every movement if it is not already numbered.
- Give every plan line a status. Use five codes and nothing else: C (completed as planned), CX (completed with a change), NS (no-show), CN (cancelled before dispatch), and ADD (added on the day, not in the plan).
- Check vehicle and driver. Where the sheet shows a different vehicle from the plan, note whether it was an upgrade, a like-for-like swap or a smaller vehicle.
- Recalculate time from timestamps. Work out hours used and waiting from the four timestamps, then compare with the allowance agreed at booking.
- Check distance on long legs. Compare recorded kilometres with the route. Any excess should match a requested detour or an incident note.
- Attach incident notes. Each CX, NS or ADD row should point to an explanation: a message, an incident note, or a named person’s instruction.
- Flag the unverified. Rows with missing timestamps or no confirmation get a U flag. They are not rejected; they simply go into the conversation with the operator as open items.
The result is a short list: most rows marked C, a handful of CX and NS rows with evidence, and possibly a few U flags. That list, not the invoice, is what you discuss first.
Signed or app-confirmed completion
A movement is only as solid as its confirmation. There are three workable methods, and each event should pick one as the default rather than mixing them loosely.
| Method | How it works | Strength | Weak point |
|---|---|---|---|
| Paper signature | Passenger lead or coordinator signs the row at drop-off | Simple, familiar, no battery needed | Nobody wants to sign a clipboard at 1 am outside a marquee |
| Named message confirmation | Driver sends “MEHNDI-03 dropped 22:40” to a group; a named coordinator replies to confirm | Time-stamped automatically, easy to export | Group chats get noisy; confirmations get buried under congratulations |
| App confirmation | The operator’s driver app records arrival and completion times on the job | Consistent timestamps, often with location | Only covers what the app records; waiting reasons still need a note |
For weddings, a dedicated WhatsApp thread with only drivers and one or two family members is usually the most honest compromise. For corporate events, ask in advance how completion is recorded. Either way, the confirmer needs authority to say the job is done; a cousin standing near the car is a witness, not a confirmer.
Handing the record to finance: the event transport completion report
Finance wants one document, not twelve photographed clipboards: what was ordered, delivered, changed and still open. An event transport completion report does that in about two pages.
What goes in the report
- Header: event name, dates, booking references, the name of the person who reconciled it, and the date of reconciliation.
- Summary counts: movements planned, completed as planned, completed with change, no-shows, cancellations before dispatch, additions on the day.
- Time and distance totals: hours used against hours booked, chargeable waiting by code, and total kilometres on any leg with a distance allowance.
- Exceptions table: one line per CX, NS, ADD or U row, with the evidence reference.
- Pass-through costs: tolls, parking and venue entry fees, each with a receipt or a statement line.
- Incident notes: attached in full, referenced by ID.
- Open items: anything the operator has been asked to explain, with the date it was raised.
Tolls and parking need their own proof
On motorways the toll is usually a pass-through cost, so it should be evidenced separately from the driver’s time. The M-2’s interchange toll plazas are paid through the M-Tag system introduced in December 2021, according to the M-2’s route history, which means the proof is often a tag statement line rather than a paper slip. Ask the operator in advance which form the evidence will take. Toll rates change, so check the figures against the motorway tolls and drive times guide and the operator’s statement rather than a number someone remembers from last year.
Finance should not have to interpret waiting codes or chase drivers. By the time the report lands, every exception should already carry a recommendation: accept, query, or reject. How long the sheets are kept is for your accounts team to decide under its own record-keeping obligations.
What is actually included before you start counting extras
Much friction comes from a mismatch between what the client assumed was included and what the booking said: waiting, fuel on a long day, driver meals, overnight allowances. Before the event, read what a car with driver in Pakistan typically includes and what changes the cost, and write the agreed allowances at the top of your trip sheet: free waiting minutes, hours per vehicle, any distance cap, and the latest release time.
For driver days charged by the hour, our sister service Pakistan Taxi publishes a practical hourly duty sheet covering times, changes and cost approval, which pairs well with the event sheet when some vehicles are on hourly duty and others run fixed transfers.
The same thinking applies to driver welfare. The HSE’s journey planning guidance points out that the Highway Code recommends a 15-minute break every two hours and says journey times should allow enough time at pick-up and drop-off, and its guidance for employers on work driving lists fatigue and time pressures among the main hazards. A driver on the mehndi until 2 am should not be on the 7 am airport run; build the break into the plan.
A worked example: three functions, six vehicles, one evening of arguments avoided
This is a hypothetical example to show the method, not a real booking.
A family in Lahore plans transport for a mehndi, a baraat and a walima over three days. The plan has 22 numbered movements across six vehicles: two sedans for elders, two Hiace vans for guest shuttles between two hotels and the venue, one decorated car for the couple, and a spare sedan on standby for the baraat night.
After the walima, the coordinator sits down with the sheets and the plan. The status count comes out like this:
- 18 movements marked C, completed as planned.
- 2 marked CX: a hotel shuttle that ran two extra loops at the walima, confirmed in the coordinator thread by the bride’s uncle, and a pickup that moved from one hotel to another at the family’s request.
- 1 marked NS: an elder’s pickup where the sedan was on site at 19:05, three calls went unanswered, and the coordinator released the car at 19:50 after learning the guest had gone with relatives.
- 1 marked CN: a mehndi shuttle cancelled the afternoon before, by message.
- 1 marked ADD: the standby sedan was used for an unplanned airport drop the morning after the baraat.
Waiting is logged as 55 minutes of W1 at the baraat (photographs at the venue gate ran long) and 20 minutes of W4 when one Hiace arrived late to the second hotel. The coordinator recommends accepting the W1 minutes, querying the W4 minutes, accepting both CX changes, and noting the NS as a genuine no-show with the on-site time and call log attached. There is one U flag: the decorated car’s release time on the walima night is missing because the driver’s phone died.
The invoice check that follows takes minutes: every line either matches an accepted row or sits in a short list of queries.
A trip sheet created after the event is a reconstruction, so set it up while the movement plan is being agreed. If you are planning the movements now, the weddings and events car and driver booking page is where to set out the functions, vehicle mix and timings, and you can start a journey request for individual legs. Any quote, vehicle and timing is confirmed by the team after they review the request; nothing is fixed until you receive that confirmation, which is one more reason to keep your own sheet.
Questions people ask
What is the simplest vehicle trip sheet format for a small event?
One row per movement with the plan reference, vehicle and plate, driver, lead passenger and head count, from and to, the four timestamps, kilometres, waiting minutes with a reason code, and a completion confirmation. Everything else is optional.
How do I record a no-show fairly?
Log the time the vehicle reported on site, the call attempts to the passenger lead, who authorised release and when. Keep it separate from cancellations made before the vehicle was dispatched, because those are treated differently.
Is a WhatsApp message good enough as completion proof?
It can be, if the confirmer is a named person with authority, the message carries the movement ID, and the thread is kept separate from the family or office chat so it can be exported cleanly.
Who should write the incident report?
Whoever saw it first, usually the driver or the coordinator, while it is fresh. The reconciler then attaches it to the relevant row. Collisions, injuries and damage still go to the operator and police immediately; the note does not replace that.
