Put workforce decisions inside your product.

Send worker context and evidence. Dockt applies the requirements and returns an explainable decision your workflow can use.

Book a walkthrough View developer docs

Construction workers coordinating around steel structures on site

Delivery One API behind your product

Processing Under 30 seconds per worker

Commercial model Credits per worker assessment

Keep your product. Add the assessment layer.

Dockt maintains the evidence rules, document processing, Universe, and decision model. Your team keeps the product experience and customer workflow.

01 · Send context Start with what your product already knows.

Send the worker, assignment, and available evidence in one scoped assessment.

Identity and nationality
Employer and posting status
Assignment and role context
Available documents

02 · Build the Universe Assemble the evidence picture before deciding.

Dockt connects document evidence with worker and assignment context, then runs supported checks that add relevant, sourced context.

Evidence normalized
Relationships connected
Relevant sources checked
Conflicts preserved

03 · Take action Return a decision your workflow can use.

Receive the outcome, reasons, and missing evidence so your product can continue, request more, or route a review.

Explicit outcome
Missing evidence
Review reasons
Route or continue

One request in. One useful result out.

Your product sends the worker and assignment context, then attaches the documents it already holds. Dockt returns structured findings and an explicit decision your workflow can render, route, and explain.

Request

POST /v1/assessments

{
  "external_id": "worker-case-1042",
  "worker": {
    "first_name": "Amina",
    "last_name": "Diallo",
    "date_of_birth": "1990-05-17",
    "nationality": "FR"
  },
  "context": [
    {
      "code": "employment.relationship",
      "value": "posted_employee"
    },
    {
      "code": "employment.employer_country",
      "value": "FR"
    }
  ]
}

Result

GET /v1/assessments/ast_example1042

{
  "status": "assessed",
  "review": {
    "review_required": false,
    "reason_codes": []
  },
  "latest_decision": {
    "decision_id": "dec_example1042",
    "assessment_input_version": 3,
    "decision": "compliant",
    "signal": "green",
    "explanation": "The available evidence satisfies every evaluated requirement for this assessment version.",
    "findings": [],
    "recommendation": null,
    "created_at": "2026-08-23T09:31:00Z"
  }
}

Open in developer docs

Build the Universe. Keep the evidence clear.

Dockt assembles a sourced, versioned evidence picture around each worker, then evaluates it against the requirements for that assignment. Anything missing, conflicting, or uncertain stays visible for review.

A Universe around each worker

Universe

Worker input, assignment context, document evidence, and supported external checks come together in one connected assessment picture.

Reviewers receive the usable result without reconstructing the surrounding context by hand.

Assignment-aware requirements

Policy

Worker, employer, posting, assignment, and workspace configuration determine which evidence applies.

Each assessment starts from the real worker context.

Social and technical evidence

Evidence

Dockt evaluates supported workforce evidence and configured qualifications against the requirements that apply.

Each source remains connected to the result it supports.

Conservative results

Review

If Dockt cannot verify a requirement, it remains Incomplete or Review required for a human to resolve.

Uncertain evidence never passes silently.

Make every result clear to review.

Every decision keeps the relevant Universe evidence, source lineage, findings, and review reasons attached. Unverified requirements remain Incomplete or Review required for a person to resolve.

Review required

What matched: The A1 certificate and Limosa notification satisfy two active requirements.
What needs attention: Right-to-work evidence is missing for this assignment.
Review reason: Dockt could not verify the missing right-to-work requirement automatically.
Human check-off: An authorised reviewer makes the final operational decision and records the downstream outcome separately.
Source record: Documents, supporting sources, findings, configuration version, and decision time remain retrievable.

One integration. A clear boundary.

Create an assessment, upload evidence, and receive the result through signed events and the REST API. Your product keeps the interface and the next action.

View developer docs

Keep the interface

Collect evidence, show progress, and present the result through your existing interface and brand.

Separate each workspace

Credentials, configuration, assessments, and webhook endpoints stay within one customer boundary.

Receive signed events

Completion events keep your workflow updated while document and assessment processing run asynchronously.

Choose the next action

Request another document, route a review, or continue the workflow using the structured result.

Know what happened. Keep the record.

Customer boundaries, processing events, and assessment history stay explicit as the workflow moves forward.

EU hosted

Assessment processing and operational data stay in the European Union.

Read the security and data posture.

Workspace scoped

Customer configuration and assessment data remain separated by workspace.

Versioned inputs

A new assessment input produces a new decision while earlier decisions remain retrievable.

Auditable history

Evidence, findings, review reasons, and decision metadata remain connected over time.

See Dockt in your workflow.

Bring the worker context, evidence, and next action. We’ll map the quickest path to a working integration.

Book a walkthrough View developer docs