By role: how the architecture serves each kind of employee
The four constraints stay the same; the role, scope, and approved sources change with the user.
Every role in the company can use the assistant. Below are five working examples drawn from the deployment that built it — installer, foreman, PM, safety, owner. More roles (HR, accounting, estimating) join as the operating company brings them in.
Installer
The installer works where the answers aren't. Ladders, plenums, mechanical rooms, crawl spaces. A clearance question comes up at the rough-in and the foreman is two floors away. The OEM startup sheet is in a binder in the gang box or a PDF on someone else's laptop. Waiting for a callback costs twenty minutes of a four-man crew. Most of the day is craft work, but the delay minutes add up.
Code clearance at the rough-in
Installer on a scissor lift asks out loud how much clearance an RTU gas connection needs from the building opening. Answer comes back with the IMC section and the manufacturer's published requirement, whichever is more restrictive. He keeps working.
Spec lookup without climbing down
Apprentice pulling a branch run off the main needs the approved hanger spacing for the specified duct gauge. He asks from the lift. Answer cites the SMACNA table and the project submittal so he knows which controls.
OEM startup sequence
Journeyman commissioning a VRF condenser needs the pre-startup oil check procedure for that specific model. He asks, gets the OEM steps in order, and runs through them without leaving the equipment pad.
What the system does for this role
- Voice questions answered from the field, hands-free on a lift or in a plenum
- Answers cite the code section, submittal page, or OEM document they came from
- Access to company SOPs and standard details without leaving the work
Foreman
The foreman runs the crew all day and does paperwork at night. Daily logs get reconstructed from memory after dinner. Verbal change directions from the GC superintendent at the 10 a.m. walk get written down at 7 p.m., if at all. RFIs sit in drafts because writing them clearly takes focus the foreman doesn't have during the work. The documentation that protects the job is the work that keeps getting pushed.
End-of-day log from voice notes
Foreman leaves voice notes through the day as he walks the floors. At closeout the system returns a structured daily log with manpower, areas worked, deliveries received, and issues raised, formatted the way the GC wants it.
RFI drafted from a field observation
Foreman finds a conflict between the ductwork and a sprinkler main in a ceiling pocket. He describes what he sees in thirty seconds of voice. A draft RFI comes back with the location, the conflict described cleanly, and the question posed, ready for review.
GC verbal change captured on the spot
GC superintendent tells the foreman at a walk to relocate a diffuser two feet. Foreman says it into his phone with the room number and the reason. The item lands in a change-order-pending list with the time, the person, and the context intact.
What the system does for this role
- Structured daily logs generated from voice notes taken during the work
- RFI and submittal drafts started from field observations, not from a blank page at night
- Verbal change-order items captured immediately and flagged for the PM
Project Manager
The PM runs four to eight jobs and sees each one through a narrow window of weekly meetings and forwarded emails. Status is usually what the foreman had time to type, which is usually the good news. Schedule drift shows up at the three-week-out look-ahead when it's already a two-week problem. Budget variance shows up at month-end when the fix is a change order nobody wrote.
Weekly status from the field record
Monday morning the PM opens a summary for each active job built from the week's daily logs, RFIs, and change-order items. Manpower trends, open items, and areas completed are laid out without the PM chasing the foreman for an update.
Early budget variance flag
Labor hours on the rough-in phase of a job are tracking above the estimated curve for the third week running. The PM sees the flag with the phase, the delta, and the daily log entries most likely explaining it, in time to respond.
Milestone coordination across jobs
Two projects have T&B scheduled the same week and share a balancer. The PM sees the conflict early with the milestone dates pulled from each project schedule and the dependency called out.
What the system does for this role
- Weekly and monthly project summaries built from the field record, not from re-asking the foreman
- Budget and schedule risk flags tied to specific daily log entries and phases
- Cross-project view for shared resources, milestones, and recurring issues
Safety & HR
The safety lead writes briefs that get read at the truck and forgotten at the lift. Near-miss reports don't get filed because filing one takes fifteen minutes on a laptop the crew doesn't have. Training gaps show up after an incident, when the pattern of questions and mistakes was already visible for months. HR finds out about a retention risk when the resignation comes in.
Daily brief tied to the day's work
The morning brief for a crew cutting in a new riser references the specific hazards of that work, the relevant OSHA section, and the crew's recent near-miss entries in that scope. Not a generic toolbox talk printed for every job.
Near-miss reported by voice
A journeyman has a ladder shift under him on a wet slab. He reports it in a thirty-second voice note at lunch. The report is filed, tagged to the project and the scope, with the location and conditions intact, without him touching a form.
Training gap from question patterns
Three apprentices on three different jobs have asked brazing-related questions in the past two weeks. Safety and HR see the pattern with the questions grouped by topic, and schedule a targeted refresher before it becomes a workmanship callback.
What the system does for this role
- Safety briefs tailored to the scope and crew of the day, not generic templates
- Near-miss and incident reports filed from voice with full context preserved
- Question and error patterns surfaced so training is directed where it's needed
Owner
The owner sees the company through filtered reports. PMs summarize, the summaries get summarized again, and the picture that reaches the owner is the one the organization wants the owner to see. Revenue leaks at closeout, verbal changes that never made it to a formal CO, workmanship trends that only show up in warranty calls, a crew whose numbers look fine until they don't. The owner wants to ask the company a question and get an answer that isn't someone's opinion.
Monday morning portfolio question
The owner asks in plain English which active projects are trending over on labor and which have open change-order items older than thirty days. The answer comes back with the jobs listed, the numbers cited, and a link to the underlying daily log entries and CO drafts.
Pending change-order items flagged weekly
Every Friday the owner sees verbal change directions captured in the field that have not yet been formalized as change orders. Project, date, GC contact, scope described, dollar impact estimated where possible. Items that would otherwise get eaten at closeout.
Quality trends across crews
Recurring punch list items, RFI patterns, and rework entries from daily logs are grouped by crew and by scope. The owner sees which foremen's jobs close cleanly and which ones develop the same issue twice, with the source entries one click away.
What the system does for this role
- Portfolio view of active projects built from the field record, answerable in plain English
- Revenue leak detection focused on unsubmitted change-order items and unbilled scope
- Quality visibility from the company's own documented outcomes
Quality visibility, defined
Quality visibility here means the company's own field record, structured and searchable — not a score invented by a vendor. Punch list closure, RFI patterns, rework entries, and commissioning results are kept as documented outcomes over time.
That record is something an owner can show a GC, an estimator can reference on the next bid, and a foreman can point to when the work speaks for itself.