Compliance FL-300
Validation Checks by Instafill.ai
1
Validates party identity fields are complete (Petitioner/Respondent/Other Parent/Party)
Checks that the form includes the names for Petitioner and Respondent, and includes Other Parent/Party when that role is selected or referenced elsewhere in the request. This is essential to ensure the court and all parties can identify who the orders apply to and who must be served. If missing or inconsistent, the submission should be flagged as incomplete and prevented from filing until corrected.
2
Validates case number presence and format consistency across pages
Ensures the CASE NUMBER field is provided (when required for an existing case) and matches the same value wherever it appears on the form. This prevents misfiling into the wrong case and ensures the clerk can associate the request with the correct docket. If the case number is missing or inconsistent, the system should reject the submission or route it to manual review depending on whether the filing is initiating or post-judgment.
3
Validates court venue fields (County, branch, addresses) are complete and non-contradictory
Checks that the Superior Court county is provided and that branch name and court address fields are present when required, especially if an 'other (specify)' address is selected for the hearing location. Accurate venue information is critical for scheduling, service, and ensuring the request is heard in the correct location. If venue fields are incomplete or contradictory (e.g., county missing but branch address provided), the submission should be blocked for correction.
4
Validates attorney vs. self-represented section completeness (State Bar number, firm, contact info)
If an attorney is indicated, verifies that attorney name, State Bar number, firm name (if applicable), and contact details (address, phone, email) are provided in acceptable formats. If the filer is self-represented, ensures the attorney fields are not incorrectly populated in a way that implies representation. If validation fails, the system should require correction to avoid improper service and incorrect attorney-of-record designation.
5
Validates contact information formats (telephone, fax, email, ZIP code)
Checks that telephone and fax numbers (if provided) follow a valid North American numbering format and that email addresses match standard email syntax; ZIP codes should be 5 digits or ZIP+4. Reliable contact information is necessary for notices, service coordination, and court communications. If formats are invalid, the system should prompt for correction; if required contact fields are missing, the submission should be marked incomplete.
6
Validates Notice of Hearing fields are complete when present (TO, date, time, dept, room, address)
Ensures that when the Notice of Hearing section is included in the submission, the 'TO (name)' recipient is specified and the hearing date, time, department, and room are provided, along with a valid hearing address selection. These fields are essential for due process and proper notice to the served party. If any are missing or malformed, the system should prevent finalization or require court/clerk completion before issuance.
7
Validates service deadline logic (service date and responsive declaration due date)
Checks that the 'Service must be on or before' date and the 'Responsive Declaration must be served on or before' date are valid dates and logically occur on or before the hearing date/time. This prevents impossible or unlawful timelines and reduces the risk of defective notice. If deadlines occur after the hearing or are not valid dates, the system should flag the filing for correction or clerk review.
8
Validates restraining/protective order information completeness when indicated
If the filer marks that domestic violence restraining/protective orders are in effect, verifies that at least one court type (criminal/family/juvenile/other) includes a county/state and, if known, a case number. It also checks that the parties between whom the orders are in effect are identified (Petitioner/Respondent/Other Parent/Party). If incomplete, the system should require additional details or an explicit 'unknown' indicator to avoid misleading the court about existing protective orders.
9
Validates child custody/visitation child list completeness and date-of-birth format
When child custody or visitation is requested, ensures at least one child is listed with a name and a valid date of birth (e.g., MM/DD/YYYY) and that custody designations are provided (physical custody to, legal custody to) for each child or via a clearly referenced attachment. This is necessary for the court to identify the children subject to the requested orders. If any child entry is missing required elements or DOB is invalid/future-dated, the submission should be rejected or require correction.
10
Validates custody/visitation request method selection (attached forms vs. narrative) and attachment references
Checks that the filer either identifies the attached forms used to specify requested custody/visitation orders or provides the 'As follows' narrative, and that any marked 'Attachment' references (e.g., Attachment 2a) are actually included. This prevents blank requests where the court cannot determine what orders are being sought. If neither method is completed or attachments are missing, the system should block submission as incomplete.
11
Validates 'change from current order' fields include prior order date and description
If the filer indicates the request is a change from a current order (custody/visitation, child support, spousal/partner support, or property control), verifies that the prior order filing date is provided and that the existing order terms are described. This is important because modification requests require the court to know what is being modified and when it was ordered. If the change box is checked without the prior order date/terms, the system should require completion before filing.
12
Validates child support request entries and monetary amount rules
When child support is requested, ensures each child entry includes the child’s name and age (or DOB from the custody section if the system cross-links), and that any 'Monthly amount requested' is a valid non-negative currency amount with reasonable precision (two decimals). It also checks that the filer does not provide a non-guideline amount without indicating guideline basis or providing an explanation in the support-reasons field. If amounts are invalid or required child details are missing, the submission should be rejected or returned for correction.
13
Validates required financial disclosure forms are included for support/fees requests
If child support, spousal/partner support, or attorney’s fees and costs are requested, verifies that a current Income and Expense Declaration (e.g., FL-150) or a qualifying simplified financial statement (e.g., FL-155) is indicated as filed, consistent with the form’s checkboxes. Financial disclosures are typically required for the court to set support and evaluate fee requests. If the request is made without the required financial form selection/attachment, the system should flag as noncompliant and prevent submission.
14
Validates spousal/partner support amount and modification/end selection consistency
When spousal or domestic partner support is requested, checks that the monthly amount is a valid currency value and that the filer selects whether they are requesting to change or end an existing order when a prior order date is provided. If the request is post-judgment modification, verifies that the Spousal or Partner Support Declaration Attachment (e.g., FL-157) or an equivalent declaration is attached/indicated. If these elements are missing or contradictory, the system should require correction to avoid an unsupported or ambiguous request.
15
Validates property control requests include property description and responsible party selection
If property control is requested, ensures the filer selects which party is to receive exclusive use/possession/control and provides a meaningful description of the property (owned/buying/lease/rent selection should not be blank when property is listed). For debt payment orders, validates each line item includes payee, purpose, amount (valid currency), and due date (valid date). If property/debt details are incomplete, the system should flag the request as insufficient for enforcement and require completion.
16
Validates attorney’s fees and costs total amount and supporting attachments
When attorney’s fees and costs are requested, checks that the total amount is a valid non-negative currency value and that at least one supporting basis is indicated (Income and Expense Declaration and/or the relevant fee request/supporting declaration attachments). This ensures the court has the information needed to assess need and ability to pay. If the amount is missing/invalid or no supporting documentation is indicated, the system should prevent submission or route to manual review per court policy.
17
Validates urgency/time-shortening request fields (court days) and justification
If the filer requests shortened time for service or an earlier hearing, verifies that the number of court days is a positive integer and that a specific justification is provided in the 'I need the order because' field. This is important because expedited relief requires a stated basis and a clear requested timeline. If the filer selects urgency options without a valid day count or without a justification narrative, the system should require completion before allowing the request to proceed.
18
Validates declaration signature block completion (date, printed name, signature) and page-limit acknowledgment
Ensures the declaration section includes a date, the applicant’s typed/printed name, and a signature indicator (electronic signature acceptance or wet signature capture, depending on channel). It also checks that any attached 'Facts to Support' declaration does not exceed 10 pages unless an explicit court permission indicator is included. If signature/date are missing or attachments exceed limits without permission, the submission should be rejected as not properly executed or noncompliant.