Guide

How to document your work so your manager can advocate for you

Updated November 2026 · by Jerry Liu, Dayflow's founder

Write it down as it happens, not at review time. Keep a two-line daily log on paper or in a text file, send your manager a short weekly note with outcomes and blockers, and roll it into a monthly brag doc tied to team goals. If your Mac days blur together, Dayflow can keep an automatic timeline to jog your memory before you write.

Review season shows up and the form asks for your “key accomplishments this cycle.” You open a blank document and type out the last two weeks in detail. Everything from three months ago is a fog. You know you were busy, you know some of it mattered, but the specifics are gone: which launch you rescued, whose onboarding you ran, what that migration actually saved.

Meanwhile, your manager walks into a meeting where they have to argue for your rating or your promotion. The other managers in the room have names, dates and outcomes. Yours has “they’re really solid.” It is not that your manager doesn’t value you. They just don’t have the sentences.

This guide covers why good work goes unnoticed, six things you can start this week to fix it (most need nothing but paper), and where an automatic record of your day fits. Dayflow, a Mac app we make, comes up once near the end.

The short version

Why doesn’t my manager already know what I do?

Because they see a slice. A manager with several reports catches your work in standups, one-on-ones and whatever lands in their inbox. The careful review you did on someone else’s project, the hour you spent untangling a customer problem, the risk you flagged early: most of that happens out of their view.

Memory works against you too. Many people find that recent weeks feel huge and older months shrink to a sentence. When you write a self-review from memory, you get a summary of the last few weeks plus whatever was dramatic. Steady, quiet work disappears, and quiet work is often the most valuable kind.

Then there is prevention. When you stop a problem, nothing happens. Nobody notices an outage that didn’t occur or a deadline that didn’t slip. Unless you write down what you avoided, the record shows a calm quarter.

Many people also discount their own work as it happens. A hard thing, once done, starts to feel obvious. “That was just my job” is a common thought, and it quietly deletes the line from your review.

Finally, the decisions that matter often happen without you. Ratings, promotions and project assignments get argued in rooms you aren’t in. Your manager can only repeat what they know, and they can repeat specifics much more convincingly than general praise.

None of this is a character flaw. It is how memory and organizations work. The fix is to write things down while they are fresh and in a form your manager can reuse.

1. Keep a two-line daily log

At the end of each day, write two lines. The first is what you moved forward. The second is what changed because of it, or what you learned. That is the whole habit. Use a notebook, a text file, or the daily work log template.

Keep it small on purpose. A long daily journal is a habit most people drop within a week. Two lines takes a minute, and a minute is something you can do on your worst day.

An illustration: “Finished the pricing page copy and sent it to legal. Legal flagged one claim, so I fixed it before launch instead of after.” Another day: “Spent the afternoon on the flaky test. Found it was a time zone bug and wrote it up so the next person doesn’t lose a day.”

How to tell after a week: You have five entries, and reading them back reminds you of at least one thing you had already forgotten. If you missed days, move the habit to something you already do every day, like closing your laptop or your commute home. If you want more structure, the complete guide to work journals covers other formats.

2. Write outcomes, not activities

“Attended planning meetings” tells your manager nothing they can use. “Pushed back on the Q3 scope in planning, which kept the launch date realistic” gives them a story. The difference is a single question: what is different because I did this?

Activities are easy to write and mean little. Outcomes take one more second of thought and carry the meaning. Name who it helped, where you can: a customer, a teammate, another department, your manager’s own goals.

An illustration: Activity: “Answered support tickets.” Outcome: “Cleared the backlog of billing tickets so the support lead could focus on the enterprise migration.” Activity: “Reviewed pull requests.” Outcome: “Caught a permissions bug in review that would have exposed admin settings to regular users.”

How to tell after a week: Read your entries and mark each one A for activity or O for outcome. If most are activities, that is normal at the start. Rewrite two of them as outcomes. By week two, more of your first drafts should come out as outcomes without the rewrite.

3. Save evidence while it exists

Praise and proof are easy to find on the day they happen and nearly impossible to find six months later. Make one place to keep them: a folder, a notes page, a starred-messages list. When something useful shows up, drop it in with a one-line note on why it matters.

Useful evidence includes a thank-you message from another team, a link to the thing you shipped, a before-and-after from your own project, a ticket you closed that others had been stuck on, and the date you raised a risk that later turned out to be real.

An illustration: A product manager in another team messages “this doc saved us a week of back and forth.” You save the link to the message and write “Spec for the export feature - cut cross-team review from a long thread to one meeting.”

How to tell after a week: You have at least one or two items in the folder. If it is empty, you probably aren’t missing evidence. You are missing the reflex to save it. Put a reminder in your end-of-day log: “anything worth saving today?“

4. Send your manager a short weekly note

A weekly note turns your private log into something your manager can see and forward. Keep it short enough to read on a phone. Three sections work well:

You can start from the weekly status report template, and the guide on how to write a weekly status report has more examples. Write it from your daily log, not from memory. That is where the daily habit pays off.

An illustration:

Moved forward: Pricing page live on Tuesday after the legal fix. Onboarded Sam to the billing codebase; Sam shipped a first fix Thursday. Blocked: Waiting on design for the settings redesign. If it slips past next Friday, the beta moves too. Next week: Settings redesign, plus a write-up of the time zone bug for the wider team.

How to tell after a week: You sent one note and it took under fifteen minutes. After a few weeks, a better sign is that your manager refers to something from a note in a one-on-one, or forwards a line to their own manager. If they never mention the notes, ask whether a different format would be more useful.

5. Make the invisible work visible

Every team has work that never becomes a ticket: answering the same question in chat, reviewing others’ work, interviewing candidates, running the meeting nobody wanted to run, mentoring, fixing the thing before it broke. It eats real time and rarely shows up in a review.

Give it its own line in your log. When a good outcome is something that didn’t happen, write down what would have happened. If you are curious how much of your week this kind of work takes, the where does my week go calculator gives a rough split to start the conversation.

An illustration: “Ran four interviews this week. One hire accepted.” Or: “Noticed the certificate was expiring Sunday and renewed it Friday. Without it, the customer login page would have been down for the weekend.”

How to tell after a week: Your log has at least one line of support, prevention or coordination. If you still can’t see any, ask yourself which messages you answered for other people this week. That is usually where it hides.

6. Hand your manager the sentences they need

Once a month, spend half an hour turning your notes into a brag doc: a running list of accomplishments with evidence, in language your manager can repeat. The monthly status report template is a reasonable shape for it. For each item, add a short line connecting it to something your team or company cares about this year.

Then have one conversation. Ask your manager: “When you make the case for people in reviews, what do you need to have?” Some managers want customer impact. Some want scope and ownership. Some need things that match the written criteria for the next level. Their answer tells you what to emphasize.

An illustration: Monthly entry: “Led the billing migration (March to May). Closed with no customer-facing incidents. Supports the team goal of moving off the old payments system this year. Evidence: launch post, incident log, thank-you from the finance lead.”

How to tell after a week: For this step, check after a month. You have one brag doc page with a handful of items, each linked to evidence and a goal. When review time comes, writing your self-review means copying and trimming, not remembering. The guide on preparing for a performance review picks up from there.

Where seeing your actual day helps

Every step above depends on remembering what you did. That is the weak point on days made of small things: a dozen reviews, three calls, a bug that ate the afternoon. By evening it blurs, and the log you meant to write turns into “busy day.” If that sounds familiar, where did my day go walks through the problem.

Dayflow is a free, MIT-licensed Mac app (macOS 14 or later) that records the screen at one frame every 10 seconds and has AI write the day into a readable timeline. You don’t start or stop anything. At the end of the day you read the timeline and pull your two log lines from it. For a weekly note or a monthly brag doc, you can export a date range as Markdown from Settings → Export, then edit it down. The export work history workflow shows the steps.

Recordings and the timeline stay on your Mac. Analysis can run on-device through Ollama or LM Studio, through a cloud provider you configure, or through the optional Dayflow Pro plan at $20 a month. The details here come from Dayflow’s documentation for version 2.2.0, reviewed September 6, 2026.

Treat the timeline as a draft. AI summaries can miss or misread work, so check before anything reaches your manager.

Dayflow publishes this article.

Where Dayflow is the wrong pick

You don’t work on a Mac. Dayflow runs only on macOS 14 or later. On Windows or Linux, a paper notebook or a plain text document is the better tool for every step in this guide.

Your important work happens away from the screen. Dayflow only sees what is on your Mac’s display. Whiteboard sessions, hallway conversations, phone calls and in-person mentoring won’t appear. If that is most of your job, a pocket notebook beats it.

You can’t record your screen on a work machine. Some employers restrict screen recording on company devices. Check your company’s rules before installing it. If the answer is no, the paper log is the right tool.

You want your manager to see a team view. Dayflow has no team reports and no manager dashboard. If your team wants shared visibility, the project tracker your team already uses is the better place for status, and Dayflow stays a private notebook.

You need help writing, not remembering. Dayflow is a record. It won’t decide which outcomes matter to your manager, phrase your promotion case, or coach you through a hard conversation. That part is still you, your notes, and a direct question to your manager.

You need billable hours or invoices. Dayflow doesn’t produce invoices or payroll approvals. If documentation means timesheets for a client, look at Mac time trackers built for billing.

The bottom line

Your manager can’t advocate with work they never saw or can’t describe. Give them specifics. Two lines a day, a short note on Fridays and a monthly brag doc add up to a record your manager can repeat in rooms you’re not in, and a self-review that writes itself. Start tonight with a notebook and two lines. If your Mac days blur together and you keep forgetting what filled them, an automatic timeline can fill the gaps, but the habit of writing down outcomes is what does the work.

Frequently asked questions

What should I include when documenting my work for my manager?

Include what changed because of your work, not just what you did. For each item, note the outcome, who it helped, and any evidence such as a message, a link or a number from your own project. Add the invisible work too: reviews, unblocking teammates, interviews and fixes that prevented problems. Keep each entry to a line or two so you actually keep writing them.

How often should I update my manager on my work?

A short weekly note works for most people. It is frequent enough that nothing important gets lost and rare enough that it does not feel like noise. Keep it to a few lines: what shipped or moved, what is blocked, and what is next. Before reviews, roll the weekly notes into a longer summary instead of writing one from scratch.

What is a brag document?

A brag document is a running list of your accomplishments, written in plain language with evidence attached. It is not about boasting. It gives your manager specific sentences they can repeat when you are not in the room, such as in a promotion discussion. Most people update it monthly from their daily or weekly notes, and add a line connecting each item to a team goal.

How do I document work that doesn't produce a visible result?

Write down what would have happened without you. If you caught a problem in a code review, note what it would have broken. If you spent a day helping a new teammate, note what they could do afterward. Prevention, support and coordination rarely show up in a tracker, so the sentence describing the avoided cost is the documentation. Write it the same day while the details are clear.

Is it awkward to send my manager a weekly update they didn't ask for?

It usually feels more awkward to the sender than to the reader. A short, factual note saves your manager from asking and gives them something to forward. Ask once whether the format is useful and whether they want it shorter, longer, or on a different day. If they say no, keep writing it for yourself and bring the highlights to your one-on-ones instead.

How can I remember what I worked on if I forget to write it down?

Reconstruct from the trails you already leave: your calendar, sent messages, commits, closed tickets and edited documents. Spend ten minutes on Friday scanning them. On a Mac, an automatic record such as Dayflow's timeline can fill gaps without you starting a timer. Treat any reconstruction as a draft and check it before sharing, since memory and AI summaries both miss things.

Can I use Dayflow to document my work on a Windows PC?

No. Dayflow runs only on macOS 14 or later. On Windows or Linux, a paper notebook or a plain text document beats it for this job, because it works anywhere and takes a minute a day. The habit matters more than the tool. Two lines at the end of each day, rolled into a weekly note, gives your manager what they need.

Should I share my Dayflow timeline directly with my manager?

Usually not. The timeline is a detailed record of your screen, which is more than your manager needs and may include private or sensitive material. Use it as raw notes, then write your own short summary of outcomes. AI summaries can also miss or misinterpret work. If you use a cloud assistant on your Dayflow data, that conversation is not local even though the recordings are.

What if my manager doesn't seem to read my updates?

Keep sending them, but make them easier to use. Put the single most important line first, cut anything routine, and link evidence instead of describing it. Then raise one item in your next one-on-one so it gets discussed. Even if your manager skims, the archive is still yours for review season, a promotion case, or a conversation with a new manager.

See where your day actually went

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