Here is the text we could read:
PETITIONER/PLAINTIFF:
RESPONDENT/DEFENDANT:
CASE NUMBER:
FL-342(A)
NON-GUIDELINE CHILD SUPPORT FINDINGS ATTACHMENT
Attachment to
Child Support Information and Order Attachment (form FL-342)
Judgment (Family Law) (form FL-180)
Other (specify):
The court makes the following findings required by Family Code sections 4056, 4057, and 4065:
1. STIPULATION TO NON-GUIDELINE ORDER
The child support agreed to by the parties is
The amount of support that would have been ordered under the guideline formula is: $
The parties have been fully informed of their rights concerning child support. Neither party is acting out of duress or coercion.
Neither party is receiving public assistance and no application for public assistance is pending. The needs of the children
will be adequately met by this agreed-upon amount of child support. If the order is below the guideline, no change of
circumstances will be required to modify this order. If the order is above the guideline, a change of circumstances will be
required to modify this order.
the statewide child support guidelines.
per month.
below or
above
OTHER REBUTTAL FACTORS
2.
Support calculation
a. The guideline amount of child support calculated is: $
per month payable by
petitioner/plaintiff
respondent/defendant
b. The court finds by a preponderance of the evidence that rebuttal factors exist. The rebuttal factors result in an
increase
decrease
in child support. The revised amount of support is: $
per month.
c. The court finds the child support amount revised by these factors to be in the best interest of the child and that application
of the formula would be unjust or inappropriate in this case.
These changes remain in effect
until (date):
until further order
d. The factors are:
(1)
(2)
(3)
(4)
The sale of the family residence is deferred under Family Code section 3800, and the rental value of the
family residence in which the children reside exceeds the mortgage payments, homeowners insurance, and
property taxes by: $
per month. (Fam. Code, § 4057(b)(2).)
The parent paying support has extraordinarily high income, and the amount determined under the guideline
would exceed the needs of the child. (Fam. Code, § 4057(b)(3).)
The
children at a level commensurate with that party’s custodial time. (Fam. Code, § 4057(b)(4).)
respondent/defendant
petitioner/plaintiff
is not contributing to the needs of the
Special circumstances exist in this case. The special circumstances are:
(i)
The parents have different timesharing arrangements for different children.
(Fam. Code, § 4057(b)(5) (A).)
The parents have substantially equal custody of the children and one parent has a much lower or
higher percentage of income used for housing than the other parent.
(Fam. Code, § 4057(b)(5)(B).)
The child has special medical or other needs that require support greater than the formula amount.
These needs are (Fam. Code, § 4057(b)(5)(C)) (specify):
(ii)
(iii)
(iv)
Other (Fam. Code, § 4057(b)(5)) (specify):
Form Adopted for Mandatory Use
Judicial Council of California
FL-342(A) [Rev. January 1, 2008]
NON-GUIDELINE CHILD SUPPORT FINDINGS ATTACHMENT
Page 1 of 1
Family Code, § 4056
www.courtinfo.ca.gov
Non-Guideline Support Findings Attachment
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): 1
- Fields(s): 26
- Average fields per page: 26
- Reading Level: Grade 8
- LIST Grouping(s):
FA-06-00-00-00, FA-00-00-00-00.
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.
fill_text__1 was FillText27 (0.53 conf)fill_text__2 was FillText29 (0.38 conf)fill_text__3 was FillText28 (0.38 conf)check_box__1 was CheckBox23 (0.37 conf)check_box__2 was CheckBox22 (0.37 conf)check_box__3 was CheckBox21 (0.37 conf)fill_text__4 was FillText24 (0.38 conf)check_box__4 was CheckBox18 (0.37 conf)fill_text__5 was FillText26 (0.38 conf)check_box__5 was CheckBox17 (0.37 conf)fill_text__6 was FillText30 (0.38 conf)check_box__6 was CheckBox16 (0.37 conf)check_box__7 was CheckBox15 (0.37 conf)fill_text__7 was FillText32 (0.38 conf)fill_text__8 was FillText31 (0.38 conf)check_box__8 was CheckBox10 (0.37 conf)fill_text__9 was FillText33 (0.38 conf)check_box__9 was CheckBox9 (0.37 conf)check_box__10 was CheckBox6 (0.37 conf)check_box__11 was CheckBox5 (0.37 conf)check_box__12 was CheckBox4 (0.37 conf)check_box__13 was CheckBox3 (0.37 conf)check_box__14 was CheckBox2 (0.37 conf)check_box__15 was CheckBox1 (0.52 conf)fill_text__10 was FillText25 (0.38 conf)fill_text__11 was FillText34 (0.38 conf)
We've done our best to group similar variables togther to avoid overwhelming the user.
Suggested Screen 0:
fill_text__1fill_text__2fill_text__3check_box__1check_box__2check_box__3fill_text__4check_box__4fill_text__5check_box__5fill_text__6check_box__6check_box__7fill_text__7fill_text__8check_box__8fill_text__9check_box__9check_box__10check_box__11check_box__12check_box__13check_box__14check_box__15fill_text__10fill_text__11
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