Friday 5:40: My Weekly Report Used to Be Four Empty Words — Here’s What Changed

“Steady progress” says nothing. Park three things into a daily note — what got done, what got stuck, where things live — and let AI draft a weekly report your manager can actually act on.

At 5:40 PM on Friday, a message pops up in the team chat: “Please send in your weekly reports before logging off.”

I stare at a blank document. Chat logs on my left screen, two meeting recaps on my right, and an unfinished to-do list still hanging in my browser. After ten minutes of scrolling back and forth, I type out four words: Making steady progress.

Even I feel guilty typing it.

A bit of background first: I am about as ordinary an office worker as it gets. I handle operations and project execution grunt work. I do not study productivity tools, I do not chase workflow trends, and I can’t even be bothered to install a to-do app on my phone. For a recurring chore like weekly reports, I basically grind it out from memory on Friday afternoons—a process that feels a lot like dumping out a week’s worth of trash and digging through it to see if anything looks like a real result.

Those four words are the most familiar cover-up for people like me: they sound perfectly fine, but nobody has any clue what you actually progressed. Even if you worked your tail off all week, AI cannot piece together what your manager needs to see first from a floor covered in paper scraps.

I used to think my problem was that “I just didn’t know how to write a weekly report.” Only later did I realize that I had dropped all my material along the roadside. By the time Friday arrived, AI wasn’t looking at my actual achievements; it was facing a messy mental cloud of “I swear I wasn’t slacking off this week.” Honestly, no one could do anything with that.

My current fix is embarrassingly low-tech: I set up a dedicated “parking spot” for my week’s work.

Before Wrapping Up Each Day, Park Three Things

Don’t overcomplicate it. This is not a complex system or a fancy template—a dedicated doc, a sheet of paper, or even a sticky note list only I can decipher works fine. Two minutes before logging off each day, I only drop in three things:

• What got done: Not “followed up on the project,” but “what was confirmed, what was delivered, and what milestone was reached”;
• What got stuck: Who hasn’t replied yet, what dependency hasn’t arrived, and what item might slip behind schedule;
• Where things live: Where the relevant meetings, docs, and chat logs are hiding—just note where it lives.

I used to love putting down “communicated” and “steady progress.” Now, whenever I see phrases like that, I ask myself: If I have to write the report next Friday and read this, will I remember what actually happened? If the answer is no, it doesn’t count as a record.

This parking spot isn’t about forcing myself to write a daily report. It simply keeps Friday-me from feeling like I’m digging for an earbud dropped in the trash.

Then, Hand AI a “Good Sample Your Manager Liked”

I also used to do something pretty foolish: I would tell AI to “write in a style my manager likes,” without ever showing it what my manager actually likes.

That’s basically like telling a new coworker, “You know what I mean, right?” They can only nod politely and then wing it—churning out corporate bureaucratic fluff or a rambling essay, neither of which is what my manager wants.

I’ve learned my lesson: I find one or two past reports that my manager gave positive feedback on. I tell AI not to copy the business content, but just to look at how results are ordered, how risks are framed, and what gets kept short. Then I feed it the material from my parking spot:

Please draft an initial report based on: “This Week’s Results, Bottlenecks / Blockers, Attempts Already Made, and Items to Confirm Next Week.” Do not invent details without supporting evidence; flag anything uncertain.

With a real sample to go off of, AI finally understands I’m not asking for an essay. I just want my manager to grasp in three minutes: what got finished this week, and where they need to provide sign-off or decisions.

Don’t Skip That Final Pass

Once AI finishes the draft, I only do three things: swap out vague verbs, double-check dates and numbers, and bump the items that genuinely need manager support right to the top.

For example, instead of writing “continue following up on client requirements,” I change it to: “Waiting on client to confirm API scope; if no response by Wednesday, need sales team support to push forward.” It might not sound poetically polished, but my manager knows immediately whether to step in and where to direct their effort.

A weekly report isn’t about packing up your week of hard work and shipping it off. It’s more like taking the loose items scattered across your desk and putting them where everyone can see them: what’s finished, what’s stuck, and whose turn it is to move next.

Next Friday, when you see that message pop up saying “Please send in your weekly report before logging off,” don’t rush to dump raw chat logs into AI. Give it a proper place to park first: what was completed, where things got stuck, and where the files live—laid out clearly on the table.

Before 6:00 PM on Friday, what you send out will no longer be four empty words, but rather “three things completed this week + one sentence requiring manager sign-off.” As you walk out of the office, you’ll feel grounded: this week wasn’t spent in vain.

Keep that report. When next Friday rolls around, it will be your new good sample.