Skip to content
For program managers who run the meeting

A prep checklist you can actually finish.

Most prep checklists assume you have an hour to read every board and thread. This one is built to be filled from the work itself, so you walk in knowing what changed.

Husn reads your tools - never changes them

Pre meeting checklist, filled from the work3 to know
  • A blocker you marked resolved last week is open again after a dependency slipped.
    Risk
  • The owner of the data migration changed on Tuesday and no handover note exists.
    Changed
  • An open decision from the last sync is still unrecorded and being debated in Slack.
    Watch
Checklist complete - 4 items confirmed - 1 needs a decision
The problem

Meeting preparation checklist for program managers

Program managers know what good prep looks like. The trouble is that running the full checklist means reading Jira, scanning Slack, and reopening last week's notes, and the time to do that rarely exists. So the checklist sits unticked and the meeting becomes the prep.

  • A real checklist asks you to confirm what changed across several tools, which is exactly the reading that never fits the calendar.
  • Open decisions and quiet owner changes are the items most often skipped, because they take the longest to verify.
  • When prep is rushed, the room finds the gaps live, and the meeting slows to the speed of catching up.
Why this gets hard at scale

Why the checklist breaks down at scale

01

The more workstreams you carry, the longer each checklist item takes, so prep gets cut on the weeks it matters most.

02

The change worth flagging is usually small and buried in a thread, the kind a quick skim will not surface.

03

A checklist is only as good as the reading behind it, and that reading is the part nobody has time to repeat every week.

How Husn helps
Step 01Husn reads Jira, Slack, and docs and fills the checklist for you, so you know what changed before the meeting starts.
Step 02It flags the open decisions, risks, and owner shifts each item asks about, traced back to where they happened.
Step 03You arrive with the checklist already complete and accurate, instead of half guessing in the last five minutes.

Husn reads and reasons, and never changes your tools.

What is inside

The sections, in the order leaders read them.

  1. 01What changed since last meeting, a short read of every shift across boards, threads, and docs.
  2. 02Open decisions, the calls still waiting and who needs to make them.
  3. 03Risks and blockers, what is at risk now and what is actively stuck.
  4. 04Dependency status, which cross team handoffs moved and which are at risk.
  5. 05Owner changes, where work changed hands and whether a handover happened.
  6. 06Asks for the room, the few things you need decided or unblocked in this meeting.
Use cases

Weekly program sync prep

Run the checklist in two minutes before your sync, with every item already confirmed against the work.

Standing up a new program

Use the same checklist each week so a new program builds a consistent prep habit from day one.

Covering for a colleague

Walk into a meeting you do not normally run with a filled checklist of what changed and what needs a decision.

Who this is for

Built for the people who have to keep it all straight.

  • Program and project managers
  • Delivery managers
  • PMO leads
  • Chiefs of staff
FAQ

Questions, answered.

  • What is on the checklist?

    What changed since last meeting, open decisions, risks and blockers, dependency status, owner changes, and the asks you need to put to the room.

  • Do I still have to read everything myself?

    No. Husn reads Jira, Slack, and docs and fills each checklist item, with a source link so you can confirm anything in seconds.

  • Can I change which items appear?

    Yes. The checklist is yours to shape, and Husn fills the items you keep against your actual program.

  • Does it write anything back to our tools?

    No. Husn reads to fill the checklist and never writes to Jira, Slack, or docs.

Know what changed before your meeting starts.

Finish your prep before the meeting starts.

Connect your stack and Husn will fill your prep checklist for the next sync in about fifteen minutes, so you know what changed before you walk in.