Product update
Smarter contract field suggestions
Uploaded contract PDFs suggest customer, vehicle, contact, payment, and signature fields more accurately—including repeated vehicle and contact rows.
Building a template should not mean clicking every blank on a fifty-page storage agreement.
Why we built it
When you upload a contract PDF, the editor reads AcroForm names, printed labels, and table headers to propose field types before you drag signatures. Smarter contract field suggestions improve that inference for everyday labels—customer and provider names, VIN and plate lines, payment blocks, initials, and signature boxes—and for vehicle schedules with multiple rows. Column headers map through the same rules as one-off labels (including license plate vs plate state), and repeated rows advance so each car line gets its own field set instead of duplicating the first row only.
Who it is for
- Admins onboarding legacy PDFs from attorneys or prior software.
- Teams with multi-vehicle agreements and additional contact tables.
- Anyone pairing upload suggestions with License plate region contract fields for split plate/state columns.
What you can do
- Upload a PDF and accept or adjust suggested field types and Team vs Signer modes.
- Let vehicle schedule detection propose a row of car fields when headers look like a garage list.
- Rely on clearer label rules for combined headers (for example License plate / state split correctly).
- Finish placement with snap-to-line controls in the template editor—see Create a contract template.
How it fits your day
Upload a new storage agreement, review the first page of suggestions, confirm vehicle row headers on the schedule page, then publish. Most fields should land on the correct blank with one pass; fix edge-case labels in Edit field before sending live contracts.
Get started
Upload a test PDF with a vehicle table, accept suggested car columns, and compare one send preview to the printed form before enabling the template for customers.
Questions about this update?
Book time with our team or browse the rest of the changelog.