Ask first: five designs for the step before the intake

The ticket adds one screen between "Scan starten" and Step 1: staff confirm the customer is 18 or older and has none of the 14 alarm signs, or stop the scan. Every screen below is live: tick, tap, stop, and go back. Copy is the ticket text; new words are marked in the design notes. Round 2 (design F, first below) answers the request to make it one tap on one screen; designs A to E are round 1.

Where the step sits

Home"Scan starten"

Eerst vragennew route, outside the intake

Step 1replaces the gate; intake starts here

Steps 2 to 9, captureunchanged

Eerst vragen"Scan stoppen" (or back)

Geen scanterminal

Home"Terug naar start", back arrow or Android back

The gate is its own route in the app navigator, before the intake route, so the intake context (participant ID, intake_started) mounts only after "Intake starten". A stop leaves nothing behind (AC9) without touching the intake code.
"Intake starten" replaces the gate with Step 1, so back from Step 1 still lands on Home with the existing "Scan stoppen?" dialog (AC10), and the gate never reappears mid-intake.
Back from "Geen scan" goes Home, not back to the gate: the stop screen is a decision, and a mis-tap costs one tap on "Scan starten" to recover.
The intake header reads the intake context to guard logout, so the gate needs that header without the context (nothing to discard yet).

One change in all five: the stop screen order. In the ticket order the under-18 instruction comes after the 14 signs, about three screens down on a 360 × 640 phone, and the screen opens with "Always refer the customer to a doctor". For a 16-year-old without complaints that first instruction is the wrong one. All five designs put both cases first, as plain lead-ins, and start the list directly under "Verwijs de klant altijd door naar een arts", so "deze klachten" points at it and "de SEH of 112" shows without scrolling on 360 × 640.

Two smaller moves on that screen: "Er wordt niets bewaard." sits under the title instead of in the footer (at large text a two-line footer ate the scroll area), and the list title "Alarmsignalen: niet scannen" is left out, as it repeats "Geen scan".

Comparison and recommendation

Round 2: F, one tap

One question with two answers that are also the actions, and the full list one tap away. It fits one screen without scrolling, with 148 dp to spare on 360 × 640. Continuing is one tap, stopping is one tap.
The trade: the list is optional, so a staff member who forgot the training can answer without seeing a sign. If the regulatory follow-up asks for the signs on the gate itself, D is the fallback: the same idea with the list in the second card, at the cost of two ticks and a scroll.
Ticket impact: AC2 to AC5 go from two confirmations to one question, and there are five new strings (the question, the two answers, an example line and the link).

Round 1 recommendation: D, the list belongs to the confirmation

The second statement and the signs it covers are one card, so "hieronder" points into the card and a first-time staff member meets the signs at the box they tick.
The largest reading window of the four sticky-footer designs (398 dp on 360 × 640, against 338 dp in A and E), and the only one where "de SEH of 112" shows on the gate without scrolling.
No new strings, and the intake look holds: same header, cards and footer surface. Its footer pair follows the app's own side-by-side pair in the "Scan stoppen?" dialog.
Its weak spot was the side-by-side footer at large text. The buttons now grow instead of clipping; in the app the footer should stack once the system text size is above about 1.15.

The others

A, second. The cleanest on craft and closest to today's intake, but the list sits apart from what it confirms and reads in the smallest window.
C, third. The strongest guarantee that staff pass the signs, and the most robust at large text. It costs about three screens of scrolling on every scan, and it is the only intake screen without a sticky footer.
E, fourth. Group panels keep the group visible while scrolling; the panels could be added to D's stop screen later if staff mix up the groups. The first-round red and orange tints were dropped: they shared the error red, read as one pink at a glance, and showed on every scan.
B, fifth. The fastest stop for an under-18 or alarm case, but four new strings, the longest page, and a main button that changes its label.

Carried into the build, whichever design

The gate is its own route before the intake. "Intake starten" replaces it with Step 1. The stop screen goes Home on "Terug naar start", the back arrow and Android back.
The intake header works without the intake context on the gate, and without the progress bar its border and the band border must not stack into a 2 dp line.
A tap on the muted "Intake starten" marks the first unticked statement and scrolls to its checkbox row, as the intake steps do today.
"Terug naar start" ignores taps for about half a second after the stop screen opens, so a double tap on "Scan stoppen" cannot skip the referral.
Buttons use a minimum height of 48 dp, not a fixed height. The sign number column grows with the text size. The header title is capped at 1.3 times text size, as the session cards already are.
Keep two deliberate differences from older screens: statement text at 16 px ink (the Step 9 grey fails contrast) and secondary button text in #4D757F (#6796A2 fails contrast).
Two-button footers use 16 dp padding and a 12 dp gap (side by side: 10 dp, as in the "Scan stoppen?" dialog); single-button footers keep 24 dp.
The checked statement shows the tick icon that already exists in the shared UI package, not the Step 9 ring, so two stacked circles do not read as a pick-one choice.