Digital site log
Digital site log: the day's record is closed and keeps a history of corrections
The site engineer notes what happened today, from the phone. Once published, the entry can no longer be edited: it can only be corrected with a stated reason, and every correction stays in plain view.
The problem
A site log that can be rewritten is useless when there is a claim
On many sites the log is filled in at the end of the week, from memory, or copied over from a notebook. The weather, the lost hours, who was there and what instruction the supervising engineer gave are missing.
And if the file can be edited without leaving a trace, any later discussion turns into a fight over versions.
How it works
From the field note to the day's PDF
New entry
You choose the project and the date and write what was done today. Everything else is optional: weather, rain, lost hours, personnel by trade, equipment with hours, visits, delays, supervising engineer instructions, inspections and deliveries with delivery note.
Photo, audio or PDF
You upload what you have from the work front and the "Autofill" function proposes the fields. Whatever isn't in the document is left empty, not invented.
Publish
The platform asks for confirmation. From that moment the project and the date can't be changed, and the entry can't be deleted or archived; it can only be corrected with a stated reason.
The day's PDF
You download the PDF with the current entries, with the publication and correction stamps (name or role, never the email). CSV export is also available.
What sets it apart
What you can check, not just take on faith
- Published is published
- It's not just a button: the database rejects changing or deleting a published entry without going through a correction. There is a revision history with the most recent ones.
- Also through Telegram
- Notes that arrive through the Telegram bot come in as unpublished entries, so someone can review them before closing them.
- Waits for the signal and uploads itself
- With no connection, the new entry stays on the phone and uploads by itself when the signal returns, as long as the screen stays open; retrying never duplicates it and, if the server rejects it, it stays visible with the reason. It is in testing: not yet used on real phones or on iPhone. Corrections do need a connection.
- Roko proposes, you confirm
- The assistant can prepare a site log entry from what you tell it, but it doesn't create it until you confirm.
- Field finding through to closure
- A finding captured via Telegram can become a pending task with an assignee and closure evidence, keeping follow-up from getting lost in the chat.
What it doesn't do
The limits, stated up front
- A published entry is not immutable in the forensic sense: it is corrected with a stated reason and leaves a history, but it is not a cryptographically sealed record.
- There is no handwritten signature or location capture on the web site log screen.
- Automatic upload without signal is in testing and needs the screen to stay open: if you reload with no network, you see the “offline” page. It does not upload photos.
- An external client or supervising engineer has no site log screen; they receive the PDF.
Compared with what you use today
Compared with the notebook, the spreadsheet and the chat
- Spreadsheets
- Anyone can change a cell without leaving a trace. Here, what is published can only be corrected with a stated reason and a history.
- WhatsApp and shared folders
- Photos and audio get buried in the chat. Here they become fields of the day's entry, ready to review.
- Generic ERP
- An ERP knows nothing about weather, lost hours or supervising engineer instructions. The site log is the data model, not a form bolted on.
Frequently asked questions
What people usually ask before trying it
Can it be used without internet?
With the screen open, yes: the new entry stays on the phone and uploads by itself when the signal returns, without duplicates. This is in testing and not yet used on real phones or on iPhone. If you reload with no network you'll see the “offline” page, and corrections need a connection.
What happens if I make a mistake after publishing?
You correct it by stating the reason. The previous version stays in the revision history and the PDF marks that there was a correction.
Who can see the site log?
The people in the company with permission for that project. The client receives the PDF; they don't enter the site log.
Next step
Let's take your project's site log digital this week
Tell us about your project and we'll show you this module with your own data, no commitment.
On the same topic
Other platform modules