Skip to content
Everything that matters, one page

One page, the whole truth.

A status report should fit on one screen and still say something. This template holds the six things a reader needs, and Husn can fill it from the work so it stays current.

Husn reads your tools - never changes them

One-page status, this week3 to know
  • The next milestone slipped four days and now lands after the demo it was meant to support.
    Decision
  • A risk that was amber last week is now red after the staging environment failed twice.
    Changed
  • A dependency on the platform team has no committed date and no owner since the reorg.
    Watch
1 page - 1 decision needed - 1 milestone at risk
The problem

One-page project status report

Most one-pagers are one page in name only, then a second page of caveats and a third of charts nobody opens, because no one was willing to decide what to leave out.

  • The headline ends up below the fold, so a busy reader closes the page before they reach the line that mattered.
  • Risks and decisions get folded into a paragraph of progress, where they read as background instead of a prompt to act.
  • The single page is accurate the day it ships and wrong by the next meeting, because nobody updates a static document.
Why this gets hard at scale

Why this gets hard at scale

01

Fitting a real project onto one page forces choices about what to cut, and under deadline those choices fall to whoever is least informed.

02

A one-pager per project is fine. Forty of them, kept current by hand every week, is a job no one has time for.

03

The discipline that keeps a page short is the first thing to go when the news is bad, which is exactly when brevity helps the reader most.

How Husn helps
Step 01Husn reads Jira, Slack, and docs and fills each section of the page, leading with the headline and the decisions, not the activity.
Step 02It keeps the page current as the work moves, so the version someone opens on Thursday reflects Thursday, not Monday.
Step 03Every line on the page links back to the issue, message, or document behind it, so a reader can check any claim without leaving the page.

Husn reads and reasons, and never changes your tools.

What is inside

The sections, in the order leaders read them.

  1. 01Headline: the one sentence a reader would repeat if they only remembered one thing.
  2. 02Status: overall health with a plain reason, not a color alone.
  3. 03Key changes: what moved since the last report, and why it moved.
  4. 04Risks: what could go wrong, how likely, and who is watching it.
  5. 05Decisions needed: the specific calls waiting on a leader, with the cost of waiting.
  6. 06Next milestone: the next date that matters and the confidence behind it.
Use cases

Weekly distribution

Send one page per project that opens with the headline and ends with the next milestone, ready to read in under a minute.

Quick stakeholder check-in

Hand a sponsor a single page that answers where things stand without scheduling a meeting to explain it.

Standard format across teams

Give every team the same six sections so a reader knows where to look no matter whose project it is.

Who this is for

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

  • Delivery and program managers
  • TPMs and EPMs
  • Chiefs of staff
  • Heads of engineering and product
FAQ

Questions, answered.

  • What sections does the one-pager include?

    Headline, status, key changes, risks, decisions needed, and next milestone. Six sections that hold what a reader needs and nothing they do not.

  • Can Husn keep the page up to date?

    Yes. Husn reads across Jira, Slack, and docs and refreshes each section as the work moves, so the page reflects the current state, not last week's.

  • Can I verify what is on the page?

    Yes. Every line links back to the source it came from, so any claim can be checked in a click.

  • Does Husn change anything in our tools?

    No. Husn reads and explains only. It never writes back to Jira, Slack, or your documents.

Generate executive briefings automatically.

Put the whole project on one honest page.

See the one-page status Husn would write from your own tools, in about fifteen minutes.