> For the complete documentation index, see [llms.txt](https://docs.scribeware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.scribeware.com/into-the-weeds/using-pdf-forms.md).

# Using PDF forms

ScribeWare can fill in PDF forms for you, such as Florida's 4-Point and Wind Mitigation forms or a wood-destroying insect report. You record your findings in the report as usual. When you publish, ScribeWare fills the form with them and attaches it to the report. Forms fill the same way whether you publish from desktop or mobile.

There are two kinds of PDF forms:

* **ScribeWare forms.** These are official forms that ScribeWare already knows. Every field is mapped for you, and ScribeWare can set up the chapter that fills it.
* **Your own forms.** You can fill any other fillable PDF by [configuring the form fill yourself](https://docs.scribeware.com/into-the-weeds/configuring-pdf-form-fills-in-scribeware.md).

## ScribeWare forms

These forms are ready to use:

| Form                                                              | Version |
| ----------------------------------------------------------------- | ------- |
| Florida 4-Point                                                   | v9      |
| Florida Wind Mitigation (OIR-B1-1802)                             | 7.4     |
| Citizens Roof Inspection Form (RCF-1)                             | 03-2025 |
| Florida Wood-Destroying Organisms Inspection Report (FDACS-13645) | 05-2021 |
| Maryland Wood Destroying Insect Inspection Report (MD-1)          | 11-2005 |
| NPMA-33 Wood Destroying Insect Inspection Report                  | 07-2019 |
| Texas Official Wood Destroying Insect Report (SPCS/T-5)           | 09-2020 |

We add new forms, and new versions of these ones, as they come out. If you need a form that isn't listed, [let our support team know](mailto:support@getscribeware.com).

ScribeWare recognises a form by its fillable fields, not by its file name. A copy that has been renamed, re-saved or partly filled in is still recognised.

### Where to find them

The forms are in the **PDFs** folder of the media bar. A blue check badge on a PDF means it's a ScribeWare form. When we release a new version of a form, we update the copy in your PDFs folder.

<figure><img src="https://3342988038-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRmvEyXa42lNFnWTj9YA8%2Fuploads%2Fgit-blob-b9ddcdd602ecba1e2866242c0fb14f70e8b331eb%2Fcapture-desktop-pdf-forms-01-pdfs-folder.png?alt=media" alt="The PDFs folder in the media bar, with a check badge on each ScribeWare form"><figcaption><p>The PDFs folder in the media bar. The check badge marks a ScribeWare form.</p></figcaption></figure>

### Adding a form to a report

1. Open the report and go to the chapter for the form, such as **Wind Mitigation Inspection**.
2. Open the **PDFs** folder in the media bar.
3. Drag the form into a section of that chapter.
4. Double-click the PDF to open it. If the chapter is missing anything the form needs, click **Add missing fields**.

ScribeWare adds the form's sections and fields to the chapter, with each field already mapped to its place on the form. Your existing sections and fields are left as they are; new ones go in the same order they have on the form. If the form has a photos section (the 4-Point's **4-Point Photos**, for example), it's set to print after the form.

<figure><img src="https://3342988038-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRmvEyXa42lNFnWTj9YA8%2Fuploads%2Fgit-blob-a6cb3839005b0ea989988f11420ffa31ba76f1aa%2Fcapture-desktop-pdf-forms-setup.gif?alt=media" alt="Dragging the FL Wind Mit form into the Wind Mitigation Form section, opening it, and clicking Add missing fields"><figcaption><p>Setting up a Wind Mitigation chapter: drag the form in, open it, click <strong>Add missing fields</strong>.</p></figcaption></figure>

Then complete the chapter as you would any other. The form is filled in when you publish.

{% hint style="info" %}
If the report came from one of your own templates, ScribeWare offers to **Update template** after adding the fields, so your next report has them from the start. Only that chapter of the template is changed. If you dragged the PDF in from a library observation, the PDF is also saved to that library entry.
{% endhint %}

### When a form's chapter needs attention

A form needs the right fields in its chapter to be filled correctly. If something is missing, the PDF shows an orange warning badge instead of the blue check. Hover over the badge to see how many things need fixing. A form that needs attention also counts as one of the report's **Review** items, so you won't publish it half-filled by mistake.

<figure><img src="https://3342988038-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRmvEyXa42lNFnWTj9YA8%2Fuploads%2Fgit-blob-880d8c0a98b6e52194a95e0533fb38f77e672de0%2Fcapture-desktop-pdf-forms-02-warning-badge.png?alt=media" alt="An orange warning badge on a PDF whose chapter doesn&#x27;t match the form, and the Review count in the sidebar"><figcaption><p>The warning badge and its tooltip. The form also adds one to the Review count.</p></figcaption></figure>

To fix it, double-click the PDF to open it:

1. The form ScribeWare recognised, and its version.
2. What the chapter needs before it can fill this form.
3. The button that makes those changes.

<figure><img src="https://3342988038-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRmvEyXa42lNFnWTj9YA8%2Fuploads%2Fgit-blob-711b8ff8ce7908628100166b3203c286efa8cd0f%2Fcapture-desktop-pdf-forms-03-dialog-needs-changes.png?alt=media" alt="The PDF&#x27;s dialog: the ScribeWare form name, a message listing the changes needed, and the Add missing fields button"><figcaption></figcaption></figure>

The button's label matches what's needed:

* **Add missing fields**: the chapter doesn't have every field the form needs.
* **Update mappings**: the fields are there, but some are mapped to an older version's field names, or to fields this version doesn't have.
* **Add observations**: the form expects default observations, such as a diagram placeholder, that the chapter doesn't have.
* **Add section** / **Set append section**: the form's photos section is missing, or the PDF isn't set to print it.

When everything is in place, the dialog says **This chapter has every field the form needs**.

<figure><img src="https://3342988038-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRmvEyXa42lNFnWTj9YA8%2Fuploads%2Fgit-blob-98b34d6727ca502ce48510d09490c99054601704%2Fcapture-desktop-pdf-forms-04-dialog-ready.png?alt=media" alt="The dialog after Add missing fields: the chapter has every field the form needs, and the Wind Mitigation Photos section is appended"><figcaption><p>After <strong>Add missing fields</strong>: the chapter is complete, and its photos section prints after the form.</p></figcaption></figure>

{% hint style="warning" %}
If you switch to a new version of a form, remove the old version's PDF from the chapter. Once the chapter's mappings are updated for the new version, the old PDF stops filling. The dialog warns you when both are in the same chapter.
{% endhint %}

The dialog also tells you about PDFs that aren't ScribeWare forms. It shows **Custom PDF form with N fillable fields** for your own forms, and warns you when a PDF has no fillable fields at all, so ScribeWare has nothing to fill in.

Use **Preview PDF** to see the form filled in with what's in the report so far, and **Open Original PDF Form** to see the blank form.

### Each form gets its own information

A report can hold several forms, and many forms reuse the same field names, like "Date" or "Owner Name". ScribeWare works out which values belong to which form:

* Fields in the PDF's own chapter take priority over fields with the same mapping elsewhere in the report.
* A mapping made for a specific form takes priority over ScribeWare's mapping for that form. ScribeWare's mapping takes priority over one you made for **Any PDF**.

## Your own forms

You can configure any fillable PDF yourself. See [Configuring PDF form fills in ScribeWare](https://docs.scribeware.com/into-the-weeds/configuring-pdf-form-fills-in-scribeware.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.scribeware.com/into-the-weeds/using-pdf-forms.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
