One running log for the field, the PM, and management. Capture a conflict or an RFI once and it's on the board, rolled up, and legible to management without anyone re-keying it. All from where it happened.
Conduit run clashes the structural beam at grid C-4? Log it once, on the job, in the moment not back at the trailer three hours later.
Conflict → RFI → the status-mix, the completions trend, the per-job load. Management sees which job is busy without chasing anyone for a report.
complete · in progress · delayed · conflict · RFI · submittal. Status tags a builder already thinks in — conflict reads red, RFI reads purple, so the entries that matter get their own slices.
Built for GCs running multiple jobs where the field-to-office handoff is the leak — occupied-hospital fit-outs, lab build-outs, renovations, anywhere "captured once, legible to management, nobody re-keying" is the win.
On a real job, progress isn't linear. Work gets interrupted, re-prioritized, blocked on someone else, sent back for revision. By the time anyone asks "where are we?", the why is gone — and the only record is whatever someone remembers in the moment.
Gantt charts show the plan. They don't show the six interruptions that moved the date.
"Why is this late?" gets answered from memory, days later, defensively.
No one can see that the same blocker keeps recurring, because nobody's logging it.
Log a status change in under a minute, from the floor. Five fields, append-only, plain-text first. It feels like jotting a note — but every entry is structured data the moment it's written.
Reports, calendars, Gantt exports, pattern analysis, AI summaries — none of them need a translation layer, because there's nothing proprietary to translate. The simplicity of the data model is what makes the integration potential real.
Job, status, area of work, change, reason — captured from the floor in one line, with the date stamping itself. The full status update a PM would otherwise chase across a dozen conversations.
A demonstration dataset — eight weeks of activity across 32 jobs, each entry input in under a minute. This is the shape of the record CHANGELOG produces.
The same six-column log, rendered as the view a manager actually wants: cumulative completions climbing, with weekly activity underneath.
Completions are less than half the story. Active work, delays, conflicts, and open RFIs are the hidden cost of every project — and for the first time, they're measured instead of remembered.
"Help people focus on what needs to get done
by understanding how it got done."— CHANGELOG · the mission, v0.1