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: Massachusetts Lists

Here is the text we could read:

LAND COURT 
SURVEY DIVISION

PLAN ORDER 
REQUEST FORM 
LandCourt.PlanOrder@jud.state.ma.us 

REFERENCE # 
LCPLAN- 
RECEIPT #  

NAME 

ADDRESS 

DESCRIPTION OF REQUEST 

PLAN NO(s). 
in numerical order 

SURVEYOR 

LAND 
COURT 

PLAN TYPE 

CITY/TOWN 

COMMENTS/NOTES 

PHONE 

EMAIL 

PLAN FORMAT REQUESTED 
 ELECTRONIC (PDF) BY EMAIL
 PRINT COPIES FOR PICKUP
 PRINT COPIES BY MAIL

 FOR COURT USE ONLY 

SHEET QTY 
LC 

SURV 

TOTAL 

Payment must be received by the court before documents will be provided.  

 Online payment by credit card or electronic check/ACH (convenience fees apply) 

www.govhub.com/ma/landcourt/pay

 Payment by mail (check only)
 In-person payment at Land Court Recorder’s Office (check, credit card, or cash)

Requestor authorizes the court to complete this transaction and agrees to pay the amount due in full. 

REQUESTOR SIGNATURE 

X
COMMENTS FROM LAND COURT 

GRAND TOTAL: 

PLAN COSTS 

Surveyor Plan: $5/sheet 

Land Court Plan: $1/sheet 

DATE 

PREPARED BY 

SURVEYPO (07/2022) 

https://www.mass.gov/orgs/land-court 

Page 1 of 1

Survery Division Plan Order Request Form

This info page is part of the LIT Lab's Form Explorer project. It is not associated with the Massachusetts 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 www.mass.gov (2023-03)
Page(s): 1
Fields(s): 116
Average fields per page: 116
Reading Level: Grade 8
LIST Grouping(s): MO-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.

users1_name was NAME (1.00 conf)
users1_address_line_one was ADDRESS (1.00 conf)
users1_phone_number was PHONE (1.00 conf)
email was EMAIL (0.38 conf)
descriptio_n_f_request was DESCRIPTION OF REQUEST (0.45 conf)
pla_n_os_numerical_order_row__1 was PLAN NOs in numerical orderRow1 (0.49 conf)
citytown_row__1 was CITYTOWNRow1 (0.35 conf)
commentsnotes_row__1 was COMMENTSNOTESRow1 (0.35 conf)
pla_n_os_numerical_order_row__2 was PLAN NOs in numerical orderRow2 (0.49 conf)
citytown_row__2 was CITYTOWNRow2 (0.35 conf)
commentsnotes_row__2 was COMMENTSNOTESRow2 (0.35 conf)
pla_n_os_numerical_order_row__3 was PLAN NOs in numerical orderRow3 (0.49 conf)
citytown_row__3 was CITYTOWNRow3 (0.35 conf)
commentsnotes_row__3 was COMMENTSNOTESRow3 (0.35 conf)
pla_n_os_numerical_order_row__4 was PLAN NOs in numerical orderRow4 (0.49 conf)
citytown_row__4 was CITYTOWNRow4 (0.35 conf)
commentsnotes_row__4 was COMMENTSNOTESRow4 (0.35 conf)
pla_n_os_numerical_order_row__5 was PLAN NOs in numerical orderRow5 (0.49 conf)
citytown_row__5 was CITYTOWNRow5 (0.35 conf)
commentsnotes_row__5 was COMMENTSNOTESRow5 (0.35 conf)
pla_n_os_numerical_order_row__6 was PLAN NOs in numerical orderRow6 (0.49 conf)
citytown_row__6 was CITYTOWNRow6 (0.35 conf)
commentsnotes_row__6 was COMMENTSNOTESRow6 (0.35 conf)
pla_n_os_numerical_order_row__7 was PLAN NOs in numerical orderRow7 (0.49 conf)
citytown_row__7 was CITYTOWNRow7 (0.35 conf)
commentsnotes_row__7 was COMMENTSNOTESRow7 (0.35 conf)
pla_n_os_numerical_order_row__8 was PLAN NOs in numerical orderRow8 (0.49 conf)
citytown_row__8 was CITYTOWNRow8 (0.35 conf)
commentsnotes_row__8 was COMMENTSNOTESRow8 (0.35 conf)
pla_n_os_numerical_order_row__9 was PLAN NOs in numerical orderRow9 (0.49 conf)
citytown_row__9 was CITYTOWNRow9 (0.35 conf)
commentsnotes_row__9 was COMMENTSNOTESRow9 (0.35 conf)
pla_n_os_numerical_order_row__10 was PLAN NOs in numerical orderRow10 (0.49 conf)
citytown_row__10 was CITYTOWNRow10 (0.35 conf)
commentsnotes_row__10 was COMMENTSNOTESRow10 (0.35 conf)
pla_n_os_numerical_order_row__11 was PLAN NOs in numerical orderRow11 (0.49 conf)
citytown_row__11 was CITYTOWNRow11 (0.35 conf)
commentsnotes_row__11 was COMMENTSNOTESRow11 (0.35 conf)
pla_n_os_numerical_order_row__12 was PLAN NOs in numerical orderRow12 (0.49 conf)
citytown_row__12 was CITYTOWNRow12 (0.35 conf)
commentsnotes_row__12 was COMMENTSNOTESRow12 (0.35 conf)
pla_n_os_numerical_order_row__13 was PLAN NOs in numerical orderRow13 (0.49 conf)
citytown_row__13 was CITYTOWNRow13 (0.35 conf)
commentsnotes_row__13 was COMMENTSNOTESRow13 (0.35 conf)
signature_date was DATE (1.00 conf)
check_box__1 was Check Box2 (0.37 conf)
check_box__2 was Check Box1 (0.52 conf)
check_box__3 was Check Box3 (0.37 conf)
check_box__4 was Check Box4 (0.37 conf)
check_box__5 was Check Box5 (0.37 conf)
check_box__6 was Check Box6 (0.37 conf)
check_box__7 was Check Box7 (0.37 conf)
check_box__8 was Check Box8 (0.37 conf)
check_box__9 was Check Box9 (0.37 conf)
check_box__10 was Check Box10 (0.37 conf)
check_box__11 was Check Box11 (0.37 conf)
check_box__12 was Check Box12 (0.37 conf)
check_box__13 was Check Box13 (0.37 conf)
check_box__14 was Check Box14 (0.37 conf)
check_box__15 was Check Box15 (0.37 conf)
check_box__16 was Check Box16 (0.37 conf)
check_box__17 was Check Box17 (0.37 conf)
check_box__18 was Check Box18 (0.37 conf)
check_box__19 was Check Box19 (0.37 conf)
check_box__20 was Check Box20 (0.37 conf)
check_box__21 was Check Box21 (0.37 conf)
check_box__22 was Check Box22 (0.37 conf)
check_box__23 was Check Box23 (0.37 conf)
check_box__24 was Check Box24 (0.37 conf)
check_box__25 was Check Box25 (0.37 conf)
check_box__26 was Check Box26 (0.37 conf)
surv_row__1 was SURVRow1 (0.35 conf)
lc_row__1 was LCRow1 (0.35 conf)
total_row__1 was TotalRow1 (0.32 conf)
surv_row__2 was SURVRow2 (0.35 conf)
lc_row__2 was LCRow2 (0.35 conf)
total_row__2 was TotalRow2 (0.32 conf)
surv_row__3 was SURVRow3 (0.35 conf)
lc_row__3 was LCRow3 (0.35 conf)
total_row__3 was TotalRow3 (0.32 conf)
surv_row__4 was SURVRow4 (0.35 conf)
lc_row__4 was LCRow4 (0.35 conf)
total_row__4 was TotalRow4 (0.32 conf)
total_row__5 was TotalRow5 (0.32 conf)
lc_row__5 was LCRow5 (0.35 conf)
surv_row__5 was SURVRow5 (0.35 conf)
total_row__6 was TotalRow6 (0.32 conf)
lc_row__6 was LCRow6 (0.35 conf)
surv_row__6 was SURVRow6 (0.35 conf)
total_row__7 was TotalRow7 (0.32 conf)
lc_row__7 was LCRow7 (0.35 conf)
surv_row__7 was SURVRow7 (0.35 conf)
total_row__8 was TotalRow8 (0.32 conf)
lc_row__8 was LCRow8 (0.35 conf)
surv_row__8 was SURVRow8 (0.35 conf)
total_row__9 was TotalRow9 (0.32 conf)
lc_row__9 was LCRow9 (0.35 conf)
surv_row__9 was SURVRow9 (0.35 conf)
total_row__10 was TotalRow10 (0.32 conf)
lc_row__10 was LCRow10 (0.35 conf)
surv_row__10 was SURVRow10 (0.35 conf)
total_row__11 was TotalRow11 (0.32 conf)
lc_row__11 was LCRow11 (0.35 conf)
surv_row__11 was SURVRow11 (0.35 conf)
total_row__12 was TotalRow12 (0.32 conf)
lc_row__12 was LCRow12 (0.35 conf)
surv_row__12 was SURVRow12 (0.35 conf)
surv_row__13 was SURVRow13 (0.35 conf)
lc_row__13 was LCRow13 (0.35 conf)
total_row__13 was TotalRow13 (0.32 conf)
grand_total was Grand Total (0.34 conf)
users1_signature was Signature (1.00 conf)
comments_court_survey_division was Comments from Land Court Survey Division (0.37 conf)
prepared was Prepared By (0.35 conf)
reference_number was Reference Number (0.43 conf)
receipt_number was Receipt Number (0.36 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

Survery Division Plan Order Request Form

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