On the Files tab, the Required here rail down the left lists the forms and disclosures this address triggers — and matches them to the documents in the table beside it. The counter (e.g. 9/13 collected) shows at a glance how much of the file is in place.
How items get checked off
You don't normally tick boxes by hand. When you upload a document, LetterScript classifies it; if it satisfies a required item, that item is marked collected automatically. Each row carries a small status chip:
- Collected — a matching document is on the transaction.
- Missing or To collect — still outstanding; obtain it and upload it. Outstanding rows carry their own Upload button.
- Attestation — an action to perform or confirm rather than a document to collect.
One packet can satisfy several rows
A single PDF often carries several C.A.R. forms. When a row is satisfied by a form bundled inside a packet rather than by the file's own type, its document tag reads SCO · in packet — the form code, then the tag — so you can see which of the packet's forms did the work. Hover the tag for the detail.
You always have the last word
Every row has an Override control beside it: mark a requirement satisfied, waived, or not applicable when you know something the documents don't show. An overridden row goes struck through with a badge naming the verdict — Marked satisfied, Waived, Not applicable — and hovering it says who set it and when. Collaborators with view-only access see neither the upload nor the override control.
The sections
- Required items — what this property's jurisdiction and hazards demand.
- May also apply — depends on facts we can't see from the address — items whose obligation hinges on something the parcel record doesn't say: whether the property is tenant-occupied (local rent-control and just-cause notices), whether it's on a private well rather than public water, whether it sits in a Mello-Roos district, or how many dwelling units it has. Each one says what would settle it. They are not counted in the collected total, because we can't confirm they apply — review them yourself and act on the ones that do.
- Other POS documents on this transaction — disclosure documents you uploaded that aren't tied to a required item.
Where the requirements come from
The checklist is driven by the same property-level data as the full Point-of-sale requirements card beneath it — jurisdiction ordinances plus hazard overlays for the exact address. Informational only — not legal advice. Rules change and the list may be incomplete; the local jurisdiction is always the final authority — confirm each requirement with the city or county before close.