The Shift That Goes Wrong Before the First Call
It happens at 07:58. The outgoing crew signed off four hours ago. The vehicle sat in the bay overnight, and now you're the pilot inheriting whatever state it's in. Cylinder A reads 40% — nobody logged it. The odometer photo from yesterday's handover is blurry and timestamped three hours after the previous crew's last recorded call. You don't know if the fuel was topped off or if someone fudged the reading. You have two minutes before the station supervisor asks for your start confirmation, and you're standing there with nothing verified.
That is the exact failure mode this template was built to prevent.
The Daily Start Report for UnM vehicles isn't an administrative nicety. It's the paper trail that proves due diligence when a patient outcome is questioned, when a vehicle incident investigation starts reconstructing a timeline, or when fleet management asks why CG04NM9086 burned through consumables three shifts faster than projected. Without a consistent start-of-shift log, you're operating on assumption. In emergency medical services, assumption kills.
What Gets Captured at 0600 That Saves You at 1800
The oxygen fields are where most informal systems fall apart. Cylinder A and Cylinder B are tracked as discrete percentage values — not as a combined average, not as a vague "adequate/inadequate" toggle. The split matters because dual-cylinder setups have independent regulators, and a partially depleted B cylinder masked by a full A cylinder has sent crews into calls with less reserve than they realized. Logging both values separately, with a timestamped photo of the gauge face, removes the ambiguity entirely. If Cylinder A reads 72% at start of shift and 31% at end, and the call count reconciles, you have a complete oxygen consumption audit.
The vehicle odometer reading, paired with the odometer photo field, creates an immutable mileage baseline. The photo isn't redundant — it's corroboration. A typed number can be entered retroactively. A geotagged, timestamped photograph cannot. When MH14JL4407 accumulates 800 more kilometers in a billing cycle than its call log justifies, the start-of-shift odometer photos are the first thing fleet operations pulls.
Duty Pilot Name and Duty EMT Name tied to mobile and tab numbers complete the accountability chain. When a call comes in during the handover window and there's a dispute about who was technically on duty, this record answers it definitively. The tab number field in particular addresses a common operational gap — personnel phones change, but the assigned tab stays with the post. Logging both means you can reach whoever is actually holding the vehicle.
What a Month of Clean Data Looks Like
After thirty days of consistent start reports across a fleet of twenty vehicles operating out of locations like RHMS, STEEL PLANT, and CSR posts, the patterns become unavoidable. You'll see which duty time slots — the 10pm-to-8am rotation specifically — consistently produce lower fuel levels at start of shift, suggesting either after-hours consumption that isn't being called-in or a fueling schedule mismatch. You'll see which vehicle numbers generate disproportionate oxygen consumption relative to patient count, which flags either a regulator issue or a crew habit of running supplemental O2 on non-critical transports.
The call count field, cross-referenced against shift duration, gives you average response density per location. Crews posted at high-volume nodes like BARHI TOLL TP or JHUMRI TELAIYA average 40% more calls per shift than those at rural posts — and their consumable depletion rates should reflect that. When they don't, something in the reporting chain is broken.
The vehicle cleaning photo — easy to dismiss as bureaucratic box-ticking — becomes a liability shield the moment a patient or family raises a hygiene complaint. The timestamp on the photo predates the shift. The record exists. The complaint has no traction.