Fleet citations
Paperwork → people → payment
Different citation formats. One question before payment: who had the vehicle?
- CITATION ANOTICE BTICKET C
- Vehicle V-042Date 12 May · 10:30
- 09:00 ━━ 10:30 ━━ 17:00V-042 → Alex (sample)
- Human review↓ approval requiredPayment handoff
Uncertain reading or assignment? Route to a person—not straight to payment.
Explore each step to see how the process connects.
Where the value comes fromConnect the paperwork to the responsible person and approval decision, with less repeated handling.
Read the full story
The challenge
A vehicle record alone wasn’t enough. The citation needed to be connected to the person assigned to that vehicle at the relevant time, then routed through notifications, approvals, and payment processing.
What the Engine Built
A workflow combining OCR, vehicle lookup, assignment cross-referencing, notifications, payment-system integration, and an approval gateway. The value was in connecting the whole process—not just reading a piece of paper.
The value provided by the solution
Less repeated handling between paper intake, vehicle records, and payment processing. A clearer connection between the citation, the responsible person, and the approval decision.
What the Engine could add next
Roll citation costs into per-driver and per-route reporting, so repeat patterns show up before they become a budget line. Flag vehicles or routes generating citations at an unusual rate, and extend the same approval gateway to related fleet expenses like toll violations or impound fees.
The broader pattern: connect incoming paperwork to the records, people, and decisions needed to act on it.
See how this conversation actually wentAn invented but realistic transcript—not a real client exchange, but the kind of back-and-forth that shapes a build like this.
We manage a fleet of about 40 vehicles, and we get 200+ parking and toll citations a month—different formats depending on which city or agency issued them. Right now someone manually reads each one, figures out which vehicle it's for, figures out who had it that day, and routes it for payment. It eats a ton of time and stuff falls through the cracks.
A few questions before I scope it: how are citations coming in today—mail, email, a portal? And how do you currently track which driver had which vehicle on a given day?
Mostly mail, some email PDFs. Vehicle assignments live in a shared spreadsheet—drivers check vehicles in and out.
Got it. And when a citation comes in but the assignment record is unclear—say two drivers overlap, or the log wasn't filled in—what happens today?
Honestly, it usually just sits until someone has time to dig into it, or it gets pinned on whoever's currently driving that truck, which isn't always fair.
Here's what I'd build: read each citation regardless of format, extract the vehicle and date/time, cross-reference your assignment records to find who had it, and route it for approval before anything reaches payment. Where the reading is uncertain or the assignment is ambiguous, it goes to a person—not straight to payment.
Who approves the payment?
That's one thing I need from you—who actually has authority to approve a citation payment, and does that change by amount? I'll build the approval gate around how it really works, not assume one approver.
Ops manager for anything under $200, me above that.
I'll build the gate at that threshold. I'll pull a few months of your real citations and assignment records so I can test extraction and matching against your actual formats before anything touches a live payment.
Continued
One more thing on the approval side—who exactly is "the ops manager" here? I'd rather route this to a small distribution list than one person's inbox, so nothing stalls if they're out sick or on vacation.
Good point. It's usually Maria, but Dave covers when she's out.
I'll set it up as a shared distribution list—fleet-approvals@yourcompany.com—with Maria and Dave both on it, so either can approve and you're not blocked by one person's inbox. Sound right?
Yeah, that works.
Now, on the intake side—where should these citations actually land? A dedicated inbox I monitor, or an existing one?
Let's set up a dedicated one—citations@ourcompany.com or something. Easier to forward mail there too if something comes in physically.
I'll watch that inbox specifically, so nothing else in a shared mailbox gets touched by mistake. Two things I want to handle carefully there: duplicates, and citations I can't confidently read.
On duplicates—agencies sometimes resend the same notice, or a citation gets forwarded twice by different people. I'll check incoming citations against citation number, vehicle, and date before creating a new record, and if it looks like a repeat, I'll link it to the existing one instead of starting a second approval chain.
Good, because that's happened before—same ticket, two people forward it, and we almost paid it twice.
That's what the duplicate check is for. And if a citation comes in and I can't reliably read it—bad scan, handwriting, a format I haven't seen before—I won't guess. It goes into a "needs a human look" queue with the original attached, and I'll flag it by email rather than silently dropping it or blocking everything else behind it.
That's fine, as long as it doesn't just get lost.
It won't—nothing leaves the queue without either being processed or explicitly reviewed by a person. Since we're talking about visibility—do you want a standing aging report? Something that shows citations sitting in review, how long they've been there, and which ones are getting close to a late-fee deadline?
Oh, actually—that would be really useful. We've eaten late fees before because something sat too long.
I'll build that in as a weekly aging summary. Who should that go to?
Same distribution list, plus me on Fridays.
Got it. Last piece—how do you want these actually paid once they're approved? Should I post directly to your payment system, or does someone need to review the transaction first?
Create the entry in QuickBooks, but don't pay it automatically—I want a person to actually look at it before money moves.
Understood—I'll create the bill in QuickBooks on approval, flagged for payment, but the actual payment step stays a manual action on your end. Nothing pays itself.
Perfect.
Before I build against your real data—can you forward one sample citation, whatever format is easiest, to citations@ourcompany.com so I can see exactly what I'm working with?
OK, sent.
Waiting…
Got it—that came through as a PDF from the city's Parking Authority. I can read the citation number, vehicle plate, and violation date and time clearly. The issuing agency's letterhead is in the top corner too—I'll use that to help identify the format going forward. One thing I want to flag: the fine amount on this one is handwritten in a stamped box, not printed—that's the kind of thing I'd rather send to a person to confirm than guess on. Does that match how these usually look?
Yeah, that's pretty typical actually—the amount is often stamped by hand.
Then I'll treat a handwritten or stamped fine amount as an automatic "needs review" trigger, even if everything else on the citation reads cleanly. Better to have a person confirm a dollar figure than have me guess at one.