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.
And the question is the point. One optional question, asked inside the wait, is the only part of this that sends something back the other way. Decline it and the work still gets prepared — just with less of them in it.
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.
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.
Pick a verb.
Not “book a demo”. Any of these is a real next step, and the third 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.