It is Friday, half past three, and the weekly report is due. You know it was a full week. You were busy from the first coffee to the drive home. But when you sit down to write what you actually did, and for whom, the week has turned into a blur of three or four big things and a feeling that there was a lot more. So you open the calendar, scroll through sent mail, check the chat history, and an hour later you have a list you know is incomplete.
Most work does not go missing because it was not done. It goes missing between doing it and recording it. The task finished on Tuesday is forgotten by Friday, the thing you promised to "get to" never gets done, and the half-hour spent on a client's problem never reaches their report or their invoice. None of it is laziness. It is what happens when the only record of the work is somebody's memory.
Three ways work disappears
When we look at teams that struggle to report on their work, the gaps fall into three patterns. They look similar from a distance, but each has a different cause and a different cost.
| What goes missing | How it happens | What it costs |
|---|---|---|
| The forgotten task | Done, but never written down. Small, quick, interrupted-by-something-else work fades first. | Work that is never reported, never credited and often never billed |
| The wishlist nobody addressed | Promised or noticed, but parked in a head, an inbox or a sticky note, with no list to come back to | Broken promises, repeated requests and the slow loss of trust that comes with "I thought you were doing that" |
| The job nobody tracked | Recorded somewhere, but not against the client, project or site it was for | Reports that cannot say what each job received, and invoices that undercharge the busiest clients |
The forgotten task
Memory keeps the big, unusual events of a week and drops the routine ones. The two-day migration will make the report. The fifteen minutes spent resetting a password, the quick call that sorted out a supplier's query, the small fix made on the way past someone's desk: those fade within a day or two, because nothing about them was memorable. Yet in most roles the small tasks are most of the work. A report built from memory is a report of the highlights, and it consistently says you did less than you did.
The wishlist nobody addressed
The second gap runs the other way: things that should have been done and were not. A client mentions a minor change in passing. You notice a report that could be faster. Someone asks, "When you have a moment, could you look at...". Each of these is a small promise, and each one is stored wherever it happened to be said, a meeting, a hallway, a message. Without one list that holds them all, they are not declined, they are simply never seen again, until the person asks a second time and it becomes a complaint.
The job nobody tracked
The third gap catches people who do keep notes. A notebook or a notes file records that something was done, but not which client, project or site it was for. That is fine until someone asks "what did we do for Smith House this month?" and the answer is spread across thirty pages of mixed work. If the work is billed by the job, untracked work is unbilled work. If it is reported by the job, the clients who took the most effort can look like they received the least.
The work you do not write down is the work nobody knows you did, including, by Friday, you.
Why the usual fixes do not stick
Most people have tried to fix this at least once. The attempts tend to fail in one of three ways.
- Too heavy. Time-tracking and project-management systems ask for a start time, an end time, a project, a category and a task code for every entry. That is reasonable for a team billing by the hour, and far too much for everyone else. Logging becomes a chore, chores get postponed, and by the second week the system is being filled in from memory on Friday, which is exactly where we started.
- Too loose. A notes file or a paper notebook is quick, but it has no structure. There is no way to see one job across days, no place for the things still to do, and nothing to turn it into a report without copying it out by hand.
- Too far away. A tool that lives behind a login, on a different screen, in a system meant for someone else's purpose, gets opened when there is time. There is never time. The record has to be one keystroke from where you are working.
The lesson from each failure is the same one we come back to in ways of working: a habit only survives if it costs less than skipping it. Recording a task has to be quicker than the guilt of forgetting it.
What a work log actually needs
Strip the problem back and a useful work log needs surprisingly little. We would put it at six things.
- Seconds per entry. One line, typed when the task is finished, saved without a button. If it takes longer than finishing the task, it will not happen.
- A job on every entry. Set the client, project or site once, and every line after it goes against that job until you change it. That one habit closes the third gap entirely.
- A place for what is not done yet. One list for every promise, idea and "could you look at", each with its job, so it can be found again. When one is done, it moves into the log rather than being retyped.
- A home for the routine. The weekly timesheet, the Monday backup check, the monthly site visit. They should take one click to log, not a fresh line every time.
- A report on demand. Today, this week, this month or one job across every day, copied straight into an email, a timesheet or an invoice. The Friday hour should become a Friday minute.
- Privacy you do not have to think about. A daily log says a lot about your clients and your work. It should not need an account, and it should not live on someone else's server unless you choose that.
Notice what is not on the list: timers. Knowing how long something took is genuinely useful for some work, but it multiplies the effort of every entry. For most people, the first and biggest win is simply knowing what was done, and for whom.
Write it at the end of the task, not the end of the day
The single biggest improvement is when you write things down. A log filled in at five o'clock already has gaps, because the morning has started to fade. One line the moment a task is finished, even a vague one, beats a careful summary written later from memory. You can tidy the wording on Friday; you cannot recover the task you forgot.
Why we built Docket
We hit all three gaps ourselves, and then saw them in more than one customer team: people working across several jobs at once, who had to report on each of them, and who were rebuilding every week from memory. So we built the lightest tool we could that closes them, and made it free. It is called Docket.
- For the forgotten task, a daily log that saves as you type. One line and Enter, and it is recorded.
- For the wishlist, a list of work still to do, each item with its job. Drag one onto a day when it is done, and it becomes an entry in the log.
- For the untracked job, jobs that stay set while you log a run of entries, each with its own colour, and a job view that shows everything ever done on it, with its open wishlist items alongside.
- For the routine, recurring tasks that log with a drag or a click and stay in the list for next time.
- For the report, one button that copies the day, week, month or job, ready to paste.
Docket runs in your browser and can be installed as an app that works offline. It has no account, and your log never leaves your device: it is downloaded once and runs locally, even when you open it from the link. Because of that, export a backup now and then, since clearing the browser's data clears the log. It deliberately does not track time, for the reasons above. You can open Docket here, and more on how it works is on the Docket page.
Docket is offered as is, a finished tool rather than a product with a roadmap. If you would like it to do something it does not, tell us: we can build it for you, or, if it would help everyone, add it to Docket at our own cost. And if your team needs the same idea shared across people, with owners and deadlines, that is a job for Owners Log, or for a system built around how your team works.
Update, 27 October 2026: what Docket has added
A week after this post, Docket has grown. It can now back itself up to a folder you choose after every change (Chrome or Edge on a computer, and a OneDrive or Dropbox folder keeps a copy off the machine), and it reminds you when an export is overdue. Jobs can be printed or saved as a PDF report and archived when they are finished. Recurring tasks can be given due days, so the Friday timesheet is waiting at the top of Friday's log. The full record is on the Docket page.
Start this week
Whatever you use to keep it, a work log is a habit before it is a tool. Try this for one week.
- List your jobs. The clients, projects or sites you work across. Five to ten is typical. If something does not fit, it is "Admin" or "Internal".
- Empty your head onto a wishlist. Every promise, request and "I must look at that" you can remember, each against its job. Most people find more than they expected.
- Add your routine tasks once. The weekly and monthly things you would otherwise retype every time.
- Log as you finish. One line, the moment a task is done. Do not wait for the end of the day.
- Move, do not retype. When a wishlist item is done, move it into the log, so the list only ever holds what is still open.
- Report from the log on Friday. Copy the week, or one job, and see how long the report takes now.
Then compare it with the report you would have written from memory. In our experience, the difference is not a few lines. It is the part of the week that was most of the work, and it is also the evidence you will want later, the same argument we make for systems in the audit trail that saves you.
