About
Help people focus on what needs to get done.
CHANGELOG grew from real work: field teams, millwork crews, and project operators who needed a record of why their plans changed.
The problem it was born from
Status lives in heads, not in a system. On real jobs, work is interrupted, reprioritized, or blocked. By the time anyone asks "where are we?", the reason is gone and the only record is whoever remembers.
The principle
Write-once, append-only, plain-text first, local-first. Your data stays yours. Every entry is the source of truth, not a draft that gets overwritten.
The data model
Five fields and an auto-stamped date, every feature on top.
date
auto-stamped
·
job
which project
·
status
state of the work
·
area of work
where on the job
·
change
what happened
·
reason
why
This is the honest core: every report, chart, and integration is a view on a single plain-text record. No proprietary intermediate format needed.
Where it's going
Layer 1 · shipping
Log the work
- Simple entry in under a minute
- Local-first and exportable
- A fixed status vocabulary, not free-form noise
Layer 2 · integrations
Fit the workflow
- Connect to calendars, spreadsheets, and tools
- Keep the data model intact
- Expose the same entry anywhere
Layer 3 · intelligence
Make it useful
- Stale-task alerts
- Weekly work summaries
- Recurring blocker detection
We use the same idea that built the product: capture what happened, then make sense of it later.— CHANGELOG