The one asking for it might be a customer questionnaire.
The hard part of export classification is not the call itself. It is producing the basis when someone asks. Docket keeps the inputs, the rule version, the source line numbers and the timestamp as one record, ready to pull up. The decision stays with you.
Sandbox access is being prepared with demonstration data. Reserve now and we will notify you at opening. The cloud edition is planned for roadmap Stage 1.
Assistive initial assessment, not legal advice. Final classification rests with BIS/CCATS.
ECFR 2026-05-28 · 88 LEGAL-REVIEWED RULES
419 AUTOMATED TESTS · BACKTEST DETAILS IN 4.0
Customer questionnaires, customs and auditors all ask the same thing: on what basis is this EAR99? Being controlled is rarely the problem. Proving that you are not is.
One amendment and the whole product line needs reassessment. You have to say which part numbers are affected, right away. By hand, that does not scale.
Repetitive classification questions eat the annual legal budget. The cases that genuinely need counsel end up waiting.
Type what engineering gives you and leave unknowns blank. The engine computes with rules vetted through legal review. Every threshold sits next to its source line.
Type what engineering gives you. Leave unknowns blank and the system will not guess for you.
The engine computes an initial ECCN assessment with rules vetted through legal review. Every threshold cites "source line N". Click it to read the regulation verbatim.
One click produces a classification evidence page. Inputs, rule version, source lines and timestamp are all on it, with the scope and any missing inputs shown. It is ready for whoever asks.
Assistive initial assessment, not legal advice. Missing input returns UNKNOWN, with no guessing and no forced conclusions.
Regulation text rises from the bottom. Only rules that pass the human sign-off gate become decision rules. The decision itself is computed by a deterministic engine, with no AI at runtime.
When inputs are missing it answers UNKNOWN, which means insufficient information. It does not guess and it does not force a conclusion. Every step behind a formal record is traceable. Whatever the rules leave uncovered is disclosed rather than papered over.
Saving official records, exporting evidence files, adding items to annual reports, sending for sign-off. All of it stays locked. This is a lock, not a polite warning.
Some conclusions this product will not give you. For the people who sign, "this tool will not vouch for me behind my back" is exactly the reason to buy it.
Data residency, spec confidentiality and audit trails are covered under security and data governance. The sandbox runs without real specs. In the formal edition every conclusion carries a version and a timestamp for audit.
We backtest against ECCNs that chip vendors publish themselves, feeding public specs into the engine. The sample is NVIDIA public data. ARM's public list is queued as the next validation batch and is not part of these numbers.
The remaining 391 lacked key parameters in public specs, so the engine returned "insufficient information". Those are excluded from the match-rate denominator, and not one below-threshold part was misjudged as controlled. Honest disclosure: of the 305 decided parts, the product identity of 1 part comes from third-party channel identification, corroborated by the vendor's public product brief and flagged in the results layer. Tests guard against regressions. Regulatory correctness is guarded by legal review.
Backtests use NVIDIA public data and imply no customer or endorsement relationship. The full methodology and the qualifier behind every figure are in the backtest method and figure table.
Ask about terms, why something was assessed a certain way, or the impact of an amendment. Every answer carries citation cards that open the source text. When nothing grounds an answer, it says so. It supplies the material and you make the call.
All three are illustrative, none is a customer case. The first two are within sandbox scope. The third belongs to roadmap Stage 2, and we only claim it once it ships.
Sales lands an order with a new part and a new destination. The owner types the engineering specs into the workbench. Minutes later there is an initial ECCN assessment and a classification evidence page, every threshold next to its source line. Unknown fields stay blank and the system returns "insufficient information" instead of forcing an answer.
A customer questionnaire, an auditor or customs asks for your basis. You pull up the classification snapshot archived at the time. Inputs, rule version, source lines and timestamp are all there, with nothing to reconstruct from memory.
When a shipping order is created, the ERP queries the part's classification and sign-off status via API. Decisions and records stay on the platform and the ERP only reads results. This is not built yet, so it appears on the roadmap rather than the feature list.
| Counsel + manual + spreadsheets (status quo) | This product | Heavyweight platforms | |
|---|---|---|---|
| Auditability | opinions yes, manual trails scattered | every conclusion traces to source lines | module-dependent |
| Speed | weeks | minutes (initial assessment) | quarters to deploy |
| Cost | eats counsel budget | subscription, tiered by part count | often six figures |
| Fit | low-frequency, case-by-case | mid-size fabless daily classification & proof | very large enterprises |
Positioning reference, not a feature-comparison claim. Counsel is irreplaceable on high-risk matters. Our goal is to reserve counsel hours for the cases that truly need them.
5A002/5A992 classification → encryption license-exception context + annual self-classification report.
Planned. Still only "what to check" context, never a shipping conclusion.
Planned. Records become your audit asset.
Planned.
Pricing: content subscription, tiered by managed part count. Our pricing goal (a goal, not a savings guarantee) is one year of subscription below the counsel budget you burn on repetitive classification. Actual effect depends on your product mix and how you work with counsel. Early-access plans are available, and the tiering and worked example are on the pricing page.