Postcode lookups in SchemeServe allow you to enrich a quotation with external data (e.g. crime scores, subsidence scores) and use that data within your rating and referral logic.

There are two main approaches:

• Static postcode lookup tables
• API-based postcode lookups

Option 1: Static Postcode Lookup File

⚠️ Static postcode lookup files are generally considered a dated approach due to their high maintenance requirements and risk of becoming outdated compared to API-driven solutions.

How It Works

A large postcode file (typically 1.6 million+ rows) is uploaded into SchemeServe. This file contains UK postcodes along with associated data such as:

• Crime scores
• Subsidence scores
• Other risk indicators

During quotation:

• The postcode entered in the quotation is used as a key
• The rating file performs a lookup against the uploaded dataset
• Matching values are returned and stored in hidden questions
• These values can then drive rating or underwriting logic

Example Use Case

• Postcode lookup returns a Burglary Score = 9
• Hidden question stores this value
• Rule applied:
• If burglary score > 8 → Refer

Advantages

• Fully contained within SchemeServe
• No dependency on third-party services
• Fast and predictable performance

Limitations

High maintenance overhead

Files must be manually updated when:

• New postcodes are introduced
• Scores or datasets change
• Large file sizes can be cumbersome to manage

Data can become outdated if not regularly maintained

Option 2: API-Based Postcode Lookups

How It Works

Instead of storing postcode data locally, SchemeServe can call an external API (e.g. AddressCloud) to retrieve live data.

Configuration involves:

• Creating an API question
• Defining the API call within the rating file (typically at the top)
• Passing the postcode from the quotation
• Receiving live response data
• Storing selected values in hidden questions

These values can then be used in rating and rules, just like static lookups.

Further API information can be found here.

Example Use Case

• API returns Crime Score = 9
• Stored in a hidden question
• Rule applied:
• If crime score > 8 → Refer

Advantages

• Live, up-to-date data
• No maintenance required within SchemeServe
• Eliminates the need for large lookup files

Considerations

• Requires a commercial relationship with the API provider (e.g. AddressCloud)
• Initial setup requires API configuration within the scheme

Implementation Support

SchemeServe can support the setup of API integrations, including:

• Building the API question
• Configuring the API call in the rating file
• Mapping response fields into usable values