You dictate the report, the platform fills in the rest.
SCRIBA has the technician review and confirm it, then files it under the right activity.
By voice, from the phone
Linked to activities
Nothing goes in without confirmation
SCRIBA · voice-dictated site reports
The problem
The work gets done. The report arrives late, or not at all.
Paper, photos, messages, spreadsheets: every site writes it its own way, often at the end of the day and from memory.
In the office someone pieces it all together and copies it onto the activities.
from the site to the office
SCRIBA · voice-dictated site reports
Why it happens
It isn’t a matter of willingness: writing takes too much effort.
1
Written at the end of the day
Tired, from memory, gloves just off.
2
It comes in a thousand forms
Paper, photos, voice notes, spreadsheets: each team has its own.
3
It isn’t linked to the activity
Someone in the office has to match it up by hand.
click a card to open the details
SCRIBA · voice-dictated site reports
How it works
Four steps, from the spoken account to the activity.
The technician talks as they would to the site foreman. The platform does the rest, and always stops before writing.
one report, step by step
SCRIBA · voice-dictated site reports
An example illustrative
A few seconds of voice, a complete report.
🎤 The technician dictates
▶ Play
📋 The resulting report
Waiting for the technician’s confirmation
Illustrative example: sentence, fields and values are made up to show how it works. The real report fields are decided with you.
SCRIBA · voice-dictated site reports
The rule
No report goes in without the technician’s yes.
Artificial intelligence prepares, the person decides. It’s the same rule that applies throughout NexusOS.
1
The technician reviews
They see the completed form before it is sent.
2
Corrects in a moment
By voice or with a tap, whichever field is wrong.
3
Confirms, and it’s on record
Who confirmed, what and when.
click a card to open the details
SCRIBA · voice-dictated site reports
For coordinators illustrative example
In the office, the day on every site is already one screen.
Reports confirmed today
0
Hours logged on activities
0
Reported issues to review
0
by site · reports received out of those expected
▶ Play
Sample figures and sites. The dashboard is built on your sites and your activities.
SCRIBA · voice-dictated site reports
What already exists and what we build
The foundation is already running. We build the voice part with you.
live in NexusOS
Activities with assignee, priority, deadlines and hours
iOS and Android phone app: activities, attendance, calendar
Documents linked to the activity
An assistant that proposes and asks for confirmation before writing
Roles and permissions: everyone sees only their own
to be built in the pilot
Report dictation and automatic field filling
The connection to the task manager you use today
The languages spoken on your sites
Working where there’s no network: to be checked with you
we’ll say it first: there is no demo of the voice part yet, there is the platform it runs on
SCRIBA · voice-dictated site reports
How we start
A small pilot, with the metrics agreed beforehand.
One team, one site, your real reports. It expands only if the metrics say it works.
the path
Metric 1
How long does it take from the work to the report in the office?
Metric 2
How many reports arrive complete on the first submission?
Metric 3
How many corrections are needed before confirmation?
SCRIBA · voice-dictated site reports
SCRIBA · built on NexusOS
How long from the work to the report in the office?
Let’s start there: a call about your current reports, to decide together on fields, languages and the pilot site.