Skip-Level Meeting Template — Free Agenda & Question Bank

A meeting where a senior leader sits down with someone two levels below them — their direct report's report — without the manager in the room. It exists to hear how work really flows before that signal gets smoothed out on its way up the chain. Run well it is the highest-signal half hour on a leader's calendar; run badly it is a rumor generator. The fix is structure: a stated purpose, a timed agenda, and clear confidentiality ground rules.

Five timed blocks for a 45-minute meeting: 5 minutes to open and restate the purpose out loud, 15 minutes on their actual work (wins, what is harder than it should be), 10 minutes on friction and process between teams, 10 minutes on manager support and growth, and a 5-minute close where you commit to one thing you will look into. Keep the manager topics in the middle third — leading with them turns the meeting into an inspection.

Pick three to five, not thirty. Open with the work ("what are you building that you're proud of?"), move to friction ("where does work get stuck between teams?"), then manager support, and always close with "what's one thing you'd like me to look into before we talk again?" The single highest-signal question: "what question do you wish I would ask?" — it hands them the agenda and almost always produces the most useful sentence of the meeting.

Quarterly is the standard cadence for most organizations, monthly during heavy change, with every engineer or IC who reports to your direct reports on the rotation. Consistency beats frequency: a predictable quarterly rhythm compounds trust in a way one-off "let's talk" invites never do. New hires and teams going through transitions deserve more frequent slots.

Yes — always, and it is the single biggest failure point for skip-level programs. A manager who learns about the meeting from their report's calendar reads it as a signal of distrust, and that manager's behavior changes for weeks. Explain what you are doing, why, and that it is a regular rotation for the whole team — then share the aggregated themes back with them as support, never quotes.

State the ground rules out loud at the start: this is a conversation, not an evaluation; nothing goes to a performance review; you share themes, never names, and even a "helpful detail" can reverse-engineer its source. If you hear something serious — harassment, safety — say plainly that you must route it properly, and do. Confidentiality is a norm, not a guarantee, and honest leaders say that too.

Four failure modes: making it an evaluation (pointed questions that signal "checking up"), assigning work directly, overriding a manager's decision in the room, and fixing things on the spot. Take notes, don't promise, and bring what you heard back to the manager afterward — the work happens after the meeting, with your direct report, not in front of theirs.

Yes — and locally, which matters here. VocalFuse transcribes the conversation on your Windows PC with Whisper: no meeting bot joins the call, and no audio is uploaded, which is exactly the discretion a skip-level needs. Pro Note Turning then drafts the notes into this template's structure — wins, friction, commitments — and you verify and approve before anything is saved or shared.

A 1:1 is between a manager and their direct report, weekly or biweekly, and the report drives it — it is for coaching and unblocking. A skip-level skips the manager entirely: the senior leader runs it, cadence is quarterly, and the goal is unfiltered signal about how the organization actually works, not coaching. If your skip-level turns into a status update or a performance conversation, it has stopped being a skip-level.

Yes — the .docx on this page is free with no email gate. It includes the 45-minute agenda table, a grouped question bank for every rotation, a notes section, the confidentiality ground rules, and a before-the-meeting checklist. It opens in Word 2016+, Word on the web, and Google Docs, and the page also gives you the copy-paste plain-text version below.