A paper waiver can look finished while leaving a lot of work for a digital form. The line marked “Name” might mean the participant, the person paying, or a parent. A blank beside a paragraph might be for initials. A row of boxes might allow one answer or several. The document's appearance does not settle any of those questions.
Importing a PDF or Word waiver should give you a starting point you can edit, not a picture that customers have to work around. The important part is checking two things separately: whether the agreement survived intact, and whether each field collects the right information.
Start with the right source document
Use the latest approved, unsigned master. A completed customer waiver contains personal information and is also a historical record. It should not become the source for a new public form.
If you have both a Word file and a PDF, start with the cleanest editable version. Remove tracked changes and comments in your source editor after resolving them. Check that the file contains the approved wording, not an earlier draft with a similar filename. Keep an untouched copy so you can compare it with the imported result.
Waiver.com accepts PDF and DOCX imports, plus pasted text. An older .doc file needs to be saved as .docx first. The upload limit is 10 MB; PDFs can contain up to 60 pages. A long document still deserves a readability review before you ask someone to finish it on a phone.
A PDF needs readable text. Scanned pages are images, even when the words look sharp on screen. Waiver.com's importer does not perform OCR and rejects scanned or unreadable pages. Obtain the original Word file or create a text-based copy, then proofread that copy against the original. A password-protected file also needs an accessible export before importing.
Separate the agreement from the form controls
Open the source beside the builder. Read one paragraph at a time and then inspect the controls that follow it. Waiver.com's import process recognizes some standalone field labels, but it cannot infer every relationship from a document's visual layout. It also adds essential signing controls when needed. Review those additions instead of assuming the imported document was already complete.
This mapping is a review aid, not a promise that every item converts automatically:
| In the original document | In the editable form | What to check |
|---|---|---|
| A paragraph of agreement text | A text section | Every sentence, exception, and paragraph is present. |
| Participant name and a blank line | A name field | The label identifies whose name belongs here. |
| Initials beside a statement | An initials field near that statement | The intended statement is still visible beside the control. |
| Several answer boxes | A choice or checkbox control | The form allows the intended number of answers. |
| Space for children | A minors section, if appropriate | Children remain associated with the correct guardian. |
| Signature and date lines | Signing controls and a date field where needed | The stored record contains the values shown during signing. |
Pay special attention to tables and columns. A two-column source might extract in a different reading order. A footer can become ordinary text between paragraphs. Repeated headings might be meaningful sections, or they might simply be page headers. Compare the result before removing anything.
Make ambiguous fields explicit
Suppose the source has two lines labeled “Name.” One sits near the top and one above a signature. On paper, staff may explain what each means. Online, a customer has only the form.
Rename the controls according to their actual purpose, such as “Participant full name” and “Parent or guardian full name.” Do not change approved agreement wording to solve a labeling problem. If the wording itself is ambiguous, route that question to whoever approves your forms.
Inspect required settings individually. An importer seeing a field label does not know your operating policy. A newsletter checkbox should not accidentally become a condition of participation. An emergency contact question should not silently replace the signer's contact details. If an answer should alert staff, configure and test that rule in the builder rather than expecting a sentence in the PDF to create it.
For family forms, check the relationship as well as the fields. Two child names collected as unrelated text boxes are not necessarily equivalent to a structured minors section. Use the guardian and minor waiver workflow when that matches your approved process.
Review the text without rewriting it by accident
Keep a short review log with three columns: source location, imported result, and action. “Page 2, second paragraph: last sentence missing” is useful. “Looks different” is not enough for someone else to resolve.
Separate visual changes from changes in meaning. Joining a line that wrapped in the PDF may be harmless. Losing “unless,” moving an exception away from its condition, or dropping an attachment reference is not a formatting adjustment.
Check lists item by item. Verify names of activities, locations, organizations, and referenced policies. If the source mentions “the rules below,” those rules must still be below it. Do not publish while a reviewer is still deciding which version is authoritative.
The template builder lets you work on sections and fields in the same editor used for other templates. Importing does not lock you into an uneditable document image.
Run a complete signing test
Preview is useful for checking layout. It is not the whole acceptance test. Use a clearly labeled internal test template and fictitious details to complete the signing flow, then inspect the resulting record.
Try a normal submission, a required field left empty, and any family or special-answer path your form includes. Confirm that labels are understandable on a phone. Open the saved result and compare the names, answers, date, and agreement with what you entered. If you change the template after that test, repeat the affected path before using it with customers.
Our online waiver testing checklist covers those checks in more detail. Historical customer records belong in a separate provider migration plan; uploading an old signed PDF as a template is not a records migration.
Import questions
Will the imported waiver look exactly like the PDF?
Not necessarily. The goal is an editable, mobile-friendly form, not a reproduction of page margins and line breaks. Preserve the wording, its order, and the relationship between statements and answers. Review presentation separately.
Can I paste text instead of uploading a file?
Yes. Pasted text can be useful when you have a clean text source or a file that cannot be imported directly. Paragraph boundaries and clear standalone labels help, but you still need to review the controls and required settings.
Can AI improve the wording during import?
Treat those as separate decisions. First preserve and check the approved source. If you want help drafting activity information, use an AI draft and review it separately. Do not let a request for cleaner formatting turn into an unreviewed change to an agreement.