What it does
The personal Requirements page is your compliance checklist. It lists every requirement assigned to you with its status, due date, and instructions, and is where you complete, track, and resubmit them.
Who it's for
Anyone with assigned requirements — learners, faculty, and staff — uses this page in the personal portal.
How it works
The page opens focused on items needing your attention. Summary cards show Total, To Do, Pending, Completed, and Rejected counts — select one to filter, or search and filter by status, type, due date, or date created. Packet items show the packet name underneath; overdue items show a warning icon next to their due date.
How you complete an item depends on its submission mode:
Document upload — attach one or more files (at least one is required), optionally add a certification number, an expiration date, and notes, then submit.
Attestation — check the confirmation statement, optionally add a comment, and complete.
External task — follow the provided link to the outside system if there is one, do the work there, then return and mark it done.
Admin verification — nothing to submit; your program team completes it for you and the drawer says so.
Submissions needing approval move to pending review. If rejected, the requirement returns to your list with the reviewer's reason and a resubmit action to correct and resend. Approved and pending submissions stay viewable, including attached documents.
Before you start
The requirement must already be on your checklist — an administrator or a packet assignment puts it there.
For document upload, have your file ready. Accepted types are PDF, JPG, JPEG, PNG, DOC, and DOCX, up to 10 MB each.
The requirement must be in an actionable state: incomplete, in progress, overdue, or rejected. Approved items can't be resubmitted.
Do this
Open the Requirements page (
/requirements) → you should see your checklist with status summary cards.Find the item you need to finish and select Complete on that entry → a panel opens with the requirement's name and instructions.
On a document-upload panel, attach at least one file. Add a certification number and expiration date if you have them, plus any notes → select Submit Requirement and confirm the panel closes.
On an attestation panel, check the confirmation statement and add an optional comment → select Complete Attestation and confirm the panel closes.
On an external-task panel, select Open external task if a link is shown, do the work there, then return to the panel → select Mark External Task Done and confirm it closes.
Check the item on the checklist page → you should see its status change to Pending (if it needs review) or Completed.
You're done when
✓ The requirement's status changes from To Do to Pending or Completed on the checklist.
✓ For document uploads, your attached file shows a paperclip icon in the Attachments column.
✓ A rejected item you resubmitted shows Pending again, with your correction attached.
Boundaries and limits
Document uploads accept PDF, JPG, JPEG, PNG, DOC, and DOCX files, up to 10 MB per file. At least one file is required for a document-upload requirement.
Uploaded files are verified against their claimed file type before they are accepted; files that fail verification are rejected.
Attestations cannot be completed without checking the confirmation statement.
You can only submit requirements assigned to you, and only in an actionable state (incomplete, in progress, overdue, or rejected) — approved requirements can't be resubmitted.
Once a submission is pending review you cannot edit it — the next step belongs to the reviewer.
Your attached documents are private to you and the reviewing staff; downloads use short-lived secure links.
Common questions
Q: Why can't I upload anything for one of my requirements? A: Its submission mode is not document upload. Attestations only need your confirmation, external tasks are marked done after you finish them elsewhere, and admin-verification items are completed by your program team.
Q: What happens after I submit? A: Requirements that need approval show as pending review until a reviewer approves or rejects them. If rejected, you will see the reviewer's reason and can resubmit.
Q: Why does a requirement show a packet name under it? A: It was assigned as part of a packet — a bundled checklist such as onboarding or annual renewal. It behaves like any other requirement.
Q: My list looks empty — where did everything go? A: The default view shows only items needing action. Use "View All Requirements" to include approved and completed history.
Related articles