Skip to content

Benchmark Checklist

Available Roles: Docs contributor Platforms: Web Reviewed: 2026-03-14

Use this before publishing or revising any canonical page.

  • A clear workflow description, not only a feature definition.
  • Role clarity: who can do the action.
  • Platform clarity: where it works or differs.
  • Explicit settings or policy interactions.
  • At least one troubleshooting section.
  • Related task links that help the reader continue the workflow.
  • An opening that explains the task in plain language before any product framing.
  • At least one wireframe placeholder until screenshots are ready.
  • Ordered steps for setup or execution.
  • Notes on limits, rollout, or policy interactions.

Required on admin, security, IT, and mobile pages

Section titled “Required on admin, security, IT, and mobile pages”
  • Clear separation between workspace defaults, meeting-level controls, and downstream sharing when relevant.
  • A reference section or table when readers need to compare roles, platforms, or policy outcomes.
  • Explicit rollout status when the page describes preview or planned functionality.
  • A new reader should be able to complete the task without prior product context.
  • The page should reflect Hyper terminology, not generic competitor terminology.
  • The page should explain how the feature connects to prep, live meeting behavior, and follow-up when relevant.
  • The page should avoid internal placeholder headings and product-marketing claims that are not necessary for task completion.