# Use properties with responses and projects

> How a mapped form submission creates or updates a property, where the link shows, how properties connect to projects and contacts, and autofill.

## Before you start

- A property connects to the rest of EDOS through form submissions. A
  respondent has to submit a form whose fields are mapped to property fields
  — either individual **Property** field mappings or **Property Information**
  pages — for a property to appear here. See
  [Map fields to your CRM](https://kb.incenti.co/forms/map-fields-to-your-crm.md) and
  [Field groups and reusable field sets](https://kb.incenti.co/forms/field-groups.md) for how to
  set that up on a form.
- Anyone signed in on the account can view these connections — there's no
  separate admin-only step.

## How a submission creates or matches a property

When a mapped submission comes in, EDOS decides whether it describes a
property you already have or a new one:

- A property is matched by its **street address and city** — both must be
  present on the submission and match an existing property's address and
  city exactly once normalized (case, punctuation, and abbreviations like
  "Tennessee" vs. "TN" are ignored; a ZIP+4 extension matches its 5-digit
  form). State and postal code, when present on both sides, must also agree
  — a same-street match in a different state or ZIP is treated as a
  different property. Street suffixes are not treated as equivalent: "123
  Main St" does not match "123 Main Street", and a new property is created
  instead.
- If the submission's street address or city is blank, EDOS neither
  matches nor creates a property from it — an address that could never be
  matched again would just seed duplicates on every later submission.
- **No match creates a new property.** A match **fills in only the blank
  fields** on the existing property; a field the property already has a
  value for is never overwritten, even if the submission disagrees. Where a
  submitted value disagrees with an existing value, that difference is
  recorded as a sync conflict — see
  [CRM sync and conflicts](https://kb.incenti.co/responses/crm-sync-and-conflicts.md).
- A form with **Property Information pages** can submit **more than one
  property in a single response** (one page per property). Each page is
  matched and filled independently, in order — if two pages on the same
  response share an address, the second is matched against the property the
  first one just created or updated, rather than creating a duplicate.

## Where the link shows on the property

Open a property and its detail panel lists every response that created or
updated it under **Form Responses**, each showing the response's title, the
form it came from, and when it was submitted (or created, if it hasn't been
submitted yet). Click a response to open it; the response page's **Back to
property** link returns you to Properties.

_Screenshot: A property's detail panel showing the Form Responses section listing a linked incentive-application response._

## Where the link shows on the response

A response created or updated from a mapped submission shows a **Property**
card with the property's name (linking to `/properties?selected=<id>`, which
opens that property's detail panel directly), its address, status badge,
total and available acreage, and a small map when the property has
coordinates. Until it does, the card reads "Awaiting geocoding" in place of
the map (see [See properties on the map](https://kb.incenti.co/properties/properties-on-the-map.md) for how a
property gets its coordinates). If
the response's form has Property Information pages and more than one
property was submitted, the card shows the first one plus a "+_N_ more
proper&#x74;_&#x79;/ies_ connected" line. A response whose form has no property mapping
shows no Property card at all.

_Screenshot: A form response's detail page showing the Property card with the linked property's name, address, status, and a small map._

## How properties connect to a project

A project (opportunity) page shows a **Properties** section listing every
property connected to any response linked to that project — there's no way
to connect a property to a project directly or by hand. The section is a
clustered map: each pin opens a popup with the property's details and a
"Via _N_ response(s)" line naming how many responses connected it. When
exactly one response did, the line is a link to that response, and the
response's back link returns you to the project. The section only appears once at least one
property is connected; a project with none shows nothing here.

_Screenshot: A project's Properties card showing the connected-properties map with a pin for the property that a linked response connected._

## How properties connect to a contact or organization

A contact's or organization's detail page shows a **Properties** card on its
**Overview** tab listing every property connected to a response that contact
or organization is linked to. As with projects, the connection always comes
through a response — there's no way to connect a property to a contact or
organization by hand.

1. Open **Contacts**, then open the contact — or switch to the
   **Organizations** tab and open the organization.
2. On the **Overview** tab, find the **Properties** card. It shows a small
   map of the properties that have coordinates, then one row per property
   with its name, address, and status badge.
3. Click a row to open that property's detail panel on the **Properties**
   page.

The card appears only once at least one property is connected; a contact or
organization with none shows no **Properties** card. If some connected
properties have no coordinates, the card notes how many are "without
coordinates" — they're listed but have no pin.

## Properties as an autofill source

When someone with their own Incenti account answers another organization's
form inside the portal, **Autofill** can fill property-mapped questions
straight from one of their properties — they pick the property in a card the
Agent shows (or it's chosen automatically when exactly one is already
linked to the response), and the values copy over exactly, with a source chip
so you can see what came from where. See
[Autofill a response](https://kb.incenti.co/responses/autofill-a-response.md) for the full flow,
including the profile and organization details it also draws on and how to
change the source afterward.

## Common questions

**Q: I submitted a form with a property address but nothing shows up on my
Properties page — why?**
A: The submission needs both a street address and a city for EDOS to
match or create a property from it. If either is blank, the property step is
skipped entirely for that submission.

**Q: A response updated the wrong property — can that happen?**
A: Only if the submitted street address and city exactly match an existing
property's (state and ZIP, when both are present, must also agree). Two
different properties on the same street in different states or ZIP codes are
never confused for each other.

**Q: Why didn't a submission change a field on my property?**
A: Matching a property only fills fields that are currently blank. If the
property already had a value, it's kept, and the submission's value is
recorded as a sync conflict instead of overwriting it.

**Q: Where can I see which properties an organization (or a contact) is
connected to?**
A: Open the organization or contact from **Contacts** and look at the
**Properties** card on its **Overview** tab. It lists every property
connected through a response that organization or contact is linked to, and
it doesn't appear when there are none.

## Related

- [Browse the property directory](https://kb.incenti.co/properties/property-directory.md)
- [Map fields to your CRM](https://kb.incenti.co/forms/map-fields-to-your-crm.md)
- [Field groups and reusable field sets](https://kb.incenti.co/forms/field-groups.md)
- [CRM sync and conflicts](https://kb.incenti.co/responses/crm-sync-and-conflicts.md)
- [Autofill a response](https://kb.incenti.co/responses/autofill-a-response.md)
- [Work an opportunity](https://kb.incenti.co/contacts-and-pipeline/opportunities.md)
