September 7, 2026
A producer forwards a prospect's email: “Can we get options before renewal?” There are three attachments, two business names, and no clear owner. The account manager opens the same files the producer already read. By afternoon, someone is still asking which information is missing.
Submission triage should leave the next person with something they can act on: the request, the deadline, the sources, the gaps, and an owner. A label in the inbox is a useful start. A usable handoff is the finish line.
This checklist is for an independent agency preparing client work. It does not describe a carrier's underwriting decisions or risk-selection process.
Start with one account and one next action
Create one task for the request before moving information into forms or carrier sites. Link the original email and attachments so the next colleague can find the evidence without searching the inbox again.
Use these seven fields as a working template:
| Field | What to record |
|---|---|
| Client | Account name and any entity-name question |
| Request | The actual work requested, in one sentence |
| Dates | Requested response date and intended coverage date, separately |
| Sources | Document names, relevant periods, and email references |
| Missing details | Questions that stop the next step |
| Owner | The person responsible for moving the task forward |
| Next action | One specific action with a follow-up date |
Download the submission handoff worksheet to use these fields in your own spreadsheet. The worksheet is a process aid, not a required insurance form.
Work through an incomplete request
Consider this fictional example. Bluebird Electric asks for renewal options. The email says September 30. The attached declarations show an October 1 expiration. A prior application lists one location, while the email mentions a new shop. Last year's payroll is attached without a current estimate.
A useful handoff would say:
Request: Prepare renewal options for Bluebird Electric. Dates: Client asks for options by September 30; confirm the intended effective date against the policy. Gaps: Confirm the new location, current operations, and exposure figures required by the intended markets. Owner: Assigned account manager. Next action: Send the reviewed missing-information request, then update the task when the client answers.
Notice what it does not do: silently turn last year's payroll into this year's estimate, replace the old location with an unconfirmed address, or treat the email deadline as a coverage instruction.
Separate blockers from work that can continue
A request can be incomplete without every task being blocked. Your team may be able to organize the documents, identify policy periods, or prepare a list of questions while waiting for a current exposure figure.
Use a small set of statuses that explain what happens next:
- Needs clarification: The request or client identity is uncertain.
- Waiting on client: A specific question has been sent and has an owner.
- Ready for preparation: Enough information is available for the defined draft task.
- Ready for review: The prepared work is waiting for the responsible reviewer.
“Ready for preparation” does not mean ready to submit or bind. Keep the next action visible beside the status so a teammate can tell the difference.
Ask AI for a handoff, then check it
Try this prompt with a permitted sample in the tool your agency uses:
Read this request and its attachments. Prepare a handoff with client, requested work, dates, source documents, missing details, and proposed next action. Show conflicting facts separately. Do not invent an owner, deadline, or missing answer. Reference the source for each important fact.
Then compare the summary to the originals. Did it distinguish the response deadline from the effective date? Did it notice the second business name? Can you find the source of each exposure figure? A fluent summary can still omit the detail that changes the work.
Relay's AI assistant gives your team a place to work with supplied client information and continue into document or configured browser tasks. Confirm any inbox monitoring, automatic assignment, or AMS updates separately. This checklist works even when the first request is added manually.
Measure the handoff rather than the number of labels
For a small pilot, record the time from receipt to an actionable handoff, active staff minutes, clarification loops, and requests returned because the next person lacked information. Keep client waiting time separate from staff work.
Review a few ordinary requests and a few awkward ones. A process that works only for a perfectly complete submission will disappoint the team when the inbox gets busy.
The submission triage overview explains the broader workflow. If ownership across the inbox is the larger problem, use the shared inbox guide alongside this checklist.
Give your team a clearer starting point. Join the Relay waitlist with the workflow you want to improve first.