
The remote-days proposal, in one page
A proposal that argues for remote work loses. Write the coverage guarantee instead, with an override, a review date and a stated way to end it.
Your manager decides much of what your job feels like, and most of that relationship happens in short conversations. The posts here help you have them well: a first one-to-one agenda, a raise request written so it can be passed up the chain, a one-page proposal for remote days, a schedule change request that sticks, and a short way to say no to work that is not yours. They also cover the message to send after a mistake and how to stay visible on a hybrid or remote team.

A proposal that argues for remote work loses. Write the coverage guarantee instead, with an override, a review date and a stated way to end it.

The decision is made in a meeting you are not in. Your job is to arrive before it, in writing, with something your manager can carry.

A standing change is rarely refused. It is agreed and then it quietly never happens. What a scheduler needs from you, and how to make it stick.

A decline gets overturned because it was too long, not because it was too blunt. Every extra reason you give is one more thing to argue with.

The first hour is not for fixing it. It is for making sure nobody finds out from a customer, and that is a writing job, not a repair job.

Eight questions for one meeting, sequenced so the two that matter most are still answerable by the time you get to them.

A team's hybrid schedule collapses when the office day stops being worth the drive. That is a coverage problem, and tightening the rule makes it worse.

A green dot measures your mouse. What a manager can actually repeat about you is built from writing that travels, and that takes one note a week.