A commercial change request is finished only when it has passed through every stage. It is received, any missing inputs are collected, it is sent on under your agency’s procedure, and any response is reviewed by the licensed person your agency designates. Then the client is told the outcome and the request is closed. Each stage needs one named owner on the actual request. The agency systems checked for this guide document task tools, so start by checking what yours can do.
What this guide covers
This guide covers the administrative status of a mid-term service or change request: who holds it, what it is waiting for, and when it is finished. It doesn’t cover whether a change should be made, what it means for coverage, how quickly anything will happen, who may legally perform a step, or errors-and-omissions exposure. Those remain with your licensed staff and your agency’s procedures. Your agency also sets its own due dates.
Receipt is not review
When a carrier document arrives, a request can drift in two ways. Someone treats the arrival as the end of the job, or the document sits attached while the follow-up stays open and no one looks at it. Arrival is a stage. The licensed person your agency designates still compares what came back with what was asked for, under your procedures, before anyone tells the client it is done. Some systems can show a downloaded change as confirmed when its fields match. That status is information, not your agency’s review. The review stage stays in the routine, and your procedures set how it is done. Keeping “received” and “reviewed” as separate stages makes both kinds of drift visible.
Waiting on inputs is not the same as ready
A request can stall while it waits on something: details from the client, a decision from a producer, or a response from a carrier. Waiting is fine as long as someone owns the chase. For each missing input, record who is chasing it and when they will check again. A request moves to “ready to send” only when every input is in and it has whatever approval your agency requires. Naming a chaser doesn’t make it ready.
Start with your agency system
EZLynx’s endorsements and change requests article describes task reminders for a change request and comparing a returned endorsement with the request. It notes that a downloaded endorsement whose fields match exactly may already show as confirmed, and that completing the open task is a separate step after checking accuracy. It applies to specific EZLynx products, so check yours. HawkSoft’s renewal workflow guide documents task templates, renewal reports and assignment across administrators, managers and servicing staff. Its example is renewals, not mid-term changes, so check whether the same task tools fit your change requests. (Product check: November 1, 2026.)
You may want one view that shows each request’s age, whether a response has arrived, and whether it matches the request. We haven’t verified that any particular system combines all three for change requests. Check yours before planning around it.
Principal-led vs service-team agencies
Principal-led: when the principal also handles servicing, ownership may be clear, but requests can wait behind sales work. A fixed daily look at open change tasks, sorted by stage, is one habit to try.
Service team: when account managers and assistants share the work, the risk is the handoff between stages. Keep a default role for each stage. Then put a named person or queue on each actual request, with cover for absences, and have the receiver confirm they have it. Agree which licensed people may move a request past review.
Copyable stage table
| Stage | Owner | Done when | Exception goes to |
|---|---|---|---|
| Received | Service team member | Logged with the client’s request in their words; the named owner has confirmed they have it | Service lead |
| Waiting on inputs (if anything is missing) | Service team member | Every missing item collected. While waiting, each item has a named chaser and recheck date | Service lead, if a recheck date passes with the item still missing |
| Ready to send | Per agency procedure | All inputs in, and any approval your agency requires recorded | Licensed account manager |
| Sent on | Per agency procedure | Submitted as your agency requires | Licensed account manager |
| Response received | Service team member | Logged as “received, not reviewed” and assigned to the reviewer | Service lead, if not reviewed by the time your agency sets |
| Review | Licensed person your agency designates | Reviewed under agency procedure; any substantive question stays with licensed staff | Principal or designated licensed lead |
| Client informed and closed | As your agency assigns | Client told per procedure; task closed | Service lead |
These stages and columns are our suggested routine, not fields from any particular product.
Synthetic example, not a customer result
A small agency with a principal, one licensed account manager and one service assistant. On Monday a commercial client emails asking to add a newly leased vehicle. The assistant logs the request, confirms they own it, and marks it as waiting on inputs because the vehicle details are missing. The assistant owns the chase and sets a recheck for Wednesday.
The client sends the details on Tuesday. The account manager confirms the request is ready to send, and it is sent on under agency procedure. When the carrier’s document arrives, the assistant logs it as “received, not reviewed” and assigns it to the account manager. The account manager reviews it and finds a detail that doesn’t match the request. Because that is a substantive question, it stays with the account manager rather than being settled by the assistant. Once the question is resolved and reviewed, the client is informed and the task is closed.
The routine didn’t make any decision. It made sure every stage had a name on it, and kept the mismatch with someone qualified to handle it.
Next step
Walk the synthetic request above through your own system with your service team, using made-up details and no client or policy records. Note any stage where no one would clearly own it, or where a request could look finished before review. If a gap remains after you’ve checked your system’s task and template options, Abundance Applied is open to a short process conversation, with no client or policy records involved.
Sources
Product documentation checked 1 November 2026. Features depend on the current plan, permissions and setup.