PhaseNote

Demo

Voice-assisted daily crew labor reporting

Say what the crew did.
Check the hours.
Submit the daily report.

A job lead dictates the day. PhaseNote turns it into employee hours by phase code, asks about anything unclear, and hands the office a Daily Job Activity Report it can check and use for its existing job-tracking entry.

Open the demo →See how it works

Fictional company · synthetic data · demo personas, not production accounts

Riverside Medical Office · RIV-026 · Oct 9

“Today John, Mike, and I worked eight hours each. John and Mike spent six hours installing branch raceway on phase 1000 and two hours installing lighting fixtures on phase 3500. I spent four hours on branch raceway, phase 1000, and four hours working on switchgear, phase 3000.”

EmployeePhase#Hours

John Davis1000 Branch Raceway6

John Davis3500 Lighting Fixtures2

Mike Lewis1000 Branch Raceway6

Mike Lewis3500 Lighting Fixtures2

Sam Turner1000 Branch Raceway4

Sam Turner3000 Switchgear4

Crew total24

John 8 · Mike 8 · Sam 8 · confirmed by the lead · example data

How it works

Field to office in four steps. Nothing is guessed.

Record the day

Pick the job and date, tap Record, and talk: who worked, how long, on what. Typing works too, and there's a sample narration for repeatable demos.

Rows, not guesses

The transcript becomes employee × phase × hours rows with the supporting words attached. Unknown codes, ambiguous names, or bare “conduit” become questions instead of assumptions.

Check and confirm

Fix a row and the totals update instantly. Stated daily totals are checked against the rows. The lead explicitly confirms before anything is submitted — any later edit clears it.

Office review and prep

The administrator reviews, returns for correction with a note, or marks reviewed. Then downloads the Daily Job Activity Report PDF and a generic CSV to prepare their own entry.

Ambiguity handling

It asks. It doesn't invent.

Extraction only sees the selected project, date, assigned crew, and the project's permitted phase codes. Everything it returns is validated again by the app before a row can exist. Missing data stays a question until the lead answers it.

Submission is blocked until every identity, code, and hours question is resolved, totals agree with anything stated, no one exceeds 24 hours on a date, and the lead has confirmed the current rows.

“John worked eight hours, six on 1000.”
John has 8 total hours but only 6 allocated. Which phase received the remaining 2?

“Alex worked eight hours on 1000.”
“Alex” matches Alex Carter and Alex Reed. Who worked these hours?

“John worked six hours installing conduit.”
Was that branch raceway, feeder raceway, underground, or another listed phase?

“Mike spent eight hours on phase 999.”
Phase 999 isn't a permitted code on this project. Which listed phase did Mike work on?

What this demo is — and isn't

It is

Daily crew labor reporting: employee, phase code, hours, with the work date on every row.

A review step for the office with return-for-correction and immutable submitted revisions.

A Daily Job Activity Report PDF (Date · Employee · Phase# · Hours, with the phase legend) and a generic CSV.

A way to measure whether speaking plus review beats typing every allocation, for the field and the office separately.

It isn't

–

A payroll system. No pay rates, overtime, or payroll submission.

–

A crew HD or Construction Monkey integration. Nothing is synced or imported; the administrator's entry step stays their own until a supported transfer is verified.

–

Time tracking. No clock-in, GPS, or attendance verification.

–

Production tracking. Hours by phase only — no quantities, units, or productivity rates.

Try the walkthrough.

Enter as Sam, the foreman on Riverside Medical Office. Load the sample narration or dictate your own, answer the questions, confirm, submit, then switch to the Administrator to review and export.