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:

CONSERVATORSHIP 

GUARDIANSHIP     OF 

CASE NUMBER:

GC-400(F)/GC-405(F)

(Name):

Date
(mm/dd/yyyy)

Schedule F, Changes in Form of Assets—Standard and Simplified Accounts

Conservatee

Minor

Changes in Form of Assets During the Account Period

Transaction

(Add pages as required to list all changes in the form of assets.  Although this schedule is a required part of an account where there 
has been a change in the form of an asset, the schedule is not shown in the Summary of Account (form GC-400(SUM)/GC-405(SUM)). 

The page total to the right is the number of pages in Schedule F.)

Form Approved for Optional Use 
Judicial Council of California
GC-400(F)/GC-405(F) 
[New January 1, 2008]

SCHEDULE F, CHANGES IN FORM OF ASSETS—
STANDARD AND SIMPLIFIED ACCOUNTS
(Probate—Guardianships and Conservatorships)

Page  F

of

pages

Probate Code, §§ 1060–1064, 2620;
Cal. Rules  of Court, rule 7.575 
www.courtinfo.ca.gov

Schedule F, Changes in Form of Assets—Standard and Simplified Accounts

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): 68
Average fields per page: 68
Reading Level: Grade 7
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.

fill_text__1 was FillText11 (0.53 conf)
fill_text__2 was FillText12 (0.38 conf)
fill_text__3 was FillText3 (0.38 conf)
fill_text__4 was FillText18 (0.38 conf)
fill_text__5 was FillText75 (0.38 conf)
fill_text__6 was FillText19 (0.38 conf)
fill_text__7 was FillText76 (0.38 conf)
fill_text__8 was FillText20 (0.38 conf)
fill_text__9 was FillText77 (0.38 conf)
fill_text__10 was FillText21 (0.38 conf)
fill_text__11 was FillText79 (0.38 conf)
fill_text__12 was FillText22 (0.38 conf)
fill_text__13 was FillText80 (0.38 conf)
fill_text__14 was FillText23 (0.38 conf)
fill_text__15 was FillText82 (0.38 conf)
fill_text__16 was FillText24 (0.38 conf)
fill_text__17 was FillText83 (0.38 conf)
fill_text__18 was FillText26 (0.38 conf)
fill_text__19 was FillText85 (0.38 conf)
fill_text__20 was FillText27 (0.38 conf)
fill_text__21 was FillText86 (0.38 conf)
fill_text__22 was FillText28 (0.38 conf)
fill_text__23 was FillText88 (0.38 conf)
fill_text__24 was FillText29 (0.38 conf)
fill_text__25 was FillText89 (0.38 conf)
fill_text__26 was FillText31 (0.38 conf)
fill_text__27 was FillText91 (0.38 conf)
fill_text__28 was FillText33 (0.38 conf)
fill_text__29 was FillText92 (0.38 conf)
fill_text__30 was FillText35 (0.38 conf)
fill_text__31 was FillText94 (0.38 conf)
fill_text__32 was FillText36 (0.38 conf)
fill_text__33 was FillText78 (0.38 conf)
fill_text__34 was FillText38 (0.38 conf)
fill_text__35 was FillText81 (0.38 conf)
fill_text__36 was FillText39 (0.38 conf)
fill_text__37 was FillText84 (0.38 conf)
fill_text__38 was FillText41 (0.38 conf)
fill_text__39 was FillText87 (0.38 conf)
fill_text__40 was FillText42 (0.38 conf)
fill_text__41 was FillText90 (0.38 conf)
fill_text__42 was FillText44 (0.38 conf)
fill_text__43 was FillText93 (0.38 conf)
fill_text__44 was FillText45 (0.38 conf)
fill_text__45 was FillText96 (0.38 conf)
fill_text__46 was FillText47 (0.38 conf)
fill_text__47 was FillText99 (0.38 conf)
fill_text__48 was FillText48 (0.38 conf)
fill_text__49 was FillText102 (0.38 conf)
fill_text__50 was FillText50 (0.38 conf)
fill_text__51 was FillText105 (0.38 conf)
fill_text__52 was FillText51 (0.38 conf)
fill_text__53 was FillText108 (0.38 conf)
fill_text__54 was FillText53 (0.38 conf)
fill_text__55 was FillText95 (0.38 conf)
fill_text__56 was FillText54 (0.38 conf)
fill_text__57 was FillText97 (0.38 conf)
fill_text__58 was FillText56 (0.38 conf)
fill_text__59 was FillText7 (0.38 conf)
fill_text__60 was FillText4 (0.38 conf)
fill_text__61 was FillText8 (0.38 conf)
fill_text__62 was FillText5 (0.38 conf)
fill_text__63 was FillText9 (0.38 conf)
fill_text__64 was FillText6 (0.38 conf)
fill_text__65 was FillText10 (0.38 conf)
fill_text__66 was FillText2 (0.38 conf)
fill_text__67 was FillText1 (0.38 conf)
fill_text__68 was FillText74 (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

Schedule F, Changes in Form of Assets—Standard and Simplified Accounts

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