The Project POV · Field Reference

Texting a work log

Everything the system understands, exactly as it understands it. Text these to the job number and the work is filed against the right job, priced from your own price book.


Two ways to send a work log

Both work. Use whichever suits — the second is how most crews already write, and the system was taught to read it.

Format 1 — with a locate ticketmost precise
LOG
2026-0641821
JT-01 135
MISC-12 4
Alex, Sam
What happens: the ticket names exactly one job, so nothing has to be guessed. Codes are priced from your book, names checked against your crew.
Format 2 — the way most crews writeno LOG needed
9-3-26
ABCD123
8256 Example Rd
280' 2" + 2 med vaults
Alex, Sam
What happens: date first, then who the work is for, where, and what ran. The date on line 1 is what tells the system this is a work log and not conversation.

Format 2 needs two things to be recognised

A date on its own first line — and then either a measurement (280', 400 ft) or a job name the office has registered. Without one of those it reads as ordinary conversation and is left alone, which is deliberate: most traffic on this number is people talking to each other.

What each line can be

Dates9-3-26, 9/3/26, 9-3-2026, or the words today / yesterday. Day and month can be one or two digits.
Locate ticketA run of 7–15 digits, or the 2026-0641821 shape. Put it on its own line.
Labor codesJT-01 135 — code then quantity. A colon, an x, an @ or a dash between them all work: JT-01: 96, JT-01 x157, JT-01@157.
Quantities135, 135ft, 135', 36' 2" (feet and inches), 1,157. A full stop at the end is ignored.
CrewNames on their own line, separated by commas, and, or &: Alex, Sam. First names are fine as long as only one person on the roster matches.
Labelled fieldsAny line can be labelled instead. JOB: (or PROJECT/SITE/P), TKT: (or TICKET/LOCATE/T), DATE: (or D), CREW: (or C/MEN), NOTE: (or NOTES/N).
Anything elseUnlabelled lines before the codes become the description — the address, the run, what was done.

Confirming and fixing

Nothing is written to the app until you say so. The system texts back what it read, with a short code.

Approve
YES 4821
Saves it. A bare yes works when only one draft is waiting.
Discard
NO 4821
Throws the draft away. Nothing is kept.
Fix one thing without retyping the whole log
DATE: 8/19
JT-01 150
4821 CREW: Alex
Send just the line that was wrong. Add the short code if more than one draft is waiting.

If the system changed your words, it tells you

When a name or code is read as something slightly different, the confirmation says so on a Read line, right above the YES — for example Read "Jon Doe" as John Doe. Check that line before approving. If two people or two jobs are equally close, nothing is guessed: it asks which.

Photos

Send them straight after the logup to 10
[ photos, no message needed ]
What happens: they attach to the work log you just sent, and the system replies to say how many it kept.

Send the log first, then the photos, while the draft is still waiting. Photos sent out of the blue — with no recent log — cannot be placed against a job, so they are recorded but not attached.

Days with no work to log

A roll call, somebody out, or a day nothing ran. Send it the same way — date first.

Everyone turned up
9-3-26
all crew members
Reply: Noted for 2026-09-03: full crew.
Somebody was out
8-26-26
Sam called out sick
Reply: Noted for 2026-08-26: absence noted.
Nothing ran
8-21-26
all crew members
Bonifey project canceled
Reply: Noted for 2026-08-21: no work.

These are recorded against the day they name and answered, but they do not create a work log and they do not mark anyone present or absent on the roster — that stays something a person does in the app.

What won't be picked up

✕A job name with no date and no LOG. ABCD123 400' 2" on its own reads as conversation. Put the date on the first line.
✓A day with no work on it. 9-3-26 all crew members is read as a day report, not a work log — see below. It is recorded and answered; it just doesn't create a work log.
✕Texting from an unregistered number. Nothing is parsed until the office has verified your number — you will get one notice and then silence.
✓Typos in a name or code. These are fine. They are corrected where the answer is unambiguous and reported back to you, or asked about where it isn't.

Keywords

HELPTexts back the format.
STOPOpts you out. Nothing further is sent to your number.
STARTOpts you back in.

Drafts don't wait forever

An unapproved draft expires, and a shift-end log is stale by morning. Reply YES while you are still on site rather than the next day.