How it works

From a document to a submittable file

Six steps, start to submission — plus one setup pass you do once. Every screen below is the actual product, not a mockup.

Step 1 · Create the prospect

Every extracted field carries a confidence level, and you correct it before anything is created

Click through at your own pace, or open any frame full screen at actual size.

Step 1

Create the prospect from a document you already have

Start from an ACORD application or a broker submission rather than retyping it. RTU reads the document and pre-fills the risk file — applicant identity, NAICS, year established, locations, coverages.

Every extracted field carries a confidence level, and you review and correct before anything is created. The completeness meter is explicit that fields you fill in yourself don’t count toward what was extracted.

Step 2

Check the quote readiness score

A readiness score, the risk tier, and the specific items standing between you and a submittable file — weighted, so you can see what actually moves the number.

It tells you when a file isn’t ready and why. It never stops you from proceeding: the score is advice, not a gate.

Step 3

Match against your own carriers

Each carrier in your portfolio is scored against this risk, with the reasoning broken out dimension by dimension — coverage lines available, industry appetite, size band, geography, prior performance.

Where the data is thin, RTU says so instead of inventing a number, and a carrier that doesn’t fit comes with the reason it didn’t.

Step 4

Face the gaps — fix them, or carry on

One checklist of everything still outstanding, each item marked critical, warning or suggestion and showing the readiness points it’s worth. That severity is RTU’s own reading of the file — where to start, not a prediction of what a carrier will say.

Fix an item now, or acknowledge it and move on. Nothing here stops you from proceeding; whether a gap is worth closing is your call.

Prospect portal · not every file needs it

Some gaps aren’t yours to close — send those to the prospect

Plenty of what’s missing sits with the client, not with you. RTU builds them a questionnaire from this file’s own gaps, and sends it to a portal of their own: a one-time code to get in, no account to create.

The back-and-forth happens there rather than across a chain of emails chasing one field at a time, and what comes back lands in the risk file itself — where the readiness score is recalculated against it.

Step 5

Compile the submission package

Compiling bundles the narrative and the supporting documents into one package you can download — a single PDF or a ZIP, your choice.

Anything you chose to carry forward is still listed alongside, so the package is assembled with the gaps visible rather than quietly omitted.

Step 6

Generate the ACORD forms — and submit them yourself

The ACORD applications in the package stay pending until you generate them. RTU fills them from the risk file you already built, so the data is entered once.

ACORD forms are licensed, not sold. Your agency confirms it holds its own ACORD licence once for the batch, then certifies each form’s accuracy individually.

Then you download the bundle and submit it the way you submit today — email, carrier portal, or an AMS import. RTU never transmits anything to a carrier on your behalf. Record the outcome when it lands; those outcomes are what sharpen the matching on the next risk.

Setup · done once

One setup pass — your carriers, and what each of them will write

Everything above runs against the carriers you actually place business with, so once — before the first prospect — you tell RTU who they are. Search the carrier registry, or add one it doesn’t cover: a wholesaler, an MGA, a direct appointment. Carriers you add yourself are visible only to your agency.

Then you write what each one will take: industry and NAICS, coverage lines, size bands, geography, red flags. Everything you set is badged Your custom rule, so it is always clear which rules are yours.

For a carrier you add yourself, the appetite is entirely yours — RTU has no estimates for it and doesn’t pretend to. For carriers in RTU’s registry, it offers estimates as a starting point, labels them not authoritative, and your rules override them.

Run one of your own prospects through it

Start with a document you already have and see where the file stands.

Or talk to us first — we’ll walk a file through with you.