Clarify “main document” versus Tyler “Lead Document” filing components

[nonprofittechy]

Partner testing feedback

Illinois LITEFile testing on a laptop in Chrome:

• @VTskier After uploading three documents together, all three appeared to be Lead Documents, and the tester could not unselect Lead Document. This was confusing because it looked as though all three PDFs were being designated as the one lead/main document.

Code check / feasibility

The current implementation has two different concepts that use similar language:

1. organize_documents.html asks Which PDF is the main document? and enforces exactly one overall main_document radio choice.
2. Each PDF is then sent as its own filing/document record and has a court Filing Component. In organize-documents.js, if no component has been saved, LITEFile deliberately selects the component marked required or with EFSP code LEAD. The code comment explains that each document's filing needs its own required lead component or Tyler rejects it later.

So the observed behavior appears technically intentional at the Tyler filing-component layer, but the UI terminology makes it look like the filer has selected three overall lead documents. Simply allowing the required component to be unchecked could make the filing invalid.

Proposed behavior

• Keep the single overall main document concept visually and linguistically distinct from the Tyler/court filing-component metadata.
• Rename the per-document Document role section to a clearer user-facing label, or add help text explaining why more than one PDF may have a court value called Lead Document.
• If a filing component is required and cannot validly be unselected, explain that rather than presenting it as a freely optional choice.
• Consider hiding a single required filing-component choice from the filer and showing it as read-only explanatory metadata if there is no meaningful decision to make.

Related

• Case Category / Case Type / Filing Type should probably be addressed together on the same screen #134 discusses Case Category / Case Type / Filing Type and user intent on the same screen.
• This issue should not change the payload semantics without confirming Tyler requirements.

Acceptance criteria

1. A filer can understand that only one PDF is the overall main document even when several per-document court components are named Lead Document.
2. Required court filing components are not presented as if they can safely be deselected.
3. Existing valid Tyler payload behavior is preserved.