
Measurement
Business insurance attribution methods for small firms
Business insurance attribution methods for small firms: connect quote, policy and service outcomes to their sources without claiming unsupported causation.
Attribution assigns an outcome to a source, action or owner. For small businesses buying commercial cover, business insurance attribution methods help distinguish what influenced an enquiry or policy outcome from what can be shown to have caused it. Several contacts, advisers and controls can affect one result, so describe it accurately as allocation, contribution or causal evidence.
Apply attribution to small-business cover
Small businesses may need public liability, employers’ liability where required, professional indemnity, business contents or tools cover. These policies address different risks, so define the outcome you are measuring rather than treating every enquiry or sale as equivalent.
For example, a small contractor requests public liability and tools cover. The first recorded source shows where the enquiry came from; the last meaningful touch can identify who completed the proposal. If turnover is later corrected, record where the error was entered and detected, and whether the issued documents match the requested cover. This shows allocation and process contribution, not proof that one contact caused a suitable policy or claim outcome.
What to take away
- Choose an attribution method that matches the question and label it as allocation, contribution or causal evidence.
- Define a measurable outcome, its denominator and window before selecting any source fields.
- Do not use marketing attribution to decide whether a policy met demands and needs.
- Attribute operational defects to where the error was created, detected and why the control failed.
- Report attributed and unattributed outcomes, and do not turn correlation into generated or saved.
Compare common methods
Useful for
- First recorded source
- How an enquiry entered the service
- Last meaningful touch
- Which interaction preceded a completed stage
- Rule-based multi-touch
- Sharing credit across known interactions
- Process-owner attribution
- Assigning errors or delay to a workflow stage
- Before-and-after comparison
- Monitoring change after an intervention
- Controlled test
- Estimating effect of a defined change
Main limitation
- First recorded source
- Ignores later influence and may depend on tracking
- Last meaningful touch
- Over-credits the closing step
- Rule-based multi-touch
- Weights reflect a chosen rule, not proven cause
- Process-owner attribution
- Discovery stage may differ from root cause
- Before-and-after comparison
- Other changes may explain the difference
- Controlled test
- Requires ethical design, sufficient sample and stable measurement
Do not use marketing attribution to decide insurance suitability. A source can explain acquisition without determining whether the policy met demands and needs.
Attribution methods and limits
Method
- First recorded source
- Enquiry entry
- Last meaningful touch
- Preceding completed stage
- Rule-based multi-touch
- Sharing credit
- Process-owner attribution
- Errors or delay
- Before-and-after
- Monitoring change
- Controlled test
- Defined change effect
Useful for
- First recorded source
- Ignores later influence
- Last meaningful touch
- Over-credits closing step
- Rule-based multi-touch
- Rule, not proven cause
- Process-owner attribution
- Discovery may differ from cause
- Before-and-after
- Other changes explain difference
- Controlled test
- Ethics, sample, stability
Main limitation
- First recorded source
- Last meaningful touch
- Rule-based multi-touch
- Process-owner attribution
- Before-and-after
- Controlled test
Define the outcome first
Choose a measurable event such as verified submission, issued-document match, completed change, successful handoff or reduced correction. Define its denominator and window before selecting source fields.
Avoid "policy sold" as the only success event. It can reward volume while hiding inaccurate facts, missing documents, later cancellation or complaints.
In a small-business sale, an issued policy document matching the requested cover is a more informative outcome than an enquiry alone. Record whether the policy meets the stated needs separately from which source or contact receives attribution.
Preserve identity and timing
Use stable identifiers for entity, customer, policy, claim and interaction. Store event time, source, consent or lawful-basis context, campaign parameters and system version. Where records contain personal data, handle them under the UK GDPR and Data Protection Act 2018. Distinguish a person opening a page from the business completing a controlled insurance step.
The ICO’s direct marketing guidance and the Privacy and Electronic Communications (EC Directive) Regulations 2003 (PECR) address planning, lawful basis, collection, transparency and objections. Tracking for acquisition requires its own privacy and PECR analysis.
Attribute operational defects to causes
When a submission is corrected, record where the error was created, where it was detected and why the control failed. A quotation team discovering a wrong turnover did not necessarily cause it. Use root-cause review for material or recurring faults.
Defect attribution flow
- Submission corrected
- Where error created
- Where error detected
- Why control failed
- Root-cause review if material
Separate supplier downtime, integration error, missing customer evidence, internal delay and insurer response. This supports action without turning attribution into blame.
Test improvements cautiously
For a before-and-after result, keep definition, audience, season and source stable. Record other changes in pricing, eligibility, staffing, product or marketing. If a controlled test is appropriate, predefine allocation, outcome, duration and stop conditions, including customer-harm monitoring.
External FCA complaints data can show reported firm-level measures above thresholds, but broad groups, joint reporting and different business mixes limit causal comparison. It cannot show that one content or process change caused a firm's result.
Report attribution honestly
State the model, window, missing data, unmatched records, exclusions and sensitivity to alternative rules. Show attributed and unattributed outcomes. Do not convert correlation into "generated", "prevented" or "saved" without a defensible causal design.
Outcome reconciliation view
- All outcomes before attribution
- Matched records
- Unmatched records
- Duplicates removed
- Final allocated total
- Return to original population
Use attribution to choose the next investigation or test. The sound conclusion is often that a source contributed to a measured stage under a stated rule, while the final insurance outcome depended on several actors and facts.
Create a reconciliation view showing all outcomes before attribution, matched records, unmatched records, duplicates removed and final allocated total. The numbers should return to the original population. Investigate missing identifiers by source rather than distributing them proportionally without disclosure.
Review incentives before publishing channel or team results. A last-touch target can encourage unnecessary closing contacts, while process-owner scoring can encourage teams to pass an unresolved case onward. Pair allocation with quality and customer-outcome measures, and let staff challenge a demonstrably wrong assignment through an auditable correction route.
Before you act
- Define the measurable outcome, denominator and window first.
- Use stable identifiers for entity, customer, policy, claim and interaction.
- Record event time, source, consent context and system version.
- Separate supplier downtime, integration error, missing evidence and internal delay.
- State the model, window, missing data and exclusions.
- Build a reconciliation view that returns to the original population.
Common questions
Why is policy sold a poor sole success event?
It can reward volume while hiding inaccurate facts, missing documents, later cancellation or complaints. The article says to avoid using it as the only success event and to choose a measurable event such as verified submission or issued-document match instead.
How should a corrected submission be attributed?
Record where the error was created, where it was detected and why the control failed. A quotation team discovering a wrong turnover did not necessarily cause it. Use root-cause review for material or recurring faults, and separate supplier, integration, customer, internal and insurer factors.
What limits causal comparison of FCA complaints data?
Broad groups, joint reporting and different business mixes limit causal comparison. The data can show reported firm-level measures above thresholds, but it cannot show that one content or process change caused a firm's result, so it should not be used as causal evidence.

