The intended audience for this article is Agents.
Autofill uses data from your Risk Profile, risk data schedules, forms, and other connected sources to help fill out forms faster. If a question doesn't autofill on a mapped form, it means there is no reliable or accurate match to existing data. Autofill only works when a clear connection exists between stored information and a form question.
Types of autofill
Autofill works in different ways depending on the type of data and the structure of the form.
Schedule and account autofill
This is structured autofill. The rule is straightforward: this data consistently maps to the same section.
Risk Data schedules, such as vehicles or locations, connect directly to ACORD sections that function as lists. It works best when the ACORD layout mirrors the structure of the schedule.
This forms the foundation of ACORD Autofill and is supported across core forms today.
Cross form autofill
This connects equivalent questions across different forms within the same Risk Profile. If a reliable mapping exists, answers from one form can populate matching questions on another form. Wunderite supports this today and continues to expand cross form coverage.
Contextual autofill
This type of autofill depends on additional conditions. In some cases, data should only populate if other answers or structural rules on the form are met. For example, payroll and exposure on ACORD 130 may need to be grouped by location, and placement may depend on other selections within the form.
Because placement depends on context rather than a simple one-to-one mapping, this type of autofill is more complex. Wunderite doesn't support contextual autofill yet, but it's on our roadmap.
Scoped autofill
Scoped autofill would allow only a selected subset of Risk Data records to populate a form, rather than automatically including all records. Wunderite doesn't support contextual autofill yet, but it's on our roadmap.
How form mapping works
Wunderite maps questions based on three core principles:
Literal meaning
Structural compatibility
Strong contextual alignment
To protect data accuracy, mappings are only created when two fields are highly equivalent in both meaning and format.
In most cases, questions must meet an approximately 80 to 90 percent contextual similarity threshold before a connection is created. If a mapping could result in conflicting, ambiguous, or misleading data, it is intentionally excluded.
Because Autofill can pull from multiple sources and is bi-directional across forms, even small inconsistencies can create risk. For that reason, accuracy is prioritized over aggressive matching.
Common reasons a question doesn't autofill
Supplemental forms are intentionally specific
Supplemental forms are designed to ask highly detailed or carrier-specific questions. Many carriers use proprietary wording, multi-part questions, or expanded underwriting detail that goes beyond standardized formats such as ACORD.
If a question is materially different in scope, multi-part, or less than approximately 80 percent contextually equivalent to an existing mapped field, it is excluded from mapping to preserve accuracy.
Data type mismatches
Some questions may appear similar but use different data structures. For example:
A Yes or No question can't be mapped to a dropdown.
A combined coverage limit, such as $100k/$300k Auto Liability, can't reliably map to a form that requests separate per-person and per-accident limits.
Even when two questions relate to the same general concept, structural differences can prevent safe reuse of data. In limited cases, a transformer can manipulate the shape of data. However, this is used selectively and doesn't broadly resolve structural mismatches across forms.
Similar context is not the same context
Some questions appear logically related but aren't technically equivalent.
For example:
"Does the restaurant close before 11 PM?"
"Does the restaurant close before 10 PM?"
Although these look similar, they are not interchangeable. Autofill is bi-directional and may reuse data across multiple forms within the same Risk Profile.
If a restaurant closes at 10:30 PM and the questions were mapped together, the system could incorrectly populate “Yes” for closing before 10 PM. To prevent incorrect or misleading data, mappings are not created when contextual differences could produce conflicting answers.
Where mappings are prioritized
Mapped fields are focused on areas that deliver the most immediate Autofill value and structured reuse across a Risk Profile.
Priority areas include:
"First page" questions to ensure core insured and applicant information populates correctly
Risk schedule data such as vehicles, equipment, drivers, and premises to support structured, repeatable data
ACORD standard forms, where mappings are cross-referenced for consistency
Many supplemental forms extend beyond ACORD standards. In those cases, mappings are only created when the data can be accurately and safely reused from the Risk Profile, schedules, or other completed forms.
Why some fields outside the Risk Profile may not autofill
Some data exists outside of structured Risk Profile and schedule data. In certain cases, the system can't reliably determine which person or entity a form expects, such as agent, primary agent, or current user.
When that ambiguity exists, mappings may not be created to avoid incorrect population. For a full list of all Wunderite mapped and unmapped fields, check out our mapping table.
Will these fields ever be mapped?
Some currently unmapped fields may become eligible for mapping in the future if:
Additional equivalent questions are added to the Forms Library
Contextual matching capabilities are improved in future product iterations
However, fields that are structurally different or materially different in meaning will likely remain unmapped to maintain data integrity.
If a question is not autofilling, it is typically a safeguard. Autofill is designed to reuse data confidently, not assume equivalency where accuracy could be compromised.
For more information on how to get more fields to autofill, checkout our dedicated article.