You clicked through your own signup last week. Every page loaded, every button worked, the form validated, and you marked it passing. Then a new user reported they never got the verification email, got it 40 minutes late, and the link had already expired. Your review never saw that, because your review stopped at the screen.
Signup is not a sequence of pages. It is a sequence of pages and the emails those pages trigger. The confirmation, the verification link, the welcome note, the password reset: each one is a step a real person has to complete, and each one happens outside the browser tab you were reviewing. A flow walkthrough that follows the whole signup includes the emails it sends, because that is where a lot of quiet abandonment lives.
Capture the email as a step, not an afterthought
When you run the signup, treat the inbox as part of the flow. After you submit the signup form, switch to the inbox, wait, and capture the email that arrives. Screenshot the whole thing: the sender name, the subject line, the time it landed, the body, and the button or link a user is supposed to click. Pin the call to action and note where it goes.
Why this works: the email is a real page in the journey, and it carries decisions a user has to act on. If the sender shows as a no-reply with no brand name, if the subject is vague, if the verification button is below three paragraphs of legal text, a user stalls there. A screen-only pass records that your signup page is clean and misses that the step after it is confusing.
The failure mode when you skip it: you ship a signup that tests perfectly in a demo and leaks users in production. Support starts fielding "I never got the email" tickets, and nobody can reproduce it because the page always worked. The break was never on a page.
Time the email and write down the delay
Note the clock. Record when you submitted and when the email arrived. Thirty seconds is fine. Three minutes is a problem, because a user who has to verify before they can continue will not sit on an empty inbox for three minutes. They close the tab.
This matters more than it looks. Delivery delay is invisible on a page review and invisible to the developer who built the send, because in a clean test environment the email fires instantly. Capturing the real delay, with a timestamp in your comment, gives whoever fixes it a concrete number to chase instead of a shrug. A walkthrough you capture as you go leaves that timestamp in the record.
The failure mode: the email is correct in every way except it arrives late, and because "it works" nobody files it. The drop-off shows up only in your funnel numbers weeks later, with no clue what caused it.
Click the link from the email, do not jump back to the tab
Here is the one most page-only reviews get wrong. After the email arrives, click the link from the email, the way a user would, instead of flipping back to the browser tab where you started. The link in the email is its own thing. It can be expired, point to the wrong environment, open a page that assumes you are already signed in, or dump you on a generic dashboard with no sign you just verified anything.
Walking it this way catches the mismatch between what the email promises and what the link delivers. A "Confirm your account" button that lands on a login screen asking for a password the user has not set yet is a dead end, and you only see it if you follow the actual path. Capture that landing page as its own item, pin the confusing part, and say what you expected to see instead.
The failure mode when you skip the link: your signup review certifies the full flow as working while the single most fragile link in it, the one that leaves your product and comes back, goes untested. That is the link users complain about most, because it is the one that breaks silently.
What the finished review looks like
Each email and its landing page becomes an item alongside the screens. Numbered pins mark the call to action on the email, the delay goes in the comment, and the page the link opens sits right after it in order. Whoever reads the review sees the signup the way a user lived it: page, email, click, landing, in sequence, with the timestamps baked in.
You can publish that as a link the receiver reads without logging in, export it as a PDF for a stakeholder, or send it as clean markdown an agent can act on. If you want to compare this against a lighter pass, an onboarding feedback pass covers different ground: the flow walkthrough is the one that names the single flow and walks every step including the emails, while an onboarding pass reacts to first impressions across the product.
Cobalt Capture runs in a browser tab with no install and no extension, and you can try it on your own signup for free, with reviews editable for seven days before they go read-only unless you keep them open on the $5 Pro plan. See the full pricing and the 7-day rule before you start, then capture your first email step the next time you walk your own signup.