Capture work drives
Client visits and supply runs become drafts before details fade.
Product
A mileage log built around client visits, job sites, and supply runs.
MileLedger is organized around one yearly habit: capture work drives automatically, review business versus personal versus commute, add purpose and client/job context, then export records that make sense later.
iPhone-first workflow Capture, review, context, and export stay visible in one mileage loop.
Product proof
The app keeps the whole mileage story in view.
Capture, review, classify, and export are separate enough to stay clear, but close enough that tax-time cleanup does not become the product.
Review before tax time
Unfinished trips stay visible while the job is still fresh.
Classify with context
Business, commute, and personal choices stay explicit.
Export cleaner records
Package mileage totals and context for tax-season review.
App surfaces
Four surfaces, one job: keep the log moving.
Trips
Know whether today's driving is being captured.
Shows tracking health, recent work-drive drafts, pending review, and the manual fallback when a drive needs correction.
Review
Turn drafts into records you can stand behind.
Turns captured trip drafts into cleaner records through category, purpose, client, job, and site context.
Reports
Prepare exports before the year becomes a memory test.
Previews monthly, quarterly, and yearly totals with CSV and readable summary exports for the user or their CPA.
Settings
The context layer.
Keeps saved places, vehicle, profession, mileage rate, permissions, and privacy controls understandable.
Operating loop
Linear by design, because users come here to finish records.
-
Capture
Catch work drives before the day turns into guesswork.
Automatic trip drafts are the main path for client visits, job sites, estimates, and supply runs, with manual entry kept as a real fallback.
-
Review
Sort business, personal, and commute while details are fresh.
The review queue keeps unfinished and low-confidence records visible so category, purpose, and context can be fixed before tax season.
-
Add context
Add the client, job, site, or purpose behind the miles.
Service work needs more than a mileage total. MileLedger keeps the reason for the drive close to the record.
-
Export
Export records instead of rebuilding the year from memory.
Monthly, quarterly, and yearly exports keep business miles, review status, and context together for the user or their CPA.
Point of view
What the product protects when driving and tax records meet.
The old way breaks at tax time
A pile of map history, calendar guesses, and partial mileage notes is too fragile for a self-employed worker who drives every week.
A good log is built all year
MileLedger keeps capture, review, purpose, and export in one loop so the record is built while the work is happening.
Trust comes from visible gaps
Tracking health, low-confidence trips, and incomplete records should be visible before export, not discovered after the year is over.
Permissions
Background tracking has to earn trust before it earns permission.
Value before permission
Show why tracking matters before asking for background behavior. The product should earn permission, never ambush for it.
Manual fallback remains real
If a user declines location access, the app still needs a credible manual path so basic use is never held hostage.
Tracking health should stay visible
A calm product still explains whether capture is working, paused, or needs attention. Silent failure erodes trust faster than visible friction.
Download