Map activities rather than labels
Identify who designed the product, produced components, supplied software, integrated services and brought the item to the relevant market. A supplier title may cover more than one activity, while several businesses may share one stage of the process.
Record the supporting material
Connect each role to contracts, specifications, approvals or supply records. Note the relevant dates because relationships can change between releases. A current website description may not explain who performed a role when the affected product was supplied.
Keep legal and factual conclusions separate
A responsibility map is a factual working document. Legal obligations and liability depend on the applicable regime and circumstances. Use the map to organise questions for the relevant advisers rather than presenting it as a final allocation of fault.
Records that help the review
Use the following as a practical starting point. Select and preserve records appropriate to the product, incident and applicable procedure.
- Business identities and activities
- Product and component relationships
- Relevant contracts and approvals
- Dates and changes in responsibility
Illustrative resource for a fictional product-risk practice. Adapt the material to your services, expertise and jurisdiction before publication.
Reference notes and scope
This demonstration uses fictional scenarios and practical record categories. It makes no claim of legal authority, certification or successful client outcomes.
Adapt this resource to the buyer’s expertise and jurisdiction before publication.