Tuesday, June 21st, 2011

How to improve a government form (part 2)

If you’re just joining us, you might want to read yesterday’s post, “How to improve a government form (part 1),” that introduces the Ohio Department of Jobs and Family Services’s new JFS 84221 form.

As mentioned yesterday, something good about the new JFS form is that it’s in Microsoft Word format and set up as a fillable form. However, it seems that the fine folks at JFS could learn a thing or two about fillable forms in Word.

Also as mentioned yesterday, a challenge with the JFS 84221 form is having it competed in accordance with the government’s rules. One challenge in particular is correctly completing the “Number of people in househodl by age” section. Each age group must be completed; if a household has no members in a range, that group may not be left blank but instead must have “0” or “--” in it (nothing else is acceptable, not “none” or “N/A” or “X”). In addition, the total field must be filled in, and correctly (you might be surprised, or then again you might not, how many people cannot add).

Number of people in household by age as designed by JFS with dumb fields
“Number of people in household by age” section
as designed by JFS with dumb fields

What the JFS seems not to have realized (or perhaps they did but chose not to implement—more on that below) is that in Word all the above problems can be solved. Want to make sure that a field is always completed or has a default value? Want to do a total automatically? Word can do that!

To tell Word what you want to do, right-click on each of the fields to be changed (after you unprotect the document—see yesterday’s post to see how) and change the properties as shown below.


Properties for the total field

Properties for the age range fields
For each of the age range fields:

  1. Change the type to “Number”
  2. Set the default number to “0”
  3. In “Bookmark” give the field a meaningful name (this makes the total equation easier to understand)
  4. Check the “Calculate on exit” box

For the total field:

  1. Change the type to “Calculation”
  2. Change the expression to “=Number60+Number18+NumberBirth” (these field names should be whatever you used above)

Presto! You now have a JFS 84221 in Word that has household fields that cannot be left blank, filled in with anything but numbers or totaled incorrectly.

Number of people in household updated with smart fields
“Number of people in household by age” section updated with smart fields

There is one challenge with this updated form, which may well be the reason that JFS chose not to implement these features—if you print this form without filing anything in, you’ll get a hardcopy with “0” in each of the household fields, making it unsuitable for someone to complete by hand. If you need blank forms for people to write on, you’ll want the original form (or yesterday’s form that eliminates the temptation to sign in the wrong box).

However, something I’ve learned while managing Cross Creek’s Feeding Friends food pantry, is that you really don’t want to let clients fill out forms on their own. The rules for filling out the forms correctly are complicated, leaving you with the choices of pedantically making clients fill out new forms to correct mistakes (something that I see as disrespectful and that takes too long) or of having intake volunteers fill out the forms as they interview clients.

So why did I bother with improving JFS’s fillable form? Because, with the introduction of this new JFS 84221 form that takes effect in July, we’re going to have every single one of our clients complete new forms next month. To make that manageable, I and other Feeding Friends volunteers are going to use the new fillable form to enter our existing recent clients’s data, so the clients, unless they’ve had some change in address or household, won’t be bothered next month with completing new forms. They’ll each get a nice new form, pre-printed with their information, to sign (inside the “Signature” box).

Those of you who are savvy about Foodbank Dayton might well be asking, “Well what about the Virtual Case Manager software that was demonstrated at a recent Miami Valley Hunger Coalition meeting? If you were using that, wouldn’t you avoid all this hassle?” Maybe so, and I have some opinions about that, which I’ll share in another post.

Monday, June 20th, 2011

How to improve a government form (part 1)


A slightly improved version of Ohio’s
JFS 04221 form (in PDF format)

The Ohio Department of Jobs and Family Services has released a new version of their JFS 04221 form, Federal and State Funded Food Programs — Eligibility to Take Food Home. This is the form that people picking up food at government-subsidized food pantries have to fill out to affirm their eligibility. Because the food pantry I volunteer for (Feeding Friends, a program of Cross Creek Community Church) gets food for a fee from Foodbank Dayton, our clients are required to complete this form. As the Feeding Friends team leader, it’s part of my job to try to get our clients to fill the form out in accordance with the government’s rules, and that’s more difficult than you might think.

One of the difficulties is that the forms are not supposed to have any extraneous marks on them. No cross outs, no circling words on the form, etc. Something minor related to this is that people are supposed to sign the form inside the box that has the title of “Signature,” but very often people sign above that box. Poorly designed signature box Why? I guess because there’s such a tempting blank space above the “Signature” heading and then people are used to putting their signatures on a line that has the word “Signature” below it.

Yes, it should be obvious when filling out this form, after having put your name inside the box marked “Name” and your address inside the box marked “Address” and your city inside the box marked “City” that your signature should go inside the box marked “Signature,” but guess what? For many of the people filling out this form, it’s not obvious.

Fortunately this problem is really easy to fix—format the “I certify” text so that there’s no tempting blank space above the “Signature” box and people signing the form will have no alternative but to sign the form inside the “Signature” box. The JFS folks even distributed the new form in Microsoft Word format, which is why it’s easy to fix this problem, but they oh-so-cleverly password-protected it so that it couldn’t be altered.

Except that if you have access to the internet, the password is easily circumventable. As pointed out on the page “Can I crack a password protected Microsoft Word file?”, all you have to do is to save the file in XML format, open the XML file in a text editor, remove the <w:documentProtection> tag, save the file and then re-open it back in Word.

So here’s how I changed the signature block on our copy of JFS 04221:
Better designed signature box
People who get the form with this box won’t be signing above the line unless they decide to sign on top of printed text.

As mentioned above, JFS distributed their new form in Microsoft Word format, and they even set it up as a fillable form. However, that too has room for improvement, which will be part 2 of “How to improve a government form.”

 
Blog tools
Tags
Feeding Friends (2)
AJ Wagner (2)
Amazon Kindle Fire (4)
Amazon.com (2)
American Express (2)
American Family Association (3)
Amy Grant (2)
Berlin (4)
Books (15)
Candi Cushman (1)
ChMS (3)
Christianists (16)
Christianity (21)
Christmas (2)
COM101 (4)
Computer tips (20)
Conservatives (6)
Cross Creek Community Church (28)
Cute actors (4)
Dan Savage (3)
David Esrati (9)
Dayton (52)
Dayton Art Institute (3)
Dayton Christian High School (2)
Dayton City Paper (5)
Dayton Daily News (15)
Dayton Dialogue on Race Relations (4)
Dayton Gay Mens Chorus (11)
Dean Lovelace (3)
Derek (9)
Dick Chema (2)
Diversity Dayton (2)
Driving (4)
Drunkenness (6)
English (2)
Epiphany Lutheran Church (3)
Exodus (2)
Facebook (13)
Fairborn High School (6)
False prophets (2)
Firefox (2)
Flash (2)
Frankfurt (3)
French films (3)
Gary Leitzell (11)
Gay (85)
Gay bars (2)
Geekiness (5)
German (3)
Germany (34)
Good Friday (3)
Google (2)
Government forms (6)
Grafton Hill (4)
Greasemonkey (2)
Greek Orthodox Church (2)
Hamburg (2)
Hebrew (3)
Issue 1 (5)
Joey D. Williams (2)
Köln (3)
Ken Blackwell (2)
Kiva (1)
Lüneburg (20)
Library (2)
München (2)
Mark Luedtke (1)
Marriage (23)
Mary Cheney (2)
Mazer (4)
MeetFred (3)
Microsoft (10)
Mike Turner (3)
Movies (14)
MVFHC (3)
My stupidity (5)
Nan Whaley (1)
Natalie Barney (1)
Neon Movies (10)
Occupy Dayton (4)
Ohio (2)
Olive (2)
Oregon District (4)
Panera (7)
Park Layne (3)
Parking (5)
Parties (2)
Paul Noah (1)
Paul Pyle (4)
Photos (49)
Politics (36)
Proposition 8 (2)
Racism (3)
Remembering (34)
Republicans (4)
Reviews (9)
Scams (5)
Sean Harris (1)
Sirius (1)
Snow (6)
SPAM (5)
Stivers (2)
Teaching (6)
Telemarketing (3)
Tomatoes (2)
Travel (12)
TV Guide (2)
Typing (6)
Uncle Bill (10)
Verizon (5)
Web design (bad) (17)
Web hosts (4)
Whining (61)
Wright State University (6)
Writing (5)
Yellow Springs (2)
Months
Email
david@davidlauri.com