Product

Controlled contract answers for airline crews and their reps.

ContractIQ combines cited answers, deterministic tools, and follow-up facts for tenant-specific airline contract questions.

Answer flow

Question to answer without pretending missing facts are known.

The tenant corpus and rule catalog decide whether a question needs cited prose, a deterministic tool, or a follow-up. The safer behavior is to ask for missing dates, times, and assignment facts before calculating.

Spirit ContractIQ ask composer with citation-only status and suggested contract questions. — The question surface is deliberately narrow: ask, cite, disclose limits, and prompt users toward real contract questions.

Spirit day-off protection checker asking what scheduling is trying to do. — Tools ask explicit branch questions before they calculate. This is where repeatable contract logic belongs.

Product model

Reusable checks, union-controlled sources.

ContractIQ should not require a code fork for every contract. The reusable layer handles citations, missing facts, rule binding, and deterministic evaluation. The tenant layer supplies the agreement, side documents, approved guidance, and launch boundaries.

Source-bound Q&A
Answers cite the configured tenant corpus.
Deterministic rule tools
Clock math and implemented branches run in code.
Clarification loop
User facts can drive calculations, but they are not source evidence.

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