Understand the borrower path before the workflow gets heavier

This page explains what Corteran does, what it does not do, why the document layer matters, and when a borrower should expect the process to move into licensed or formal-document territory.

Borrower credit guide

This is not a formal approval

Precheck, upload, AI organisation, and the status center are borrower-first intake layers. They help clarify readiness, missing items, and next steps. They do not amount to a final credit approval or funding promise.

Borrower credit guide

Documents do the explanation work

Income, statements, tax evidence, identity, and address proof are the usual explanation layer. The stronger that file becomes, the less the case should remain in repair or manual review.

Borrower credit guide

Formal documents come later

A borrower should only move into heavier lender, broker, or partner documentation once readiness, route posture, manual-review controls, and downstream handoff conditions are aligned.

Borrower credit guide

AI is a support layer

AI is used for organisation, draft support, and next-step guidance. It should not operate as a standalone credit or suitability decision-maker.

What the borrower public layer should do first

Its first job is to clarify the case posture before making the workflow feel heavier than it should.

Borrower first

The public layer should do

Explain readiness, missing items, and the next route.

Organise documents, consent, and status into one borrower workflow.

Keep files in repair or manual review when the explanation layer is still weak.

Boundary first

The public layer should not do

Present intake pages as if they were formal approvals.

Make strong promises while the file still has unresolved gaps.

Blur the borrower experience into investor, fundraising, or controlled-disclosure territory.

Four things borrowers should know

If you are on contact, precheck, or upload pages, the platform is handling intake and routing rather than a final approval process.

Where the explanation layer is incomplete, the case should stay in repair or manual review instead of being pushed outward.

Consent and follow-up should stay visible, revocable, and auditable through the consent center.

Questions about service boundary, privacy handling, or follow-up should move into the complaints or contact path directly.

Related guidance pack

Public disclosures

Review entity facts, boundaries, and where formal documents take over.

Review platform role, disclaimers, and document precedence.

Privacy notice

Review collection purpose, sharing logic, and cross-border handling.

Consent center

Review follow-up permission, consent history, and revoke actions.

Borrower credit guide

The goal is not to push faster. It is to explain the path correctly first.

The borrower public layer earns trust by explaining what the current file still needs, what it does not yet justify, and where the next formal document layer begins.

Start readiness check Complaints and concerns