Two kinds of crew, two kinds of yes. Your own crews: you tick who's going, each man is texted and emailed his field link, and he taps Accept job — you are told every time someone does, and the job's header counts them, 2 of 3 accepted, with a Remind. A subcontractor crew signs: its leader sees the job, the customer, the address, the phases, the dates and what the crew stands to earn, then signs with a typed name and a drawn signature, or declines. Nothing is edited in place — every change of state adds a record. We build only for post-frame and barndominium builders, who run their own framing and slab crews and hire subs for doors and concrete — so each gets the right kind of yes.
Also called: crew signs for the job · sub agreement · crew lead signature · project acceptance · accept the job · crew accepts on phone · who's going
Every crew on the job, and whether it has said yes
The job's header lists every crew on it, each with its own state. Your own crews count acceptances person by person — all 4 accepted, 2 of 3 accepted — and a subcontractor crew reads waiting to sign until its lead signs. Change the lead crew, add another, or take one off, right there. The crews themselves are set up on crews.
Three crews are on one garage and the only way to know who has agreed to turn up is to ring all three leaders.
Knowing who has said yes is what lets you promise a customer a date with a straight face. The answer sits on the job, where you are looking when you need it.
Pick who's going, and hear about every yes
Try itFor your own crew, tick who's going — the whole crew, or three of six for this slab. Each person gets a text and an email with his field link, plus a phone alert if he uses the app, and has to tap Accept job. You are told each time someone accepts, and anyone still waiting has a Remind beside his name.
You split the concrete crew three to one slab and three to another, and by Monday nobody is sure who was meant to be where.
Being asked by name makes a man feel counted on — and being told the moment he says yes means you stop chasing. It turns "did everyone see it?" from a round of calls into a glance.
Putting a subcontractor crew on a job is what creates its contract
Try itPut a subcontractor crew on a job the way you always would and that act alone writes an acceptance waiting to be signed — and emails its lead to sign it. There is no second step, no separate document to remember, and no sub on a job with nothing in writing. Your own crews skip the paperwork and accept on their phones instead.
The office means to get crew acceptance on every job. It happens on the big ones, and on the small ones somebody says they will sort it later. Later is the week the crew walks off and nobody can produce anything they agreed to.
Subs are the crews most likely to walk, and the ones you have least hold over — so their yes is the one that needs a signature. Hanging it off the assignment makes forgetting impossible rather than unlikely, on exactly the rushed jobs where it gets skipped.
The brief he actually reads before he signs
Not a signature line at the bottom of a blank page. The job, the customer, the address, the building type, the phases his crew owns with days against each, the start and end, the plans, and the project manager's notes — then Accept or Decline at the foot.
The crew turns up expecting a two-day pour and finds four. Everybody agrees somebody should have told them, nobody can say who, and the argument is settled by whoever shouts loudest — usually at the cost of the schedule.
A crew lead who knows the span, the dates and the sequence turns up ready — and can't say later he didn't know. A signature on something unread is worth nothing to either side, so the whole brief sits above the button.
Your own men accept on the link they already have
Try itA new job lands on the crew app as an amber banner and a New project card — his part, the dates, the address, the slab or the building, the plans, and who else is going. He taps Accept job, the office is told, and the job is on his phone to clock into. No app to install, no login, no account to issue. Until he accepts, there is nothing to clock into.
The job went out in a group text on Sunday night, two men never saw it, and Monday morning the slab crew is one short.
A man who taps Accept has made a promise — and people keep promises they made themselves. It also ends "I never saw it": the yes is his, on his phone, with the time on it.
They see their own money, and only their own
The brief shows what the crew stands to be paid and nothing else. Your margin is not on it, and neither is what the customer agreed to. Pay is transparent to the men doing the work; the rest of the job's economics are not theirs to see.
Either the crew is asked to accept a job without being told what it pays, which nobody sensible agrees to, or somebody forwards them the estimate and they discover the customer's number. From then on every conversation about their rate starts from your gross.
Nobody agrees to a job without knowing what it pays — but nobody needs to see your margin either. Showing the crew's own money, and only that, is fair to them and keeps every future rate conversation off your gross.
And the number is not invented for the occasion
What a crew stands to earn comes off the day rates and pool you already set — the same figures the payout runs on when the job is done, not a figure typed into a contract by whoever wrote it.
The acceptance says one figure because somebody estimated it, and the payout says another because it was worked out properly at the end. The crew remembers the first number and the business pays the argument.
A crew remembers the number it was promised — so the promise and the payout have to be the same number. Reading both off one set of rates means what they signed for is what they get paid.
Your agreement, in your words, versioned
Try itThe body is your text with fill-in placeholders — labour total, project name, customer, today's date. Edit it once and every future acceptance carries it; saving makes a new version and already-signed ones keep the wording they were signed on.
Crew terms live in a Word file that gets printed when somebody remembers. Which crews accepted which version of it is a question with no answer, because the file has been edited eleven times and never versioned.
Your crews are agreeing to your terms, in your words — that is what makes it stand up. We automate the assembly and the record; the wording stays yours, and every signed copy keeps the version it was signed on.
A refusal is a record, not a phone call nobody logged
Declining asks why, from reasons you can pick rather than a text box nobody fills in. The office is told immediately, and the reason sits on the crew's record beside every job they did accept.
A crew says no on the phone to whoever answered. It gets rescheduled and forgotten. Three months later nobody can say why that crew never takes the barndominiums, or that they have been telling you the reason each time.
A no with a reason tells you something you need to hear — that a crew keeps turning down barndominiums, or always for the same reason. One decline is scheduling; four for the same reason is a pattern, and you only see it if refusals are captured like acceptances.
The office sees it on the crew, not buried in the job
Every subcontractor crew's own record carries what is still awaiting signature at the top — with a resend button — and everything already answered beneath it, accepted or declined, dated, with the decline reasons attached. When several crews share a job, each crew's lead signs his own, even if another crew on the job has already signed.
Acceptance status lives inside each job. Finding out whether one crew has signed everything means opening six jobs one at a time, so nobody checks and the gaps are found by accident.
The office's question is about a crew — "is Ridge Overhead signed up for everything we gave them?" Filing it on the crew answers that by opening one card instead of six jobs.
Frozen the moment it is signed
Typed name plus a drawn signature, with the time and the brief exactly as it stood. Later edits to the job do not reach backwards — what he signed stays what he signed, and if the dates or the payout change materially he is asked to re-confirm.
The job changes after the crew signs — two extra days, a phase moved, a different payout — and the acceptance silently updates. The crew is now on record agreeing to something they never saw, which is worse than having no record at all.
A crew needs to know the deal it signed is the deal it gets — and so do you. A record that follows the job's current state is not a record; freezing it, and asking again when the dates or pay change, keeps it honest.
- 1Put a crew on the job — from the job's header, alongside any other crews already on it.
- 2Your own crew: tick who's going. Each man is texted and emailed his field link (plus a phone alert if he uses the app).
- 3He taps Accept job on his phone. You are told every time, and the header reads 2 of 3 accepted, with Remind beside anyone still waiting.
- 4A subcontractor crew: its leader is emailed the acceptance contract and signs from Team or from the job.
- 5He reads the brief — job, customer, address, phases, dates and the crew's pay — and signs with a typed name and a drawn signature.
- 6Or he declines with reasons, and the job needs a new crew.
A crew that walks off a job halfway through leaves the builder holding a promised date and nobody to hit it — and a verbal yes is worth nothing at that point. For a subcontractor crew that means a document its lead signs before work starts: a personal commitment to the job, responsibility for the men under his direction, and a clause requiring any incoming lead to sign the same thing. Signatures are permanent. For your own crews a contract was the wrong tool — the problem was simpler: jobs went out over group texts and nobody could prove a man had seen one. So each man going now taps Accept on his own phone, and the person who put him on the job hears about every acceptance.
- Jobs sent over group texts with no proof anyone saw them.
- Crew commitments existing only as a verbal understanding.
- No record of who accepted a job or on what terms.
- Reassignments with no handoff paperwork.
Crew lead signs before work starts
For a subcontractor crew, the agreement covers personal commitment (walking off without written authorisation is a breach), responsibility for the crew under that lead, reporting, safety, code compliance and handover on reassignment. Every change of state adds a record rather than overwriting one, so the history reads end to end. Signatures cannot be altered.
Your own crew agreement, versioned
Builders have their own crew agreements — wording their lawyers have already been through — and a generic one they cannot change is one they will not use. Editing yours saves a new version and retires the old one, so every signed acceptance still points at the exact text its signer read. Admin only.
Typed name and drawn signature
A signature pad that draws cleanly at any size, on a phone or a laptop. Nothing signs without a typed name, ink on the pad and a ticked acknowledgement.
The signed record is frozen
An agreement stored as a pointer to a template is an agreement that changes after it was signed. What is kept instead is the document as it appeared at the moment of signing, with the job's details of that moment, frozen.
Why a crew turned a job down
A crew turning down a job used to be a phone call, so the reason lived with whoever took it. Now the same reason means the same thing everywhere it is counted — and what you get is not one refusal but a count.
The crew lead gets the contract by email
A contract waiting on a signature the signer has not been told about is a contract that just waits. The email goes out as soon as the subcontractor crew is assigned. Where no address can be found for the leader, it goes to someone on the crew who has one. An in-house crew never gets this email — each man going taps Accept job on his phone.
Read and print the signed contract
Opening a contract that had not been signed yet used to show a blank page, so nobody could read what they were about to be asked to sign. Signed or waiting, the whole document renders: the agreement text, the job's details, and the signature once there is one.
Swapping crews mid-job
Taking a job off one crew and handing it to another used to erase the fact that the first crew had ever held it, along with the agreement they signed. Now the old assignment stays on the record with its signature intact and a reason for the change, and an incoming subcontractor lead signs the same agreement before taking over.
Signed, waiting, or never sent
Whether a crew had actually signed for a job used to take a phone call, and the answer arrived after the crew was already meant to be on site. Three states, on the job, at a glance. Signed and waiting open the document; never sent is informational, because there is nothing yet to show. With several crews on a job the office sees the lead crew's, and each crew lead sees and signs his own.
The crew sees their pay, not your price
The document a crew lead signs has to state the job, the scope and what the crew is paid. None of that requires him to see what the customer was charged. The only money on it is the crew's own.
