Formatting is not what signals presence
It would be easy to tell you that a clean, professional packet signals executive presence before anyone reads the details. I'm not going to, because I've already published the opposite. When someone tells you to work on your executive presence, it usually means how you communicate under pressure is undercutting how capable you clearly are. It's a communication gap, not a wardrobe note. Presentation doesn't read as presence before the content is read. Only the content does.
What actually matters about form is narrower and more useful. The test isn't polish. It's portability. If your manager could not repeat your point to the board without translating it first, it isn't ready. Clear enough to travel is the bar, every time.
The five parts of the packet
Your packet is a value brief with five parts, the same five that belong in any case you make for yourself.
- Money and time. What you saved, what you earned, what you shipped faster. Delays you prevented count as much as revenue you added.
- Scale and scope. Teams you built or led, budgets you managed, the size and stakes of what you were trusted with when it was hard.
- Before and after. The state of things when you arrived and the state of things now, named in the reader's terms, not yours.
- Proof. For every claim, a source you could point to on request: a dashboard, a report, a colleague who would confirm it. A claim you cannot back is a claim you should cut.
- The gap you're ready to close. The problem the next level is trying to solve that your work already speaks to. This is the bridge from what you've done to why you're the bet.
Add two more sections around that core. A summary paragraph at the top naming your current title, the title you're asking for, and the scope you've absorbed since your job description was written. And a continuity plan at the end: who covers your current work after you move, what stops, and what the first ninety days look like.
The test that tells you a section is not finished
Each part has its own version of the same test.
- The summary isn't done if it needs a second paragraph to make sense. Someone should be able to read it aloud in a meeting and understand the request.
- A line in the value brief isn't finished if a reader could answer it with compared to what. Attach the baseline every time.
- Sponsorship isn't real if every name in the section reports to your own manager. At least one name has to sit outside that org.
- The continuity plan isn't done until someone else's name appears in it besides yours.
Keep it tight and send it twice
Keep the whole thing short, send it as one file, and put the summary paragraph in the body of the email too. The person who has to argue for you may never open the attachment before the meeting.