Compliance FW-003
Validation Checks by Instafill.ai
1
Validates Request Filed Date is present and in an acceptable date format
Checks that the 'A request to waive court fees was filed on (date)' field is not blank and matches an allowed date format (e.g., MM/DD/YYYY) and represents a real calendar date. This is important because the filing date can affect deadlines, processing order, and later calculations tied to service and hearing timelines. If validation fails, the submission should be rejected or flagged for correction because the court order record would be incomplete or ambiguous.
2
Enforces mutual exclusivity of outcome: Grant vs Deny vs Needs More Information
Validates that only one primary outcome path is selected: (a) the court grants the request, (b) the court denies the request, or (c) the court needs more information and sets a hearing. These outcomes are logically incompatible and selecting more than one creates conflicting court orders. If multiple outcomes are selected (or none are selected), the form should fail validation and require the user/clerk to choose exactly one.
3
Requires applicant identity and address completeness when an order is issued
Checks that Applicant's name, street/mailing address, city, state, and ZIP are all provided when the form is being used as an order (i.e., any of grant/deny/hearing paths is selected). This information is necessary for proper identification, mailing, and enforcement of the order and related notices. If any required identity/address element is missing, the submission should be blocked or routed to manual review because service and record matching may fail.
4
Validates State and ZIP code formats for the applicant address
Ensures the applicant state is a valid US state/territory abbreviation (e.g., 'CA') or an allowed jurisdiction value, and ZIP is either 5 digits or ZIP+4 (##### or #####-####). Correct formatting supports reliable mailing and reduces returned mail and service issues. If the state/ZIP format is invalid, the system should prompt for correction and prevent finalization.
5
Validates Case Number presence and allowed character pattern
Checks that the case number is present and matches the courtâs expected pattern (commonly alphanumeric with dashes/slashes, no illegal characters, and within a reasonable length). The case number is the primary key for docketing and associating the order with the correct case. If invalid or missing, the submission should fail because it cannot be reliably filed or matched to the correct case.
6
Validates Case Name is present and not placeholder text
Ensures the case name field is completed with meaningful party/case caption text and does not contain placeholders like 'N/A', 'unknown', or only whitespace. The case name is used for human verification, indexing, and preventing misfiling when case numbers are mistyped. If validation fails, the form should be flagged for correction to avoid misassociation with the wrong matter.
7
Validates Previous Fee Waiver Order date dependency and chronology
If 'The court made a previous fee waiver order in this case' is checked, this validation requires the previous order date to be provided and to be a valid date. It also checks logical chronology: the previous order date should not be after the current request filed date (and should not be in the future). If the dependency or chronology fails, the system should reject or flag the record because it indicates inconsistent case history.
8
Validates 'Additional Fee Waiver' selections require at least one item or 'Other (specify)' detail
When the Additional Fee Waiver section is indicated as granted/selected, the system verifies that at least one additional fee item checkbox is selected (e.g., jury fees, peace officer testimony, interpreter, experts) or 'Other (specify)' is selected with a non-empty description. This prevents issuing an order that claims additional fees are waived without identifying what is actually waived. If no items are selected (or 'Other' is selected without text), validation fails and the user must correct the selection.
9
Requires 'Other (specify)' text when 'Other (specify)' checkbox is checked
Checks that the 'Additional Fee Waiver â Other (specify)' description field is populated with a clear fee name/purpose when the 'Other (specify)' checkbox is checked. This is important because 'Other' without details is unenforceable and cannot be implemented by clerks or financial systems. If missing or too short/blank, the submission should be blocked until a meaningful description is provided.
10
Validates Denial reason path requires a specific reason and supporting details/attachment selection
If the denial box is checked, the system requires at least one denial basis to be selected (e.g., incomplete request b(1) and/or not eligible b(2)). It also enforces that the corresponding details are provided either 'Below' (with text entered) or via the appropriate attachment option. If the denial path lacks a reason or lacks the required detail/attachment indicator, validation fails because the order would not provide legally sufficient notice.
11
Validates Incomplete Request (b(1)) detail entry or attachment selection
When b(1) 'Your request is incomplete' is selected, the system checks that exactly one location is chosen for the missing-items list: 'Below' or 'On Attachment 4b(1)'. If 'Below' is selected, the missing items/details text must be non-empty; if attachment is selected, the system should require an attachment reference/flag. If these conditions are not met, the submission should be rejected because the applicant would not know what to correct within the 10-day window.
12
Validates Not Eligible (b(2)) reason entry or attachment selection
When b(2) 'not eligible' is selected, the system requires the reasons to be provided either 'Below' (with non-empty reasons text) or 'On Attachment 4b(2)'. This ensures the order contains the factual/legal basis for denial and supports due process. If neither text nor attachment selection is present (or text is blank), validation fails and the order should not be finalized.
13
Validates Hearing scheduling fields when 'Court needs more information' is selected
If the court indicates it needs more information and schedules a hearing, the system requires Hearing Date, Time, Room, and Dept to be completed and valid (date is real and not in the past relative to the order date, time is in a valid format). These fields are essential for notice and to avoid missed hearings due to incomplete scheduling information. If any are missing/invalid, the submission should be blocked or flagged for urgent correction.
14
Validates Hearing issues/questions (c(1)) are provided via 'Below' text or Attachment 4c(1)
When the hearing path is selected, the system enforces that the eligibility questions/issues to be addressed are specified either by selecting 'Below' and entering text, or by selecting 'On Attachment 4c(1)'. This is important because the applicant must know what information the court is seeking and what will be discussed at the hearing. If neither is provided (or 'Below' is selected with blank text), validation fails due to insufficient notice.
15
Validates Proof items requirement (c(2)) is consistent and includes a list or attachment when checked
If the form indicates the applicant must bring items of proof (c(2)), the system requires that the proof items are specified either 'Below' with a non-empty list or 'On Attachment 4c(2)'. This prevents an order that demands proof without identifying what documents are needed, which can lead to unfair denials for noncompliance. If c(2) is checked but no list/attachment is provided, the submission should fail validation.
16
Validates signature role selection and required signer/date fields for the order
Checks that exactly one signer role is selected (Judicial Officer or Clerk/Deputy, as represented by the signer radio list) and that the order date is present and valid. A court order must be attributable to an authorized signer and dated to be enforceable and to calculate deadlines. If signer selection is missing/ambiguous or the date is missing/invalid, the system should prevent finalization and require correction.