This article is written as a working review tool rather than a universal formula. Apply the parts that match the product, evidence and constraints in front of you.
Document priority before breakpoints
Start by identifying which information must remain visible, which actions are primary and which elements can collapse, move or become progressively disclosed. That decision is more reusable than a list of pixel values.
Breakpoints then become moments where the existing hierarchy needs a different layout, not arbitrary device categories.
Tables need a strategy, not horizontal optimism
For each table, document what remains visible on narrow screens, whether rows become cards, whether secondary columns can hide and how filters or row actions remain reachable.
If horizontal scrolling is necessary, make the important identifier sticky or persistent enough that values still have context.
Explain filter and sidebar behavior
State whether filters become a sheet, drawer, collapsible region or inline control. Define how active filters remain visible after the panel closes and how users clear them without reopening the entire control surface.
Sidebars need the same treatment: what becomes navigation, what becomes contextual control and what can disappear.
Include empty, loading and error layouts
Responsive handoff often documents the populated dashboard only. Empty states, skeletons, permission states and errors can have very different height and spacing behavior, especially on smaller screens.
Show the rules that keep those states legible without creating layout jumps or hidden actions.
Give engineering acceptance criteria
Write a short set of outcomes the implementation should satisfy: no horizontal page overflow, primary actions remain reachable, 44px mobile targets, readable table context and no content hidden behind fixed navigation.
Acceptance criteria turn handoff from a visual reference into a shared definition of responsive quality.