Collecting new data offline is one problem. Updating a record that already exists is a harder one, because the returning answers must find their way back to the right item.
Ultimate Forms solves it with a loop built from three components. Print generates an editable PDF from the item, pre-filled with its current values. An action emails it to the person who should update it. And Import reads the returned PDF and updates the original item, identified by an ID carried in the email's subject line. The user needs nothing but a PDF reader and an email app, works entirely offline, and the reply sends itself when the connection returns.
This guide builds the loop end to end with an address-verification example. For the other intake channels it belongs beside, see the complete import guide.
The loop at a glance
Four moves, each automated:
- An item is created or reaches the right stage, and an action generates an editable PDF from it, pre-filled, and emails it out.
- The recipient opens the PDF on any device and changes what needs changing, with no connection required.
- They reply to the email with the updated PDF attached. Offline, the reply waits in the outbox and sends itself later.
- The import profile reads the arriving email, extracts the values from the PDF, and updates the original item.
The pre-filling is what makes this an update rather than a form. The recipient sees the current values and corrects only what is wrong, which is faster for them and safer for the data: nothing is retyped that was already right.
The trick: the ID travels in the subject line
An update has to know which item to update, and the loop solves it elegantly. When the action emails the PDF, it writes the item's unique ID into the subject line. When the person replies, the subject comes back with the ID still in it.
On the import side, a condition compares each item's ID with the value extracted from the subject, using the Extract function to take whatever follows "ID:". The returning answers land on exactly the item they left, however long the round trip took and however many PDFs are in flight at once.
It is the same email-borne routing idea the offline submission recipe uses for form types, applied to individual items: the subject line is the address label, and nobody writes it by hand.
Building it: the address verification loop
The example: customers enter their details, and each receives their record as a PDF to verify and correct.
1. The list. A simple list with the columns to verify: name, address, city, ZIP, and the email address the PDF will travel to.

2. The modern form. Design the SharePoint form in Form Designer. This step is optional, but giving users a similar interface in SharePoint and in the PDF keeps the experience consistent.
3. The editable PDF template. In Print, create a template and enable the Create editable PDF option. The template's column placeholders become editable form controls in the generated PDF, matched to your list columns.

And the PDF section of the template:

4. The sending action. Create a Print list item action triggered on Item is added, so the verification email goes out the moment a record is created. In the action settings, pick the template; in the email settings, send to the Email column's value, and set the subject to include the item's unique ID, the detail everything else depends on.

This is how the action is configured:

Here are the email settings:

5. The import profile. In Import, configure the Data provider with the monitored mailbox and set it to extract information from a PDF. The profile learns the PDF's structure from a sample; create one by entering a test item, and the action mails you the sample itself.

6. The update action and its conditions. Add an import action mapping the PDF's form controls to the list's columns. Then the two conditions. Under Item, match the item's ID against the value extracted from the subject line, so the update finds its target. On the profile, filter to the expected subject text, so only the loop's own emails are processed, and your other mail is left alone.

Watching it run
The test is satisfying enough to narrate.
Enter an item with your own details.

Within a minute or so, the email arrives with the PDF attached.

Open the attachment, change a value, the ZIP code, say, and save.

Reply to the email with the updated file attached.

On the next import run, every 15 minutes by default, the profile picks up the reply, matches the ID, and the list item shows the new ZIP.

That is the whole system: one template, one action, one profile. No app was installed, no sync framework deployed, and the person who verified their address never knew they were operating an integration.
Where the update loop earns its keep
Record verification. Customers, vendors, and employees confirm their own details, addresses, contacts, banking, with the current values in front of them and only the corrections to type.
Periodic re-certification. Compliance data that must be re-confirmed on a cycle goes out pre-filled on schedule, and the confirmations file themselves, with the laggards visible as items not yet updated.
Field corrections. The asset record travels to the technician who can see the asset; the corrected readings and statuses come back to the record, from whatever dead zone the asset lives in.
External case updates. The claim, the application, the work order: the outside party updates their own item through a document, with no portal account and no login, the same no-access principle external forms serve online.
Across all four, the loop's quiet feature is its audit trail: the item's version history records exactly what changed when the PDF returned, which the paper version of the same process never offered.
Hardening the loop
A few decisions made up front keep the loop dependable at scale.
Decide what a conflict means. If the item can change in SharePoint while its PDF is traveling, choose which side wins, and the simplest policy is usually right: the PDF updates only the columns it carries, and the item's other columns stay SharePoint's. Keep the PDF's scope narrow, and conflicts mostly stop existing.
Expect the imperfect reply. Someone will forward instead of replying, breaking the subject line, or return a scanned printout with no form controls. The subject filter keeps these from corrupting anything; a weekly glance at unprocessed messages in the mailbox turns them into quick manual fixes.
Close the loop with a courtesy. An alert on the import's update can thank the sender and confirm the record changed. The person who hears "got it" does not email to ask, and the ones who never hear it are your list of non-responders, ready for a reminder action.
And version the template deliberately. PDFs live on devices long after you improve the template, so when the columns change, change the subject tag too, and let the old profile keep handling stragglers while the new one takes over.


