FieldLog is the simplest way for a trade crew to get clean job photos and notes from the field to the office — offline, without bloat, priced for small teams. That sentence has been the whole brief since day one. Every feature is measured against it.
When they say it never happened, you send this.
Every trade business eventually stands in an argument about a job that's already closed. The warranty callback in March about the August repair. The chargeback that says nobody showed up. The GC who never saw the rough-in before the wall closed. Whoever has the better record usually walks out of it — and the record most crews have is a camera roll on somebody's phone.
Two people have to trust the same document: the technician on a driveway with one thumb free and no signal, and the owner who needs that document to still be true six months later. FieldLog is built for both.
A filed report cannot be edited afterwards — the database refuses it. Photos can only be added in the moment the report is created. A customer's sign-off is written once. Nothing about the record depends on somebody remembering a rule.
A burned-in timestamp survives forwarding, which is exactly why a home address must not. Your own copy may carry the address and coordinates; the copy that leaves never does. The long version.
Basements, plant rooms, rural sites. The app holds everything and sends when it can, and it never shows a green tick over work that hasn't left the phone. A queue may not drain until Monday. We design for that.
The owner pays, but the crew decides whether the app gets used. A price that pays the owner to keep technicians off it kills its own adoption — so within a band, an extra technician is free. Why we rejected per-seat.
No testimonials until real customers agree to be quoted. No outcome statistics we haven't measured. When something isn't ready — the field app is invite-only today — the page says so.
A small company registered in India, serving trade businesses in the United States and Canada in US dollars. Support and sales are one inbox — hello@fieldlog.us — so you get the person who can change the thing, not a ticket number.
We're early. Sign up now and you're one of the first firms on it: direct access to the people building it, and your requests at the top of the list. You'll also find the odd rough edge before anyone else does. We'd rather say that here than have you find out.
Infrastructure, named because "our hosting provider" is not something you can check: identity by Clerk, database by Supabase, photo storage on Cloudflare R2, billing by Stripe, hosting by Vercel. Full list in the privacy policy.
A visit is a time, a place and optionally a person. No recurrence, no route optimisation, no capacity planning, no customer booking, no reminders.
Arrival as evidence, yes. Arrival plus departure is a running clock, and a running clock is payroll.
Quotes and invoices are documents on the job. No ledger, no bank feeds, no tax filing, no card payments from your customers. We export to your accounting software instead.
Materials used go on the report as text. Nothing tracks stock or knows what's on the van.
A customer is a name, how to reach them, and one notes box. No pipeline, no lead source, no activity feed.
Your office worker's own phone can text a crew invite. We won't message your customers on your behalf.
Say roughly how many people go out on jobs and what trade you're in. We'll tell you plainly whether FieldLog fits, and what it can't do for you yet.
One inbox · A person answers · No form that goes nowhere