Units and reporting periods in renewal forms
A revenue figure needs the period it describes. A headcount needs to say whether it counts people employed on a particular date or an average over a period. The form should supply that context before the applicant enters a number.
Define what each field asks for
| Requested information | Unit | Period or other context |
|---|---|---|
| Revenue | USD | The specified fiscal year or requested 12-month period. |
| Payroll | USD | The year or other period requested, using the supplied definition. |
| Employee headcount | People | The specified as-of date, or an average if that is what the question requests. |
| Premises floor area | Square feet | The particular risk location and the area the question asks the applicant to measure. |
These are examples of field design. The actual questions and definitions come from the insurance business. A label such as “annual figure” is too vague when different applicants may use a calendar year, a fiscal year or the next 12 months.
Retain the unit and period with the value
The reviewing screen needs the same context the applicant saw. Storing only a number leaves a later reader to infer whether it was dollars, people or square feet and which period it covered.
A field can retain its measure, unit and reporting period alongside the entered value. If the form permits an estimate, it should also retain that status. The application should not silently turn an estimated figure into a confirmed one.
Keep property figures with their risk location
A business with several premises may report a separate area or other requested property figure for each. Give the field a location reference so the reviewing team can see which address the answer concerns.
Use the requested unit consistently. If the form accepts another unit, retain it explicitly and make any conversion visible. The field definition should state the basis of any requested property value; the software should not choose a valuation method for the applicant.
Distinguish an unanswered field from zero
- An empty field means an answer has not been supplied.
- Zero is a numeric answer and should remain distinguishable from an empty field.
- Unknown records that the applicant cannot supply the requested figure.
- Not applicable is a separate response when the question allows it.
Validation can ask for a missing answer or flag a format the form cannot use. It should preserve the response supplied, including an allowed unknown or not-applicable state. The reviewing team can then identify which figures still need clarification.
Separate answers for each premises
Consider a constructed renewal form asking for the floor area of two premises. One answer belongs to Location A and another to Location B. If an export sends only two numbers, the receiving system must guess which is which. The location reference belongs with each answer.
| Answer context | What should travel with it |
|---|---|
| Location A floor area | Location A reference, entered figure, square feet and the area definition supplied in the question. |
| Location B floor area | Location B reference, entered figure, square feet and the same applicable question definition. |
| Estimate permitted by the question | The entered figure and its estimated status, without presenting it as confirmed. |
Checking the exported submission
Before connecting the form to another system, look at the record the reviewer will receive. Can a reader identify the requested period without reopening the original question? Can they distinguish an estimate from a confirmed figure? Can they find the location a property answer describes?
If that context appears only as help text on the entry screen, it may disappear at submission or export. Include it in the field specification and check the receiving record with the same care as the form.