Here is the text we could read:
Sample Form 27
ORDER GRANTING MOTION FOR PROTECTIVE ORDER
In the__________________________
court of________________________
County
________________________
Case Number
TATE OF ALABAMA
S
State of Alabama
v.
________________________
Defendant
Defendant (or State) having moved the Court for an order (State
the relief sought by the moving Party)________________________________
______________________________________________________________________
______________________________________________________________________
And it appearing to the Court that (state grounds for said
order) ______________________________________________________________,
it is
ORDERED, that: __________________________________________________
______________________________________________________________________
_______________________________________________________________ (State
document, record, etc., is vacated, modified, restricted or deferred).
AND FURTHER ORDERED, that Exhibit B be sealed but preserved
in the records of this Court to be made available to the
appellate court in the event of an appeal.
________________
Date
______________________________________
Judge
_
R
ule 16.4
Order granting Motion for Protective Order
This info page is part of the LIT Lab's Form Explorer project. It is not associated with the Alabama 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 eforms.alacourt.gov (2023-03)
- Page(s): 1
- Fields(s): 13
- Average fields per page: 13
- Reading Level: Grade 10
- LIST Grouping(s):
GO-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.
text__1 was Text1 (0.97 conf)text__2 was Text2 (0.35 conf)text__3 was Text3 (0.35 conf)text__4 was Text4 (0.35 conf)text__5 was Text5 (0.35 conf)text__6 was Text6 (0.35 conf)text__7 was Text7 (0.35 conf)text__8 was Text8 (0.35 conf)text__9 was Text9 (0.35 conf)text__10 was Text10 (0.35 conf)text__11 was Text11 (0.35 conf)text__12 was Text12 (0.35 conf)text__13 was Text13 (0.35 conf)
We've done our best to group similar variables togther to avoid overwhelming the user.
Suggested Screen 0:
text__1text__2text__3text__4text__5text__6text__7text__8text__9text__10text__11text__12text__13
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