Understanding how uploaded files become forms
Last updated: August 18, 2026
When you upload a document, Onboarded converts it into a draft form. The draft is where your review starts — not a finished form ready for candidates.
What it is
Onboarded can build a form out of a document you already have — a PDF of a tax form, a policy packet, a state notice. You upload the source file, and Onboarded reads it and produces a draft form: pages, fields with types, read-only content, and a mapping back onto the original PDF so a completed form can be written onto the source document.
If you remember nothing else: conversion produces a draft, and every draft gets a human review before candidates see it.
Why it matters
Most forms in your account start life as a document somebody handed you. Conversion removes the transcription work — laying out pages, typing labels, choosing field types — which is the slow part of building a form. What it doesn't remove is the judgment: whether a field is required, whether a step stays hidden for some candidates, whether the acknowledgment language survived intact.
Knowing the shape of a conversion tells you where to spend your review time, and explains the statuses on your forms list — the most common question after a first upload.
This matters most when:
You're standing up a new account with a stack of documents to bring in.
You upload a long document and get back a short form — which is often correct, for the reason in the example below.
A form comes back with fewer fields than the source, and you need to tell a miss from a deliberate choice.
How it works
What a conversion produces
Onboarded reads the source document and writes a new form with a draft version. That draft holds the pages, the fields — each typed as a date, a currency amount, a signature, a tax ID, and so on — any read-only content the form needs to display, and a link back to the source PDF.
The source document stays attached to the form, so the PDF tab in Form Studio shows you the original next to what was built from it.
Conversion never touches a published version. A form you've already published keeps serving candidates while a new draft sits alongside it.
Reading the build status
Your forms list carries a build status while a conversion runs and after it finishes. The status tells you whose turn it is.
Status | What it means |
|---|---|
| The conversion is running. Nothing for you to do yet. |
| The conversion finished. The draft is yours to review and publish. |
| The conversion finished and you checked |
| Onboarded couldn't build a form from that file — either the contents didn't match the extension, or the language couldn't be detected or isn't one your organization supports. |
Document type shapes the result
Every file you upload carries a document type, which tells Onboarded what kind of document it's reading. Auto-detect reads the document and picks a type; you can override it per file.
The type matters because the right output for one kind of document is the wrong output for another — a tax form wants precise numbered fields, a handbook wants a short acknowledgment.
Document type | What it's for |
|---|---|
| Content-heavy handbooks, posters, and notice packets that are mostly verbatim text with few real inputs. |
| Disclosures, consents, and notices whose body is read-only text and whose only input is an acknowledgment. |
| Government tax and withholding forms (the W-4 family) with precise, numbered fields. |
| Forms that establish who someone is from the documents they present (the I-9 family): a set of acceptable documents, a choice between them, and an examination step. |
| Standard data-collection forms with no document-type specialization — self-identification, screening questionnaires, notices. |
Language
Onboarded detects the language of the source document and builds the form in that language. Any additional languages you pick under Output language are translated from it, so the detected language is the one the translations derive from.
A converted form is a draft, not a live one. Candidates don't see it until you publish it.
Onboarded also records what it wasn't confident about — structural and fillability findings, each with a severity — and surfaces them in Form Studio as you work. A conversion with no findings isn't a promise that every field is right for your process; it means nothing tripped the checks.
Waiting for Customer means the conversion finished, not that it went perfectly. A form built from a scanned or image-background PDF can arrive with few or no fields and still show that status, because the labels were pixels rather than text. Open every draft before you count on it.
Example
Take an account bringing in a 40-page state labor-law poster packet. The source is almost entirely statute text, with one signature line at the end.
Converted as Handbook / posters, the result is a single page: a short summary naming each posted notice, a link to the full packet, the acknowledgment sentence, and a signature field. Not 40 pages of inputs.
That's the intended outcome. Turning the packet into form fields would hand a candidate hundreds of boxes for a document they were meant to read, not fill in. Your review here is about confirming the acknowledgment language is verbatim and the link resolves — not hunting for missing fields.
A tax document goes the other way. Converted as Tax / withholding, a W-4 comes back with the official step and line numbers preserved in the labels, dollar amounts typed as currency, computed lines carried as formulas rather than boxes the candidate adds up, and the exemption path gated so someone claiming exemption doesn't see the middle steps. There your review is about the branching.
Same conversion, two very different shapes — which is why the document type is worth setting deliberately when you know what you're uploading.