Request demo Demo
Menu

Trust

Built for contract teams that need answers they can inspect.

ContractIQ is designed around citations, deterministic checks, visible limits, and source-backed issue handling. It is not legal advice and it is not a replacement for union judgment.

Process

Trust starts before the first pilot asks a question.

The work is not just loading documents into a chat box. Each tenant needs a source package, an authoritative knowledge layer, deterministic checks where the rules allow them, and a way to turn misses into source or eval work after launch.

  1. 01

    Receive the source package

    Start with the contract, side letters, policies, public authorities, and any union-approved guidance that should define the answer boundary.

  2. 02

    Build the authoritative layer

    Structure sources, stable references, rule branches, and deterministic tools so answer behavior is grounded in something inspectable.

  3. 03

    Test and review

    Run evals, test representative questions, review edge cases, and tune missing-fact prompts before the site is shared broadly.

  4. 04

    Launch the tenant surface

    Publish the tenant answer site with clear limits, contact paths, analytics posture, and rule tools that match verified behavior.

  5. 05

    Improve from feedback

    Reported misses should become source updates, new eval cases, or tool fixes instead of disappearing into a chat transcript.

Knowledge base, but as infrastructure first.

A user-facing knowledge base may become useful later. The immediate trust feature is the underlying tenant knowledge layer: organized source material, stable references, rule catalogs, and evals that the answer system can rely on.

Posture

What we make explicit.

Citation model

Responses should point to the specific contract or supporting text used. If the source does not support the answer, that is a product problem.

Tool boundary

Deterministic tools only own branches that have been implemented and tested. Other questions stay in cited-answer or clarification mode.

Missing facts

The safer behavior is asking for dates, timestamps, or assignment facts instead of inventing them.

Issue handling

A reported miss should point to the answer path, the source path, and the fix needed if the issue can recur.

Tenant specificity

A tenant answer site is bound to that tenant's corpus and configuration. It should not imply coverage for other airlines.

Human authority

Union reps, contract specialists, and legal counsel remain the arbiters for ambiguous, disputed, or high-stakes cases.

Limits

Plain language boundaries matter.

ContractIQ does not sell itself as full assignment legality, universal airline coverage, or a legal-advice product. Public claims should track implemented behavior and named eval coverage.

Marketing analytics

When enabled, this site uses GoatCounter page-view analytics. Tenant product data and marketing page views are separate concerns.

Read privacy notes

Talk to us

Bring a real contract problem.

Demo conversations are most useful when they start with the repeated questions your contract team sees.

Request demo Review trust posture