A client of mine, a director with close to twenty years of experience, told me she had started blocking Sunday evenings to write her Monday status document.
Not to do work. To describe work.
By the time she came to me, she estimated she was spending six to eight hours a week writing updates, answering “quick question, where are we on…” pings, and re-explaining things she had already explained in a different channel to a different person.
When your manager asks for constant updates on your work, you end up with two jobs: the job itself, and the full-time project of proving the job is happening.
This article covers why managers do this, what the constant reporting is costing you, the system I give my clients to make most of it stop, and how to tell the difference between an anxious manager and something more serious. It pairs closely with my article on how to deal with a micromanaging boss.
What Constant Update Requests Are Doing to Your Week
Start by taking the cost seriously, because most people underestimate it.
Every update request carries three costs.
The time to write the update. The interruption cost from the ping arriving mid-thought and the thought does not come back for free.
And there is the anticipation tax: once you know the question is coming, you start pre-drafting answers in your head all day. It is exhausting.
The numbers on how much of our work has become talking about what we are working on are bleak.
Microsoft analyzed activity across its own apps and found the average employee spends 57% of their time communicating and only 43% creating, and 68% of people say they do not get enough uninterrupted focus time in the workday.
In one survey of US employees, 43% admitted spending more than ten hours a week on performative work.
Performative work is activity whose main purpose is to look busy and responsive rather than to produce. The researchers called it “productivity theater”.
Ten hours a week is more than a full workday spent performing that could be actually spent doing the work itself.
If you are losing hours every week to proving your work instead of doing it, it is worth talking it through with someone who has untangled this before.
Why Does Your Manager Keep Asking for Updates?
Is it because your manager doubts your work? Sometimes that is true.
More often, in my experience coaching senior women through exactly this, the updates are about your manager’s own anxiety as opposed to your individual performance.
The most common one is pressure from above. Your manager has a boss too, and that boss asks questions.
If your manager cannot answer “where are we on X” in their own staff meeting, they feel exposed, so they harvest answers from you in advance, sometimes several times a day.
The second is what Microsoft’s researchers named productivity paranoia.
In their survey of 20,000 workers, 85% of leaders said hybrid work made it hard to feel confident employees are productive, while 87% of employees said they are in fact productive.
Only 12% of leaders said they had full confidence in their team’s productivity. Managers who could previously gauge progress by walking past your desk lost their visual cues and replaced them with unending questions.
The third is scattered communication. If your progress lives in five places, a comment here, a standup remark there, a thread somewhere else, then from your manager’s seat there is no coherent picture.
Every gap gets filled with a new request. This is easy to fix and I’ll go over it below.
And the fourth, less common but real, is that the updates are needed documentation with a purpose, which I cover near the end of this article.
The Trap of Defensive Documentation
Before the fix, one warning, because I watch my clients fall into this trap constantly.
When the update requests start, the mistake capable people often make is to respond by documenting harder.
Longer status reports. Receipts for every decision. It feels like protection.
For women there is a real instinct behind it: research on workplace bias shows women are often required to provide more evidence of competence than men to be judged equally capable. Over-documenting feels like the rational response.
But defensive documentation backfires double.
It eats the hours that would have gone into the work itself, which means the next update has less progress to report, which invites more scrutiny.
And it trains your manager to expect ever more detail, ratcheting the reporting burden up instead of down.
The Visier survey found a third of employees prioritize tasks based on what makes them look most visible rather than what creates value. That is the treadmill.
Once you are writing updates to manage perception instead of to transfer information, the updates own you.
The goal is not more reporting. It is less reporting that does more.
Build One Canonical Update
Here is the system I give clients, and it usually cuts the ad-hoc requests dramatically within a few weeks.
Create a single, predictable update that answers your manager’s questions before they ask. Once a week is right for most senior roles.
Keep it short and keep the structure identical every time: what moved forward, what comes next, where the risks are, and what decisions I need from you (your manager).
Four sections, a few lines each. It should take twenty minutes to write, not an entire evening.
Three rules make it work.
Put it where your manager already looks, whether that is email, a pinned doc, or your one-on-one agenda, and send it at the same time every week so it becomes a rhythm they know they can rely on.
Include the risks honestly, because the entire trust-building power of the update comes from your manager learning that bad news arrives from you before it happens. No one wants surprises that need to be solved asap.
And then route everything back to it. Do not skip this part. This is the most important part.
When the ad-hoc ping arrives on Tuesday, answer briefly and anchor back: “Covered in Friday’s update, third bullet. Happy to go deeper in our one-on-one.”
You aren’t being evasive. You are teaching every stakeholder that there is one main place where your status lives, and it is current.
The canonical update works because it gives your manager what they actually need which is a feeling of coverage. And it comes at a fraction of what the constant requests were costing you.
Building the update is the easy half. Getting your manager to actually let go of the daily check-ins is where I can help.
Scripts To Talk To Your Manager
Open with their need, not your frustration: “I want to make sure you always have what you need when leadership asks about my projects. Can we agree on what an ideal update looks like and how often you need it?”
Often the manager reveals the upward pressure driving everything, and you can shape the update to answer their boss’s questions directly.
That turns you into the person who makes your manager look prepared, which is the exact opposite of the person they need to frequently check on.
Then name the trade: “If I get you that every Friday, can we let go of the daily check-ins? The focused time will show up in more productive work.”
If they hesitate, propose it as a one-month experiment. Anxious managers say yes to reversible things.
If you have this conversation, run the system faithfully for two months, and the daily interrogation continues anyway, then the updates were never really about information.
That tells you something important, and it moves the situation into the territory I cover next.
For the fuller playbook on that dynamic, see my guide to dealing with a micromanaging boss.
Normal Oversight or Are You Being Managed Out?
I would be doing you a disservice if I skipped this part. Sometimes a sudden demand for written updates is not managerial anxiety but is documentation for PIP.
Here is how I help clients read the difference.
Context matters first: a new manager, a new project, or a company in turmoil resets reporting norms for everyone, and heavier check-ins in those moments are usually benign and temporary.
Reorgs in particular make scrutiny cascade through every layer, something I wrote about in what to do after a tough reorg.
The questions to ask are: Is this happening to my peers too, or only to me? Did it start after a specific conflict, a missed target, or a performance conversation?
Has the tone shifted from “keep me posted” to “confirm in writing”? Is the scrutiny arriving alongside other signals, like shrinking scope, exclusion from meetings you used to attend, or feedback that has suddenly turned vague and cold?
Selective scrutiny, a paper-trail tone, and shrinking scope together are a different situation than an anxious manager who pings too much.
If that cluster describes your situation, protect yourself calmly: keep your own dated record of what you deliver and what is said about it, get your accomplishments documented somewhere you control, and start thinking about your options before you are forced to.
Deciding What This Job Gets From You Next
Whether your situation turns out to be a fixable visibility problem or a genuine warning sign, the weeks you spend inside it are clarifying. Pay attention to what they tell you.
Some of my clients run the canonical update, reset the cadence, get their focus time back, and remember why they liked the job. Others fix the reporting problem and discover the resentment does not leave, because the scrutiny was a symptom of the culture.
If you suspect you are in the second group, my article on how to know it’s time for a career change will help you test that honestly.
And if you want help thinking it through with someone who has seen this pattern from the inside of big tech and from across hundreds of coaching conversations, that is exactly what I do.
You can read about how we can work together or book a complimentary clarity call.
You do not need to have it figured out first. Most women book the call precisely because they do not.
FAQ
How often should I actually be updating my manager?
For most senior individual contributors and managers, one structured weekly update plus a real-time flag for anything urgent is the healthy baseline.
Daily written updates are appropriate only in narrow cases: a launch week, an incident, a brand-new working relationship, or an explicitly agreed short-term arrangement.
If daily reporting has become permanent and you are senior, the cadence is serving someone’s anxiety rather than the work.
My manager suddenly wants everything in writing. Should I be worried?
First check for innocent explanations: new leadership above your manager, an audit or compliance push, or a team-wide process change.
If the shift applies only to you, started after a conflict or critical feedback, and arrives with other cooling signals like shrinking scope or vaguer feedback, treat it as possible documentation and respond in kind: keep your own dated records, deliver cleanly, and quietly widen your options.
You do not need a tidy answer before you reach out. Bring me the messy version and we will work out what this job is really telling you.