Example: Field reports
Site paperwork drafted the same evening, from a voice note.
A foreman talks through the day in a two-minute voice note. By evening a daily log, safety check or equipment log is waiting in the job folder, in your template, for them to read and sign. If five foremen each spend five hours a week typing up paperwork, that is 25 paid hours a week.
Typing up site paperwork after the shift. About 30 minutes each time, every time it comes up.
Handled for you, and nothing reaches a customer in words you have not approved.
What a diagnostic would check first
The diagnostic decides what gets built, or whether anything should. What follows is one way it could look.
- Which form the crew hates filling out most
- How many days the paperwork runs behind the work
- Who signs each document off today
One way it could look
Open the working exampleQuick look. The full example has every screen. Made-up electrical contractor, jobs and voice notes. The page cannot record audio, so each voice note is shown as its transcript. Nothing is sent from this page.
How it would work
- Step 1
The foreman talks
A voice note on WhatsApp or the phone's voice memo app, recorded before leaving site. No form and no typing.
- Step 2
It is written down and matched
A transcription service turns the audio into text. The job is matched from the job number, site name or street. If two jobs fit equally, it asks which one instead of guessing.
- Step 3
It becomes a draft
A daily log, safety check or equipment log in your own template. Missing fields are listed, every number is marked to confirm, and a hazard alerts the owner right away.
- Step 4
A person signs it
The draft lands in the job's folder in your shared drive and goes to the foreman. Only a signed document is filed as final.
Waits for your OK
- Every document. It stays a draft until the named person reads it and signs. Nothing is filed as final or sent to a client, inspector or general contractor before that.
- Every number. Crew counts, hours, quantities and meter readings are marked to confirm, because fifteen and fifty sound alike.
- Which job, when a note fits two. It asks instead of picking one.
Konsul builds it. Kustos keeps it running and right.
Once it is live, Kustos checks it on a schedule and drafts a fix when something breaks. A person approves every change.
What could go wrong
The transcription mishears a number.
Every number it pulls is shown next to the words it heard, and the document cannot be signed until each one is confirmed.
A note is filed under the wrong job.
It matches on job number, site name and street. When two jobs fit equally, like two jobs on Maple, it asks which one and files nothing until a person picks.
A hazard is buried in the middle of a long note.
Every sentence is checked against a list of hazard words like exposed wire, cover off, near miss or got hurt. You set the list. A match alerts the owner right away, before anyone signs, and the hazard sits at the top of the draft.
A voice note comes from someone not on the crew list.
It is held for the owner instead of drafted for a foreman. Nothing from an unknown number reaches a job folder until the owner checks it.
Next step
Start with the process that costs you the most.
Rough numbers are fine. Describing it takes about three minutes.
Tell us what's breaking