Four-minute daily log
Pre-filled from yesterday, structured for a thumb, and finished before the site gate closes. Queues offline and syncs when there is signal.
Offline-firstDaily site record · Pre-launch
When the claim comes, you will have the record.
Worksill is the daily log your site actually files. Headcount by trade, plant on the ground, weather, progress against programme and geotagged photographs — four minutes on a phone, then locked into an append-only record a quantity surveyor can put in front of a lawyer.
01 The problem Evidence
The argument is never about the delay. It is about the evidence.
When a project runs late, everyone already knows roughly what happened. What nobody can prove is who caused it, on which day, and what it cost. The record that decides it was written in a notebook that lives in a van.
-
The foreman's notebook
Written up on the tailgate, three days later, in handwriting that will be challenged line by line. Entries can be added, moved or lost, and everybody in the room knows it.
-
Four camera rolls, no order
Two thousand photographs across four phones, with no site, no grid reference and no link to the day's programme. Half of them belong to somebody who left the company in March.
-
The group chat nobody exported
The real project record is a messaging thread: the pour that got rained off, the drawing that arrived late, the gate that was blocked. None of it is admissible in the form it exists.
-
Safety walks signed off backwards
The form was in the site office and the walk happened at seven in the morning, so the sheet gets completed on Friday for the whole week. That is not a record. That is a liability.
Fig. 01 Evidence sources on a typical site · nothing here survives cross-examination
A diary says what someone remembers. Evidence says what happened, when, and proves it was not edited afterwards.
02 The daily log The record itself
Four minutes at the end of the shift. One record that cannot be rewritten.
This is the whole product. A site manager opens the app on the way to the gate, confirms what the site already knows, and files. Weather arrives on its own. Photographs carry their own time and position. The moment it is filed it is closed — corrections are appended, never overwritten, and every version stays visible.
Northgate Phase 2 — Block C
Contract NG-2291 · Day 148 of 320 · Filed by J. Okonkwo, site managerTue 12 Aug Logged 18:38 · offline · synced 19:04
Weather Automatic · station 3.1 km
14°CTemp, mean
6.2mmRainfall
22km/hWind, gust 41
WetGround state
Stoppage recorded
Pour to grid B4–B6 stood down 11:20–14:05. Rainfall exceeded the pour tolerance in the method statement. 18 operatives stood down, 2h 45m plant idle.
Labour on site By trade
| Trade | Subcontractor | Heads |
|---|---|---|
| Groundworks | Kelso Civils | 12 |
| Steel erectors | Ardent Steel | 6 |
| Formwork | Kelso Civils | 8 |
| M&E first fix | Halbrook | 9 |
| Drylining | Vaneck Interiors | 4 |
| Site staff | Principal contractor | 3 |
| Total on site · 18 stood down 11:20 | 42 | |
Plant on site Hired & owned
| Item | No. | Status |
|---|---|---|
| 50t crawler crane | 1 | Idle 2h 45m |
| Telehandler | 2 | Working |
| 25t excavator | 1 | Working |
| Concrete pump | 1 | Stood down |
| Forward tipping dumper | 3 | Working |
| Diesel generator, 100kVA | 1 | Running |
| Plant on hire, charged today | 9 items | |
Safety & sign-off 3 records
| Safety walk, zones A–C | 07:12 |
| Toolbox talk — working at height | 14 signed |
| Near miss — reversing dumper, gate 2 | 14:40 |
| Permit to dig, grid D2 | Open |
| RFI 214 — drainage invert level | 9 days open |
| VO 31 — instructed verbally, PM | Confirmed |
| All records timestamped at capture | No paper |
Progress against programme 4 activities · 2 flagged
Pile caps, grid B1–B6 Planned 100% · actual 82%
−1 day
Core wall, lift 4 Planned 100% · actual 100%
On programme
Drainage run D3 Planned 70% · actual 40%
−3 days
Steel frame, zone 2 Planned 55% · actual 61%
+1 day
Photo record 4 of 23 shown
51.5188N 0.1301W
51.5187N 0.1299W
51.5190N 0.1304W
51.5185N 0.1296W
Every photograph carries the device time, the GPS fix and the log entry it belongs to. Position is written at capture, not at upload.
Entry hash 9f4c1a…a71b
Previous 3d2e77…88c0
Signed J. Okonkwo 18:42
Append-only · revisions add, never replace
Illustrative example. Sample project, sample data — not a real contract.
03 How it works Capture → lock → compile → defend
Built so the record is finished before the van leaves.
Nobody on a site has an appetite for admin at six in the evening. Worksill assumes that, and makes the honest version faster than the dishonest one.
-
01
Capture
The form opens pre-filled from yesterday: same trades, same plant, same activities. You change what changed and photograph what matters. No signal in a basement or a cut-and-cover box — it queues on the handset and syncs at the gate.
-
02
Lock
On filing, the entry is hashed and chained to the one before it, stamped with server time rather than handset time. Nothing can be deleted. A correction is a new revision, linked to the original, with both versions visible for good.
-
03
Compile
Logs roll up on their own: labour curves by trade, plant-days on hire, weather stoppages, programme variance per activity, and the photo record indexed by date and grid reference. No one re-types anything into a spreadsheet.
-
04
Defend
Choose a window and an activity. Worksill assembles the pack: daily logs in order, weather data, photographs with their original metadata, labour and plant standing, and a chain-of-custody sheet a QS can reference by page.
Fig. 02 The record chain · corrections append, originals persist
04 The claim pack Evidence, assembled
Pick a window. Pick an activity. Get the pack.
A delay claim is an argument about a specific stretch of time and a specific piece of work. Worksill already holds every day in that window in order, so assembling the evidence is a selection, not a reconstruction.
-
Every day in the window, in order
Including the nil returns. A day with nobody on site is evidence too, and an empty week in a notebook proves nothing.
-
Photographs with their original metadata
Capture time, GPS fix, device and the log entry each one belongs to — exported as originals alongside the PDF, not as flattened thumbnails.
-
Weather from a station, not from memory
Hourly readings for the site postcode, logged on the day, so a rain-off stoppage is corroborated by something other than your own note.
-
A chain-of-custody sheet
Who filed what, when, from where, and which hash follows which. The part that turns a folder of files into something a QS is willing to sign under.
18 logsEvery day in the window, nil returns included
412 photosOriginals with capture time and position
1 custody sheetHashes, filing times and signatories
Illustrative pack. The figures above describe a sample export, not a completed case.
05 Features What ships
Everything a site already does, captured once and kept properly.
No modules to buy, no configuration project, no consultant. One log, one record, one export.
Geotagged photo record
Position and time written at the moment of capture, tied to the log entry and the grid reference — not to whoever happened to upload it later.
GPS + device timeAutomatic weather log
Hourly readings for each site's location, recorded every day whether anyone remembers or not. Rain, wind, temperature and ground state.
Per site, per dayLabour and plant by trade
Headcount per trade per subcontractor, plant on hire with its idle hours, and the standing time that a claim eventually turns on.
Rolls up automaticallySafety walks and near misses
Toolbox talks with signatures, safety walks timestamped where they happened, near misses filed in the minute. No retrospective sign-off, because the record won't allow it.
Timestamped at captureProgress against programme
Activities from your programme, updated daily, with variance flagged the day it opens up rather than at the monthly report.
Variance flagsOne-click claim pack
Select a window and an activity; get the logs, the weather, the photographs with metadata intact, and the chain-of-custody sheet as one export.
PDF + CSV + originalsPortfolio view
Every live site on one board: who logged today, who didn't, which sites are carrying open near misses, and where variance is opening up.
For contract managersExport, always
Your logs and your photographs leave in open formats on demand, including after you stop paying. The record belongs to the job, not to us.
No lock-in06 Two decisions Where we differ
Two decisions the rest of the market did not make.
Priced per active site, not per person
Site software is usually sold per user, which means the moment the record matters — when the man who saw the thing takes the photograph — somebody has to decide whether he is worth a licence. He never is, so the record thins out at exactly the point it should be thickest.
Worksill charges for the site. Every operative, every subcontractor's foreman, every visiting engineer can capture, at no additional cost. Sites open and close; headcount does not stay still. Bill the thing that is stable.
Append-only, or it is not evidence
Most site apps let you edit yesterday. That is convenient, and it is precisely why the other side's solicitor will ask when each entry was created and whether it was changed afterwards. A record that can be quietly tidied is a record that has to be argued for before it can be used.
In Worksill nothing is overwritten. A correction is filed as a linked revision with its own time and author, and the original stays visible underneath it. Every entry carries a hash of the entry before it, so a missing or altered day shows up as a broken link rather than a clean gap.
It makes the product slightly less comfortable to use. It is the entire reason the file is worth anything eighteen months later.
A diary
- Written up days later from memory
- Editable, with no history of what changed
- Photographs with no fixed position or time
- Weather recalled, or left blank
- Gaps that nobody can account for
- Assembled into a claim by hand, months later
A record
- Filed the same day, on site, in four minutes
- Append-only, with every revision visible
- Photographs carrying time and position from capture
- Weather logged automatically, every day
- Nil returns, so a quiet day is still evidence
- Exported as a pack in one action
07 Pricing One number
Sixty dollars a site. Everyone on it logs free.
One price, published. No seat count to negotiate, no module upsell, no implementation fee for a product that should be usable on the first evening.
Per active site
$60
per active site
per month
Billed monthly. Unlimited users on every site — site managers, engineers, subcontractors' foremen, the operative with the camera. Nobody is a licence.
- Unlimited daily logs, users and photographs
- Offline capture and automatic weather logging
- Safety walks, toolbox talks and near-miss records
- Claim-pack export included, not charged per pack
- Portfolio view across every live site
- Full export in open formats, on demand
Prices in US dollars, excluding sales tax and VAT. Worksill has not launched: pricing is published now so you can judge it, and the founding cohort's rate is held for twelve months from the day their first site goes live.
What counts as an active site
A site is active in any month in which at least one log is filed against it. Set-up weeks, shutdowns and the long tail after practical completion cost nothing. Close a site and it becomes read-only and free — the record stays, because that is when you tend to need it.
Twenty-five sites or more
Portfolio agreements for main contractors running larger books: annual terms, single invoice, single sign-on and a shared configuration across every project. Same product, same append-only record, priced against the number of sites you actually run.
Founding cohort
We are taking a small number of contractors onto the first release, chosen so that we see fit-out, civils and new build rather than one job type. You get the rate held, a direct line to the people writing the software, and an honest answer about what does not work yet.
08 Where we are Pre-launch
We have not shipped. These are the numbers we will publish when we do.
A product about honest records should not open with invented ones. There are no customer logos on this page and no testimonials, because there are no customers yet. Here is the scoreboard we intend to keep, in public, dated.
0
Sites logged
Sites that have filed at least one daily log. Counted once, never re-counted.
0
Longest logging streak, days
Consecutive days logged on a single site, nil returns included.
$0
Claim value supported
Value of claims a Worksill pack was used in, self-reported by the contractor and dated.
Read this before you take anything on trust
Every counter above is blank because the software is not in anyone's hands yet. When the first cohort starts logging we will fill them in with the date of the reading next to them, and we will not name a contractor without written permission. Until then, the product mockups on this page are illustrations built from plausible sample data — a real screen with an invented project on it. If you want to see the actual build rather than a drawing of it, ask, and we will show you where it genuinely is.
- The record is yoursFull export of logs and original photographs on demand, including after you stop paying. No hostage data, no export fee.
- Published pricingThe number on this page is the number. If it changes, it changes on this page, not in a quote written for you specifically.
- No selling your site dataYour logs are not aggregated into an industry benchmark product, sold on, or used to train anything for anyone else.
- Honest about the gapsWhen you ask whether Worksill does something and it does not, you get told so plainly, with a date if there is one and none if there is not.
09 Questions Asked plainly
Questions we would ask.
What happens when there is no signal?
The log is written on the handset and queued. Photographs keep the time and position captured at the moment the shutter went, not the moment the phone found a mast. When the device reconnects, entries sync in order and the server records both the capture time and the sync time — both are in the pack, because the gap between them is sometimes the point.
Can somebody edit yesterday's log?
No. They can file a revision against it, which is a new entry with its own author and timestamp, linked to the original. Both are visible for good, and the pack shows the sequence. This is deliberate and it is not configurable — an append-only record with an off switch is just a diary with extra steps.
Does this replace our programme software?
No. Your programme lives where it lives; Worksill takes the activities you care about and records what actually happened against them each day. Think of it as the layer underneath the programme rather than a replacement for it. If you already run Procore, Fieldwire or similar for drawings and RFIs, Worksill sits alongside them and does the one thing it does properly.
What integrations are there?
Today: CSV and PDF export, and original photograph files with metadata intact. A read API is planned and there is no date on it yet. We would rather tell you that than list logos of systems we have not connected to.
Who owns the data, and what happens if we leave?
You do. On cancellation the account becomes read-only rather than deleted, and the full export stays available. Closed sites are free to keep and free to read — a record you can only see while you are paying is not much of a record when the dispute lands two years after practical completion.
When can we actually start?
Worksill is pre-launch. We are onboarding a small founding cohort site by site, in person for the first week, so that the four-minute claim is tested against a real gate at a real time of day. Tell us how many sites you run and what you build, and we will tell you honestly whether you are in the first group or the one after it.
Founding cohort · pre-launch
Start a site log.
Tell us what you build and how many sites are live. We will show you the daily log against one of your own jobs, and be straight with you about what is finished and what is not.
No sales sequence. One reply, from someone building it.