Conditional application steps
Keep application summaries aligned with changed answers
Capture the earlier answer that changes a later step, then show whether the final summary follows that branch.
- ✓Inactive answers remain in summaries
- ✓Required fields outlive their branch
- ✓Backward navigation loses orientation
Application-form evidence across branches
Branch-aware reproduction
Preserve the answer change that makes a later summary field irrelevant.
Hidden-data policy made explicit
Separate clearing inactive answers from omitting them in the current application view.
Step recovery with clear limits
Define visible navigation outcomes without claiming submission or eligibility verification.
Pick a branch that changes later questions
A multi-step application form can collect different information depending on an earlier answer. In your product, prepare a fictional applicant and choose a branch that reveals an additional field. Capture the step indicator, initial answer, conditional section, and final summary. Record the intended branching rule and required fields from your test setup. Use invented names and addresses so the review does not expose real applicants or documents containing personal information.
Record a backward change across steps
Complete the conditional branch, advance to the summary, return to the earlier question, and choose the alternative answer. An example issue is Application summary retains an employer field after the applicant switches to the student branch. Show both the changed answer and the stale summary line. Keep that inconsistency separate from whether the form should retain hidden answers for later editing. A submitted screen alone does not prove the application reached a reviewer or passed eligibility checks.
Define the approved summary boundary
Capture with Retick or upload supported screenshots and recordings. Review AI candidate issues, edit assumed submission outcomes, reject eligibility conclusions, and annotate the irrelevant summary field. Example acceptance criteria: the summary reflects the active branch; required-field feedback matches the questions currently presented; and returning between steps preserves answers according to the product-approved policy. Have the application owner decide whether inactive branch data is cleared or simply omitted before the issue describes that behavior as mandatory.
Revisit recovery and step navigation
After implementation, manually repeat with an incomplete required field, a long answer, and cancellation before submission. Check the step indicator and keyboard focus after moving backward. Validate persistence, actual submission, eligibility rules, and document handling in your own application tests and operational systems. Retick does not process applications, verify applicant information, or establish regulatory compliance. Remove sensitive material before capture; do not expect automatic redaction of form answers or attachments.
Download reviewed findings as a file handoff, or export selected issues from the individual media item to an accessible Trello board and list. Include the original branch, changed answer, and approved hidden-data policy so the receiving developer can reproduce the stale summary without guessing at application rules.
Review a changed application answer
Show the branch switch and the summary that should follow it.