MGA submission intake, triaged by your own rules
An MGA or program administrator lives on broker submissions: a steady stream of risks, most of them incomplete, some outside appetite, a few that need someone with authority to look. Faldaro turns that stream into records — each submission checked against your referral rules, priced by the server, and moved from Received to Quoted or Declined by the people allowed to move it.
A submission, end to end
From broker email to quote or decline
The same four steps whether the risk came in through the form or through the inbox.
-
1 The submission arrives
A broker fills in your submission form through a public link — no account, no seat — or forwards it by email. Class codes, territories and other long lists come from datasets you maintain, so the broker picks from your list, not free text.
-
2 Your rules read it
Referral rules raise named outcomes — “Refer to underwriting”, “Outside appetite” — with a message saying why. The indication is computed by the server from the broker’s answers and stored apart from what the broker typed, so nobody can submit a premium of their own.
-
3 Someone owns it
The submission gets a reference number, lands as Received and can be assigned. Moving it to Quoted, Declined or Referred is a separate, permissioned act from editing it, and a move can require fields to be filled or a condition on the values to hold.
-
4 A decision goes out
The move to Quoted can generate the quote letter from your template and email the broker. Referrals can wait on an email approval from whoever holds the authority, and a deadline can move a quote that nobody answered to Lapsed on its own.
The parts doing the work: workflows for the states and moves, email approvals for referrals, and records for the reference number, history and status link. This page is one part of claims and submission intake for insurance.
Referral rules
Appetite, written down once
The rules underwriters apply in their heads, stated where every submission meets them.
A referral rule is a condition and an outcome: when the total insured value is over your line, when the class is on the referral list, when the loss history says more than two claims — raise “Refer to underwriting” with a message naming the reason. Rules can also show or hide questions, so a broker quoting a warehouse is asked about sprinklers and a broker quoting an office is not. A hidden question contributes nothing to the calculation, so an answer the broker can no longer see cannot inflate the indication.
The indication itself is a formula over the broker’s answers — rate times exposure, adjusted by the factors you choose — and the server works it out on every save. What the broker typed and what the server computed are stored separately, which is what lets a referral rule, a transition or a quote letter rely on the number.
Keep in mind what a formula here is: arithmetic and a small set of functions, not a rating engine with its own tables. If your rating needs a large rate table, keep it where it lives and bring the result into the record; if it fits in a handful of factors, it fits in the form.
Control
Built for rules that change every quarter
Appetite moves. The platform is shaped so that changing it is routine rather than risky.
-
Rating you can change safely
Every published version is immutable. Change a rate, publish, and new submissions use the new version while old ones keep theirs — the indication on a bound risk never shifts under it.
-
Changes tested before they ship
Form test cases pin named inputs to expected outputs. Run them against a draft and you know whether this week’s rating change moves a figure somebody relied on.
-
Formulas that cannot run code
Expressions run through a closed evaluator with a fixed set of operators and functions — no scripting engine behind the rating, and a budget on every evaluation.
-
A trail that answers for itself
Every create, move and publish is written to an append-only audit log. When a broker asks why a risk was declined, the record says who moved it, when, and against which version of the rules.
Where brokers come in
Brokers are never seats
Submission intake is work from outside your organization, so the people sending it are not users you pay for.
Brokers reach you through a public link or a form’s email address — neither needs an account. Each submission can carry a status link the broker keeps, and with the submitter portal switched on a broker can list every submission filed under their email address. The broker submission portal page covers that side in detail, and claims email intake explains how emailed submissions are verified and filed.
On the servicing side, the same account can run the smaller requests brokers send all day. Start from the free certificate of insurance request, loss run request or first notice of loss templates — each opens as an editable draft with its workflow included.
Questions
MGA submission intake, plainly
Can brokers see our referral criteria or rating from the submission form?
No. The public form carries no logic document, no formula text and no calculated values — computed fields are marked as computed with the expression withheld. Referral outcomes and their messages appear only to your own staff inside the app, so the form never becomes an oracle for your appetite or your rating.
What happens to submissions already in flight when we change the rating?
Nothing. Publishing creates a new immutable version, and every submission keeps the version it was filled against. Before you publish, form test cases re-run pinned inputs through the real engine against the draft, so you see which indications would change before any broker does.
Can an underwriter with referral authority approve from their inbox?
Yes. A workflow move can request an approval by email: each approver gets a private link to a decision page showing only the fields you chose, and their verdict fires the move you configured. Every approver must agree for an approval to pass, any decline reads as declined, and an expired request never counts as a yes.
Can brokers email submissions instead of filling in a form?
On the Team plan and above, yes. Give the form its own address and allow-list your brokers’ domains; each message becomes a submission with its attachments, a verified sender and fields read out of the email. See the claims email intake page for how the checks work — the same mechanism serves new business.
Put your submission desk on one queue
A submission form, your referral rules and four states make a working intake — built by the underwriting team, changed the day appetite changes.
No card required.