Roadmap

Where ConditionRail is going — and where it isn't

Mortgage ops teams have been burned by AI promises. We publish what's planned, what we're still exploring, and the things we will not build.

Planned
  • Bulk condition templates per investor

    Reusable condition packs keyed to investor overlays so new loans inherit the right checklist on intake.

  • Processor workload balancing

    Auto-suggest reassignments when one processor's open-condition count drifts outside the team band.

  • Borrower portal accessibility pass

    WCAG 2.2 AA audit on the upload and verification flows, plus high-contrast theme.

  • Encompass field-mapping editor

    In-app mapping for custom fields without re-deploying the integration config.

Exploring
  • Income calculation worksheet

    Structured worksheet from extracted pay stubs and W-2s. Always Needs review — never autonomous.

  • Voice-note borrower replies

    Transcribe and summarize voice replies for processor review. Routing rules still apply.

  • Investor-specific packet rules

    Per-investor packet ordering and cover-letter blocks driven from a config, not code.

Not planned
  • Autonomous loan approval

    Final underwriting stays human. We will not ship a path that lets the system mark a loan approved on its own.

  • Autonomous adverse-action decisions

    Denials and adverse-action notices are a regulated human decision. The product will not generate or send them automatically.

  • Borrower-facing approval/denial language

    Borrower messages never imply a credit decision. We will not add templates that suggest one.

  • Using borrower data to train models

    Borrower and customer data is not used for model training. This is a product boundary, not a config toggle.

Want to push something up the list? hello@conditionrail.com · See what shipped