Brokering runs on two clocks: the lender's and the client's. Most of the writing exists to keep both moving — asking for documents, explaining what is happening, and setting expectations about timing. That writing is repetitive and safe to draft.
The exposure sits in a specific category: statements about what a client qualifies for, what a rate will be, and whether something is approved. Those are regulated representations in most markets.
Where it clearly helped
Document request lists
The clearest win. Requests previously written from scratch each time became a fixed list: which document, which period, what form it takes, and why it is needed. Explaining why each document is required reduced repeat questions, which was the actual source of delay.
Pipeline status updates
A short structured update — where the application sits, what is outstanding, what happens next, and when the client will hear again — took about 4 minutes to draft against roughly 12 to write. Consistency here matters: clients forward these to partners and solicitors.
Explaining process, not outcomes
What happens at valuation, why a lender asks a question, what conditional approval means. Descriptive, verifiable, and safe to generate. The discipline is keeping it descriptive — the moment a draft predicts an outcome, it needs rewriting.
Where it nearly caused problems
Eligibility and borrowing capacity
Given a few client details, drafts stated borrowing capacity as fact. Capacity depends on lender policy, verification and circumstances — a generated figure is not an assessment and must never reach a client.
Rate statements
Drafts referenced rates and comparisons. Rates change, and comparative claims usually carry disclosure obligations. Leave rate information to your current lender data and required disclosures.
Timeline promises
Generated text gave confident timeframes. Real timelines depend on valuation bookings, lender queues and document completeness. Describe the steps and the dependencies, not a date you cannot control.
Expectations worth setting in writing
Most difficult conversations late in a transaction come from expectations that were never documented at the start. Three are worth putting in writing early. What the lender will ask for next — an application rarely needs one document, and saying that further requests are normal stops the second request from feeling like a problem. What you control and what you do not: you can prepare and submit; you cannot set the lender's assessment timeline. Establishing that in week one is far easier than explaining it in week six. What would change the numbers — which circumstances would alter the terms, so a change in employment or borrowing is disclosed promptly rather than discovered later.
The other document worth the effort is the post-settlement note: what was agreed, what the ongoing obligations are, and when you will next be in touch. It is short, it is the cheapest source of referrals and refinance work available, and almost nobody sends it.
Editing time, from our 30-day benchmark
A document request list that took around 14 minutes to assemble came down to about 4 minutes, near $5 saved at $30 per hour. Pipeline updates went from roughly 12 minutes to 4. Post-settlement check-ins — the messages nobody had time to send — went out consistently for the first time.
A workflow that holds up
Standardise the request lists; that alone removes most of the delay. Generate status updates from a structure you define, then check each line against the lender's actual position. Keep descriptions of process separate from any statement about outcomes. Everything touching eligibility, rates or approval is written by the broker, and follows the disclosure requirements that apply in your market.
Standardise the paper chase
Requests, updates and explanations scale. Anything about eligibility, rates or approval does not.
Try Rytr →Frequently Asked Questions
Can AI write my client emails?
Requests, status updates and process explanations, yes. Anything about eligibility, rates or approval, no.
Can it calculate borrowing capacity?
No. Capacity depends on lender policy and verification. A generated number is not an assessment.
What about rate comparisons?
Use current lender data and include the disclosures your market requires. Do not generate comparative claims.
Can it promise a settlement date?
No. Describe the steps and what each depends on instead.
Does it help with compliance documents?
It can format them, but regulated content must come from your own compliance process.
Where is the biggest time saving?
Document request lists — roughly 10 minutes each, and they were the main source of delay in our test.