Skip to content

Produce a board report

A board report is a written document assembled inside Humavera for the people who read board papers rather than dashboards. It carries an executive summary and however many sections you write, and it moves through review and approval before it is published.

Required role: Administrator.

  1. Go to Performance → Insights → Board Reports.
  2. Select Create Report.
  3. Enter the Title and the Period.
  4. Optionally write the Executive summary now, or leave it for later.
  5. Add each Section, giving it a title and optionally its content.
  6. Select Create report.
  7. Open the report and select Edit to write or revise its sections.
  8. Select Submit for Review when the content is complete.
  9. Select Approve and confirm, once the report has been reviewed.
  10. Select Publish and confirm, when it is ready to circulate.
OptionDescription
DraftBeing written. Content can be edited freely.
In ReviewSubmitted for review.
ApprovedReviewed and accepted, and eligible for publishing.
PublishedFinal. A published report is read-only.

Publishing is the state to understand before you reach it. A published report cannot be edited. The confirmation says so before you publish: further edits require creating a new report. That is what makes a published report safe to circulate — the copy in the board pack is the copy in the product.

Example: HC Corp publishes its Q2 2026 board report and then finds a figure moved. The published report stays as it is, and the correction goes into a new report rather than silently rewriting a document the board has already read.

Both actions belong to an administrator in your own workspace. Nothing about a board report waits on anyone outside your company, so a report can be written, reviewed, approved, and published without leaving your team.

Submitting for review moves the report to In Review, where an administrator can approve it. Approving moves it to Approved and makes it eligible for publishing. Publishing is the last step and the irreversible one.

The report records who approved it and on what date, and shows that on the report itself. That is the audit trail for a document the board will act on, so approve under your own account rather than sharing one.

Example: Sophie Clarke writes HC Corp’s quarterly report and submits it. Daniel Okonkwo reviews and approves it, and his name and the date are recorded on the report. Publishing then fixes it.

Editing remains available to an administrator at every state except Published, so a report can go back and forth between drafting and review as often as it needs to before anybody publishes it.

OptionDescription
TitleThe report’s name.
PeriodThe period it covers, as you typed it.
StatusWhich of the four states it is in.
AIWhether the report carries a generated summary.
SectionsHow many sections it has.
Created byWho created it.
CreatedWhen it was created.

The Status filter narrows the list, which is the quickest way to find what is waiting on you.

The Executive summary is a single block at the top. Sections are titled blocks beneath it, added and reordered from Edit, and a section can be created with a title and filled in later.

Example: HC Corp’s quarterly report runs headcount and cost, capability and skills, retention and risk, and progress against the year’s goals — four sections, each written by whoever owns that area, assembled into one document.

Two AI-assisted outputs are available on a report.

OptionDescription
Generate AI SummaryProduces a summary of the report. It appears separately, and Use as Executive Summary copies it into the executive summary field.
AI Q&A PrepLikely questions and prepared answers, populated when the summary is generated.

The generated summary is a draft you own, not the report’s voice. It is written from what is already in the report, so read it against your own sections before you accept it — and edit it, because a board report goes out under your name.

Question prep exists for the meeting rather than the document. It is a rehearsal aid, and it is only as good as the content it read.

A published report is a fixed record of what the company reported and when, which is the point of the state machine. Company goal health, workforce figures, and capability analysis all read more usefully into a board report than into a live dashboard, because a board wants a position at a date rather than a screen that has moved by the time they read it.