The system has built-in technology to populate multiple locations to search so that your client does not have to worry about coverage. Any search type that is jurisdictional can have a location automatically populated and assigned based on either the "applicants address" or results on the “Past Address History Trace, SSNT”.

Verocity offers multiple ways to populate locations for specific location-based search types.

Search population can be controlled at the client type, client level, or individual package level.

If “Applicant Address” is chosen, the system will populate off of the city, state and zip code that is entered into the order. The system will run the city and state first and populate all counties associated with that city. Next, it will populate off of the zip code. If a county is listed as having at least 5% match within that Zipcode, then that county will populate.

**Please note several systems have customizations to this feature.

**If there is a matching Name and DOB with a partial SSN and the partial SSN did not match the applicants. There was not an SSN match therefore it will inherit the SSN from the applicant profile at the report level.

Past Address History is an integrated tool that can pull a list of past addresses based on a person's name and Social Security Number (SSN). Then the past addresses can be used to populate county-level and state-level searches during the ordering process. This way, you can search all counties that are appropriate for the applicant in question. The system default is to populate all counties listed within a 5% match of that zip code. In addition to addresses, the Past Address History search can trigger automatic alias population, depending on the Ordering Options. Aliases derived from historical address data can trigger additional searches, thereby generating unique Search IDs for each variation of an applicant's name. This adds an additional layer of accuracy by ensuring all potential name variations are accounted for in the search process.

Alias names generated via SSN trace will now include an asterisk (*) next to the name. This can be seen in the admin module at the report level.

ALL alias names will also be highlighted within the admin module’s full report view to visually distinguish them from searches conducted on the main report name.

You can also choose how many years back you would like the past address history trace to go at the top of the client's ordering options, or on the package level.

Client type/client level population controls are located in the Ordering Options. Note: The ability to auto-populate searches should be "checked" when using the client/client type population options.

There are three options for auto-population settings

These options can be set for each search type:

Bankruptcy Report, County Civil, County Civil 2, County Criminal, Federal Civil, Federal Criminal, Sex Offenders, Statewide Criminal, Workers Compensation.

Custom searches are exempt from these settings. All custom searches have a simple yes/no setting. This means they will populate off of “applicant address and SSNT” or not populate at all.

If an extra address is entered into the HR portal or SHM, and any auto-population settings are turned on, the extra address will auto-populate.

Auto-population can also be controlled in the package. Note: Package level controls will override client/client type population settings. Package level population controls are available for search types:

Bankruptcy Report, County Civil, County Civil 2, County Criminal, Federal Civil, Federal Criminal, Sex Offenders, Statewide Criminal, Workers Compensation.

Any custom search that is marked as state or county type in the System Settings will now be available in the 'Autopopulate' list in the ordering options.

When AutoPopulation is set to "ON" (yes selected) -

When AutoPopulation is "OFF" (no selected)-

These population rules apply whether one or more states are active in the researcher network.
Also apply whether package contains only CDS state, CDS county, or both a CDS state and CDS county.

The searches will be set to 'No' when released so as not to cause any issues with the current behavior of the custom search.

You can additionally add locations to search based on where the applicant went to school, or where they have been employed. This way you are covering your bases on all locations.

In the client or client type ordering options, choose "Use verification location for population". Any of the search types chosen to populate will now take the locations entered into the verification into account.

AKA names attached to the applicant's address or the SSNT will continue to populate if the option "Ability to populate alias names" is turned on in the client/client type settings. Remember you can control the population of AKAs by search type in the package. Please see this link for more information.

*NOTE*
1. The settings do not affect orders entered through the admin module or Hubworks integration orders.
2. The "none/applicant address/SSN trace" options for auto-population located in the client/client type and package level settings apply