App demo
Hallworth Site DiaryHallworth Construction, Fort Collins
What still has to go in
Twenty minutes before knocking off: enter the stoppage from 11:20 AM, confirm 62.75 hours, keep an eye on the deadline for M-07. Whatever is not in by 4:30 PM is in no report.
- In the hands of
- Site foreman on a building site
- Shown on
- Android — title on the left, three system buttons below
- Replaces
- Replaces the site diary in the folder in the site hut, the timesheets on the clipboard and the defect photos sorted out of a phone into an email at night. The report is finished on site at 4:30 PM instead of at home at 8:00 PM, and the delay notice for the rain rests on 11:20 AM — a time captured when it started, not a recollection two days later.
Everything in this demo is laid out and none of it acts: buttons only report that they have no effect in the demo, checkboxes are fixed, input fields lead nowhere. Nothing is stored, sent or fetched.
How Awelior would approach this project
Hallworth Construction, Fort Collins is invented — the way it is built is not. None of this is work delivered for a client. It is the shape we would give such a project — with the same depth, but without a client who would have to answer for it.
Where it starts
Hallworth Construction keeps a site diary for every project. Weather, crew, hours, disruptions and defects accumulate across the day on site and get written into a folder in the hut in the evening — from memory. When the client recalculates a disruption four weeks later, money hangs on it, and the time of day in question is the one thing nobody wrote down.
Decisions
The report is written in quarter hours, not in the evening
Weather, and the start and end of a stoppage, are captured as they happen and not rounded to whole hours. The office writes the formal notice of disruption out of exactly those entries; without a time it is worthless, and by the evening nobody knows it precisely.
Once released, a report cannot be changed
A released daily report can only be added to. A site diary that can be smoothed over afterwards is not evidence in a dispute but a claim with a date on it — and then it will not carry the variation.
What is recorded is time on site, not whereabouts
A site app could log position as a side effect. Where somebody spends their break is none of the report's business; the foreman enters the hours, with a reason, because the office will not accept an unexplained addition anyway.
Deliberately left outNo tracking, no attendance capture by site boundary, no automatic crew time. That would be the obvious next step, and on a union site it is something to settle with the steward first — here, not collecting it is a decision rather than an oversight.
What is in it
- Screens
- 5
- Tabs
- 4
- Content blocks
- 16
- Languages
- 4
Navigation responds, including the route from the diary into a single daily report and back. The forms for weather, stoppage and additional hours, and the defects flow, are fully rendered and inert; the four states have a view of their own.
How it would go on
The route back to the office
Hours into payroll, additions into job costing, disruptions into the correspondence with the client. Without that route the app only replaces the folder.
Subcontractors and bought-in work
Who enters the hours of another firm's crew, who confirms them, and what happens when two companies describe the same day differently.
Evidential value and retention
How long a site diary is kept, who may inspect it, and whether the digital version carries the same weight as the folder — the business settles that before the folder goes.
An app like this for your business?
Hallworth Site Diary is invented — the fit is not. Apps come about exactly this way: from the routes that already exist in a business, only without the paper in between.
Sample app by Awelior. Invented business, invented data, nothing stored.