> ## Documentation Index
> Fetch the complete documentation index at: https://docs.incentives.leap.energy/llms.txt
> Use this file to discover all available pages before exploring further.

# Claimed Fields

> Plan which data points from rebate applications your organization will provide on behalf of customers

You can streamline the rebate application process by providing certain data directly, reducing the burden on end customers. This guide outlines common fields required across utilities.

## How Claimed Fields Work

When you claim ownership of specific fields, those fields will be:

* Removed from the customer-facing application form
* Your responsibility to keep accurate and up-to-date

<Tip>
  Start by claiming fields you already collect across all customers. You can expand to handle territory-specific data over time.
</Tip>

<Note>
  You don't need to claim all fields in a category. Focus on what you can reliably provide with high accuracy. Start with HIGH frequency fields for maximum impact.
</Note>

## Customer Information

These fields contain basic information about the rebate applicant. Most partners can provide at least some of these fields from their customer management systems.

<AccordionGroup>
  <Accordion title="View Customer Fields (11 fields)" icon="user">
    <ResponseField name="first_name" type="string">
      **Frequency:** HIGH

      The first name of the customer
    </ResponseField>

    <ResponseField name="last_name" type="string">
      **Frequency:** HIGH

      The last name of the customer
    </ResponseField>

    <ResponseField name="email" type="string">
      **Frequency:** HIGH

      The email address of the customer
    </ResponseField>

    <ResponseField name="phone" type="string">
      **Frequency:** HIGH

      The phone number of the customer
    </ResponseField>

    <ResponseField name="utility_account_number" type="string">
      **Frequency:** HIGH

      The utility account number of the customer
    </ResponseField>

    <ResponseField name="address_line1" type="string">
      **Frequency:** HIGH

      The first portion of the physical address of the customer
    </ResponseField>

    <ResponseField name="address_line2" type="string">
      **Frequency:** LOW

      The second portion of the physical address of the customer
    </ResponseField>

    <ResponseField name="city" type="string">
      **Frequency:** HIGH

      The city of the customer, found in their address
    </ResponseField>

    <ResponseField name="state" type="string">
      **Frequency:** MEDIUM

      The state of the customer, found in their address
    </ResponseField>

    <ResponseField name="zip_code" type="string">
      **Frequency:** HIGH

      The zip code of the customer, found in their address
    </ResponseField>

    <ResponseField name="mailing_address_line1" type="enum">
      **Frequency:** LOW

      Street line of the customer's mailing address (if different from service address)
    </ResponseField>
  </Accordion>
</AccordionGroup>

## Installation Details

These fields capture information about the equipment installation and purchase. Installation contractors and retailers are typically best positioned to provide this data.

<AccordionGroup>
  <Accordion title="View Installation Fields (9 fields)" icon="wrench">
    <ResponseField name="is_homeowner" type="enum">
      **Frequency:** HIGH

      A boolean variable that defines whether the customer owns their home or not
    </ResponseField>

    <ResponseField name="device_serial" type="string">
      **Frequency:** HIGH

      Serial number of the newly installed device. Required for equipment registration, warranty tracking, and to prevent double-dipping on rebates.
    </ResponseField>

    <ResponseField name="quantity" type="integer">
      **Frequency:** LOW

      Number of identical units installed at the same time. Default is 1. Used when multiple identical devices (like window AC units or smart thermostats) are installed in a single project.
    </ResponseField>

    <ResponseField name="purchase_date" type="date">
      **Frequency:** HIGH

      Date when the equipment was purchased. Must fall within program year dates and is used to verify eligibility timing requirements.
    </ResponseField>

    <ResponseField name="purchase_price" type="decimal">
      **Frequency:** MEDIUM

      The retail price paid for the equipment only, excluding installation labor and materials. Used to verify rebates don't exceed equipment cost and for calculating percentage-based incentives.
    </ResponseField>

    <ResponseField name="installation_date" type="date">
      **Frequency:** MEDIUM

      Date when the equipment was fully installed and operational. Critical for determining application deadlines (e.g., must apply within 30/60/90 days) and program year eligibility.
    </ResponseField>

    <ResponseField name="installation_cost" type="currency">
      **Frequency:** LOW

      The cost of professional installation including labor, materials, permits, and any electrical/plumbing work. Separate from equipment cost to allow programs that reimburse installation separately.
    </ResponseField>

    <ResponseField name="trenching_required" type="enum">
      **Frequency:** LOW

      Boolean indicating if underground trenching was needed for installation. Relevant for EV chargers and can affect eligible installation costs.
    </ResponseField>

    <ResponseField name="permit_number" type="string">
      **Frequency:** MEDIUM

      The building/electrical permit number issued by local authority. Required documentation for programs that mandate permits. Used for verification with local building departments.
    </ResponseField>
  </Accordion>
</AccordionGroup>

## Contractor Information

These fields identify and verify the installation contractor. General contractors and project managers typically have this information readily available.

<AccordionGroup>
  <Accordion title="View Contractor Fields (10 fields)" icon="helmet-safety">
    <ResponseField name="contractor_name" type="string">
      **Frequency:** MEDIUM

      Name of the company that performed the installation. Required by programs that mandate professional installation and used for contractor participation tracking.
    </ResponseField>

    <ResponseField name="contractor_license" type="string">
      **Frequency:** MEDIUM

      State license number of the installing contractor. Required to verify contractor is properly licensed per program requirements. Format varies by state.
    </ResponseField>

    <ResponseField name="contractor_contact_name" type="string">
      **Frequency:** MEDIUM

      Name of the primary contact person at the contracting company. Used for direct communication about projects and applications.
    </ResponseField>

    <ResponseField name="contractor_contact_email" type="string">
      **Frequency:** MEDIUM

      Email address for the primary contact at the contracting company. Used for program communications and missing documentation requests.
    </ResponseField>

    <ResponseField name="contractor_contact_phone" type="string">
      **Frequency:** LOW

      Phone number for the primary contact at the contracting company. Used for scheduling inspections and resolving application issues.
    </ResponseField>

    <ResponseField name="contractor_address_line1" type="string">
      **Frequency:** LOW

      Street address of the contracting company. Required for vendor verification and 1099 tax reporting for incentive payments.
    </ResponseField>

    <ResponseField name="contractor_city" type="string">
      **Frequency:** LOW

      City where the contracting company is located. Part of complete contractor address for business verification.
    </ResponseField>

    <ResponseField name="contractor_state" type="enum">
      **Frequency:** LOW

      State where the contracting company is located. Used to verify contractor is licensed in the state where work was performed.
    </ResponseField>

    <ResponseField name="contractor_zip" type="string">
      **Frequency:** LOW

      ZIP code of the contracting company. Completes contractor address for correspondence and tax reporting.
    </ResponseField>

    <ResponseField name="contractor_website" type="string">
      **Frequency:** LOW

      Website URL of the contracting company. Used to verify contractor legitimacy and for customer reference.
    </ResponseField>
  </Accordion>
</AccordionGroup>

## Vehicle Information

These fields are specific to EV charger installations. Auto dealerships and EV charger installers working with vehicle information are best suited to provide this data.

<AccordionGroup>
  <Accordion title="View Vehicle Fields (5 fields)" icon="car">
    <ResponseField name="vehicle_vin" type="string">
      **Frequency:** MEDIUM

      For EV charger installations, the Vehicle Identification Number of the EV. Used to enforce one-rebate-per-vehicle rules and verify EV ownership.
    </ResponseField>

    <ResponseField name="vehicle_year" type="integer">
      **Frequency:** MEDIUM

      For EV charger installations, the model year of the electric vehicle. Some programs have requirements about vehicle age.
    </ResponseField>

    <ResponseField name="vehicle_make" type="enum">
      **Frequency:** MEDIUM

      For EV charger installations, the make of the electric vehicle (e.g., Tesla, Nissan, Chevrolet). Required to verify customer owns/leases an EV.
    </ResponseField>

    <ResponseField name="vehicle_model" type="string">
      **Frequency:** MEDIUM

      For EV charger installations, the model of the electric vehicle (e.g., Model 3, Leaf, Bolt). Used with make to identify specific EV.
    </ResponseField>

    <ResponseField name="dealership" type="string">
      **Frequency:** LOW

      For EV charger installations, name of dealership where vehicle was purchased/leased. Required documentation for some EV charger rebate programs.
    </ResponseField>
  </Accordion>
</AccordionGroup>
