Guide
Start with a paper notebook or a plain text file on a device you own. Write three lines a day: what you finished, what moved, and what is stuck. Add a short weekly summary on Fridays. If you keep forgetting to write, Dayflow, a free Mac app, records your screen and keeps a timeline on your Mac for you to review. It is Mac only and does not do invoicing.
Someone asks what you worked on in March, or a review form wants three accomplishments from the past year. So you open your calendar. It shows meetings, not work. Your sent mail shows replies, not the afternoon you spent untangling a problem or rewriting a proposal for the third time. The project tracker shows tickets closed, with none of the thinking that went into closing them.
The work happened, and you were there for all of it. Almost none of it left a trace that belongs to you, though. What traces exist sit in tools your employer or client owns, arranged for their purposes and not yours.
This guide is about keeping a record that is yours: private, cheap to keep, and still useful months later. Most of it needs nothing more than paper or a text file. One disclosure up front: Dayflow, the Mac app that publishes this article, is our product. It gets one short section near the end, along with a plain list of the cases where it is the wrong fit.
Memory holds onto outcomes and drops the process. You remember that the launch went out. You do not remember the four days of small fixes that made it possible. When most days look alike, same desk, same apps, same people, they blur together, and a month later whole weeks feel empty even though they were full.
The records that do exist are usually written for someone else. Status updates, timesheets and tickets get smoothed out so they read well to a manager or a client. That makes them a poor record of what actually happened. A day spent stuck on one problem becomes “progress on X,” and the useful part is gone.
There is also a timing problem. Many people write notes on good days, when there is something to show, and skip them on chaotic days. Those chaotic days are often the ones you most need to remember later, because that is where the hidden work was.
Finally, records that feel watched tend to die. When a log lives in a shared tool, people either stop updating it or start performing in it. A record that only you will ever read is the one you can be honest in. If the end of each day already feels like a blank, where did my day go covers that feeling in more depth.
What to do. Write one line at the top of the first page or file: “This is for me.” Then choose where it lives. A paper notebook at home, or a file on a device you own, keeps it under your control. Anything on a company laptop or in a company account may fall under your employer’s access and retention policies, so check those rules before you start, especially rules about copying work information to personal devices.
Then decide what never goes in. Describe your work, do not copy it. “Fixed the billing bug for the second client” is a record. Pasting the code, the customer’s name and their account details is a liability.
Illustration. A designer keeps a small notebook in her bag, not on the work laptop. Her entries say things like “Homepage hero, round 3, the client wants it louder, I think they are wrong.” She would never write that in the team channel. That honesty is why she reads her notes again.
How to tell after a week. Look back over the entries. If you wrote at least one thing you would have softened for a manager, the record is private enough to be useful. If every line reads like a status update, move it somewhere that feels more like your own.
What to do. Before you close the laptop, write three lines:
Keep the notebook or file open next to the laptop so the note is the last thing you do. Short is fine. A few words per line still counts. If you want a ready layout, the daily work log template has these fields.
Illustration. “Done: sent revised quote. Moved: data migration, two of five tables. Stuck: login bug, waiting on access from IT.” That takes under a minute, and in three months it will tell you exactly why the migration took longer than planned.
How to tell after a week. Count the entries. Five out of five is great, three is a fine start. Then try this: without looking, can you say what you did on Tuesday versus Thursday? Now look. If the notes fill gaps your memory left blank, the habit is working.
What to do. Put a sticky note or an index card next to your keyboard. Each time you switch to a different task, write the time and a few words. No full sentences, no categories. The point is to leave marks while you still remember, so the evening note becomes copying instead of reconstructing.
If you forget, that is fine. Even four or five breadcrumbs in a day give you anchors to build from.
Illustration. One card might read: “9:10 inbox. 9:40 proposal draft. 11:05 call with Sam. 11:50 proposal again. 2:15 the login bug, ugh. 4:30 expense report.” At 5 p.m., the three-line note almost writes itself, and “ugh” reminds you why the afternoon felt long.
How to tell after a week. Notice how long the end-of-day note takes. If it got faster, or if the “stuck” line got more specific, the breadcrumbs are earning their place. If you never look at the card, drop this step. The three lines alone are enough.
What to do. Set a fifteen-minute block on Friday afternoon, a calendar entry or a kitchen timer works fine. Read the week’s daily notes and write a short summary: the two or three things that mattered most, what is carrying into next week, and one thing you would do differently. The weekly work log template gives you a simple shape for it.
The weekly summary is what you will actually reread later. Daily notes are raw material, and the weekly fold is the record.
Illustration. “Week of 2026-10-05. Shipped the quote tool. Migration halfway, slowed by access issues. Next week: finish migration, start onboarding doc. Do differently: ask for access on day one, not day three.”
How to tell after two weeks. Ask yourself, “What did you do last week?” If you can answer in two clear sentences without opening anything, the fold is working. If Friday keeps slipping, move it to Monday morning and write about the week just finished.
What to do. Start one page, or one file, that is only for evidence. Add to it whenever something happens that you would want to point to later:
Write the date and one line of context. If you save a kind message, note who sent it and when instead of copying private conversations wholesale. When review season comes, this page does most of the work. There is more on that in how to prepare for a performance review.
Illustration. “2026-10-08. Caught a pricing error in the quote tool before the client saw it. Saved a very awkward call.” Six months later, that line is the specific example a review form asks for.
How to tell after a week. Is there at least one entry? If the page is empty, the bar is set too high. Small counts. Helping a teammate get unstuck counts.
What to do. A record you cannot search is a record you will not use. Three small rules help:
Illustration. In December, a client asks when the migration problems started. A search for “Migration” in the October file brings up every entry in order, including the day IT access held things up. That takes less than a minute.
How to tell after a week. Pick one project name and search for it, or flip through for it. If you find every entry, the habit is set. If you find three different spellings, settle on one now while it is still easy to fix.
If you want a rough picture of where your hours go before you start, the where does my week go calculator is a quick place to begin. For more on the journal habit itself, see what is a work journal.
The weak spot in every method above is that you have to remember to do it. On the busiest days, the ones you most want on record, the notebook stays shut.
Dayflow takes the remembering out. It is a free, open-source (MIT license) app for macOS 14 or later that records your screen at one frame every 10 seconds and has AI write the day into a readable timeline. The full screen recordings and the timeline are stored on your Mac.
For a private record, where the analysis happens matters. With local AI, a supported model runs on your Mac and screenshot analysis stays on-device. If you connect your own cloud provider, or use the optional Pro plan at $20 a month, selected screenshots are processed off-device. Under the privacy policy, Pro deletes screenshots after processing and may retain Activity Data for sync, and your own provider has its own terms. If you ask a cloud assistant about your day, it can receive the data it retrieves. Local and cloud processing explains the details.
You can export a date range as Markdown from Settings → Export and paste it into your own notes. The AI can miss or misread work, so treat the timeline as a draft for your journal, not a replacement for it.
Dayflow details here come from its own documentation for version 2.2.0, reviewed in September 2026. Dayflow publishes this article.
For a wider look at keeping records that do not feel like being watched, see time tracking without surveillance.
A private record of your work does not need to be elaborate. A notebook only you read, three lines at the end of each day, a short fold on Friday, and a page of evidence will cover most of what you will ever need: reviews, raises, client questions, and the quiet satisfaction of knowing where the year went.
Keep it somewhere you control, keep confidential details out, and date everything. If the missing piece is remembering to write at all, an automatic timeline on your Mac can give you a draft to work from. The record itself is still the one you write in your own words.
Keep it short. Write what you finished, what moved forward without finishing, and what is stuck and why. Add the date and the project name so you can search later. A few words per line is enough. Leave out confidential details such as customer data, code, or anything you would not want on paper outside the office. The log should tell you what you did, not hold a copy of the work.
If the record is meant to stay yours, keep it somewhere you control, such as a paper notebook or a file on your own device. Employer-managed laptops and accounts can fall under company access and retention policies. Check your employer's rules on moving work information to personal devices. A safe default is to describe your work in general terms and keep the confidential details out completely.
It depends on where the journal lives. Anything stored on a company laptop, in a company account, or in a shared workspace may be visible to the employer under its policies. A paper notebook you keep at home, or a file on a personal device, is under your own control. Whichever you choose, write as if someone might read it one day, and keep secrets and colleagues' private matters out of it.
The three-line end-of-day note takes most people a few minutes once it becomes a habit. A weekly summary on Friday takes around fifteen minutes. It goes faster if you jot short notes during the day when you switch tasks, because then the evening entry is just tidying up what you already wrote rather than trying to remember a whole day from scratch.
A timesheet is written for someone else, usually to bill or account for hours, so it gets rounded and tidied. A private work journal is written for you. It can say a task was frustrating, that you were stuck for an afternoon, or that an idea came out of nowhere. That honesty is what makes it useful later for reviews, raises, or just understanding your own patterns.
For many people, yes. A notebook works on any computer, captures thoughts and context a screen never shows, and stays entirely in your hands. If you are on Windows or Linux, use a work Mac you do not want recording, or already write a few lines every day, paper or a plain text file is the better pick. Dayflow helps mainly when remembering to write is the problem.
The full screen recordings and the timeline are stored on your Mac. With local AI, screenshot analysis also stays on-device. If you connect your own cloud provider or use Dayflow Pro, selected screenshots are processed off-device. Under the privacy policy, Pro deletes screenshots after processing and may retain Activity Data for sync, and your own provider has its own terms. A cloud assistant conversation is not local.
Yes. In Dayflow you can export a date range as Markdown from Settings, then Export. Markdown is plain text, so the file opens in any text editor and can be pasted into your own notes, a weekly summary, or a review document. Because AI summaries can miss or misread work, read the export and correct it before you rely on it or share it with anyone.
Before the review, read your weekly summaries and your evidence page from the period. Group entries into three or four themes, such as projects shipped, problems solved, and help given to others. Pick one concrete example for each theme, with a date. Because the log was written as things happened, the examples are specific instead of a vague sense that the year went fine.
Leave out passwords, customer or patient data, source code, financial details you are not allowed to hold, and private information about colleagues. Also skip anything your contract or employer policy says must stay on company systems. Write what you did and why it mattered in plain terms, such as fixing a billing bug for one client, rather than copying the sensitive material itself.
Dayflow is $0 and open source. Full recordings stay on your Mac, with local AI available for on-device analysis.
Download for MacOS macOS 14+ · MIT licensed · no account required