Skip to main content

Requirement Sequencing: Setting Requirement Order and Requiring Completion in Order

How to set the order of your requirements, and how to require members to complete them in that order, for example so a cleared background check comes before everything else.

You choose the order members see their requirements in. You can also require members to complete them in that order, one at a time. For example, members can be required to clear their background check before they can start training, certifications or document uploads. Both settings are on your Requirements page.

Setting the order of your requirements

  1. In the left sidebar, click Requirements.

  2. Under your active requirements, drag each requirement up or down into the order you want.

  3. Users will see their requirements in the same order that is set in the requirement library.

Members see their requirements on their profile in this order. If you turn on completion in order, this is also the order they must follow.

Requiring requirements to be completed in order

  1. In the left sidebar, click Requirements.

  2. In the top-right, turn on the Require Requirement Order Completion toggle. The setting saves right away.

  3. Check the order of your active requirements. Members will work through them from top to bottom.

To turn it off, go back to Requirements and turn the toggle off. All assigned requirements become available again right away.

What members see

  • A message at the top of their requirements list says the requirements must be completed in the order shown.

  • Only the first incomplete requirement can be started. Each requirement after it shows a lock icon, and its button stays disabled until the requirement before it is complete.

  • This also applies to child profiles that a parent or guardian manages.

Things to know

  • It applies to your whole organization. You can't turn it on for only some programs or roles, and you can't set a different order per role.

  • A requirement must be Completed or Expiring Soon before the next one unlocks. Any other status, including Pending Review, keeps the next requirement locked. For example, if a background check is waiting on an admin decision, the member's next requirement stays locked until an admin approves it.

  • Unassigned requirements are skipped. Members only follow the order for the requirements assigned to them. Anything not assigned to them is ignored.

  • Optional requirements are skipped. An optional requirement never holds up the next one, and members can complete it at any time.

  • Admins aren't blocked. Admins can complete, upload or review any requirement on a member's profile at any time, in any order. To see what a member sees, log in as a test member.

  • Members can't skip a requirement. If a requirement doesn't apply to someone, un-assign it or make it optional for them.

Common questions

A member says their requirement is locked. What should I check?

Look at the requirement just above it on the member's profile. If it's in progress, pending review or waiting on a provider, the member has to wait until it's complete. If it's waiting on your review, approve it from the Review Requirements page.

Can I put the background check first?

Yes, that's the most common setup. Drag the background check to the top of your active requirements and turn on the toggle. Members can't start anything else until their check is cleared.

Does changing the order affect requirements members have already completed?

No. Completed requirements stay completed. The new order applies to whatever members still have left to do.

Need help?

Did this answer your question?