Skip to content
Route PacksComing soon

Repeatable work.
Ready for your review.

Pick one repeating task — checking credentials, chasing renewals, matching records. QordIQ does the work inside boundaries you set and hands your team a short list of what needs a human. Nothing sends, files or publishes on its own.

Route Packs are in design with pilot customers, not generally available. We build them on documents you already hold.

01 · How it works

From a business task to a repeatable workflow.

Five steps from a task on someone’s desk to one that runs itself — with your team checking the work.

02 · What a task needs

One task. Three boundaries.

Every route keeps the same shape: what it may use, what it may call, what it must keep — and a named person who reviews the results.

03 · Where QordiQ fits

Your tools stay. Your providers stay. QordiQ sits between.

Every request is checked against your rules before a model is called.

Set the rules — boundaries and approvals in one place  ·  Handle the work — every request checked  ·  Keep the record — every decision written down

04 · One piece of work, start to finish

Every request checked. Every outcome recorded.

Declines are prepared and explained — never silent.

05 · The pilot path

Learn first. Qualify before use.

From first setup to daily use in one quarter, with a human go / no-go before anything goes live.

* Only after the agreed qualification gate is met. Dates are illustrative, not a delivery commitment. Observation does not disable mandatory safeguards.

06 · What is inside a route pack?

A reusable starting point for one kind of work.

A pack is starting material: set it up for your organization, qualify it, and it becomes a task you can rely on.

Concept — not current availability.

07 · Healthcare credentialing

One hospital network. One reviewer. One list.

Walk through the full use case

The catalogue

13 packs.
Four ways to put AI to work.

Operational blind spots

Registers nobody keeps, built from records you already have.

  • Unanswered Questions Desk

    Coming soon

    Every question a customer, auditor, regulator or counterparty asked that never got a reply.

    Reference
    A reply on the same thread
    Your documents
    Permitted email and ticket correspondence
    Exception list
    Open questions, by age and by source
    Named reviewer
    The relationship owner
  • Expiry Horizon

    Coming soon

    Everything that lapses in one dated view: licences, certificates, insurance, leases, domains, credentials, contracts and training.

    Reference
    Expiry date plus renewal evidence
    Your documents
    Contracts, certificates, policies, vendor portals
    Exception list
    Anything inside 90 days with no renewal on file
    Named reviewer
    Operations or compliance lead
    Walk through the Healthcare credentialing use case
  • Single-Point-of-Failure Census

    Coming soon

    The decisions, systems and know-how that only one person can move.

    Reference
    At least two people able to act
    Your documents
    Approval records, vendor portals, policies
    Exception list
    What stops if that person is out
    Named reviewer
    COO
  • Shadow System Census

    Coming soon

    Spreadsheets and documents quietly acting as systems of record, compared with the official one.

    Reference
    The official system of record
    Your documents
    Shared drives and exported system data
    Exception list
    Records where the shadow and the system disagree
    Named reviewer
    System owner

Business knowledge

What was agreed, promised and known, put back in front of the person deciding.

  • Counterparty Memory

    Coming soon

    Before a negotiation, everything ever agreed, conceded, disputed or promised with that party.

    Reference
    Earlier positions with the same party
    Your documents
    Permitted contracts, emails and meeting notes
    Exception list
    Positions that contradict earlier ones, cited
    Named reviewer
    The negotiator
  • Promise Ledger

    Coming soon

    Commitments made in decks, proposals, emails and contracts, matched against what shipped.

    Reference
    Delivery and roadmap records
    Your documents
    Decks, proposals, contracts, release notes
    Exception list
    Promises with no delivery evidence
    Named reviewer
    Account or product owner
  • Decision Provenance

    Coming soon

    What was actually known when a decision was made, rebuilt from dated records only, so the review is free of hindsight.

    Reference
    Record dates before the decision
    Your documents
    Dated documents, messages and logs
    Exception list
    Claims that rest on later information
    Named reviewer
    Review board or counsel
  • Tribal Knowledge Gap

    Coming soon

    What the SOP says, next to what ticket and work-order history shows people actually do.

    Reference
    The written procedure
    Your documents
    SOPs, tickets, work orders
    Exception list
    Undocumented workarounds
    Named reviewer
    Process owner

Policies & language

When the words drift, the controls drift with them.

  • Deviation Dictionary

    Coming soon

    Reports that describe the same fault, complaint or event in different words, clustered under one proposed term.

    Reference
    Your existing taxonomy
    Your documents
    Incident, complaint and maintenance reports
    Exception list
    Clusters with no canonical term yet
    Named reviewer
    Engineering or safety lead
  • Policy Contradiction Finder

    Coming soon

    Rules that conflict with each other, or with the regulation they cite.

    Reference
    The policy corpus and its cited regulation
    Your documents
    Policies, standards, regulatory text
    Exception list
    Contradictory pairs, both cited
    Named reviewer
    Compliance lead
  • Translation Drift Check

    Coming soon

    A translated policy or contract compared with its source, clause by clause, for meaning drift.

    Reference
    The source-language document
    Your documents
    Source and translated documents
    Exception list
    Clauses whose meaning changed
    Named reviewer
    Bilingual reviewer

AI oversight

Routes that audit routes, so qualification is a habit and not an event.

  • Route Audit Desk

    Coming soon

    A qualified route's outputs, sampled against its own qualification report, with drift since the last version flagged.

    Reference
    The route qualification report
    Your documents
    Route outputs and the QordIQ record
    Exception list
    Outputs outside the recorded limits
    Named reviewer
    Compliance officer
  • Consent Trace

    Coming soon

    For each use of data on a route, the authorisation it rests on.

    Reference
    Recorded consent or legal basis
    Your documents
    Consent records, data-processing terms, route logs
    Exception list
    Data uses with no traceable consent
    Named reviewer
    Privacy or data-protection officer
What we hold back

Clear boundaries.
Human decisions.

  • Judgment dressed as a check. Safety-culture scores or “is this customer at risk” have no reference to compare against, so they cannot be qualified.
  • Anything that writes to the outside world. A pack returns a list for a person to review. It never sends, files or publishes on its own.

Shape your first Route Pack.

Tell us about a recurring task and the documents behind it. Help shape a pack with clear checks, useful findings and a named reviewer.

Pilot a route pack