Make filing checklist non-blocking

[nonprofittechy]

Illinois partner feedback

The original Illinois notes asked to remove the required Check documents / filing plan step and instead make an optional filing checklist available based on case type and party.

The main change is that filers should not be required to indicate that they have completed or reviewed the checklist before continuing with their filing.

The checklist may still be displayed as part of the Documents flow, and filers may interact with it if useful.

Proposed behavior

• Keep document checklist/guidance available in the Documents portion of the workflow.
• Do not require the filer to check off every item or explicitly confirm that they have all documents.
• Do not require document_checklist_acknowledged or an equivalent acknowledgement before proceeding.
• Allow the filer to continue to document organization and the rest of the filing regardless of checklist status.
• If checklist progress such as "have," "filed," or "later" is useful to the filer, it may remain available, but using it should be optional.
• Do not treat unchecked checklist items as errors that prevent filing.

Guidance language

Also soften the checklist language so that LITEFile does not appear to determine the legally correct or complete set of forms for the filer.

For example, instead of:

• "Always needed"
• "You need to file a Petition and Summons"
• "Your filing is missing..."

prefer language such as:

• "Commonly included"
• "May apply"
• "Some filings with these selections include..."
• "Depending on your situation, other documents may be needed."

The checklist can help users understand documents that may be associated with the filing context without representing that LITEFile has determined what they should file.

Acceptance criteria

1. The document checklist may appear in the normal Documents flow.
2. A filer can continue without checking any checklist items.
3. A filer can continue without affirmatively saying that the checklist is complete.
4. Checklist acknowledgement/state does not gate Organize Documents or later workflow steps.
5. Optional checklist progress can still be saved if that functionality is useful.
6. Checklist wording does not represent the listed documents as a guaranteed or complete set of legally required forms.
7. Unchecked checklist items do not create blocking validation errors.

Out of scope

This issue does not require:

• removing all checklist UI or making it hidden by default;
• removing the FilingPlan model or checklist-progress functionality;
• determining the correct forms for a user's legal situation;
• validating individual forms for completeness (Consider checking forms for unfilled data, or even more complex completeness checks #142); or
• changing optional AI/document analysis behavior (AI optional (and perform better) #104).

Related

• AI optional (and perform better) #104 — AI/document analysis is optional
• Consider checking forms for unfilled data, or even more complex completeness checks #142 — document/form completeness checks
• MVP: support court selection before document upload #158 — Illinois filing-flow sequencing

[nonprofittechy]

@mnewsted this sounds a lot like the filing plan...can you explain more about what the checklist is and how it differs? Can save for higher bandwidth conversation too if it's hard to describe here.

Edit: please look over revised acceptance criteria when you get a chance

[mnewsted]

@nonprofittechy By checklist, we mean something read-only that explains what forms are always, often/sometimes, and rarely filed in a certain type of case. It can also indicate when in the case process they would be filed. The below is an example copied from statewide divorce forms instructions, but I think it can be drastically simplified. The main point was that the IL reviewers thought this should be an optional, hidden-by-default (or collapse template style), read-only resource, at least at the start, rather than a functional part of the workflow.

1. Petition for Divorce or Petition for Divorce with Children — File at start
   This is the document that starts the divorce case.
   Attachments to the Petition, if needed

2. Additional Children – Petition — File at start, if needed
   Used when additional space is needed to provide information about the children in the Petition.
   Other Information About Children — File at start, if needed
   Used to provide additional child-related information associated with the Petition.

3. Certificate of Dissolution of Marriage/Civil Union —Depends on county
   In most counties, this is filed at the same time as the Petition. In some counties, it is filed later with the Judgment (the information is ultimately sent to the Illinois Department of Public Health after the divorce is final).

4. Divorce Summons — Used for service by sheriff
   Used to notify the other spouse of the divorce case.
   If using the Sheriff for service
   · Letter to the Sheriff — not filed
   o This is not filed with the court. It is used to send the Summons and other required documents to the Sheriff for service.

5. Application for Waiver of Fees— If needed to waive court fees
   Used to ask the court to waive court fees.