I have now sent the same report to the same person ten Mondays in a row.

Nobody asked me for it. There was no request, no template, no meeting where somebody said "we should be tracking this." I built it in week one because I could not answer a simple question about the week before, and I have not missed one since.

It is the single most valuable thing I produce, and it is the only thing I produce that was entirely my idea.

That is not a coincidence, and it is not a story about diligence. It is a story about what a standing document does that a conversation cannot: it makes the same shape appear every week, and the shape is what lets a busy person notice a change.

Week three, nobody comments. Week seven, the principal starts referencing something from it in a meeting I wasn't in. Week ten, a decision gets made faster because the context was already in the room a month ago.

A standing report is a claim on attention, and you only get one

Understand what you are asking for. You are proposing that someone with a full calendar give you the same five minutes every week, forever, in exchange for something they did not request. That is a real transaction, and most people lose it in the first month by treating the report as a place to demonstrate effort. Long reports are almost always about the author's anxiety. If the document exists to prove you were busy, your principal will read it twice and then stop, and you will have spent your one standing claim on attention for nothing.

The test is simple and unforgiving. If nothing in the report could change what anyone does this week, it is not a report. It is a receipt.

The Four Blocks

Four blocks, one page, same order every week. The order matters more than the content, because the order is what makes it scannable in ninety seconds by someone reading it on a phone.

1. What moved. Three to five lines, past tense, finished things only. Not "continued work on the vendor agreement." Either it was signed, or it wasn't. In-progress items are not movement, and putting them here is how a report starts lying.

2. What's stuck, and who owns it. The name goes in the line. Not "pending legal review" but "with legal since the 14th, I'm chasing Thursday." A stuck item without a name attached is a stuck item nobody is going to unstick, and writing it down that way every week is how you find out which things have quietly had no owner for a month.

3. What I need from you. The whole document is this block. More on it below.

4. What I'm watching. Two or three lines about things that are not problems yet. This is the block that builds your credibility, because in about six weeks one of them becomes a problem, and you will have named it in writing before it did. Nobody forgets that.

The ask block is the whole document

Most people fill the first two blocks beautifully and leave the third one empty because asking feels like admitting you couldn't handle it.

Reverse that instinct. Put exactly one decision in the ask block every week, and make it small enough to answer in a sentence.

One is the number. Zero and you have trained your principal that this document requires nothing from them, at which point it slides down the pile. Four, and you have handed them a task list, and a task list from a subordinate function gets read last. One decision, framed with your recommendation already attached, gets answered on the spot roughly nine times out of ten.

The framing that works: here's the situation, here's what I'd do, tell me if you'd do something else. You are not asking them to solve it. You are asking them to veto or nod, which costs them four seconds and gives you written cover for a decision that is now as much theirs as yours.

The failure mode

The report becomes a performance.

It creeps in gently. You start writing for the record instead of for the reader. The lines get longer because a longer line sounds more substantial. Wins get restated. The stuck section gets softer because naming a stuck item started to feel like naming a person.

Two warning signs, and they are quiet ones. Nobody ever replies — not with a question, not with a correction, not with a "no, do the other thing." A document that never generates a response is not being Ocean Stride Advisory | Framer production copy 4 read, whatever anyone says in the hallway. And second: you notice you are writing it on Sunday night to have it ready, rather than assembling it Monday morning from things that actually happened.

The fix is not a better template. It is deleting the two blocks you like most and seeing whether anyone asks where they went.

One thing to try this week: Send one report nobody asked you for. One page, four blocks, exactly one decision in the ask block. Do it three weeks in a row before you judge whether it worked, because week one proves nothing. — Michael J Washington, Ocean Stride Advisory