Can Related Insurance Claims Share Evidence?

Use common evidence while preserving each claim’s access and decision history

Published

Blue-and-gold illustration links one engineering report to two separate claim files, each with its own review sheet and lock, with a private photograph beside one file.

A burst pipe damages two units in the same building. Both claims handlers need the engineer’s report on the leak. Each also has photographs, invoices and correspondence specific to their claimant. Putting everything in one incident folder would make the common report easy to find while obscuring which private documents each handler is allowed to use.

Related claims can share evidence when its permitted audience and use are clear. Connect the common report to the incident and relevant claims. Keep each claim’s private material, review decisions and disclosure record separate, and identify the exact report version used for each decision.

Give the incident and each claim a distinct role

  1. 1 · Connect

    Identify the common source

    Link the incident, related claims and evidence whose audience has been reviewed.

  2. 2 · Review

    Record each claim’s use

    Keep private evidence and the exact shared version considered with the individual assessment.

  3. 3 · Follow up

    Handle changes and releases

    Review corrections, approve scoped disclosures and preserve evidence needed by open matters.

The incident reference explains why files are related. It does not grant every participant access to every linked document or make the claims share an outcome. Two claims can rely on the same engineering finding and still require different assessments under their own terms and evidence.

Choose what can be shared

Review the audience and purpose before linking or releasing evidence.
EvidenceTreatmentRecord to preserve
Common engineering reportLink to the relevant claims after checking the report’s content and permitted audience.Source, report version, access decision and each claim’s evidence reference.
Unit-specific photographs or invoicesKeep with the individual claim unless an authorised review establishes a wider need.Claim association, source and the reason for any additional sharing.
Personal or sensitive materialApply the specific access restrictions, including when it is attached to a common report.The protected original and any separately reviewed copy prepared for a narrower audience.
Evidence released externallyApprove the selected documents for the named recipient and purpose.Exact released files, versions, approval, recipient and available delivery evidence.

Keep the current report and earlier decisions distinguishable

A handler may need the latest reviewed report while assessing an open claim. An earlier decision needs the version that was actually considered. Record both relationships explicitly. Updating the working view must not silently replace the evidence reference in an accepted assessment or issued letter.

FormKiQ entities can represent reusable incident or claim records linked to documents. Document versioning supports retaining and retrieving particular versions. Configure the claim’s evidence references and verify that the required content and metadata remain retrievable under the deployment’s storage and lifecycle settings. A version history alone does not record which version an adjudicator accepted.

Worked example: two claims, one corrected report

In this fictional property-claims workflow, A-481 and A-482 relate to the same burst pipe. Their handlers may read the common engineering report, but each claim’s private photographs and correspondence have a separate audience. The identifiers illustrate the business records, rather than prescribed FormKiQ API fields.

  1. Review the common evidence

    The evidence owner checks revision 1 and its attachments before making it available to both handlers. The incident and both claims reference that report. Unit-specific photographs stay with their respective claims.

  2. Record the first claim’s decision

    A-481’s authorised reviewer records a decision citing revision 1 and that claim’s other evidence. A-482 remains open while its handler requests an invoice. The common incident does not make their review status the same.

  3. Route a material correction for review

    The engineer supplies revision 2, changing the reported source of the leak. The configured change process identifies the linked claims and routes the correction to their owners. A-481 records whether reconsideration is required under its procedure; A-482 uses the reviewed revision 2 in its continuing assessment. Both retain their earlier evidence references and the correction history.

  4. Approve a claim-specific disclosure

    A-482 needs to release evidence to an external reviewer. Staff prepare and approve the agreed selection, checking the report’s attachments and excluding A-481’s private material. Any prepared extract remains linked to its source. They retain the exact sent files, approval and recipient with A-482.

  5. Review preservation when one claim closes

    A-481 closes while A-482 remains open. The shared evidence owner checks the report’s retention requirements and any holds before disposition. Access changes for A-481’s participants do not remove A-482’s authorised route to the report or erase A-481’s retained decision evidence.

Test the document permissions behind the relationships

Test a handler assigned to only one claim against search results, metadata, previews, downloads and exports. Check the common report and its attachments as well as the private evidence. Linking a document to an incident or claim is a relationship; access must be enforced through the deployment’s configured document controls. Include external links and integration identities in that review.

Assign an owner to shared evidence so corrections, access requests and preservation decisions have somewhere to go. Closing or unlinking one claim should trigger the applicable review, rather than immediate deletion of a report still needed elsewhere. Where separate copies are required, record their source and purpose and include them in correction and preservation handling.

Test one shared item across two claims

  • Confirm the owner and authoritative identifiers for the incident, each claim and the common evidence.
  • Check the report and attachments before approving their shared audience.
  • Retrieve the exact report version cited by each claim’s review decision.
  • Correct the report and verify that each affected claim records its own response.
  • Test a claim-only handler and an external release against private evidence in the other file.
  • Close one claim and verify access, retention and hold handling for the evidence still in use.

Share the source and preserve each claim’s reasoning

Common evidence is useful when handlers can find it without losing the boundaries of their own claims. Keep its audience explicit, preserve the version each decision relied on and give corrections, disclosures and preservation a named owner.

      Start with FormKiQ Core

      The open-source foundation — API-first, deployable into your own AWS account, and free to use. Right for architecture validation and early implementation.

      Get Started Free

      Deploy FormKiQ Essentials or Advanced

      Production-ready editions for departments and complex workflows. Start with a Proof-of-Value deployment or go straight to production.

      Explore Options

      Plan an Enterprise Rollout

      For governance-heavy environments with residency, sovereignty, assurance, and multi-jurisdiction requirements. Talk to us about the right deployment model.

      Book a Call