What it does
Every review cycle tracks a report with a readiness score from 0 to 100. Open blockers drive that score down: missing evidence, incomplete report sections, and overdue action items. When the review ends, the cycle can publish privacy-safe feedback summaries. That lets the people who gave responses see what came out of the review — closing the feedback loop.
Who it's for
Cycle managers watch the Report readiness card, resolve or waive blockers, and export the report packet. Respondents and reviewers work through goal-native review packets. Published summaries close the loop after the review, rather than appearing inside Forms. People with report-export permission can also generate the report packet document.
How it works
The Readiness checklist card lists the cycle's blockers next to a Report readiness score card. Blockers come from three sources. They are required evidence items declared at cycle setup, required report sections defined by the review type, and action items that go past their due date. Each blocker shows an owner, an optional due date, and a status badge — open, resolved, or waived. The readiness score is the share of blockers that are no longer open. A cycle with no blockers scores 100.
Export packet. When every blocker is resolved or waived and the score reaches 100, the Prepare export packet button turns on. Selecting it takes a manager, or anyone with report-export permission, to the document generator. That creates a report packet — a generated document shell linked back to the cycle. Until then the button stays disabled with a note that export unlocks once every blocker is resolved or waived.
Feedback summaries. To close the loop with respondents, a manager selects Publish feedback summary. The form asks for an Audience (respondents, faculty, learners, public, or committee), a Summary title, Summary text, a Privacy level, and an optional Visible after date. The organization-portal publisher only offers Public, Aggregated, and Committee privacy. Restricted and admin-only levels are only available from the institution portal. Leaving Visible after blank publishes immediately.
Before you start
Resolving or waiving a blocker needs cycle management access. A blocker's assigned owner can also act on their own blocker.
Exporting the report packet needs cycle management access or report-export permission at the cycle's scope.
Publishing a feedback summary needs cycle management access. Draft at least 10 characters of summary text — the form rejects anything shorter.
Do this
Open the review cycle's page (
/reviews/:cycleId) → you should see the Report readiness score card next to the Readiness checklist card.In the Readiness checklist card, review each open blocker's owner and due date → confirm which ones are yours to close.
For a blocker that's been addressed, select its Resolve button → the blocker's status badge changes to resolved and the score updates.
For a blocker that doesn't apply this cycle, select its Waive button instead → the badge changes to waived and the score updates the same way.
Wait until the Report readiness card shows 100%. Select the Prepare export packet button → you should go to the document generator with the review cycle preselected.
To close the loop with respondents, select Publish feedback summary. Fill in Audience, Summary title, Summary text, and Privacy, then select the Publish summary button → the summary appears with its privacy badge on the cycle.
You're done when
✓ The Readiness checklist card shows no blockers with an open status.
✓ The Report readiness score reads 100% and the Prepare export packet button is enabled.
✓ A generated report packet appears in the document library, linked to the cycle.
✓ Any published feedback summary shows the audience and privacy you selected.
Boundaries and limits
Open blockers must be resolved or waived before the export packet button turns on; there's no way to export while any blocker is open.
Resolving or waiving a blocker requires cycle management access. The exception: a blocker's assigned owner can update their own blocker.
Exporting the report packet requires cycle management access or report-export permission at the cycle's scope. The packet is a generated document shell — it does not compose narrative content automatically.
Report records cannot be hard-deleted.
The feedback summary publisher has no fields for themes or resulting goals. It only has audience, title, summary text, privacy, and an optional visible-after date.
A future visible-after date hides the summary from everyone except cycle managers until that date passes.
The organization-portal publisher restricts privacy to public, aggregated, or committee. Publish restricted or admin-only summaries from the institution portal instead.
Respondents see published summaries only — never individual responses or raw committee evidence.
Common questions
Q: Why is our readiness score stuck below 100? A: At least one blocker is still open. Check the Readiness checklist card for missing evidence, incomplete report sections, or overdue action items. Select Resolve or Waive on each one.
Q: Can we waive a required evidence item that doesn't apply this year? A: Yes. A cycle manager can select Waive on that blocker; waived blockers stop counting against readiness and record when they were closed.
Q: When do learners see the feedback summary? A: Once a summary addressed to learners, respondents, or public is published and its visible-after date has passed, if it has one. Until then only cycle managers can see it.
Q: Where does the exported report go? A: Selecting Prepare export packet opens the document generator, which creates a document in the document library linked to the review cycle.
Q: Can we publish a restricted or admin-only feedback summary from the organization portal? A: No. That publisher only offers public, aggregated, or committee privacy. Publish restricted or admin-only summaries from the institution portal instead.
Related articles