What it does
Requirement templates save a reusable requirement configuration — name, type, default due window, default expiration window, and notes — under a memorable template name, so administrators can standardize requirements they set up repeatedly. Whole sets of templates can also move in and out of the platform as CSV files.
Who it's for
Institution and program administrators work in the institution or administration portal.
How it works
Templates can be kept institution-wide or scoped to a single program. The Templates page (/requirements/templates) lists your existing templates with their type, scope, usage count, and last-used date. You can filter by program and search by name. Each template's row actions let you View, Edit Template, or Delete Template it.
A template's fields are its Template name, Requirement name, Type, Default due (days), Default expiry (days), a Description, and Default notes. These become the defaults every time the template is used.
New templates aren't created from this page directly — instead, check Save this configuration as a template when you assign a requirement (see the assigning-requirements article), and it's added here for reuse. This page is where you review, edit, import, and export templates afterward.
Exporting. The Export button downloads your current template list as a date-stamped CSV file. This doubles as a starting point for bulk edits.
Importing. The Import button opens a panel that reads a CSV file with headers, validates every row, and shows a preview before saving. Rows that fail — for example a missing name or unrecognized type — are flagged and excluded. Only valid rows are inserted, in one batch.
Before you start
You need administrator access to the institution or administration portal.
Have your CSV ready with the expected headers — the fastest way to get one is to export the current list first and edit that file.
Know which program the imported rows should belong to, or leave them institution-wide.
Do this
Open the Templates page (
/requirements/templates) → you should see the template list with Export and Import buttons.Select the Import button → a panel opens and asks you to choose a CSV file.
Choose your file → the panel shows a preview with rows read, ready, and skipped counts, plus a table of any rows that will be skipped.
Pick an option in the Add to dropdown to set the target program, or leave it Institution-wide → confirm the Templates to import list shows the rows you expect.
Select the Import button at the bottom (labeled with the ready-row count, for example "Import 5 templates") → the panel closes and you should return to the Templates page with the new rows in the list.
You're done when
✓ The imported templates appear in the Templates list with the program scope you chose.
✓ Any skipped rows are the ones you saw flagged in the preview — nothing silently failed.
✓ The templates are ready to select from Use Template the next time someone assigns a requirement.
Boundaries and limits
Template names and requirement names must be at least 3 characters; names longer than 200 characters are rejected during import.
CSV imports are capped at 1,000 rows per file.
Invalid CSV rows are never silently imported — they are excluded and reported in the preview.
A template stores configuration defaults only; creating a template does not assign anything to anyone.
Bulk-applying many templates at once to programs is not currently available.
Templates are scoped to one institution; there is no cross-institution template sharing.
Common questions
Q: Where is the "Create Template" button? A: There isn't one — save a template by checking Save this configuration as a template when you next assign a requirement. It then appears here for editing, import, and export.
Q: How is a template different from a library requirement definition? A: A definition is the live catalog entry people get assigned. A template is a saved configuration recipe — a shortcut for standard names, types, and default windows when setting up requirements.
Q: What happens to rows that fail validation during import? A: They are flagged in the preview and skipped. The valid rows still import, so one bad row does not block the rest of the file.
Q: Can I round-trip templates between environments? A: Yes. Export produces a CSV in the same shape the importer accepts, so you can export, adjust, and re-import.
Related articles