# Every claim opens on a form. Your agent reads the fields.

An independent, typed model of the loss notice, for agents to fill and check.



**Every deadline in a claim keys off the loss notice.** Who reported, what happened, where and when. **acords.co types it.**

## One family of forms, one field model.

The industry files claims and proves coverage on standard forms. The fields, not the paper, are what an agent needs typed.

ACORD Corporation is the standards body whose published forms the industry files claims and proves coverage on; carriers, agencies and management systems license them through ACORD. When an agent says "send the 25" or "file the loss notice", they mean a specific, standardized set of fields, and it is the fields, not the paper, that an agent-first system needs typed.

This door starts with the loss notice: the first notice of loss (FNOL) an agent, broker or insured files to open a claim. Its fields are the intake record of the entire claims loop. Who reported, under which policy, what happened, where, when and who to contact: every downstream deadline and every adjuster assignment keys off this record.

The notice shown on this page is an original layout of the data fields commonly found on a loss notice, with fictional values. It is not a reproduction of any ACORD form.

- **The family:** Three loss notices and a certificate, with fields in common.
- **Published by:** ACORD, the industry's standards body. This site is independent.
- **Filled by:** Agents, brokers and insureds at first notice of loss.
- **Sent to:** The carrier's claim intake, where the claim's clocks start.
- **On this page:** An original layout with fictional values, not an ACORD form.

## The loss notice, as fourteen typed fields.

The model a filed notice resolves to, whichever form carried it. Free, with no key.

| Field | Type | Meaning | Source |
|---|---|---|---|
| `form` | property | auto | liability | The notice family. | Agent intake |
| `reported_at` | date-time | When it was filed. The claim's clocks start here. | Agent intake |
| `reported_by` | string | The insured, the agent of record or a broker. | Agent intake |
| `carrier` | string | The carrier the notice is addressed to. | Policy record |
| `policy_number` | string | The policy the loss is claimed under. | Policy record |
| `term_start · term_end` | date | Policy period: the loss date should fall inside. | Policy record |
| `named_insured` | string | Named insured on the policy. | Policy record |
| `contact` | object | Who the adjuster should reach, and how. | Agent intake |
| `date_of_loss · time_of_loss` | date · time | When it happened, as precisely as known. | Insured's report |
| `loss_type` | string | Peril: wind_hail, fire, water, collision, theft, liability. | Insured's report |
| `loss_location` | string | Where it happened. | Insured's report |
| `description` | text | A plain account of the loss, injuries noted. | Insured's report |
| `authorities_contacted` | string | Police or fire report, if any. | Insured's report |
| `remarks` | text | Anything material that fits no field. | Agent intake |

Schema: https://acords.co/schema.json · Example: https://acords.co/example.json

## What your agent does with it

- **Read a filed notice.** A completed notice in, typed fields out, whichever form it came on. `POST /parse`
- **Draft the notice.** Intake answers in, a typed notice and the questions left out. `prefill_loss_notice`
- **Check before filing.** Loss inside the term, dates in order, a contact who can be reached. `validate_loss_notice`
- **Explain any field.** What a field means, who supplies it and what depends on it. `explain_loss_notice_field`

## Hand it to your agent

Point your agent at the MCP server. Prefill, the checks and the field reference become tools.

```json
{ "mcpServers": { "acords.co": { "url": "https://acords.co/mcp" } } }
```

Tools:

- `get_loss_notice_schema`: The JSON Schema (2020-12) for the loss notice: every field, its type and what it means. Also served at https://acords.co/schema.json.
- `get_loss_notice_example`: A complete, valid example LossNotice record with fictional values. Also served at https://acords.co/example.json.
- `explain_loss_notice_field`: What one field of the loss notice means, its type, and where the value comes from. Accepts paths like authorities_contacted.
- `validate_loss_notice`: Check a LossNotice record against the schema, then run the document's own checks (sums, dates). Returns valid (the shape matches), consistent (every check passes too), errors (schema) and warnings (checks). Nothing is stored.
- `prefill_loss_notice`: Turn the fields gathered at intake into a typed LossNotice: loss_type and dates normalized, the form family inferred from the peril, and every required field still missing listed with the question to ask for it. Nothing is invented and nothing is filed.

## Built to be read by machines

- https://acords.co/llms.txt · https://acords.co/llms-full.txt · https://acords.co/index.md · https://acords.co/index.json
- https://acords.co/schema.json · https://acords.co/example.json · https://acords.co/openapi.json · https://acords.co/mcp
- https://acords.co/.well-known/agents.json · https://acords.co/sitemap.xml · https://acords.co/robots.txt

## Questions

### What is a first notice of loss?

The first report of a loss to the carrier. It opens the claim file and starts its clocks: who reported, under which policy, what happened, where and when.

### Which ACORD forms are loss notices?

ACORD 1, 2 and 3: property, auto and general liability. The ACORD 25 is the certificate of liability insurance, a different form.

### Is acords.co affiliated with ACORD?

No. It is an independent reference to the fields those forms carry, and the notice shown here is an original layout.

### Is the field model free?

Yes, with no key: the model, the example, the checks and prefill. Parsing filed notices needs an access key.

## File every loss notice from typed fields.

Request an access key for parsing filed notices. Request access: https://acords.co/#access

---

Independent reference. Not affiliated with, endorsed by or licensed by ACORD Corporation; ACORD and the form numbers are its marks, used to identify its forms. © 2026 acords.co