A manuscript endorsement is non-standard policy language — drafted by the carrier (or sometimes the broker) for a specific account, rather than a filed ISO/AAIS form with a known meaning. Because it doesn't map to a form library, it can't be judged mechanically: two manuscript endorsements with similar titles can do completely different things.
That's exactly why they're the highest-risk item on any renewal and the one place automated checking should defer to a human.
Why manuscript endorsements are high-risk at renewal
A manuscript endorsement can add an exclusion, carve back a grant of coverage, change a definition, or impose a condition — in bespoke wording that looks unremarkable in a form schedule. A renewal that introduces a new manuscript endorsement, or changes an existing one, can materially alter coverage without touching a single limit on the dec page.
Standard vs. manuscript, and why the distinction matters
A standard ISO/AAIS form is identifiable by number and edition, with a known purpose you can compare year over year. A manuscript endorsement has no such anchor — so the right treatment is to detect it, flag it, and put it in front of a person who reads the actual language. Pretending a machine 'understands' bespoke wording is how coverage surprises happen.
How human-in-the-loop checking handles them
BindCheck diffs the standard forms and dec-page numbers deterministically, and when it encounters a manuscript or non-standard endorsement it flags it for your review rather than guessing — surfacing that the renewal added, removed or changed a manuscript item so a human reads it against the account's needs. The routine comparison is automated; the judgment on bespoke language stays with the agent.