A requirement can now have more than one valid answer
Requirements like a TB status check can be satisfied by a titer, a vaccine record, or a signed declination — tracked as one task with options, not three separate ones. The questions behind them can branch based on the answer and be answered over text or email.
A requirement like "TB status established" can honestly be met a few different ways — a lab titer, a vaccination record, or a signed declination. Treating each path as its own separate task confused candidates (which one do I actually need?) and cluttered the requirement list for staff.
Requirement pathways track all the valid ways to satisfy one requirement as a single item. A candidate sees one clear task; staff can see which path applies and why, and switch it if circumstances change.
The questions that drive this are smarter too. They can now branch — a candidate only sees the follow-up questions relevant to their first answer — and can be asked and answered over text or email, not just inside the portal. In many cases, the answer itself is what resolves the requirement: pick "Positive titer," and that pathway activates and the task closes, without a separate manual step.
See it work a real file.
Thirty minutes, one placement, worked live — start to submit-ready.