What it does
Requirement packets bundle several library requirements into one named checklist — think new-resident onboarding, annual renewal, site clearance, or offboarding. You build the packet once instead of assigning each requirement one by one. When assigned, each item becomes its own requirement on the person's checklist.
Who it's for
Institution administrators, program administrators, and coordinators work in the institution or administration portal. Recipients see its items as ordinary requirements on their personal checklist, grouped under the packet's name.
How it works
On the Packets page you select the Create packet button. This opens a dialog with a Name field, a Purpose dropdown, an Audience label, and a Description. Purpose is one of onboarding, offboarding, annual renewal, site clearance, or general. Audience is a free-text hint about who the packet is for. A packet can be institution-wide or scoped to one program. Packets can be searched by name.
You then add items to the packet from your requirement library. In the Checklist items panel, pick a requirement from the Add requirement field. Optionally set a Due offset days value, then select Add to packet. The offset is relative to the packet's start date, not a calendar date. This way the packet gives the right deadlines whenever it's assigned.
When a packet is assigned to a person, group, or program, the platform creates one requirement per packet item for each person. Progress is tracked per assignment — complete, missing, pending review, rejected, or overdue.
Before you start
You need permission to manage requirement packets in the institution or administration portal.
Add the requirements you need to the requirement library first. A packet can only pull from existing definitions.
Decide the packet's purpose and its scope — institution-wide or one program — before you create it.
Do this
Open the Packets page (
/requirements/packets) → you should see your packet cards with a search field.Select the Create packet button → the Create packet dialog opens.
Enter a Name, choose a Purpose, and add an Audience label and Description if you use them → select Create packet on the dialog → you should return to the Packets page and see the new card.
Select the new packet's card → the Checklist items panel opens on the right.
In the Add requirement field, search for and select a requirement, optionally set Due offset days, then select Add to packet → the requirement appears in the checklist items list with its due-offset badge.
Repeat step 5 on the panel for each requirement the packet needs → confirm the list shows every requirement you added.
You're done when
✓ The packet's card shows on the Packets page with its purpose badge.
✓ Every requirement the workflow needs appears in Checklist items.
✓ The packet is ready to assign — see the assigning-requirements article.
Boundaries and limits
Packet items must come from your existing requirement library. A packet cannot contain ad-hoc requirements outside the catalog.
Purposes are a fixed set: onboarding, offboarding, annual renewal, site clearance, or general.
An item's due offset is relative to the packet assignment's start date. Items without an offset fall back to the requirement's own defaults.
Packets are scoped to one institution. Program-scoped packets sit alongside institution-wide ones.
A requirement already in a packet drops out of the Add requirement search for that packet, so each one is added once.
Common questions
Q: What do assignees actually see when a packet is assigned? A: Each packet item appears as its own requirement in their personal checklist, labeled with the packet name, with its own status, due date, and instructions.
Q: Can the same packet serve different programs? A: Yes. Leave the packet institution-wide, or create program-scoped variants when programs need different item sets.
Q: Can items in one packet have different deadlines? A: Yes. Each item can carry its own due offset in days from the packet's start date.
Related articles