They applied on Tuesday.
It is Friday.
Nobody has said anything.
A lending application sits in assessment for days, and the applicant hears nothing because there is nothing definite to say. This demonstrates the alternative: honest progress, no decision implied, and the one question that shortens the assessment for everyone.
“Silence during an assessment is not neutral. People read it as a no.”
Ledgerline · an invented exampleThe three days of nothing
An application went in on Tuesday. Since then: an acknowledgement email and silence. The applicant does not know whether their documents were enough, whether a person has looked at it, or whether they should be applying somewhere else at the same time. So some of them do.
Assessment queues are slow for good reasons — verification, affordability, human review. The applicant is not owed a faster answer. They are owed a truthful account of where it is, and nobody sends one because the only template says "approved" or "declined".
What happens now
An acknowledgement, then nothing until an outcome. The wait reads as a decision that has already gone badly.
What it costs
Applicants apply elsewhere in parallel, and the ones you would have said yes to are gone by the time you say it.
What the concept does
Says truthfully where it is, asks the one thing that unblocks it, and stops. It never decides.
Every application moment, one pattern.
Each of these is a moment your customer already spends with you. Each can carry what the phone above shows: watch the work, earn the wait, answer one thing.
Be relevant — right thing, right moment · Be respectful — short, skippable, quiet by design · Be measurable — real impact, on the record · Be Aotearoa — built here, for how Kiwis actually wait
Every wait in a home loan
Six moments where an applicant is waiting on a decision they cannot see, and what each wait could hand back.
You know whether to keep going to open homes this weekend or hold off for another one.
You learn the one thing actually holding it up, while you can still go and fix it.
The delay has a name and a shape, so it stops reading as a bad sign.
The wait has a person attached to it, and the decision stays entirely theirs.
The last fortnight becomes something you can organise a move around.
You choose the next term with the options in front of you, not on the morning it expires.
Four steps, every time.
- The signalSomething in your own systems says a person is now waiting, and roughly how long for.
- The predictionHow long this one will really take — not the average, this one.
- The valueSomething worth their attention goes into that window: an answer, a credit, a thing prepared while they wait.
- The exchangeThey get value. You get a customer who stayed, and one optional answer you have always wanted.
This is the reward layer, running for real on this page. Drag to scratch it. Nothing is collected, nothing is sent — it is here so the idea is something you do, not something you read.
US retailers lose an estimated $37.7 billion a year to customers who abandon because of long queues, split roughly $15.8b to competitors and $21.9b abandoned outright (Adyen with 451 Research). The New York State Department of Labor reported a 48% reduction in hang-ups after introducing virtual queuing. Theme parks moving to virtual queues reported a 36% lift in per-capita spending, because guests spent the wait somewhere that sold something. A Seattle-Tacoma Airport study found 63% of passengers said they shopped or ate more because they saved time in the security queue.
Every figure on this page carries its source. Overseas figures are shown as overseas figures — we have not found a published New Zealand equivalent, and we will not invent one.
One application. Four honest updates.
The same three days, four situations. Not one of these says approved, declined or likely — that is a lender’s decision under the CCCFA, and this concept does not touch it.
A template sends the same thing to everyone and changes the name. What matters here is the case that should get something different — or nothing at all.
The rules beside each draft are placeholders. A pilot replaces them with your actual policies. We have not seen those, and this concept does not guess at them.
The checks that run before an update is sent
Lending is the most boundaried category assembl builds in. The guards are the reason this is sendable at all.
Drafts are held against the Credit Contracts and Consumer Finance Act 2003 and the Responsible Lending Code, the Privacy Act 2020, and the Fair Trading Act 1986.
Press run to see what it catches — and what it refuses to produce at all.
One room. Your people, your agents, every action on the record.
Every concept on this page would run inside a private room like this: your team and the agents in the same space, drafts appearing with receipts, a named person saying yes. It runs on infrastructure you approve — and what is said in the room stays in it.
receipt sources: your rate card · rules: yours · held for approval
Client information stays in your room. Six months later, “where did this come from?” is one line, not a search.
Yours
Runs where you approve — your own room, your own record. Nothing in it leaves it.
On the record
Every agent action lands as a line a person can read — not a log only a vendor can open.
People decide
Drafts wait for a named person. The room shows who said yes, and when.
This panel is a concept picture, not a live room — a pilot stands up the real one, on infrastructure you approve.
The queue, before anything sends
Illustrative and fictional. No production access is requested by this concept.
| Application | Count | Prepared | Waiting on | Status |
|---|---|---|---|---|
| Complete, genuinely queued | — | Honest update, no outcome implied | Assessor, in order | Awaiting assessment |
| One document outstanding | — | The specific item named | Applicant to send it | Awaiting applicant |
| Something changed since applying | — | Flagged for an assessor | Assessor | Awaiting assessment |
| Language reads as hardship | — | Nothing drafted | A named person, urgently | Held — no draft |
| Joint, no sharing consent | — | Nothing drafted | Both applicants | Held — no draft |
| Identity not yet verified | — | Update held | Verification | Parked |
Counts are blank because this is a demonstrator. There is no Ledgerline, and therefore no applications.
Every draft carries its own working.
Not a log somebody has to go and find. The provenance travels with the work — what it read, which rules it held, who must approve it, and what it refused to do.
This matters most on the day someone asks why it said what it said.
- Artefact
- Application update — complete file, in the queue
- Read
- Invented product and process facts for an invented lender · application fields: submitted documents, outstanding items, queue position, hardship-language flag, joint-applicant consent. No credit file. No bank transactions.
- Rules held
- Credit Contracts and Consumer Finance Act 2003 · Responsible Lending Code · Privacy Act 2020 · Fair Trading Act 1986
- Refused
- No credit decision was made or implied. No rate, amount or term was personalised. Nothing was drafted for an application reading as hardship, or for a joint application without per-applicant sharing consent.
- Approver
- A named person. Unsent until then.
- Prepared
- —
- Reference
- —
What this will never do
It does not send. It prepares, and a named person sends. It does not publish to any channel, commit spend, move money, or make a decision that belongs to a person. It does not pretend to be a person — every draft says it was prepared by a machine and approved by a human.
No production access is requested by this concept.
Scope
In a real engagement: progress updates for opted-in applicants on one product, six weeks. Not the credit model, not pricing, not affordability, not the decision.
Access
Published product facts and the field names for submitted documents, outstanding items, queue position, hardship flags and joint-consent status. No credit files. No bank statements.
Scorecard
Applicants who stopped chasing. Documents supplied faster because the ask was specific. Held cases a person agreed should have been held. And whether an assessor would put their name to every update that went out.
Fail any line of the scorecard and we change the design or stop.
What a pilot actually asks of you.
Written out in full, because the honest version of this is short and most of it is your time, not your money.
One named person
The approver. Every draft stops with them and nothing reaches a customer until they say so. Expect about two hours a week — reading drafts, not managing a project.
One situation, not the business
In a real engagement: progress updates for opted-in applicants on one product, six weeks. Not the credit model, not pricing, not affordability, not the decision.
Read-only access, nothing that writes
Published product facts and the field names for submitted documents, outstanding items, queue position, hardship flags and joint-consent status. No credit files. No bank statements. No production credentials, no write permissions, no access to anything the pilot does not need.
Your actual rules
The policies, limits and words the drafts must be held against. Every rule on this page is a placeholder standing in for yours. An afternoon with whoever owns them is usually enough.
Six weeks, then a real decision
Scored on: Applicants who stopped chasing. Documents supplied faster because the ask was specific. Held cases a person agreed should have been held. And whether an assessor would put their name to every update that went out. Fail any line of that and we change the design or stop. You keep everything drafted either way.
A fixed fee, agreed in writing first
No number is published on this page, because it depends on which situation you pick. Whatever it is, it is agreed before any work starts and it does not move.
Run the pilot.
Say yes to the six weeks above, and add anything you would change first. Nothing here is fixed — most pilots move a line or two before they start, and the notes below are how that happens.
Opens your mail app to assembl@assembl.co.nz with your notes in it. Nothing is collected by this page.
- Six weeks, one situation, scored against a written line
- Read-only access, nothing production
- A named approver — nothing sends without them
- A fixed fee, agreed in writing before anything starts
- Stop any time. You keep what was drafted
Pick a verb.
Not “book a demo”. Any of these is a real next step, and the last one is a perfectly good answer.
What is the one constraint we have got wrong?
Every concept is built from the outside. There is always something about how Ledgerline actually runs that we could not see. One line is enough.
Opens your mail app to assembl@assembl.co.nz. Nothing is collected by this page.