Compliance JUD-100
Validation Checks by Instafill.ai
1
Case Number format and cross-form consistency (JUD-100, CIV-100, POS-010)
Validate that the Case Number is present and matches an allowed court case-number pattern (e.g., alphanumeric with permitted dashes/slashes) and is not placeholder text. The same Case Number must be identical across all included forms (Judgment, Request for Entry of Default, Proof of Service) to prevent misfiling into the wrong case. If the format is invalid or the numbers differ across forms, block submission and require correction before acceptance.
2
Party name completeness and consistency across headers and party sections
Ensure Plaintiff and Defendant names are provided as full legal names (not blank, not initials-only) and are consistent wherever they appear (form headers, item 5 parties, CIV-100 item 1, POS-010 item 3). This prevents judgments/defaults being entered against the wrong party or an unidentifiable party. If any required party name is missing or inconsistent, flag the submission and require reconciliation (or an attachment checkbox indicating continuation where applicable).
3
Mutually exclusive judgment basis selection (Default vs Stipulation vs After Court Trial)
Validate that exactly one primary judgment basis is selected among 'By Default', 'On Stipulation', and 'After Court Trial' on JUD-100, unless the court’s business rules explicitly allow combinations. These options represent different procedural paths and drive which downstream fields are required. If multiple bases are selected (or none), reject the submission and prompt the filer to choose the correct single basis.
4
Judgment entered by authority selection (Court vs Clerk) and compatibility with judgment type
Require exactly one selection for 'Judgment is entered by THE COURT' or 'THE CLERK' on JUD-100, and validate it is logically compatible with the selected judgment path (e.g., clerk judgment typically aligns with CCP 585(a) scenarios; court judgment aligns with 585(b) evidence consideration). This ensures the correct signing/processing workflow and prevents an unauthorized entry type. If incompatible or both/none selected, fail validation and require correction.
5
Default judgment detail requirements and exclusivity (CCP 585(a) vs 585(b)/(d))
If 'By Default' is selected on JUD-100, require completion of the default prerequisites (proper service, failure to answer, default entered) and require selection of either 'Clerk’s Judgment (585(a))' or 'Court Judgment (585(b))' as applicable. If 'Court Judgment' is selected, require at least one evidence basis checkbox (testimony/evidence or written declaration under 585(d)). If required default details are missing or conflicting (e.g., both clerk and court judgment checked), stop submission and request correction.
6
Stipulation pathway validation (filed written stipulation or on-record stipulation)
If 'On Stipulation' is selected, require at least one supporting stipulation indicator: 'signed written stipulation was filed' or 'stipulation stated in open court/on the record' (per the form’s options). This confirms the legal basis for entering a stipulated judgment and supports auditability. If none of the supporting stipulation fields are selected, fail validation and require the filer to indicate how the stipulation was made and approved.
7
After court trial fields completeness (trial date/time, judicial officer, appearances)
If 'After Court Trial' is selected, require a valid trial date and time and the presiding judicial officer’s name, and require at least one appearance entry or an attachment indicator (Attachment 3b) for each side as applicable. This ensures the judgment is tied to a specific trial event and that the record reflects who appeared. If the trial metadata is missing/invalid or appearances are blank without an attachment flag, reject the submission.
8
Statement of decision selection integrity (requested vs not requested)
When the statement of decision section is applicable (After Court Trial), enforce that exactly one of 'was requested' or 'was not requested' is selected. This prevents ambiguous records and supports downstream processing and appellate record completeness. If both or neither are selected, fail validation and require a single selection.
9
Parties in judgment (Item 5) must align with monetary directives (Item 6)
Validate that if item 6a (defendant must pay plaintiff) is used, item 5a must be selected and must include at least one plaintiff and one defendant name; similarly, if item 6c is used, item 5c must be selected with cross-complainant and cross-defendant names. This ensures the money award is tied to identified judgment creditor/debtor parties. If amounts are entered without the corresponding party section completed, block submission and require completion.
10
Monetary amount formatting, non-negativity, and currency precision
All dollar fields (damages, interest amount, fees, costs, other, totals, daily damages, service fee, memorandum of costs lines) must be numeric, non-negative, and limited to two decimal places, with no currency symbols or text. This prevents calculation errors and ensures compatibility with court financial systems. If any amount is non-numeric, negative, or has invalid precision, fail validation and highlight the offending field.
11
Totals arithmetic validation for JUD-100 item 6 (6a.6 and 6c.6)
If a total is provided in 6a(6) or 6c(6), validate it equals the sum of the component lines entered (damages + prejudgment interest amount + attorney fees + costs + other amount). This catches data entry mistakes that could change the enforceable judgment amount. If the total does not match the computed sum, reject submission or require confirmation/correction per system policy.
12
Prejudgment interest rate and amount logical validation
When prejudgment interest is selected, require an annual rate percentage within a reasonable range (e.g., 0.000–100.000) and a non-negative interest dollar amount; also ensure the rate is not provided without the interest checkbox/amount (and vice versa). This prevents incomplete or nonsensical interest awards. If the rate/amount pairing is inconsistent or out of range, fail validation and require correction.
13
‘Other’ amount requires specification text (JUD-100 6a(5)/6c(5) and item 8)
If an 'Other' monetary line is checked or an 'Other' amount is entered, require a non-empty description specifying what the amount represents; similarly, if item 8 'Other' is used, require explanatory text. This is necessary for enforceability and auditing because unspecified 'other' awards are ambiguous. If the description is missing, block submission until a clear specification is provided.
14
Natural person judgment-debtor claim-type amounts must reconcile to judgment total
If item 7 indicates the judgment debtor is a natural person and medical/personal/consumer debt amounts are entered, validate that these amounts are non-negative and that consumer debt (if provided) does not exceed the personal debt amount. Additionally, the sum of medical + personal debt portions should not exceed the overall judgment total for that debtor. If these constraints are violated, fail validation and require corrected allocations.
15
CIV-100 default request: required dates, signatures, and selection coherence
On CIV-100, require the complaint/cross-complaint filing date (item 1a), the requesting party name (item 1a 'by (name)'), and a signature with printed name and date. Validate that the request type selection is coherent (Entry of Default vs Clerk’s Judgment vs Court Judgment) and that defendant names are provided for the requested default/judgment. If any required identity/date/signature element is missing or the selection is contradictory, reject the filing as incomplete.
16
POS-010 proof of service: service method completeness and substituted-service mailing dependency
Require that exactly one service method is selected (personal, substituted, mail with acknowledgment, or other) and that the corresponding required fields are completed (service date, time, address, and person served/relationship where applicable). For substituted service, enforce the dependency that a follow-up mailing date and mailing city are provided (or an attached declaration of mailing is indicated), and that a declaration of diligence is attached when required by the form. If method-specific required fields are missing, fail validation because service may be legally defective.