Skip to main content

Gates and accountability

Make the next move explicit.

The dealership decides what can keep moving, what needs a second look, and what must wait. MIQ attaches that rule, the decision owner, the deadline, and the evidence needed to close the issue.

Configured authority pathsSix stations, three terminals
01 Authorized source02 Observed difference03 Evidence check04 Configured posture05 Dealer decision06 Reviewable recordAuditRecord and routeSoftAlert · acknowledgeHardAuthorized hold onlySigned workflow sets the bladesThe record travels · the configured blade decides the terminal
  1. 01 Authorized source
  2. 02 Observed difference
  3. 03 Evidence check
  4. 04 Configured posture
  5. 05 Dealer decision
  6. 06 Reviewable record
  7. Audit: Record and route
  8. Soft: Alert and acknowledge
  9. Hard: Authorized hold only
  10. Signed workflow sets the blades
  11. The record travels. The configured blade decides the terminal.

Configured posture

Three responses. One dealership decision.

You choose how each class of finding is handled. A finding never blocks a deal on its own.

Audit

Record and route

Preserve the exception for the assigned review cadence without interrupting the operating path.

Soft

Alert and acknowledge

Surface the issue to an assigned role when context is required before management chooses the next action.

Hard

Hold only when authorized

Use a hold only on a workflow the dealer explicitly activates, with a named reviewer and recorded disposition.

Decision path

Authority comes before posture.

Six steps, in order. Nothing acts on your store until you have authorized it.

  1. 01

    Source finding

    The evidence behind it, and the rule that flagged it.

  2. 02

    Dealer-assigned owner

    You name who looks at it.

  3. 03

    Signed-workflow authority

    Your signed workflow decides what we may do.

  4. 04

    Gate posture

    Record it, flag it, or hold it. A finding alone can never hold a deal.

    Default posture: audit / log-only

  5. 05

    Accountability record

    Who decided, and what they chose.

  6. 06

    Verification and sign-off

    Later evidence shows whether it held.

Browser illustration

See how a held decision reaches the right reviewer.

Use the illustration to follow an exception from source to owner, authority, posture, decision, and reviewable record.

Browser-only illustration. It does not connect to a DMS, hold a live transaction, or persist an event.

Sample packet S-04188

2024 used truck, term 72 months, Lender B

Ready for sample review
Retail contract
Captured
Required stipulation status
Missing
Proof of insurance
Captured
Management review
Not started
Sample event ledger· in memory

No events yet. Run the sample decision to see the configured posture, decision record, and browser-local fingerprint.

The record design carries source, actor, reason, and outcome

Next decision

Know why the decision was made.

See how the source, rule, owner, action, review state, and correction history stay attached to the decision.

MECHANUS IQ

Dealership intelligence

Whole-dealership intelligence and an operating system for Canadian automotive and RV dealerships. Machine learning finds the opportunity, MIQ makes the action happen, and the evidence shows what changed.

  • BC RIA dossier · anchored to enacted text
  • Privacy-minimizing intake
  • Human-review boundary
  • Canadian residency by design
  • Application timestamp context

© 2026 Mechanus IQ · British Columbia, Canada

More gross. Faster cash. Fewer repeat failures.

No ad-tech analytics · No session recording · No behavioural tracking