Skip to content

Creditcrest Operations

Every file in one queue, on the clock, to a checked conclusion.

Every handover is visible.

The work queue, checklist and service levels, and a second person’s check.

What you do here. Work your files in a queue: who holds each one, what is left on its checklist, and who checks the conclusion.

Open the staff console with sample filesTry it end to endTake the tour
You bring
What happened on each file
You get
The checklist, service levels and the queue
Holds the line
A conclusion stands only after a second person checks it

APP-EXAMPLE-1 — in review awaiting a second check

Ana (assessor) concluded on 3 Sept 2026: The assessor concluded the credit contract is not unsuitable for this applicant.

The lender’s workflow asks for a second check on every conclusion, so this one does not stand yet. Ana (assessor) cannot give it: the person who concluded a file is never its second check.

When Sam (senior assessor) confirms it, the file is concluded with both names on the conclusion.

The checklist

An item is closed with a note of what was seen, by the person who saw it. Nothing is completed on anybody’s behalf.

ItemStatusBy, and what was seen
Requirements and objectives inquired about and recordeddoneAna (assessor), 2 Sept 2026 — A $1,200 loan for a rental bond, over eight months; the applicant wants to repay fortnightly.
Financial situation inquired aboutdoneAna (assessor), 2 Sept 2026 — Declared income, expenses and debts recorded on the application.
Financial situation verified — statements read and figures reconcileddoneAna (assessor), 2 Sept 2026 — Ninety-four days of statement read; the rent corrected to what the account shows.
Ninety days of transactions obtained and considered, for a small amount contract (if it applies)not applicableAna (assessor), 2 Sept 2026 — Not a small amount credit contract.
Reasons for the conclusion written by the assessordoneAna (assessor), 3 Sept 2026 — Reasons written in the conclusion.

A figure corrected, and a document read by another system

Ana (assessor) changed monthly rent from 1200 to 1350 on 2 Sept 2026: The statement shows $675 a fortnight to the agent, not the $1,200 a month declared.

Fields read from a payslip the applicant uploaded, read by the lender’s document service were a proposal until reviewed: employer accepted, netPay rejected — “The payslip shows $2,201.40 net; the extraction transposed two digits.”

The queue

Past its service level first, then by priority, then oldest. Service levels are the lender’s, in business days; time waiting on the applicant is not counted.

FileWhere it isService level
APP-EXAMPLE-2receivedpast its limit
APP-EXAMPLE-1in review — awaiting a second check, held by Ana (assessor)past its limit
APP-EXAMPLE-3receiveddue 7 Sept 2026

The trail

DayWhatWho
1 Sept 2026opened
1 Sept 2026assignedAna (assessor)
1 Sept 2026extractedanother system
2 Sept 2026reviewedAna (assessor)
2 Sept 2026checked — requirementsAna (assessor)
2 Sept 2026checked — financial-situationAna (assessor)
2 Sept 2026figure changedAna (assessor)
2 Sept 2026checked — verificationAna (assessor)
2 Sept 2026checked — ninety-daysAna (assessor)
3 Sept 2026checked — reasonsAna (assessor)
3 Sept 2026concluded — not_unsuitableAna (assessor)

The roles

  • assessor — Works files assigned to them.
  • senior — Works any assigned file, may act on a colleague’s file, may give a second check, and records funding.
  • compliance — Reads everything, reports, and may give a second check. Does not work files.
  • admin — Works any assigned file, administers the queue, keeps the staff list and changes the lender’s own settings.
  • auditor — Reads everything and reports. Changes nothing.

A lender’s own system posts its workflow, staff and events to /v1/operations/case and gets this back as data.