One code on the screen
Open the meeting, put the code full screen, and it fills the display on a plain white plate so it still scans from the back of a room. The typed-out link sits underneath for anyone whose camera will not cooperate. From there it is their phone, two or three questions, and done: the answers land against the meeting, and nobody passes a laptop around or reconstructs the list from memory an hour later. The step that used to cost the most was never the collecting, it was the part afterwards where somebody typed a clipboard into a spreadsheet that then lived in their downloads folder. There is no such step here, which is the only reason a team keeps doing it every week.
Check-in questions
A check-in can carry questions, so the thirty seconds where everyone has their phone out is worth something. Who is blocked, what did you get done this week, which subsystem do you want to work on next. Questions come in the shapes you would expect, yes or no, pick one, pick several, a line of text or a paragraph, and each can be required or optional, so a form that takes ten seconds stays a form that takes ten seconds. Answers land on the meeting record next to the attendance list rather than in a separate tool nobody exports from.
Downloading and rotating the code
Download it as a PNG, a JPEG or an SVG, or copy the image straight to the clipboard and paste it into whatever you were already showing. The SVG matters more than it sounds: a code printed on a poster or dropped into a slide at full size stays sharp instead of going soft at the edges, which is where scanning starts failing from the back of a room. If a code ever leaks beyond the room, rotate it and every copy of the old one stops working immediately.
What the attendance record is for
Who attended is kept against the meeting, so a review whose required approvers never showed up is visible as exactly that. For a team that turns over every year it is also the trail that tells next year's leads who was actually across a decision, which a headcount in a spreadsheet never does. On a meeting that repeats, a set of check-in questions can be applied to the rest of the series in one go, so a weekly build meeting asks the same three things every week without anybody rebuilding the form each time.
The meeting page was rebuilt
It used to be a form with the notes bolted on. It is now built around the record: the recorder, the transcript, the briefing, attendance and access all sit on one page in the order you use them, with skeletons while things load and a real error screen instead of a blank panel when something fails. Private meetings carry their own access list, so a leadership discussion and a general build meeting can live in the same project without sharing an audience.