By a contractor, for contractors.
A former PM and tradesman in Ontario got tired of running jobs out of a truck, a notebook and a spreadsheet. This is what he built, and what it refuses to do.
I built the tool I wished I had on site.
I spent years as a project manager and out on the tools. The building was never the hard part. The hard part was everything around it: who showed up, what actually got done, the photos, the delivery that never turned up, the change the client asked for on Tuesday that nobody wrote down.
By the time you’ve locked up, you’re done in. Sitting in the truck to write the whole day up is the last thing you’ve got left in you, so it gets rushed, or it just doesn’t happen. It was never that anyone was lazy. There’s nothing in the tank for paperwork once the gate’s shut.
So I built it myself.
You talk the day through on the drive home, or chuck your photos at it, and the report writes itself off the back of all that.
Solo, or running crews across five sites, I built this so the job is the thing you’re thinking about, not the paperwork following you home. If it hands you back even one evening with your family, it’s done exactly what I made it for.
Sean Wemple
Founder of CrewLog. Former project manager and tradesman, Ontario.
Decisions the job site made for us.
Each one is a fact about how the work runs, and the software had to bend to it.
The day gets logged where the day happened
Talk it through on the drive home, type two lines between jobs, or send the photos up. The report is written off that.
It has to work with no bars
The report, the clock punches and the photos are held on the phone, and send themselves the moment you have signal.
Half the crew doesn’t work in English
English, French and Spanish, set per person, off the same record.
Safety is not a tier
The incident register and all 32 toolbox-talk topics are on every plan, Solo included.
It stops where the job stops
It quotes the job and bills it; the books and the pay run stay with the tools built for them.
It writes things down.
It doesn’t decide anything.
That is the whole of CrewLog’s position on AI. It can organize a day you described. It cannot report a day you didn’t, sign for anyone, price anything, or decide what is worth keeping.
It will not sign anything for anybody
A signature is a person attesting they were on site. Nobody signs through CrewLog on someone else’s behalf: not you, and not the AI.
It will not fill in a day you didn’t describe
Say nothing about safety and there is no Safety heading, not one with “none reported” under it. It organizes what you reported; it cannot report for you.
It will not let a language model write your money
The price table and the total on a change order are always built from your own line items. Whatever the AI wrote for the money is never what your client signs.
It will not change your account without your tap
Anything the AI wants to save comes back as a card with the values filled in. Nothing is saved until you tap Confirm, and it checks you’re allowed before it does.
It will not quietly bin field data
With no signal the report, its photos and the recording are held on the phone and sent when you have bars. If your access changed while it waited, the record is held, not deleted.
It will not train an AI model on your jobs
From the privacy policy, in those words: “We do not use your content to train any AI model.” It is not a setting you have to go and find.
Each one is how the software behaves today.
Built for the field, not the back office.
Here is who CrewLog fits, and who should look elsewhere.