Skip to content
AKITIx Solutions

Loan applications that never go quiet.

An example of a loan application run in Bridge: the form, every review, the approval and the deadlines, with a record behind each decision.

instances · loan-application
CaseCurrent stepStatus
LOAN-2041Assess credit riskRunning
LOAN-2040Committee approvalDue soon
LOAN-2038Check documentsRunning
LOAN-2035Send the offerIncident
LOAN-2031Offer sentCompleted

Sample data

The example: a loan application.

An example drawn in BPMN and run on Camunda 8. Your own process will differ; what Bridge brings to each step stays the same.

loan-application.bpmn
  1. Application submittedFormio form
  2. Check documentsBack office
  3. Assess credit riskCredit analystA case is here
  4. Above the approval limit?Yes: Committee approval · No: Send the offer
  5. Committee approvalCredit committee
  6. Send the offerAdvisor
  7. Offer sent
Sample data

How each step looks in Bridge.

Task InboxClaim a task and complete its form, without Camunda Tasklist.Sample data
  1. Application submitted

    Start · Formio form

    The applicant's Formio form starts the process, and the mapper turns its fields into process variables with no code.

  2. Check documents

    User task · Back office

    The task lands in the back office's inbox, in the lane that matches its deadline, with the form and the case history beside it.

  3. Assess credit risk

    User task · Credit analyst

    The analyst fills in the assessment; what they type is kept as a draft until they submit it.

  4. Above the approval limit?

    Decision

    The limit can live in a decision table built in Bridge, so it changes in one place and keeps its versions.

  5. Committee approval

    User task · Credit committee

    The approval is given to the committee's group, so only people whose role carries that group see it, and the audit trail records who approved, when and with which data.

  6. Send the offer

    User task · Advisor

    The SLA tracker warns before the offer deadline.

  7. Offer sent

    End

    The case closes with its history kept in the archive.

What a bank asks of the workflow.

Response times you can show
Each step has a deadline lane, the SLA tracker warns at the threshold you set, and dashboards show durations over any period.
Every decision on the record
Who assessed, who approved, when, and the data they saw: every action is in the audit trail, and any case can be replayed step by step.
Separate hands for separate steps
Assessment and approval are different tasks for different groups: a task given to a group only appears for people whose role carries it.
Audit trailWho did what, when, and with which outcome.

Questions banks ask first

Does Bridge come with this workflow?

No. It is an example of what a bank can build. Workflows are drawn in Bridge's BPMN designer or synced from your Camunda 8 cluster, and our consulting team can help design yours.

Can the approval limit change without redeploying the workflow?

If the limit lives in a decision table, you change and deploy the table, and the workflow uses the new version.

Where is our data kept?

Tell us your hosting and data-residency requirements with your trial or demo request, and we will confirm the setup that fits.

Run your loan applications in Bridge.

Start a free trial with your own Bridge organisation, or book a 30-minute demo around a workflow like yours.