Calculate monthly truck mileage from your calendar and match it to gas receipts
Have Claude Cowork use your calendar to work out a month's mileage for two work trucks, match it against your gas receipts and flag what does not line up for your review.
What the agent did
Source-reported example · as described by Shay, owner of SNL-Tech Services, a single-operator managed IT business in Columbia, Maryland (per the company's About page); author of the post on the company's own site, describing her own business use
Shay, who runs SNL-Tech Services, a single-operator managed IT business in Columbia, Maryland, drives to client sites in two trucks and needs to keep track of where she travelled, which truck she took, how many miles she drove and the related fuel information. She had Claude use her calendar to reconstruct that.
She says it worked but needed more than telling Claude to track her mileage, so she changed her own process: she colour-coded her calendar so client sites are easier to identify, started consistently noting on each calendar entry which truck she took, wrote rules for situations that should be flagged when information does not line up, and set up a dedicated email address so gas receipts arrive in one predictable place the workflow can use.
She says Claude can now review her calendar for the month, use the client-site and truck information she provides, calculate the mileage and help match it against her gas receipts, and that the workflow is designed to flag anything that does not make sense so she can look at it rather than have Claude quietly guess.
She says Claude could not reliably know which truck she drove unless she recorded it, could not consistently understand client visits without calendar structure, and could not match receipts scattered across different places. Mileage exceptions come back to her instead of Claude deciding an inconsistency is correct.
The author says the mileage workflow "saved me a tremendous amount of administrative work". No hours, dollars, miles or accuracy figures are given.
Limitations
One owner describing her own workflow in a post on her company's site that also invites readers to contact her about AI automation and AI governance.
The only reported result is her general statement that it saved a tremendous amount of administrative work; there are no numbers, no sample output and no example of a flagged mismatch, and the post says the workflow is "designed to flag" mismatches rather than showing it do so.
It took changes to her own process (colour-coded calendar, the truck noted on every entry, a dedicated receipts mailbox, flag rules) before it worked reliably; she says it worked at first but that Claude could not reliably know which truck she drove, consistently understand her client visits or match scattered receipts without that structure.
How distances are calculated, how Claude reaches the calendar and mailbox, her exact instructions and flag rules, and how often it runs (beyond her saying that mileage does not need to be recalculated every hour) are not disclosed. The mileage section says "Claude" without saying Cowork (the article names Cowork as her setup).
The post does not say what the log is used for (tax, reimbursement or records). She reviews every flagged exception herself. The article is about a wider system (dashboard, backup and security alerts, QuickBooks invoice preparation and more); this listing covers only the mileage and gas-receipt task.
Try it in your business
What you'll need
Claude Cowork (the author's setup) with access to your calendar and to the email address or folder where gas receipts arrive; a consistent calendar convention (client site, and which vehicle, on every entry); your own rules for what to flag; your own review of every flagged mismatch before the figures are used.
The workflow reads the author's calendar and a mailbox set up to receive her gas receipts. The post does not say how Claude is connected to them, so the label is our reading of what the workflow needs; it also needed her own calendar and receipt conventions.
Starting prompt
The author didn't publish their prompt (read the full post and its About page on 2026-11-11; the post describes the mileage workflow in prose and publishes no prompt or instruction text), so this is our adaptation.
How ours differs from the original setup: Same execution agent (Claude Cowork). The author did not publish her instructions; this is our starting prompt, based on the setup she describes.
It asks Claude to show how each distance was worked out, because the post does not say how she gets distances, and it only reads your calendar and receipts and produces a table and a list for your review.
It leaves out the rest of her system (the morning dashboard, backup and security alerts, invoicing and the other workflows) and her particular calendar colour-coding and mailbox; you would need your own equivalents.
Help me prepare my mileage and fuel log for [month]. Use my calendar for that month: each client visit should show the client site and, in [the title or notes], which vehicle I used ([Truck A or Truck B]). Look at the gas receipts in [the mailbox or folder where they arrive]. For each visit, work out the miles driven from [my starting address] and show how you worked out the distance. Then match each gas receipt to a vehicle and a date. Give me a table with date, client site, vehicle, miles and matched receipt(s). Do not guess. In a separate list, show every entry with no vehicle or an unclear location, every receipt that does not match a trip, and any gap or overlap, and say what is missing. Do not change my calendar, email or files; give me the table and the list to review.
Replace the [bracketed] parts with your own files and tools.
Get examples like this every Tuesday and Friday
Practical ways to put AI agents to work in your business. We check the original sources, explain the setup and point out the limits. Free.
Unsubscribe any time. Privacy policy
Related use cases
Categorize bank transactions, number vouchers, match payments to invoices and draft year-end accounts
Have Claude Cowork do the bookkeeping from a bank statement and spreadsheet, match payments to invoices and draft year-end accounts, as the author describes in a LinkedIn post that he says Claude wrote.
Our suggested starting prompt — not the author's original · untested
You'll need: Claude Cowork with access to your bookkeeping spreadsheet (and a backup copy), your bank statement export and your sales invoices; last year's accounts prepared by your accountant, for the format; a rules file kept alongside the spreadsheet; your own answers to its questions; your accountant's review.
You are helping me with bookkeeping in Cowork. Files: bank statement [file], bookkeeping spreadsheet [file], sales invoices [folder], last year's accounts from my accountant [file]. Step 1: make a backup copy of the spreadsheet before changing anything and tell me where it is. Step 2: read the spreadsheet and describe my categories, how voucher numbers run and which kinds of transaction never get a number; wait for me to confirm. Step 3: fill in only blank rows where the category and voucher number are clear from the history; for anything new or ambiguous, list a question for me instead of guessing, and never overwrite a filled row. Step 4: check your work against the backup: row counts, and gaps or duplicates in the numbering; report what you find. Step 5: match each client payment to a sales invoice and list any invoices still outstanding and any matches you are unsure about. Step 6: save the rules we agreed, and my answers, to [rules file] and show me what was added. Then, only after I have reviewed all this, draft this year's accounts in the same layout as last year's, section by section, from the categorised data, and flag anything that needs my accountant's judgement (for example depreciation, tax and opening balances) instead of filling it in. Do not send anything to my accountant or anyone else.
Screen potential clients against your ideal-client criteria and log the scores in a spreadsheet
Have Claude Cowork screen potential clients against your ideal-client criteria and log each score with a link to its proof in a spreadsheet, the agent the author describes.
Our suggested starting prompt — not the author's original · untested
You'll need: Claude Cowork; your written ideal-client criteria and any disqualifying rules; access to the sites it searches (the post does not say how); a spreadsheet for the results; your own decision on who to contact.
Screen potential clients for [my business]. My ideal client is: [criteria]. Skip any company that [disqualifying rule, for example already has its own IT staff]; check that before you score. Find companies through [job postings, LinkedIn, Upwork or other places I name] that look like [type of company or role]. For each company, read its website and LinkedIn page, then score it from [low] to [high] against my criteria. For every score, record a link to the evidence behind it. If you cannot check something, give the company no score and write down what is missing and why. If two sources disagree, record both with their links; if either source fails my criteria, disqualify the company; if you cannot tell which source is accurate, give the company no score and flag it for my review. Put everything in a spreadsheet called [name]. Do not contact any company or send anything; I decide who to reach out to.
Draft late invoice reminder emails every Monday for your approval
Have Claude Cowork set up a Monday-night agent that drafts late-invoice reminder emails for you to review and send, as the author describes.
Our suggested starting prompt — not the author's original · untested
You'll need: Claude Cowork; access to your list of overdue invoices (the post does not say how); a Google Sheet of customer names and contact names; your own reminder email template; access to your mailbox so drafts can be saved; your own review before anything is sent.
Every Monday evening, open [my receivables or invoice system] and list invoices that are past due. Match each customer against my Google Sheet [name] (customer name, contact name). For each match, draft a late-invoice reminder from my template [paste template], using the contact name and each overdue invoice's number, amount and due date. Save the drafts in my Drafts folder. Do not send any email. Then give me a short report: customers included, amount owed per customer and the total, plus any overdue customer who is not in my Sheet and anything you could not read. Do not change or mark anything in the invoice system; I review and send the drafts myself.

