Why do I need PDFs rather than a spreadsheet?

Because the document itself is often the record — a waiver, a lease, an inspection checklist. A row in a spreadsheet keeps the values and discards the wording they were given in, which is usually the half that mattered.

Can I get both a PDF and a spreadsheet?

Yes. Each response is a completed PDF, and the whole set exports as CSV when you need the data rather than the document. The export is another view of the same responses, not a conversion that costs you the documents.

What columns are in the CSV export?

One column per field you placed, plus three the export adds at the front — the submission time in UTC, the submitter's email address if they gave one, and the IP address the response came from. One row per submission.

Where are the responses kept?

In one place, under the form they came from, newest first. Nothing depends on spotting an attachment in an inbox and filing it before it scrolls away.

Do I get one PDF per person or one big file?

One per person. Fifty applicants produce fifty completed application forms, each a separate ordinary PDF you can open, print, download or forward.

Is the returned PDF really my document?

Yes. The answers are printed into the file you uploaded, at the positions you marked. Your layout, your wording, your letterhead and any clause at the bottom all survive intact.

How to collect form responses as completed PDFs

Collect the answers through a web form and have them drawn back onto the original PDF. You get the convenience of an online form and the artefact you actually need to keep: one completed PDF per response, filed in one place, exportable as CSV when you want the data instead of the document.

Why keep the document rather than the data?

Because for a lot of paperwork the document is the record, and the data is only part of it.

Ordinary form builders are built on the assumption that you want data. You ask five questions, you get five columns, and the value of the exercise is the spreadsheet at the end.

Plenty of paperwork does not work that way, and the tell is usually that the form is evidence of an occasion rather than a store of facts. A move-in inspection checklist records the state of a property on one particular morning, in the layout two people walked round it together holding. A handbook acknowledgment is worth keeping because it shows what the employee was shown. A field trip permission slip matters because of the details of the trip printed above the parent's answers. In each case half the value is in what the form said, and a spreadsheet keeps only the other half.

There is a duller version of the same problem. Forms get read again, later, by people who were not there — a colleague covering your job, someone reconstructing what happened before a dispute, an auditor working through a year of files. Hand them a completed PDF and they see the whole thing at once: what was asked, in what wording, and what came back. Hand them a row of values with no form around it and they have to infer the questions from the column headers, with no way of knowing whether a question was reworded halfway through the year.

So the requirement is not "online form" or "PDF". It is both: an online form because that is what people will actually complete, a PDF because that is what you have to keep. Fillable PDF vs online form sets that trade-off out in full if you are still deciding.

How the responses come back

Start from the document you want to end up with, since that is what everyone will be looking at afterwards. Upload it, then draw a box over every blank the form expects somebody to complete. Each of those is a field you place; nothing about the layout is read for you. It is worth passing the file through the free fillable PDF checker first for one narrow reason — if the document already carries form fields from some earlier life, you want to know that before you start putting your own on top of them. Most files come back with none, which is the easier case: a blank page and a set of positions you choose.

Recipients get a link and complete a web form. What comes back to you is not a notification with the values listed underneath it. It is your file — your layout, your wording, your letterhead if it has one — with the answers printed into the spaces you marked.

That is the part worth being precise about: it is not a rendering of a generic template that vaguely resembles what you sent. It is the same file, with values printed into it. If you send a job application with your organisation's letterhead and a clause at the bottom, the returned PDF has the letterhead and the clause.

Each submission produces its own PDF. Fifty applicants means fifty completed application forms, not one file you have to page through.

What if two people answer at the same time?

Nothing collides. Each submission is drawn onto its own copy of your PDF, so simultaneous responses produce two separate completed documents. There is no single working file that two people can overwrite, which is the failure mode of sharing one editable PDF around a team.

Keeping them in one place

Responses collect under the form they came from, newest first, and stay there. Nothing depends on you spotting an attachment in an inbox and filing it before it scrolls away.

This matters more than it sounds. The usual failure with emailed paperwork is not that a form never arrives — it is that it arrives, gets skimmed, and is never saved anywhere findable. Six months later you are searching your mail for "waiver" and turning up threads about something else. Keeping every response attached to its form means the question "did we ever get one back from him?" has an answer you can look up rather than reconstruct.

You get notified when a response arrives, so you know without checking. Each one can be opened, downloaded, printed, or forwarded on as a normal PDF, because it is a normal PDF. Nothing about it depends on the account it was collected in, which is worth knowing before you commit a year of records to any tool. If you are still emailing forms out as attachments, how to send a PDF for someone to fill out covers the switch.

When you want data instead: CSV export

Sometimes the document is not what you need. You are comparing nine applications and want them in rows so you can sort by availability. You are reconciling a list of who turned up against a list of who registered. You are pulling contact details into another system.

The whole set of responses exports as CSV. You get one row per submission and a column for each field you placed, plus three the export adds at the front: Submitted at in UTC, Submitter email if one was given, and Submitter IP. Open it in a spreadsheet and do whatever spreadsheets are good at.

The UTC column is the one to watch. If you are reading a file of Saturday's registrations from a British summer, the timestamps will read an hour behind the clock on the wall. Convert before you draw any conclusion about who submitted first.

The PDFs are unaffected. The export is another view of the same responses, not a conversion that costs you the documents.

This is why "PDF or form builder?" is usually the wrong question. Collect once, and take the shape you need at the moment you need it: the document for filing and forwarding, the spreadsheet for sorting and counting.

Templates that work this way

If you are setting this up for hiring paperwork, start from something already built. The HR and hiring templates cover the stack a new starter generates — a job application, an information sheet, emergency contacts, an employee handbook acknowledgment — each with its fields already placed. Send the link, and the completed PDFs come back and stay together.