Job Profiles and technical requirements

A Job Profile groups the requirements for a job and maps a namespaced identifier from your system to those rules. A requirement such as Basic Safety belongs to your organization. Several qualifications from different issuing bodies may satisfy it.

Requirements, qualifications and documents

Item	Purpose
Job Profile	Groups requirements and maps your job identifier.
Technical Requirement	States which qualifications you accept, which training/examination criteria you require, or both.
Qualification	Identifies what a worker has earned, with a stable catalog ID.
Document template	Describes how Dockt recognizes and reads evidence.

A document layout may exclusively identify one qualification. A shared layout may identify many: Dockt reads the qualification type code and resolves it within the configured issuing scheme. A type code is different from the serial number of an individual certificate. Registry-backed schemes continue to use the registry as the authoritative credential source.

Customer acceptance lists

Use technical_requirement to record what you accept before recognition is fully configured:

{
  "kind": "technical_requirement",
  "accepted_qualifications": [
    {
      "reference_id": "customer-course-a",
      "label": "An accepted safety qualification",
      "qualification_definition_id": "REPLACE_WITH_CATALOG_ID"
    },
    {
      "reference_id": "customer-course-b",
      "label": "Sam's safety training",
      "qualification_definition_id": null
    }
  ],
  "comparison_policy": { "mode": "accepted_only" },
  "minimum_assurance": "document_supported",
  "uploaded_proof_required": true
}

Any one linked qualification can satisfy the requirement if its evidence meets validity, assurance and proof conditions. An unlinked entry records acceptance but cannot establish a match. Keep its reference_id stable while Dockt adds support. You may also supply both scheme_code and qualification_code when the issuing scheme and qualification type code are known.

A known catalog ID can be accepted before Dockt has a training specification or a document template. The editor shows whether recognition and specification content are available. Identity, recognition and customer acceptance are separate configuration choices.

Training and examination criteria

Enable comparison when other qualifications may satisfy your own criteria:

{
  "kind": "technical_requirement",
  "accepted_qualifications": [],
  "criteria": {
    "learning_objectives": ["Identify workplace hazards and select protective measures"],
    "examination_objectives": ["Demonstrate hazard identification in a practical scenario"],
    "examination_requirements": ["Assessment conducted by an independent examiner"]
  },
  "comparison_policy": {
    "mode": "compare",
    "coverage_sufficient_in_principle": "review_required",
    "coverage_partial": "review_required",
    "coverage_unknown": "unresolved"
  },
  "minimum_assurance": "document_supported",
  "uploaded_proof_required": true
}

You can combine this with an acceptance list. Explicitly accepted qualifications are evaluated directly; other candidates can be compared with the requirement’s criteria. Set sufficient coverage to satisfied if that is your acceptance policy. Insufficient coverage cannot satisfy a requirement.

Comparison uses documented candidate content with source references. It records matching points, differences and missing information. Sufficient coverage must cite every requirement criterion and supporting candidate content. Missing specifications remain unresolved; a similar title alone is insufficient.

A comparison does not establish holder identity, validity, authenticity or registry verification. It also does not declare two qualifications universally equivalent. Its result belongs to that Assessment and frozen requirement.

Reconciliation as recognition improves

Suppose you enter Sam’s safety training, and Dockt later publishes a catalog entry named Training safety for Sam. Different display names do not prevent reconciliation:

1. Exact issuer-scoped codes and confirmed aliases can resolve automatically.
2. Name similarity suggests possible matches for Dockt’s operators to review.
3. An operator confirms that the pending reference identifies the same course, recording a reason. The confirmation applies only to your workspace and the original entry; it does not add a different acceptable qualification.
4. Dockt queues reevaluation of existing Assessments with new policy snapshots. Previously unknown credential codes are resolved from retained evidence. Newly supported layouts can trigger another read of unrecognized documents.

Existing Decisions and frozen evidence remain unchanged. Catalog recognition updates do not automatically broaden your acceptance policy. Adding a new acceptable qualification or changing criteria still follows draft, preview and activation.

Evidence and uploaded proof

minimum_assurance is an evidence floor. Authority-verified registry evidence can meet document_supported without an upload unless you require one. Document-supported credentials always need evidence bound to the worker.

Set uploaded_proof_required: true to require the accepted candidate’s own matching Document. An unrelated certificate from the same family cannot provide that proof. You can also require uploads for all Job Profile technical requirements through the Assessment Policy setting.

Follow Configure Job Profiles to create and activate a profile.