Products & rating

Application questions: field types and good practice

The seven field types, which to use when, how answers become structured data that drives rating, rules, documents and your future models.

Updated 13 November 2026 · Written and reviewed by the Soldek team

Application questions are the form a broker, a customer or your own team fills in for a submission. Every answer is stored by field name as structured data, never as free text in a note, which is what lets the rating engine, the rules and later your own analytics use it.

Field types

Choice
One answer from a list you define. The most useful type for rating: each option can carry its own factor. (Workbook type: choice.)
Yes / no
Ideal for loadings (hazardous hobbies, previous claims) and knock-out rules. (yes/no)
Date
A date. A date of birth is turned into an age automatically for factors and rules. (date)
Number
A numeric value, for example number of employees or square metres. Can drive factors and rules. (number)
Amount
An amount in the book currency, for example annual turnover or contents value. (amount)
Short text / Long text
Free text. Use for names, descriptions, anything you do not rate on. (text, long text)

Good practice

  • Ask only what you rate on, underwrite on or need in the documents. Every extra question costs conversion on the online quote page.
  • Prefer Choice over text for anything you want to price or filter later. 'Office / Light manual / Heavy manual' is data; 'what is your job?' is not.
  • Mark a question required only if the engine cannot price without it.
  • Use the order you would ask in conversation: who, what, how much, anything unusual. Drag to reorder.
  • Keep field names stable once a product is live; rates and rules refer to them.

See it running.

Book a demo and we show you the complete platform live. Still stuck? Write to hello@soldek.io.