An Interview with the Woman Who Designed Systems That Happened to Fit on Paper

Dolores "Dot" Pfeiffer retired from the General Services Administration in 1985 after thirty-one years in forms management. She does not exist. But the discipline she represents was thoroughly real, formally codified, and staffed by people who took it seriously. The practices described here are drawn from declassified agency records, official government guidance, and congressional history.¹²³

We reached Dot at her kitchen table in Silver Spring, where she was reorganizing a recipe binder using tabbed dividers she'd clearly salvaged from a government supply cabinet.

You spent thirty-one years designing government forms. When you tell people that, what do they picture?

Dot: They picture typing. Maybe a woman at a desk with a ruler and a pot of coffee. They think I was filling in forms. I designed the forms. Which meant I designed the process, the approval chain, the legal record, and the routing logic, and then I fit all of that onto paper. The paper was the last part.

That's a strong claim for what most people think of as a bunch of boxes and lines.

Dot: Every form I touched had to cite a prescribing directive. A regulation or statute that required the information to be collected.⁴ You couldn't just decide you wanted a form because you had a nice idea. You had to point to the law. If the law changed, the form changed. If the program ended, the form was cancelled, and the cancellation itself was documented. A form had to justify its own existence every single day it was in print.

When someone brought me a draft and said "we need a new form," the first thing I asked was: show me the directive. Not "what information do you want." Show me why you're allowed to ask for it.

That's a higher bar than most software features clear.

Dot: I wouldn't know about that.

Fair enough. How did field order work? Was it just top-to-bottom convenience?

Dot: You put the identifying information first because the clerk needed to pull the file before reading anything else. You put the authorization block where it belonged in the decision flow, not at the bottom because that's where signatures supposedly "go." At the point where someone with the right authority had to stop and make a judgment before the form moved forward.

On a procurement form, if the dollar amount exceeded a certain threshold, say two thousand dollars, an additional signature line appeared. Not a different form. The same form, designed so the structure of the approval chain was visible on the page.⁵ The person signing could see that their signature was required because of the amount. The field was the policy.

That's a lot of weight for a piece of paper.

Dot: A piece of paper that was also a legal record. The OPM definition, which I can almost still recite: a form is "a fixed or sequential order of data elements, designed for gathering, organizing, and transmitting prescribed information."⁴ People hear "data elements" and think of databases. But transmitting is the word that matters. The form moved. It traveled through offices. And how it traveled was designed into it.

You're talking about carbon copies.

Dot: I'm talking about routing architecture. When you specified a form as a three-part carbon set, you weren't making a printing decision. You were deciding that copy one goes to the originating office, copy two goes to personnel, copy three goes to the file. Each copy had a destination. Each destination had a reason. Each reason traced back to a directive.

I saw a revision once, at another agency I won't name, where they changed a routing slip from interleaved carbon with a side stub to NCR paper, top stub, continuous unit sets. Hundred and seventy-five thousand sets over eighteen months.² People outside the profession would call that a paper stock decision. It was re-engineering how a document moves through an institution.

After the Privacy Act passed in '74, forms had to carry specific legal language. What did that change for you?

Dot: It formalized what competent designers had been doing all along, which is a polite way of saying it forced the incompetent ones to catch up. We'd always thought about what was mandatory versus voluntary. But the Act required us to print it right on the form: the legal authority for collecting the information, whether disclosure was mandatory or voluntary, what happened if you declined.⁴

You couldn't bury it in a manual somewhere. The person holding the form held the policy.

That was the principle, really. If you separated the instructions from the form, you'd separated the policy from the act. And then someone fills in a field without knowing whether they're legally required to answer or whether they can leave it blank. That is not a minor thing when the field is your Social Security number.

Tell me about the SF-50.

Dot: [pauses, then smiles]

The SF-50. Notification of Personnel Action. Civil Service Commission designed it in 1949. Every federal hire, every promotion, every reassignment, every separation, documented in numbered blocks.⁶ Block 5 tells you the nature of the action. Another block carries the legal authority code.

People retire and they need their SF-50s from thirty years ago to calculate their pension. The form outlives the person who signed it, the person who filed it, sometimes the agency that issued it. It doesn't describe something that happened and then disappear. It is the authoritative evidence that the thing happened.

Was there ever a form you were proud of?

Dot: Proud is a strong word for government work. But there was a form I revised where the previous version had the authorization block on page two. Nobody ever flipped to page two. I moved it to the middle of page one, right after the cost estimate, so the authorizing official had to pass through the numbers before signing.

Rejection rate went up eleven percent the first quarter.

Because people were actually reading what they were approving.

Dot: Because the design made it impossible not to. I didn't collect data. I made institutional judgment visible on paper.

What happened to all of that when things went digital?

Dot: [long pause]

I retired in '85, so I missed most of it. But I'll tell you what I worried about. A form carried its own instructions, its own legal notice, its own authority chain, its own routing logic. All in one artifact. You could hold it up and see the entire system. If you take the fields and put them on a screen but leave the rest of it, the directive, the routing, the legal notice, the approval chain, somewhere else, or nowhere...

[trails off]

That's a haunting thought.

Dot: It's a forms management thought. We were trained to think about what a form carried, not just what it collected. Those are very different things.

Dot offered coffee and then immediately retracted the offer, noting she'd have to find a clean mug and the cabinet situation was "under review, pending a determination on shelf allocation." She did, however, produce a pristine SF-152, Request for Clearance or Cancellation of a Standard or Optional Form, from a folder marked "KEEPERS," and held it up like a person showing you a photograph of someone they loved.⁴

Footnotes

1. The Federal Reports Act of 1942 established the Bureau of the Budget's authority over federal information collection. See H.R. Rep. 104-37, Paperwork Reduction Act of 1995, historical discussion: https://www.congress.gov/committee-report/104th-congress/house-report/37/1 ↩

2. CIA Forms Management Branch, Weekly Report, May 23, 1956 (CREST Document CIA-RDP70-00211R000200100132-1): https://www.cia.gov/readingroom/document/cia-rdp70-00211r000200100132-1 ↩ ↩²

3. GAO Report on Federal Forms Management, October 18, 1976 (GAO ID: 100425): https://gao.justia.com/general-services-administration/1976/10/federal-forms-management-100425 ↩

4. OPM Forms Management Guide, November 2010, Office of the Chief Information Officer: https://www.opm.gov/about-us/open-government/digital-government-strategy/fitara/forms-management-guide.pdf ↩ ↩² ↩³ ↩⁴

5. US Patent 6704906, Self-directed routable electronic form system (formalizing paper-era signature routing rules): https://image-ppubs.uspto.gov/dirsearch-public/print/downloadPdf/6704906 ↩

6. LegalClarity on Standard Form 50: https://legalclarity.org/what-is-the-sf-50-form-notification-of-federal-personnel-action/ ↩