What it does
The requirement library is your institution's catalog of reusable compliance items — immunizations, licenses, certifications, trainings, background checks, attestations. Each entry sets what people must provide and how they complete it. It also sets default deadline and expiration rules.
Who it's for
Institution administrators, program administrators, and coordinators manage the library in the institution or administration portal. Assignees only see requirements assigned to them.
How it works
From the Library page, create a requirement definition with a name, a description, and a type.
Types. Twelve are available. They are general, contract, compliance, credential, license, certification, attestation, document, and training. The rest are immunization, background check, and other. A Categories page shows all twelve.
Each definition also sets the submission mode — how the requirement gets completed:
Document upload — the person attaches one or more files as evidence.
Attestation — the person confirms a statement instead of uploading anything.
External task — the person does work in an outside system, then marks it done. A URL link is optional.
Admin verification — staff complete the requirement for the person. The assignee has nothing to submit.
Behavior settings. Each definition can require reviewer approval, set a default number of days until due, and add instructions or help text. You can also add an external URL, set an expiration window, flag a supporting document, or mark it admin-only. Deactivate a definition without deleting it, or limit it to specific programs.
On the Settings page you maintain requirement tags. These are institution-level labels with a name and color that help you organize the catalog.
Before you start
You need permission to manage the requirement library in the institution or administration portal.
Decide the submission mode before you start — document upload, attestation, external task, or admin verification — since it changes which fields the dialog shows.
If this requirement should only appear for certain teams, know which programs to link before you save.
Do this
Open the Library page (
/requirements/library) → you should see your institution's requirement cards with a search field.Select the Create requirement button → the Create requirement dialog opens.
Enter a Name and, if you use one, a Description. Choose a Type and a Completion mode from the dropdown → picking external task adds an External task URL field.
Fill in Default due days, Instructions, and Acceptable evidence as needed. Toggle Requires review if submissions need a reviewer. Toggle Expires / requires renewal if evidence should lapse after a set number of days → the Valid for (days) field appears.
Select Create requirement on the dialog → you should return to the Library page and see the new card in the grid.
You're done when
✓ The new requirement card appears on the Library page with its type and completion-mode badges.
✓ The requirement is available to add to packets or assign directly.
✓ Any program links you set control which teams can see it.
Boundaries and limits
Requirement names must be at least 3 characters.
The library lives in the institution and administration portals only. It is scoped to one institution, with no cross-institution sharing.
Deleting a definition is a soft removal and needs the right permission. History is not destroyed.
The twelve requirement types and four submission modes are fixed. You cannot define custom ones.
Tags are labels for organization only. They do not change assignment or review behavior.
A definition with no program links is available institution-wide. Program links narrow that.
Common questions
Q: What is the difference between a requirement type and a submission mode? A: The type describes what the requirement is — a license, an immunization, a training. The submission mode describes how it gets completed — upload a document, attest, finish an external task, or wait for admin verification.
Q: Can I retire a requirement we no longer use? A: Yes. Deactivate it so it can't be used for new assignments, or delete it. Deletion is a soft removal, so existing records stay intact.
Q: Can a requirement complete without anyone reviewing it? A: Each definition controls whether submissions need approval. When approval is required, submissions wait in the review queue until a reviewer approves or rejects them.
Q: Can I hide a requirement from programs it doesn't apply to? A: Yes. Link the definition to specific programs to scope where it is visible.
Related articles