The Legal Innovation & Technology Lab's Form Explorer ^Beta @ Suffolk Law School Last updated 2023-04-02

LIT Lab Home | About The Explorer | Find & Compare | Explore: California Lists

Here is the text we could read:

SUPERIOR COURT OF CALIFORNIA, COUNTY OF

FOR COURT USE ONLY

(THIS FORM IS FOR COURT USE ONLY)

FL-172

STREET ADDRESS:

MAILING ADDRESS:

CITY AND ZIP CODE:

BRANCH NAME:

PETITIONER/PLAINTIFF:

RESPONDENT/DEFENDANT:

OTHER PARTY:

PETITION

The petition for
was filed on (date):

BACKGROUND DATA

CASE INFORMATION—FAMILY LAW

CASE NUMBER:

ASSIGNMENT Case assigned to

Judicial Officer (name):

Dept. No.

dissolution

legal separation

nullity

parentage

other (specify):

Date of marriage/registered domestic partnership:
Date of separation on the petition:
Length of marriage or partnership:

on the response (if different):

There is a dispute about the length of the marriage or partnership.

Interpreter needed
(1)
(2)
(3)

Petitioner's Language:
Respondent's Language:
Other Party's Language:

CHILDREN

Name of child or children

Birthdate

Age

Gender

Additional children listed on Attachment 4.

RELATED CASES

One or both of the parties, or a child or children of the parties, has been involved in other related court cases. (List county or district
and case number, if known):
a.

Custody or visitation (parenting time) for the children of this case:

Juvenile delinquency:

Juvenile dependency:

Domestic violence/protective order:

Bankruptcy:

Other:

Criminal (only if reasonably related to the issues of this case):

JUDGMENT TERMINATING STATUS OF MARRIAGE OR DOMESTIC PARTNERSHIP HAS BEEN ENTERED

a. Date of termination:
b.

Date status judgment entered:

Form Approved for Optional Use
Judicial Council of California
FL-172 [New January 1, 2012]

CASE INFORMATION—FAMILY LAW

Page 1 of 2

www.courts.ca.gov

CASE NUMBER:

FL-172

PETITIONER:
RESPONDENT:

OTHER PARTY:

SERVICE AND RESPONSE
a.

Respondent was served with the petition on (date): , by (method):

personal service

substituted service

publication or posting

notice and acknowledgement

of receipt

other (specify):

Respondent has not been served with the petition.

Respondent filed a response on (date):

Respondent has not filed a response with the court.

Default has been entered against respondent.

Respondent appeared by filing an Appearance, Stipulations, and Waivers (form FL-130).

DISCLOSURE

Service of declarations of disclosure has been completed by:

Preliminary
Final

Final has been waived by

Other (specify):

Petitioner
Petitioner

Respondent
Respondent

Petitioner

Respondent

Petitioner

Respondent

PROTECTIVE ORDERS

The parties have a restraining order that expires on (date):

Protected party (name):

Children are included as protected persons.

10.

DEPARTMENT OF CHILD SUPPORT SERVICES
a.

The Department of Child Support Services has a separate case open.

The Department of Child Support Services has intervened in this case.

11.

CUSTODY/PARENTING TIME (VISITATION)
a.

The parties have participated in child custody and visitation (parenting time) mediation.

An agreement has been reached.

Counsel has been appointed to represent the minor child or children.

A child custody evaluation

has been ordered

report has been filed.

The following experts have been appointed (include issues):

12.

EXPERTS

13.

OTHER

FL-172 [New January 1, 2012]

CASE INFORMATION—FAMILY LAW

Page 2 of 2

Case Information—Family Law

This info page is part of the LIT Lab's Form Explorer project. It is not associated with the California state courts. To learn more about the project, check out our about page.

Downloads: You can download both the original form (last checked 2023-03) and the machine-processed form with normalized data fields.

About This Form:

Sourced from selfhelp.courts.ca.gov (2023-03)
Page(s): 2
Fields(s): 105
Average fields per page: 52
Reading Level: Grade 9
LIST Grouping(s): Unknown

Use our Rate My PDF tool to learn more. Go beyond the above insights and learn more about this or any pdf form at RateMyPDF.com, includes: counts of difficult words used, passive voice decetion, and suggestions for how to make the form more usable.

Identified Data Fields:

We have done our best to automaticly identify and name form fields according to our naming conventions. When possible, we've used names tied to our question library. See e.g., user1_name. If we think we've found a match to a question in our library, it is highlighted in green. Novel names are auto generated. So, you will probably need to edit some of them if you're trying to stick to the convention.

Here are the fields we could identify.

court_county was Court.County (0.60 conf)
court_street was Court.street (0.35 conf)
court_mailing was Court.mailing (0.35 conf)
court_city_zip was Court.City.zip (0.49 conf)
court_branch was Court.branch (0.35 conf)
check_box_department was CheckBox01.Department (0.39 conf)
check_box_assignment was CheckBox01.assignment (0.37 conf)
check_box_legal_separation was CheckBox02.legal.separation (0.37 conf)
check_box_nullity was CheckBox02.nullity (0.37 conf)
check_box_parentage was CheckBox02.parentage (0.37 conf)
check_box__1 was CheckBox02.other (0.37 conf)
check_box_dissolution was CheckBox02.dissolution (0.37 conf)
department was Department (0.40 conf)
fill_text__1 was FillText02.other (0.38 conf)
fill_text_date__1 was FillText02.date (0.38 conf)
fill_text_judicial_officer was FillText01.judicial.officer (0.38 conf)
fill_text__2 was FillText03.a.2 (0.38 conf)
fill_text__3 was FillText03.a.3 (0.38 conf)
fill_text__4 was FillText03.a.1 (0.38 conf)
fill_text__5 was FillText03.a.4 (0.38 conf)
fill_text_c__1 was FillText03.c.2 (0.38 conf)
fill_text_c__2 was FillText03.c.1 (0.38 conf)
fill_text_c__3 was FillText03.c.3 (0.38 conf)
check_box_c__1 was CheckBox03.c.1 (0.37 conf)
check_box_c__2 was CheckBox03.c.2 (0.37 conf)
check_box_c__3 was CheckBox03.c.0 (0.37 conf)
check_box_c__4 was CheckBox03.c.3 (0.37 conf)
check_box_b__1 was CheckBox03.b (0.37 conf)
fill_text_name__1 was FillText04.name.1.0 (0.38 conf)
fill_text_name__2 was FillText04.name.1.1 (0.38 conf)
fill_text_name__3 was FillText04.name.1.2 (0.38 conf)
fill_text_name__4 was FillText04.name.1.3 (0.38 conf)
fill_text_name__5 was FillText04.name.1.4 (0.38 conf)
fill_text_b__1 was FillText04.DOB.1.0 (0.42 conf)
fill_text_b__2 was FillText04.DOB.1.1 (0.42 conf)
fill_text_b__3 was FillText04.DOB.1.2 (0.42 conf)
fill_text_b__4 was FillText04.DOB.1.3 (0.42 conf)
fill_text_b__5 was FillText04.DOB.1.4 (0.42 conf)
fill_text_age__1 was FillText04.Age.1.0 (0.37 conf)
fill_text_age__2 was FillText04.Age.1.1 (0.37 conf)
fill_text_age__3 was FillText04.Age.1.2 (0.37 conf)
fill_text_age__4 was FillText04.Age.1.3 (0.37 conf)
fill_text_age__5 was FillText04.Age.1.4 (0.37 conf)
fill_text_gender__1 was FillText04.Gender.1.0 (0.37 conf)
fill_text_gender__2 was FillText04.Gender.1.1 (0.37 conf)
fill_text_gender__3 was FillText04.Gender.1.2 (0.37 conf)
fill_text_gender__4 was FillText04.Gender.1.3 (0.37 conf)
fill_text_gender__5 was FillText04.Gender.1.4 (0.37 conf)
check_box_attach was CheckBox04.attach (0.37 conf)
check_box__2 was CheckBox05.0 (0.37 conf)
check_box__3 was CheckBox05.a (0.37 conf)
check_box_b__2 was CheckBox05.b (0.37 conf)
check_box_c__5 was CheckBox05.c (0.37 conf)
check_box__4 was CheckBox05.d (0.37 conf)
check_box_e__1 was CheckBox05.e (0.37 conf)
check_box_f__1 was CheckBox05.f (0.37 conf)
check_box_g was CheckBox05.g (0.37 conf)
fill_text_g_county_casenumber was FillText05.g.county.casenumber (0.38 conf)
fill_text_county_casenumber__1 was FillText05.a.county.casenumber (0.38 conf)
fill_text_b_county_casenumber was FillText05.b.county.casenumber (0.38 conf)
fill_text_c_county_casenumber was FillText05.c.county.casenumber (0.38 conf)
fill_text_county_casenumber__2 was FillText05.d.county.casenumber (0.38 conf)
fill_text_e_county_casenumber was FillText05.e.county.casenumber (0.38 conf)
fill_text_f_county_casenumber was FillText05.f.county.casenumber (0.38 conf)
check_box__5 was CheckBox06.0 (0.37 conf)
fill_text_termination was FillText06.a.termination (0.38 conf)
fill_text_b_status was FillText06.b.status (0.38 conf)
check_box_personal was CheckBox07.a.personal (0.37 conf)
check_box_publication was CheckBox07.a.publication (0.37 conf)
check_box_notice was CheckBox07.a.notice (0.37 conf)
check_box_substituted was CheckBox07.a.substituted (0.37 conf)
check_box__6 was CheckBox07.a.other (0.37 conf)
check_box__7 was CheckBox07.a.0 (0.37 conf)
check_box_c__6 was CheckBox07.c (0.37 conf)
check_box__8 was CheckBox07.d (0.37 conf)
check_box_e__2 was CheckBox07.e (0.37 conf)
check_box_b__3 was CheckBox07.b (0.37 conf)
check_box_f__2 was CheckBox07.f (0.37 conf)
fill_text_service_date was FillText07.a.service.date (0.38 conf)
fill_text_c_date was FillText07.c.date (0.38 conf)
check_box_petitioner__1 was CheckBox08.a.Petitioner (0.49 conf)
check_box_respondent__1 was CheckBox08.a.respondent (0.37 conf)
check_box_b_petitioner was CheckBox08.b.Petitioner (0.49 conf)
check_box_b_respondent was CheckBox08.b.respondent (0.37 conf)
check_box_c_petitioner was CheckBox08.c.Petitioner (0.49 conf)
check_box_c_respondent was CheckBox08.c.respondent (0.37 conf)
check_box_petitioner__2 was CheckBox08.d.Petitioner (0.49 conf)
check_box_respondent__2 was CheckBox08.d.respondent (0.37 conf)
check_box__9 was CheckBox09.0 (0.37 conf)
check_box__10 was CheckBox09.a (0.37 conf)
check_box_b__4 was CheckBox09.b (0.37 conf)
fill_text__6 was FillText08.d.other (0.38 conf)
fill_text_date__2 was FillText09.0.date (0.38 conf)
fill_text_name__6 was FillText09.a.name (0.38 conf)
check_box__11 was CheckBox10.a (0.37 conf)
check_box_b__5 was CheckBox10.b (0.37 conf)
check_box__12 was CheckBox11.a (0.37 conf)
check_box_c__7 was CheckBox11.c (0.37 conf)
check_box_b__6 was CheckBox11.b (0.37 conf)
check_box_evaluation_ordered was CheckBox11.d.evaluation.ordered (0.37 conf)
check_box_evaluation_report was CheckBox11.d.evaluation.report (0.37 conf)
check_box__13 was CheckBox11.d.0 (0.37 conf)
check_box__14 was CheckBox12 (0.37 conf)
fill_text__7 was FillText12 (0.38 conf)
fill_text__8 was FillText13 (0.38 conf)

Create an Interactive Version of this Form:

The Weaver creates a draft guided interview from a template form, like the one provided here. You can use the link below to open this form in the Weaver. To learn more, read "Weaving" your form into a draft interview.

Launch Form in Weaver

The Legal Innovation & Technology Lab's Form Explorer Beta @ Suffolk Law School Last updated 2023-04-02

Case Information—Family Law

About This Form:

Identified Data Fields:

Create an Interactive Version of this Form:

The Legal Innovation & Technology Lab's Form Explorer ^Beta @ Suffolk Law School Last updated 2023-04-02