The dispatcher pings you at 7:14 AM. Truck 27 won't start. The driver — the same one who reported a sluggish start last Wednesday — is sitting at the lot waiting. Your fleet management system shows truck 27's last service was a month ago and the next preventive maintenance is due next week. What it doesn't show: that this is the third no-start incident on this vehicle in six weeks, that the warranty conversation with the dealer is still open from the alternator replacement in February, and that the same driver has flagged two other intermittent electrical issues you've been meaning to investigate.
The fleet system holds the records. The actual operational memory of running a fleet — the running threads with vendors, the per-vehicle issue history, the driver feedback that doesn't fit a structured form — usually lives in a combination of email, the dispatcher's head, and a spreadsheet someone built two years ago.
This post is about the layer that sits next to the fleet system. The notes workspace that holds the parts that don't fit a work-order form.
What fleet management actually needs from a notes system
The shape:
- Per-vehicle continuity — a running biography of each truck, van, or asset, including the issues that keep recurring and the deferred work that's piling up
- Driver context — who reports things accurately, who's tough on equipment, who's been with the same vehicle for three years and knows its quirks
- Vendor and dealer relationships — the body shop, the tire vendor, the warranty contact at the dealer, the third-party telematics provider, the mobile-mechanic option for breakdown calls
- Cross-vehicle pattern recognition — every Sprinter with the same DEF sensor failure, every reefer unit that consistently runs hot in August, every batch of tires from the same lot showing early wear
- Compliance memory — DOT inspections, IFTA filings, IRP renewals, driver qualification files, drug-and-alcohol program records — what was done, what's coming up, what was flagged
- Capital planning — running notes feeding the next vehicle-replacement decision, the trade-in value research, the spec sheets for the next round of orders
Plus: it has to work on a phone in a parking lot. The dispatcher checking in on a roadside breakdown needs the vehicle's full context one tap away. Adjacent shapes — vehicle history at the wrench level, plus the wider buildings/assets pattern — are in AI Notes for Mechanics and Auto Shops and AI Notes for Facilities Management.
A page per vehicle, plus a vendor and driver vault
In Docapybara, every active vehicle gets a markdown page. The title includes the unit number, year, make, model, and VIN — Truck 27 — 2022 Freightliner M2-106, VIN ending 4831. Page nesting holds the structure underneath: spec sheet, service history, open issues, warranty status, accident history.
Separately, drivers and vendors get their own pages. A common shape:
Vehicles → Active Fleet → one page per active vehicleVehicles → Retired → one page per disposed vehicle (still useful for warranty disputes and future spec decisions)Drivers → one page per driver (qualification, history, current vehicle assignment, performance notes)Vendors → by trade — Dealers, Body Shops, Tire, Mobile Mechanics, Glass, Towing — one page per vendorCompliance → by regulatory area — DOT, FMCSA, IFTA, IRP, Drug & AlcoholCapital Plan → running notes by year on what's being replaced and why
Plain markdown means the pages stay searchable, copyable, exportable. If the fleet operation transitions to a new manager or gets folded into a parent organization, the operational memory comes with it as text anyone can read.
A live database for open issues and the maintenance backlog
Embed a :::database::: directive on the fleet's Open Issues page. Six column types — text, number, date, select, checkbox, link — cover the work. A typical issues board:
| Vehicle |
Issue |
Reported By |
Reported |
Vendor |
Status |
Warranty |
| Truck 27 |
No-start (3rd in 6wk) |
Driver Lopez |
2026-04-26 |
Freightliner-Dallas |
Tow scheduled |
In dispute |
| Van 14 |
DEF sensor fault |
Driver Park |
2026-04-22 |
dealer |
Diag scheduled |
Active |
| Trailer 09 |
Reefer running hot |
Driver Cole |
2026-04-19 |
Carrier Transicold |
Repaired pending verify |
Active |
Sort by reported date, you see the backlog. Filter by status, you see what's stuck. Filter by warranty, you see what needs a manufacturer push.
The same shape works for the Maintenance Backlog — one row per deferred work item across the fleet, with severity and estimated cost. When the agent reads it, "what's the deferred maintenance backlog by severity, and what's the rough total exposure?" gives you the answer for the next operations review.
The agent reads across the entire fleet
Capy, the assistant inside the workspace, reads across every vehicle, driver, and vendor when you ask. The kinds of questions a fleet manager actually has to answer fast:
- "Truck 27 won't start again — pull every electrical issue on this vehicle in the last 18 months and the warranty thread with the dealer."
- "Across the Freightliner M2 fleet, how many vehicles have had alternator replacements in the last year?" — cross-vehicle retrieval
- "List every driver whose assigned vehicle has been in for unscheduled service more than four times this quarter."
- "Draft a summary for the safety committee of the top three open accident-related items and the status of each."
The agent reads the relevant pages, drafts the summary, you adjust. The weekly report that took a Tuesday afternoon becomes thirty minutes of reviewing what the workspace already knows. The agent-acts-on-docs idea behind that is laid out in Claude Code for Documents.
Recording driver debriefs and the post-incident conversation
Most driver communication doesn't need recording. Some does. The post-accident debrief where the driver walks through what happened. The annual review with a long-tenured driver who has 200,000 miles of feedback on the equipment. The exit interview when a driver leaves and you want to capture what they learned about the vehicles they drove.
Audio with speaker labels keeps each speaker attributable. Drop the recording on the relevant driver or vehicle page. The transcript drops in alongside. Tomorrow when you're drafting the safety report and you need the driver's exact words on what led to the incident, the answer is searchable text.
The recording question is a workflow choice — what's appropriate to record, what consent looks like, what gets retained, especially around incident investigations where carrier and counsel may have opinions. Once that's settled, the workspace just holds whatever you decide to capture.
Old work orders, warranty docs, and accident reports
Fleet operations accumulate paper by the year. Work orders from outside vendors, warranty repair authorizations, accident reports, dealer service records, the original spec sheet from each vehicle's order, the DOT inspection report, the manufacturer recall notices. They're useful when findable and a problem when not.
Drop the PDFs into the relevant vehicle, vendor, or compliance page. Each one converts to markdown automatically, which means the agent can read across them. When you ask "what did the dealer's service notes say about Truck 27's alternator replacement in February?", the agent pulls the relevant section as text. When the warranty rep argues the current failure is outside coverage, you can pull the original warranty terms and the prior repair authorization in seconds.
For a long-tenured fleet operation, this is often the single highest-leverage afternoon of setup. The history that was locked in dealer paperwork becomes searchable.
The compliance calendar that doesn't get away from you
Compliance is the part of fleet work where forgetting becomes expensive. DOT annual inspection lapsed. IFTA filing missed. Driver qualification file out of date. Drug-and-alcohol random pool not pulled in the right cycle. The dates are scattered across emails from inspectors, certificates in binders, notices from the consortium administrator.
A :::database::: on the Compliance page with columns for entity (vehicle or driver), requirement, last completed, next due, status, owner gives you the running picture. Sort by next due, you see the next 90 days. When the agent reads it, "what compliance items are due in the next 30 days?" returns the list. You assign owners, schedule the work, file the resulting certificates back to the workspace.
The workspace doesn't replace whatever official compliance system the carrier or jurisdiction requires. It does mean the data isn't sitting in three different places when the auditor walks in. The audit-prep version of this is covered in AI Notes for Compliance and Audit Preparation.
The vehicle-replacement decision
Most fleet replacement decisions get made under time pressure with incomplete information. The unit hits a high repair quarter, the dispatcher complains, the manager pulls the spec sheet and the trade-in value, and the order goes in.
The workspace alternative: every vehicle's page accumulates a replacement signals section over time. Currently 240,000 miles. Three major repairs in last 12 months. Trade-in value $32K. Replacement spec roughly $96K. Driver Lopez has flagged that the next-gen platform addresses two of the recurring issues.
When the time comes to make the call, the agent can read across the fleet: "Across the Class 6 box trucks, which units are showing the strongest replacement signals based on repair history, mileage, and the driver feedback notes? Rank them and propose an order of replacement for next year's capital plan."
The agent drafts the recommendation. You verify, get fresh quotes, and walk into the capital conversation with something defensible.
Try Docapybara free
The fastest test: pick the three vehicles that are giving you the most operational pain right now. Open Docapybara, create a page for each, drop in their recent service history and any open issues, and build an Open Issues database from what's currently outstanding. Try Docapybara free, bring one fleet's worth of operational mess and a stack of dealer service records nobody can find, and see whether the workspace can hold the parts of fleet management the system of record leaves on the floor.