Non-standard coverage routing

A non-standard coverage route exists so manuscript or broker-supplied wording cannot travel the same issuance path as a library form. The classifier's job is to load the wording that will actually print, decide whether it is a known form or a bespoke term, and either produce a specialist legal route or leave the route empty. It does not rewrite the clause. It does not invent missing language. It does not issue.

Quality looks like this: if the wording is manuscript, the route cites the clause and the library gap. If the wording is a library form, the route stays empty. Empty is a completed decision, not an unfinished ticket. Counsel still reviews. Delivery waits until that review is recorded. Nothing auto-issues.

Policy administration and contract systems, including Guidewire, Duck Creek, Sapiens, and Ironclad, will assemble, file, or issue whatever the issuance process sends them. They are not the classifier. Routing has to finish before those systems treat the wording as final.

You cannot classify a term you have not loaded. Pull the coverage language that will be delivered: manuscript pages, broker forms attached to the binder, side letters that will ride with the policy, and endorsement drafts that are not yet in the form library.

Do not classify from a deal memo, a coverage summary, or an underwriter's shorthand. Those describe intent. The classifier needs the words that will print.

The policy screen and the attachments can disagree. A form code in the administration system can sit next to a side letter in a contract workspace. Load the package that will be delivered, not only the form code.

Ownership of the load matters. The person who attaches the file owns the claim that this is the wording to classify. If underwriting intended the library form and operations attached a broker manuscript, the classifier will route the manuscript. Fix the attachment. Do not override the classifier to match the notes.

Compare that loaded text against the current library, using the current form identifier. A clause that "everyone uses" is still a manuscript for routing purposes if it is not in your library. Last year's ISO number, a remembered manuscript from another account, or a broker's claim that the form is standard does not count as a match.

One illustration: a casualty file is bound with a pollution buy-back. The underwriter's notes say "standard buy-back." The attachment is a broker PDF. The trigger, the definition of "pollutant," and the notice period do not match the library form. The classifier does not "fix" the PDF to match the library, and it does not write a cleaner clause to replace it. It treats the attached text as the wording to route.

If the file also needs new endorsement text after counsel decides, that work belongs in endorsement language drafting. The classifier flags the need. It does not draft the endorsement.

A queue item that only says "send to legal" is not a usable route. Specialist review needs two cites on every non-standard item.

The manuscript clause cite tells counsel where the wording sits: section, heading, or an excerpt long enough that they do not have to reconstruct the classifier's pointer. If five clauses diverge, list five cites. Bundling them into one "manuscript package" hides which items are truly bespoke and which are library forms sitting next to a manuscript.

The library-gap cite tells counsel what was compared: the library form identifier, what that form covers, and where this wording diverges. Without that cite, counsel is doing original research, not review. The next similar file also learns nothing, because there is no recorded gap to reuse.

If the classifier cannot name a library form it compared against, it does not have a gap. Stop and load the library, or send the file back for a form identifier. Do not open a specialist path on a hunch.

A route with no library-gap cite is the first failure mode that looks like progress. The file landed in legal. Cycle time is being "managed." Nobody can say which form was missing or why this wording left the standard path. That ticket will be reworked, and the library will not get stronger.

If the loaded wording matches a library form, leave the route empty. Record the form identifier on the issuance file. Do not invent a manuscript so the file looks reviewed. Do not force a legal queue to prove the classifier is working.

Empty means the classifier found a library match and did not open a specialist path. The file still moves through ordinary issuance. Counsel still reviews under that ordinary protocol, not because this clause was flagged as bespoke.

The inverse error is filling the route because something felt unusual. Unusual to the underwriter is not the same as absent from the library. If the library contains the form, the specialist path stays closed.

Inventing a manuscript is the second failure mode that looks like completeness. An operator, or the classifier, writes coverage language that was never in the submission so the route has a clause to point at. That creates wording the insured did not negotiate and the underwriter did not accept. If there is no manuscript in the loaded file, there is no manuscript route. Use the library form, or send the file back for real wording.

The route is a work ticket. It is not an approval. Counsel still reviews. They may accept the manuscript as cited, require a named library form instead, hold the file, or send it to endorsement drafting for a controlled replacement.

Do not auto-issue because the route is complete. Do not treat "legal has the file" as "legal signed off." Close the route only when counsel records a decision against the cited clause.

Treating the route as approved is the third failure mode. Operations sees "routed to specialist legal" and issues, assuming the ticket is the control. The control is counsel's recorded decision. Until that exists, the policy is not ready for delivery.

Some issue workflows treat a closed legal queue as the condition that releases printing. Close only on counsel's decision, with the accepted text identified. A closed ticket with no accepted-text pointer is the same failure as treating the route as approved.

After that decision, assembly and bind checks still apply to the wording counsel accepted, not to the pre-review PDF. Run automated policy document assembly against the decided text. A regulatory compliance check at bind still has to run on what will actually bind. Issuance accuracy verification still has to confirm the issued pages match that decided wording, including any manuscript counsel allowed and any library form they substituted.

Keep the classifier inside the box: load wording, route with cites, leave blanks when the library already has the form, and wait for counsel. Delivery waits.