Labourers answer by text — plan

Status: PLAN ONLY. Nothing built, nothing sends. Written 2026-09-15 on Omar's instruction ("if they want to do it by text, plan a way that they will answer by text"), after the owner's Fieldflo call where he liked that a labourer never has to log in.

Scope note (Omar, 2026-09-15 20:59 UTC): Makki Demolition only. One company. The "five companies in one login" idea is dropped and not to be raised again.

The idea in one line

A labourer never opens an app. He gets two texts a day from one Makki number and answers with one character. The answer lands in the portal against his name and the job.

The two moments that matter

1. Morning — safety sign-off

Makki — 1425 17 Ave SW. Toolbox talk today: silica dust + respirator fit. Reply Y to sign off.

Y → signed. His name, the time and the talk topic go on the job's safety record, same place the Crew login writes today. The foreman's Start Day screen shows a green check beside his name instead of an empty box.

2. End of day — hours

Makki — 1425 17 Ave SW. Hours today: 8.5. Reply Y if that's right, or reply the number of hours.

Y → confirmed. 8 → logged as 8, flagged corrected by worker, foreman sees the change and the original. Nothing else needed from him. This is the same confirm step the Crew login has today.

Rules that keep it clean

• One Makki number. Every text in and out uses it. The man saves it once as "Makki".
• Roster only. A text from a number that isn't on the roster gets no reply and nothing is written. No way for an outsider to sign a safety form.
• One re-ask, then a human. Anything that isn't Y or a number gets "Didn't catch that — reply Y, or the number of hours." once. Second miss and it goes to the foreman's list as "no answer", which is exactly what an unanswered box does today.
• No links, no logins, no app install. A link in a text is the thing crews ignore.
• The Crew login stays for the men who want it — QR hard hat, their own tickets, their schedule. Text is the default so nobody is forced to log in; neither path is removed.
• Nothing auto-sends until the owner says so. Same rail as everything else: the messages are drafted, the owner approves the two wordings once, and the send switch is his to flip.

What it needs before it can be built

1. A business texting line. Either a Twilio number or Makki's existing office line ported. The owner's call, and it costs money — Omar decides.
2. Crew phone numbers on the roster. We hold names today, not numbers.
3. The owner's OK on the two message wordings above.

What it does NOT do

Not a chat. Not a way to ask the app questions. Two questions a day, one-character answers. Anything more and the crew stops answering — that is the whole reason Fieldflo's version works.

Where it fits

Sits on top of the existing Foreman's Voice tool (tools/daily.cjs) and the Crew login's Start Day / End of Day screens. No new data model: it writes the same two fields those screens already write.