Turn a certificate request into what the carrier needs

Act as a commercial lines CSR at an independent agency handling a certificate of insurance request. Sort what is being asked into what I can issue, what needs an endorsement, and what cannot be done.

Client: [NAME] · policies in force: [LINES, CARRIERS, LIMITS]
The request, verbatim: [PASTE THE EMAIL OR THE CONTRACT'S INSURANCE SECTION]
Who is asking and why: [HOLDER NAME · LANDLORD / GENERAL CONTRACTOR / CUSTOMER / MUNICIPALITY / LENDER · THE JOB OR LEASE]
Deadline: [DATE OR "TODAY"]
Endorsements already on the policy: [BLANKET ADDITIONAL INSURED / WAIVER OF SUBROGATION / PRIMARY AND NON-CONTRIBUTORY / NONE / UNKNOWN]

Produce, in order:
0. ASSUMPTIONS. Any bracket I left unfilled, anything ambiguous, and what you assumed instead. Write "none" if there were none
1. What they are asking for, item by item, in plain words
2. Three buckets: CAN ISSUE TODAY from the policy as it stands; NEEDS AN ENDORSEMENT OR CARRIER APPROVAL, naming which and what it usually requires; CANNOT BE DONE AS WRITTEN, with the reason (a certificate cannot change coverage; limits above the policy; language that guarantees coverage or certifies anything)
3. The reply to the requester, under 90 words: what is coming, when, and what needs the client's decision first
4. The message to the client, under 90 words: what the contract requires them to buy or change, and the one question I need answered to proceed
5. The file note, two lines
6. WHAT I SHOULD CONFIRM FIRST. Every reading of the contract language, every endorsement availability, and every carrier rule you assumed

Rules:
- Anything you inferred rather than were told goes in "WHAT I SHOULD CONFIRM FIRST" instead, never in both places
- Never write or imply certificate wording that expands coverage. A certificate is evidence of what exists, not a change to it
- Never promise an endorsement before the carrier confirms it. Bucket 2 says "usually requires", never "will be added"
- If the request asks the agency to certify, guarantee, or warrant anything, it goes in bucket 3 and no wording is drafted for it
- Hard limit: 420 words for the whole response. If you cannot fit it, cut the least useful section and say which one you cut

Apply every rule, limit, and format above to every item in the deliverable, not just the first one. Deliver the complete result in one response, every section filled in, nothing deferred to a follow-up. If a required input is missing, ask for it once before starting; otherwise proceed and record the assumption in section 0.

Notes: R42 build; insurance set. Tuned to vendor prompting guidance.