ACORD forms filled from the records you already keep

Agency Nexus fills seven ACORD applications and three ACORD certificates. The certificates — 25, 27 and 28 — have their own certificates page. The applications are these:

A form can be asked for by number or by name. "The workers comp application", "the umbrella section" and "ACORD 130" all find the right form, and a request that could mean two forms is answered with a question instead of a guess.

Every value placed on a form comes from one of three places, and nowhere else.

• A record. The client's name, address and contacts; the policy's carrier, dates and limits; the agency's name, license and producer block.
• A declared rule. A small set of written rules, such as deriving the expiration date from the effective date and the term.
• Nothing. A field the records do not hold stays blank. The system does not invent a value to make a form look complete.

The same prefill runs whether a person opens the form or Nexus AI prepares it, so the two can never disagree about what goes on the page.

Before a form is generated, Agency Nexus shows three lists for it: the fields that will print, the fields that are missing, and where in the system each missing value is added — the client profile, the policy or the agency settings.

That turns an incomplete application from something discovered by a carrier underwriter into something fixed at the desk, in the record where it belongs, so the next form does not have the same gap.

Florida does not use the standard ACORD 130 for its own workers' compensation business; it has its own edition, the ACORD 130 FL.

When an agency located in Florida asks for "the 130", Agency Nexus gives it the Florida edition. Asking for the standard 130 or the 130 FL by its exact name still works either way. The Florida page covers the other Florida-specific behaviour in the system.

Nexus AI can prepare an ACORD application in the agency's chat, and the same rule applies as everywhere else in the product: it prepares, a person confirms.

1. The assistant finds the client and the form, and fills it using the same prefill.
2. It shows the prepared values and anything still missing, including a signature.
3. The user confirms. Only then is the document generated and stored.

A prepared form that is not confirmed is not a document. The confirmation can be used once and expires 15 minutes after the form was prepared.

An agency administrator can upload the agency's own version of an ACORD template. The PDF is checked against the form's field map when it is uploaded, and stored as a draft: nothing is switched on without someone activating it. If the agency has no usable template of its own for a form, the system template is used.

Applications are generated as editable PDFs, so a carrier or the applicant can still complete a field by hand. Certificates are flattened, so what the holder receives cannot be edited. Every generated form is stored as a document on the client with its version, and the generation is recorded in the audit log.