Questions, answered

It’s the app your crew logs the day into and you run the job out of. Someone on site talks for two minutes about what happened and adds a few photos, and about ten seconds later there’s a proper daily report written in trade language, under your logo, ready for the client.

Around that sits the rest of the job: crews and tasks, a shared schedule, a time clock your crew taps on their phones feeding timesheets that apply your overtime rules, job costing with receipts read off a photo, safety talks and an incident register, change orders and RFIs that go out for signature and come back answered, drawings and documents you can mark up, and a map of every site. One record per job, and one search that reaches all of it.

Contractors who are on site rather than behind a desk. Residential and light commercial builders, renovators, and the trades: framing, concrete, mechanical, electrical, roofing, sitework. From one person working alone up to a company running a few dozen people across a handful of jobs at once.

It was built by a contractor who was doing the paperwork at the kitchen table at nine at night. If that’s your evening, it was built for you.

No, and we’d rather say so than let you find out. Procore, Autodesk and the rest are built for the general contractor on a large commercial job, with the module count, the implementation and the price that go with it. If you’re on one of those jobs and the GC hands you a login, use theirs.

CrewLog is for the company that was never going to buy that: the one running the job out of a group chat, a phone camera roll and a notes app, where the daily report gets written from memory on Sunday night. It costs about what a couple of hours of labour costs, and a foreman can be using it the same day with nothing explained to him. It also sits fine next to a big system: keep your own record in CrewLog and post into the GC’s when the contract says you have to.

No, the reports are one piece. CrewLog runs the job.

The day gets documented by voice, notes and timestamped photos. Safety runs on toolbox talks, an incident register and corrective actions. Change orders and RFIs go out for signature and come back answered. The crew clocks in on their phones, timesheets apply your overtime rules, and job costing shows your real margin (Crew and Pro). Around all of it: tasks, a shared calendar, drawings you can mark up, a map of every job, a critical-path schedule (Pro), and one search that reaches every one of them.

The reports are the thing you’ll use every day. They’re not the thing you’re buying.

Yes, and more than the talks. Run a briefing from a library of 32 topics that come with the points to cover, tick the hazards on site, and collect a signature from each person who was there, not one name for the whole crew.

When something happens, log it as an incident by kind and severity (near miss, first aid, medical treatment, lost time, property damage, environmental) and assign the corrective action that fixes the cause, with an owner and a due date, tracked until it’s closed. The incident register is on every plan, including Solo: a near miss is the cheapest lesson a site will ever get, and nobody should have to upgrade to write one down. Exporting a talk as a PDF is a Pro feature. (What safety records you’re legally required to keep is between you and your regulator: CrewLog doesn’t decide that, and says so in the Terms.)

One thing worth knowing: the safety score counts near misses as a good sign. Zero incidents and zero near misses scores 70, not 100, because a site reporting nothing is usually a quiet site, not a safe one.

Yes. Every photo is timestamped and filed under its job, and caption search runs across your whole archive at once, not just what’s loaded on screen. You can mark up any photo (pen, arrows, shapes, text, crop) and move, resize or rotate a mark after you’ve drawn it.

Drawings sort themselves by sheet number into trade categories, a new revision stamps the old one Superseded so nobody builds off it, and documents file under contracts, permits, specs, submittals, invoices, insurance and reports. Document markup gives you the tools you’d expect from desktop PDF software (revision clouds, callouts, highlights and APPROVED / REVIEWED / AS-BUILT stamps) and the original file is never touched: the markup lives as a separate layer you can save over or save as a copy. Photos are on every plan; drawings, documents and document markup are on Crew and Pro.

Minutes, not a project. Sign up, create your first job (a name and an address), and you can record that day’s report from the truck on the way home. Nothing has to be configured before that works.

The things you set once, when you need them: your logo for branded documents, your overtime thresholds and wage rates before you run timesheets, and the country and state or province the Assistant should answer code questions for. Inviting your crew is one email each. There’s no implementation, no data migration and no onboarding call you have to sit through, though you can book a walkthrough if you’d rather be shown than read.

No, and you can’t, which is worth saying plainly: there is no import. Nothing pulls your jobs in from a spreadsheet, from another system or off your camera roll.

So don’t try to backfill. Start with the job you’re on this week, log tomorrow into it, and let the record build forward. A week in you’ll have something you’d be happy to put in front of a client, and last year’s jobs are as fine sitting where they are as they were yesterday.

No. If they can send a voice message, they can use CrewLog. Pick the job, talk about what happened, add photos, hit generate. There’s nothing to learn and no training day, and it was built for people standing on a site rather than sitting at a desk.

It isn’t all-or-nothing either. Put one foreman on it and leave everyone else alone until it’s proved itself. The people you invite only ever see the parts you switch on for them, so nobody has to meet a screen that isn’t their job.

On Android it’s on Google Play and on iPhone it’s on the App Store, and the two are the same app.

On a computer you install it from the browser rather than downloading anything. In Chrome or Edge there’s an install option in the browser menu, and usually a small install icon at the right-hand end of the address bar; on a Mac, Safari does it from File, then Add to Dock. CrewLog gets its own icon, its own window and a spot in your taskbar or Dock, there’s no admin password to hunt down and nothing for an IT department to approve, and it keeps itself up to date.

Firefox on a desktop can’t install web apps at all, so use Chrome, Edge or Safari, or just carry on in a normal tab, which costs you nothing but the separate window.

A trades expert built into CrewLog, included on every plan. There’s one box and no mode to pick. Set your country and state or province and ask it anything (code and permit requirements, safety questions, methods, ballpark material prices) by typing, by voice, or with a photo.

Or ask it about your own jobs and it goes and looks: what’s behind schedule, which RFIs are still waiting, what’s unsigned and how long it’s been sitting. Or ask it to do something, and it drafts it. It always points you back to your local authority and the current adopted code to confirm. Viewers are the one exception: a read-only account doesn’t get the Assistant.

Only when you tap Confirm. That’s how it’s built, not a setting you can leave off. Reading runs immediately: asking what’s overdue just gets you the answer. Writing never runs on its own.

When it wants to create a task, a report draft, a change order, an RFI, a toolbox talk or a schedule phase, it comes back as a card showing the exact values that will be saved: the job it matched, the person it matched, the date, the dollar total. At the bottom it says “Nothing has changed yet.” Tap Confirm and it happens. Tap Not now and it says “Dismissed, nothing was changed.”

When you do confirm, the server re-checks your plan, your role, your permissions and your access to that job before writing anything.

It can’t write to your account without your tap. It can’t send a change order: confirming creates the draft, sending is your call. It can’t pick who an owner update goes to; that address comes off the job record. It can’t record a signature for anyone, ever: if it drafts a toolbox talk, the names go on as an attendance list and your crew still signs it themselves.

It reads photos, screenshots and PDFs, one file per message, and you attach the one you want read: it can’t go into your library and fetch a drawing on its own, and it can’t open CAD files, spreadsheets, Word documents or links at all.

And it’s built so facts about your account (a job, a person, a date, a number, a status) come out of your data rather than guesswork. If it can’t read your safety records it tells you it couldn’t, rather than telling you the record is clean. It’s still AI, so check anything you’re about to act on.

They’re organised into real sections: work completed, delays and disruptions, issues and follow-up, materials and deliveries, site conditions, safety observations, crew and manpower, and what’s planned for the next work day. It’s written in proper construction terms, as a factual record, the kind you want on hand for billing and disputes.

Two things keep them honest: it only writes the sections your notes actually support, so there’s no “Safety: none reported” filler on a day you never mentioned safety; and if there isn’t enough in your notes to write from, it stops and asks for more rather than padding it out.

Everything it writes is a draft on your screen until you do something with it. A report opens in an editor, so you fix a name, a quantity or a line you don’t like and save it. Change orders, RFIs and owner updates work the same way: you read it, you edit it, then you send it. Nothing leaves your account on its own.

If you catch something after it’s gone out, edit the report and send it again, or hand over the corrected link. Know what you can’t take back, though: an emailed report is sitting in somebody’s inbox, and the photo links inside it stay openable for about 60 days. A share link is the opposite, and it works in your favour: it has no expiry and always shows the current version, so a client holding one sees the correction without you resending anything.

You keep working. The report is saved on your phone (with the photos and the raw voice recording) and it uploads the moment you get bars, transcribes, and writes itself. You’ll see “You’re offline, saved on this device, will send when you’re back.”

Your job list is mirrored to the phone too, so you can still pick the right job with no connection. The rule the sync engine is built on is that field data is never silently deleted: if your session expired or your access changed, the record is held, not binned.

Yes, on Crew and Pro. They open Timesheets and the job is already picked for them — whatever today’s crew schedule puts them on, or failing that the last job they worked — so it’s one tap in and one tap out, with the running total and the time they started on the card. There’s a break button that stops paid time, and somebody moving to a second site switches job without clocking out: the first shift closes and the second opens at the same instant. It all works with no signal, the same way the daily report does, and the tap carries an id the phone itself generated, so a late sync can’t open a second shift or pay an hour twice.

The hours land in the timesheet you already had. Your overtime rules, wage rates, approvals, the payroll export and job costing all run on them, so there’s no second system to reconcile. A break taken on the clock is unpaid whatever a member’s paid-lunch setting says. Your side of it is a board: who is on the clock, on which job and for how long, three numbers across the top, and a map with a pin per person. It re-reads the server every thirty seconds and prints how old the answer is rather than drawing a stale number. Anything worth a look — a shift still running past your threshold, a clock-in a long way off site, hours with no job on them — waits on that board for you. Nothing is pushed at anybody: there are no alerts and no notifications.

Location is worth being exact about, because you are the one who has to explain it to your crew. A fix is taken when a shift starts, when it ends, and every so often while the app is open on screen. Exactly three points are kept per shift and the most recent one is overwritten each time, so there is no trail, no route and nothing to replay. Nothing at all is collected when the app is closed, in the background, or the phone is locked — neither app asks for background location. Distance from the job is measured at clock-in and a clock-in far from site is flagged for a human to check; it never clocks anyone in or out on its own. Two switches turn it off and neither is ours: the account owner can switch location off for the whole company, and any worker can deny the permission on their own phone and go on clocking in and out normally, showing as “location off” on your board with their hours untouched. You also set what counts as on site, when a long shift is flagged, when a forgotten one is closed, and whether the clock is on at all. This is electronic monitoring of employees, and telling them what you collect is your job as their employer rather than ours — some provinces want it in writing.

Yes, and it’s how it’s meant to be used. Hit record and talk about the day the way you’d tell a partner over the phone: what got done, who was there, what showed up, what held you up. You don’t have to structure it and you don’t have to use the software’s words for things.

Voice works on the daily report, on change orders and in the Assistant, and it records with no signal too: the audio waits on the phone and transcribes itself once you’re back on. You’re never forced into it either. Typing does exactly the same job.

English, French and Spanish, and not just the buttons. Each person picks their own language, and the content your crew types is translated for whoever’s reading it: reports, notes, safety talks, tasks and photo captions. So the foreman logs the day in Spanish, you read it in English, and it’s the same record.

Reports can also be read aloud in the listener’s language with each word highlighted as it’s spoken. The marketing site you’re on right now is English only.

Yes, and it’s the normal case on Crew and Pro. Everyone you invite works in the same jobs at once: the foreman logs the day, the office adds the receipts, you price and sign the change order, and it ends up as one record rather than three people’s versions of it.

Each person still only sees the jobs you hand them and only the areas you switch on. Solo is deliberately a single login, so the day somebody else needs one is the day you move to Crew.

No. A change order goes out as a link: your client opens it on their phone, draws a signature or types their name, and it comes back signed. An RFI works the same way: the architect answers by secure link and the answer files itself onto the RFI.

And you can copy a client link for any daily report, which opens without a login. Nobody you deal with has to sign up for anything. (Change orders and RFIs are on the Crew and Pro plans.)

Three flat plans, printed on the pricing page: Solo at $39 a month, Crew at $89 and Pro at $179, or ten months’ price if you pay for the year. No setup fee, no contract, and no per-seat surprise: seats are included in the plan, so 5 people on Crew costs the same as one.

What separates them is capacity, not a crippled product. Solo is one login and 5 jobs open at a time. Crew is 5 people, 10 open jobs, and the money side: change orders, RFIs, the time clock, timesheets and job costing. Pro is unlimited people and unlimited open jobs, plus the parts that need the whole picture: Project Pulse, the Job Forecast, your branding on documents, scheduled reports, and PDF and CSV export. “Open jobs” means jobs you haven’t marked complete, so finishing one frees the slot. You can move between plans any time in Settings.

The AI features pause. Nothing else does. Your reports, photos, timesheets, costing, change orders and the whole record stay open and you carry on working: only the parts that call the model stop, and the app tells you the date the allowance resets.

You see one percentage for the whole account, not a token count, and you see it long before it matters. If a heavy month eats it, the owner can buy more usage on the spot instead of waiting for the reset. Bought usage is a one-time purchase rather than a second subscription, and it doesn’t expire: your monthly allowance is always spent first and the balance is only drawn on after that. The owner can also split the month’s allowance across the team, so one person can’t spend all of it on their own.

AI is metered on every plan, Pro included. There is no unlimited tier, and we’d rather show you the meter than sell you the word.

Cancel from Settings in a couple of taps. No phone call, no notice period, no retention conversation. It takes effect at the end of the period you’ve already paid for, so you keep working right up to that date.

After that the account locks. Nothing is deleted and nothing is sold on, but you can’t open it again until you subscribe, and there’s no free tier underneath to land on. So export what you need before that date, or email us and we’ll send you a copy. If you want it genuinely gone rather than parked, deleting your account from Settings erases it.

Case by case, in good faith. If you were charged in error, you forgot to cancel, or it just isn’t working out, email support@crewlog.ai and tell us what happened. We’re not in the business of keeping money you don’t think you should have paid.

The written rule is that we don’t refund part of a period you’ve already used, and anything bought inside the iPhone or Android app is Apple’s or Google’s to refund under their own policies rather than ours. Neither of those stops you asking.

No, and it’s worth splitting that into the part we control and the part we don’t. We do not use your content to train any AI model. We build no models, we run no training, and we don’t hand your content to anyone for that purpose. That one is entirely ours to promise. We don’t sell your information either, and we don’t share it for advertising.

The other half is our providers, and we’d rather be straight than sound tougher than we are: Anthropic and OpenAI both state in the standard commercial API terms we use them under that they don’t train their models on data sent through the API. That’s their commitment rather than ours: we don’t have a bespoke contract with either of them, so we’ll tell you what their terms say rather than pretend we can guarantee it ourselves. If either changed that, we’d tell you before it took effect.

We name them rather than hiding behind “a third party”: Anthropic (Claude) writes the reports, change orders, RFIs, briefings and Assistant answers and reads your receipts; OpenAI does voice transcription, and read-aloud on iPhone and iPad. Either may hold what’s sent to it for up to 30 days purely to detect abuse of its own service, then deletes it. The privacy policy lists every provider we use and what each one does.

CrewLog is operated from Ontario, Canada. Your data is encrypted in transit and at rest, with row-level isolation so one account can never reach another’s: even if the contractor down the road uses CrewLog, they will never see your jobs.

Some of our providers store and process data in the United States and other countries; the privacy policy sets out what goes where and why. You can turn on two-factor sign-in from Settings (fingerprint and face sign-in aren’t available yet; we’ll switch them on when our login provider supports them). Browsing crewlog.ai sets no cookies at all, which is why there’s no cookie banner in your way.

Email support@crewlog.ai and a person answers, in business hours, Eastern time. Not a bot, and not a queue with a ticket number on it. Pro accounts sit in a priority queue and hear back faster, but everybody gets a real reply from a real person.

CrewLog is small and founder-run, and that cuts both ways, so you should know both halves: there’s no 24/7 phone line, and there’s also nobody standing between you and the person who wrote the code. If you’d rather be shown than read, book a walkthrough and we’ll go through it on your own jobs.