Compliance DE-111
Validation Checks by Instafill.ai
1
Court Venue Identification Completeness (County/Branch/Addresses)
Validates that the SUPERIOR COURT OF CALIFORNIA county is provided and that the branch name, street address, city, ZIP code, and mailing address fields are complete enough to identify the filing venue. This is important because probate petitions must be filed in the correct county and routed to the correct courthouse location. If missing or inconsistent, the submission should be rejected or flagged for correction because it may be filed in the wrong venue or be unprocessable by the clerk.
2
Case Number and Hearing Details Format (If Provided)
Checks that the case number (if already assigned) matches the court’s expected format and that hearing date/time and department fields are either all blank (for initial filing) or all populated with valid values. This prevents partial scheduling data that can cause miscalendaring or failed docket matching. If validation fails, the system should require correction or treat the filing as an initial petition without hearing details (per configured business rules).
3
Attorney/Party Contact Block Completeness and Formatting
Ensures the filer is identified as either an attorney or a party without attorney and that the name and address fields are present and structured (street, city, state, ZIP). Validates phone and fax numbers (if provided) are in a valid US format and that email (if provided) is syntactically valid. If invalid or incomplete, the petition may not be serviceable and the court may be unable to contact the filer; the submission should be flagged and returned for correction.
4
State Bar Number Required When Attorney Is Listed
If an attorney is named, validates that a State Bar number is present and matches a numeric pattern consistent with California bar numbers (and optionally cross-checks against a bar registry if available). This is important for attorney authentication and proper court record indexing. If missing/invalid, the system should block submission or require the filer to correct the attorney identification section.
5
Estate and Decedent Name Presence and Consistency
Validates that the 'ESTATE OF (name)' and 'DECEDENT (name)' fields are populated and consistent (e.g., the estate name should correspond to the decedent’s legal name). This prevents miscaptioned cases and indexing errors in court systems. If inconsistent or blank, the petition should be rejected or routed to manual review to avoid creating a case under the wrong party.
6
Decedent Date of Death and Place of Death Validation
Checks that the date of death is a valid date (not in the future, and not unreasonably old if system rules apply) and that the place of death is provided as a recognizable location (city/county/state or equivalent). This information is essential to establish jurisdiction and to support probate administration. If missing or invalid, the petition should be flagged because the court cannot confirm basic eligibility and venue facts.
7
Residency/Venue Logic for Decedent (Resident vs Nonresident)
Validates that exactly one residency status is selected: either the decedent was a resident of the named county or a nonresident with an estate located in the named county, and that the corresponding required details are provided. If resident is selected, the street address/city/county of residence at death must be completed; if nonresident is selected, the location of property in the county must be specified. If the logic fails (both/none selected or missing dependent fields), the submission should be rejected because venue cannot be established.
8
Citizenship Field Dependency (Non-U.S. Country Required When Indicated)
If the form indicates the decedent was a citizen of a country other than the United States, validates that a country name is provided and is not left blank. This matters for notice, consular issues, and potential international administration considerations. If the country is missing when non-U.S. citizenship is indicated, the system should require completion before acceptance.
9
Petition Type Selection (Mutually Exclusive Primary Relief Requested)
Validates that the petition selects at least one primary request (e.g., Probate of Will, Letters of Administration, Letters Testamentary, Special Administration, Lost Will options) and enforces mutual exclusivity where the form structure requires it (e.g., not selecting conflicting letter types simultaneously). This is critical because the court must know exactly what authority is being requested. If conflicting or missing, the petition should be blocked or routed for correction to prevent issuance of incorrect letters.
10
Personal Representative Appointment Section Completeness
Ensures that when appointment of a personal representative is requested, the form identifies the role (executor, administrator with will annexed, administrator, special administrator) and includes required supporting statements (e.g., named in will, nominee, successor). This prevents incomplete appointment requests that cannot be granted. If required appointment basis is not provided, the system should flag the filing and require the missing appointment justification/attachments.
11
Will/Intestacy Consistency (Will Admitted vs Intestate)
Checks logical consistency between selecting 'Decedent died intestate' and any selections indicating a will/codicil exists or is to be admitted to probate (including will dates and self-proving statements). A petition cannot simultaneously proceed as intestate while asking to admit a will unless the will is explicitly alleged lost and handled under the lost will pathway. If inconsistent, the system should require the filer to correct selections or provide the appropriate lost-will allegations and attachments.
12
Will and Codicil Date Format and Presence When Will Is Referenced
If the petition references a will and/or codicil, validates that the will date is present and in a valid date format, and that any codicil date provided is also valid. This is important for identifying the operative testamentary instrument and for resolving priority among multiple documents. If dates are missing/invalid, the petition should be flagged because the court cannot determine which instrument is being offered.
13
Lost Will Attachment Requirement and Explanation Dependency
If the petition indicates the original will/codicil has been lost, validates that Attachment 3f(3) is included with either a copy of the lost instrument or a written statement of the testamentary words/substance, plus reasons addressing the presumption under Probate Code § 6124. This is essential because lost will petitions require heightened proof and specific allegations. If the attachment or required explanation is missing, the system should block submission or mark it as legally insufficient.
14
Bond Election and Amount Validation (Including Blocked Account Deposits)
Validates that the bond section is internally consistent: either bond is waived (and a valid waiver reason is selected with required waivers attached) or bond is requested/fixed with a numeric dollar amount. If blocked account deposits are requested, validates that the deposit amount is numeric and that the institution and location are specified. If amounts are non-numeric, negative, or required supporting attachments are missing, the petition should be rejected or returned for correction because bond orders depend on accurate figures and legal basis.
15
Estate Value Arithmetic and Non-Negative Currency Checks
Checks that all monetary fields (personal property, real property gross fair market value, encumbrances, net value, subtotals, totals, and annual gross income fields) are valid currency numbers (no letters, no negative values unless explicitly allowed) and that computed totals match the stated subtotals/totals (e.g., subtotal equals sum of components; net real property equals gross minus encumbrances; total equals sum of required lines). This prevents incorrect fee calculations, bond calculations, and inaccurate court findings. If arithmetic fails, the system should flag discrepancies and require correction or auto-recalculate with user confirmation.
16
Heirship/Survivor Boxes Logical Consistency and Required Listing in Item 8
Validates that the survivor selections (spouse/partner, children/issue, parents, grandparents, next of kin, etc.) are not contradictory (e.g., selecting both 'no spouse' and 'spouse', or 'no child' and 'child') and that when the form states survivors are 'listed in item 8,' item 8 actually includes at least one corresponding person entry. This is important because notice and distribution depend on accurate heirship statements. If inconsistent or item 8 is missing required persons, the petition should be flagged for correction to avoid defective notice and potential due process issues.
17
Item 8 Person Entries Structure (Name/Relationship/Age/Address) and Age Validity
Ensures each person listed in item 8 (and any Attachment 8) includes a name, relationship to decedent, age (numeric and within a reasonable human range), and a deliverable address (not blank; includes city/state/ZIP where applicable). This is critical for statutory notice and for confirming adult waivers where claimed. If entries are incomplete or ages are invalid, the system should require correction because the court cannot rely on the list for notice and bond waiver determinations.
18
Signature, Verification, and Date Requirements (All Petitioners Sign)
Validates that the petition is signed and dated, includes the perjury declaration, and that all petitioners have signatures (or that additional petitioner signatures are present on the last attachment as indicated). If an attorney signature block is used, validates the typed/printed name accompanies the signature. If signatures/dates are missing, the submission should be rejected because an unverified petition is procedurally defective and cannot be accepted for filing.