Skip to content
HRTEQ

DocsDocuments & compliance

Document type reference

Selected document type examples for identity, qualifications, employment and workforce administration, with their stored codes, attachment scope and expiry settings.

Document types are editable for your organization: rename them, deactivate ones you do not use, and add your own. Configure the catalog for your hiring workflows and applicable requirements. The code is what stage requirements reference, so changing a code changes what a requirement points at. The tables below are selected examples, rather than a complete catalog.

How to read the columns. Applies to decides where the file attaches: an APPLICANT document is uploaded once and reused by every application; an APPLICATION document belongs to one application. Expiry means the gate will not count the document without a future expiry date. Portal means an applicant may upload it themselves. The settings shown below describe the seeded examples; review your organization’s configuration before use.

Applicant-level documents#

These examples describe the person and can be reused across applications. In the seeded configuration, applicants can upload these types through the portal.

CodePurposeCategoryExpiry
PASSPORTPassportIdentityYes
ID_PHOTOPassport-size photoIdentityNo
BIRTH_CERTBirth certificateCivilNo
MARRIAGE_CERTMarriage certificateCivilNo
POLICE_CLEARANCEPolice clearanceClearanceYes
RESUMERésumé / CVEmploymentNo
COECertificate of employmentEmploymentNo
DIPLOMADiploma / transcript of recordsTrainingNo
TRAINING_CERTTraining certificateTrainingYes

Uploading a RESUME also sets the applicant’s résumé file and may queue parsing. Verify which identity, qualification and clearance records your organization needs before adding them as stage requirements.

Application-level documents#

These selected examples belong to one application. In the seeded configuration, they are managed by staff rather than uploaded through the applicant portal. Use the types relevant to the role, location and placement process.

CodePurposeCategoryExpiry
OFFER_LETTERJob offer letterEmploymentNo
EMPLOYMENT_CONTRACTEmployment contractEmploymentNo
MEDICAL_RESULTMedical examination resultMedicalYes
VISAVisaVisaYes
INSURANCEInsurance recordGovernmentYes
AIRLINE_TICKETAirline ticket / itineraryTravelNo

Categories#

Every type carries a DocumentCategory, used for grouping in the UI and in reports. The available category codes are listed below. They describe how a record is organized, rather than a universal requirement to collect it.

  • IDENTITY, CIVIL, CLEARANCE, MEDICAL
  • TRAINING, EMPLOYMENT, VISA, GOVERNMENT
  • TRAVEL, FINANCIAL, OTHER

Which types track expiry#

Among the examples on this page, the following types track expiry in the seeded configuration. Once expired, a document stops satisfying a stage requirement. Review the actual expiry date and your organization’s requirements for each record.

  • Applicant examples: PASSPORT, POLICE_CLEARANCE, TRAINING_CERT
  • Application examples: MEDICAL_RESULT, VISA, INSURANCE
A type that tracks expiry needs a date at upload. A verified document of an expiry-tracking type with no expiresAt fails its requirement with “Verified but the expiry date is missing.” Capture the date when you upload, not later.
Was this page helpful?