Search
Looks through every journal entry and action item on all six jobs. Matches are highlighted.
Add note Simulated
Talk or type what happened on site. The office turns it into a journal entry and to-dos.
Simulated: no AI or speech recognition in this demo. The real version would use speech-to-text and AI, and a person confirms every entry.
What it needs to work
| Feature | Data it would need | How it would be provided |
|---|---|---|
| Jobs | Job numbers, site addresses, scope, phase, and status. | Would be typed in by the office. |
| Crew assignments by site | Crew roster, site assignments, dates, and crew leads. | Would be typed in by the office. |
| Inspections | Inspection type, requested and confirmed windows, contact, and result. | Would be entered by hand where the town has no online feed; a linked feed would still need confirmation. |
| Milestone schedule | Planned dates, phases, and completion updates for each job. | Would be typed in by the office. |
| Journal | Dated site notes, job number, and source tag. | Would be typed or pasted in and reviewed before saving. |
| Action items | Task, job, owner, due date, and completion status. | Would be typed in or confirmed from a journal note. |
| Cost | Job budget, committed costs, and spending to date. | Would need an accounting export imported by the office, or a linked accounting account. |
| Files | Plans, permits, and other job documents with access permissions. | Would need a linked shared files folder. |
| 6:00 AM text preview | Crew lead mobile numbers, daily assignments, inspection windows, and action items. | Would need an entered crew roster and a linked SMS account to send scheduled texts. |