Advice and professional judgement
A customer may rely on an analysis, recommendation, report or instruction when making a commercial or operational decision.
What decision is the customer expected to make using the advice?
Where reliance begins
Professional responsibility starts with work another party relies upon
The expectation may sit in a conversation, proposal, contract, specification, project record or accepted working practice. The first question is what the business agreed to provide and how the other party would use it.
Services and agreed scope
Responsibility may develop around what was included, what was excluded, when the work was due and which standard or outcome was expected.
Would both parties describe the scope and completion point in the same way?
Designs, specifications and instructions
An error or ambiguity can move through a project before it is discovered, affecting later work, materials, sequencing or approvals.
Who checks, approves and relies on each version before work continues?
Technology and project delivery
Software, systems, implementation work and project outputs may be judged against functionality, milestones, integration requirements or agreed completion tests.
What does successful delivery mean, and how is it tested or accepted?
Specialist pathways: Technology products and system performance may require a specialist technology liability review. Licensed healthcare and patient care may follow a Medical Malpractice structure. These pathways are not interchangeable with general Professional Indemnity and are identified separately in this guide.
What shapes responsibility
The complaint alone does not explain where responsibility may sit
Two concerns that sound similar can lead to different questions because the scope, reliance, contract, changes, external parties and records are not the same.
Scope and intended outcome
Was the business engaged to advise, perform a defined task, design to a stated brief, implement a system or achieve a specified result? The answer changes what delivery can reasonably be measured against.
How the work was relied upon
What business decision, project step or operation depended on the work? Reliance helps explain why the alleged consequence may extend beyond correcting the original task.
Contract commitments
Did the agreement add a warranty, indemnity, service level, delivery date or acceptance test? These commitments may create questions beyond the ordinary description of the service.
Changes and assumptions during delivery
Requirements, information, deadlines or assumptions may change. The position becomes harder to reconstruct when those changes are informal or are not reflected in the final scope.
External parties and dependencies
Subcontractors, suppliers, customer systems or other advisers may influence the result. The key question is what responsibility the business retained for coordination, supervision, integration or final delivery.
Approval, acceptance and records
Versions, review notes, testing, sign-offs and communications may show what was checked, accepted or still outstanding. Missing or inconsistent records can leave several accounts of the same work.
Why this matters: similar complaints do not create identical responsibility. The position turns on what was promised, relied upon, changed, accepted and recorded.
Examining a concern
A useful review separates six questions before drawing conclusions
A complaint can combine facts, expectations, consequences and assumptions. Separating them helps identify what is confirmed, what remains disputed and what may require legal, technical or specialist input.
1. The promise
- What did the proposal, contract or accepted instruction say the business would provide?
- Which limits, assumptions, dependencies and completion conditions formed part of that promise?
2. The work performed
- What was actually done, delivered or approved, and by whom?
- Were later changes, corrections or additional requests treated as part of the original work?
3. The alleged failure
- What specific act, omission, delay, function or deliverable is being challenged?
- Is the concern about the quality of work, the outcome, the timeline or a difference in expectation?
4. The link to alleged loss
- How is the disputed work said to have caused the claimed cost, delay or financial loss?
- Did a later decision, customer action or external dependency contribute to the outcome?
5. Allocation of responsibility
- Which part may involve the business, customer, subcontractor, supplier or another adviser?
- Do the separate contracts and roles describe responsibility in the same way?
6. Evidence and unanswered questions
- Which versions, approvals, test results, emails and meeting records support each account?
- What remains uncertain, and which issues require another professional to interpret?
Commercial pressure may still develop: rectification cost, delay, withheld payment, external-adviser expense and management diversion may follow. These effects do not by themselves establish responsibility or an insurance outcome.
Different work pathways
The responsibility questions change with the work being relied upon
The same review framework can be used across different professions, but the important commitments, dependencies and records are not identical. Open only the pathway relevant to the business.
What another party relies on: Customers may use recommendations, reports, calculations, instructions or other professional judgement when making business or operational decisions.
What can make the position unclear
- information or assumptions supplied by the customer may be incomplete
- limitations or exclusions may not have been understood in the same way
- new facts may emerge after the advice was given
- the advice may be used for a purpose beyond the agreed engagement
Records and decisions that may matter
- the engagement scope and intended use of the advice
- source information, assumptions and working papers
- drafts, review comments and the final issued version
- communicated limitations, qualifications and approvals
Review focus: whether the concern arises from the advice itself, the information available at the time or how the customer later used it.
What another party relies on: Customers and project parties may rely on designs, specifications, instructions, reports, coordination work and project deliverables before later work proceeds.
What can make the position unclear
- several disciplines or versions may affect the same outcome
- site information, approvals or third-party work may influence the final result
- project-management obligations may be broader than the design role
- later work may proceed before an error or ambiguity is discovered
Records and decisions that may matter
- the brief, design basis, calculations and technical assumptions
- site records, inspection information and project interfaces
- revision history, review comments and approval records
- the respective roles of designers, consultants, contractors and the customer
Specialist route: built-environment activities may require occupation-specific wording and endorsements. The precise professional services and project role must be checked.
What another party relies on: Customers may rely on software, system design, implementation, integration or technical advice to support business operations and project delivery.
What can make the position unclear
- a technology product issue may overlap with a professional-service issue
- integration and customer-environment dependencies may affect performance
- customisation or change requests may alter the original specification
- acceptance testing may not reflect every live operating condition
Records and decisions that may matter
- the statement of work, specifications and promised functionality
- change-control records, implementation decisions and customer dependencies
- test results, acceptance records and unresolved defects
- incident logs, workarounds and communications after performance concerns arose
Specialist route: technology liability can combine professional-service, technology-product and cyber-related questions. It should not be treated as identical to general Professional Indemnity or the separate Cyber guide.
What another party relies on: Patients and healthcare establishments may rely on licensed assessment, treatment, care, supervision and the professional decisions made in providing those services.
What can make the position unclear
- the practice entity and individual practitioners may have different roles
- consultants, contractors or visiting doctors may be involved in the service
- the services provided must match the licensed and declared activities
- a patient complaint may develop into a compensation demand or formal inquiry
Records and decisions that may matter
- professional licences and the services each practitioner provided
- accurate and descriptive treatment and service records
- practitioner, consultant and contractor arrangements
- communications and documents connected with any complaint or inquiry
Specialist route: licensed healthcare may require Medical Malpractice rather than general Professional Indemnity. Non-medical beauty, wellness or treatment services may follow a different Professional Indemnity or treatment-risk route depending on licensing and the actual services provided.
Responsibility overview
The review changes depending on whether the business is preparing or responding
A preventive review and an active incident review use some of the same documents, but they serve different purposes. Neither requires NRM to determine legal responsibility or promise an insurance outcome.
Before a concern arises
- Clarify scope, completion tests, record ownership and external-party responsibilities
- Compare the service and contract commitments with the current protection structure
When a concern has arisen
- Reconstruct the timeline, communications, versions, corrective work and alleged loss
- Identify notification, legal, technical or specialist questions that may require prompt attention
What NRM can help organise
- Map the service, contract, delivery chain and available policy documents
- Separate confirmed facts, unresolved questions and matters requiring another adviser
Where NRM's role stops
- NRM does not provide legal, technical or clinical conclusions
- An insurer determines coverage under the issued policy and the incident circumstances
Licensed healthcare pathway: the review may identify the practice entity, practitioner roles, licensed services, clinical records and whether Medical Malpractice is the relevant insurance route. This does not replace clinical, regulatory or legal review.
Information that can make the first discussion more useful
- The proposal, engagement letter or contract
- Relevant deliverables, versions and approvals
- A short timeline of the concern and communications
- Subcontractor or specialist agreements, where relevant
- The current policy schedule and wording, if available
- A summary of the loss, delay, injury or cost being alleged
Request a Responsibility Route Review
Use 20 to 30 minutes with NRM to map the service, contract, delivery chain and current protection. The discussion can be used before a concern arises or when one has already been raised. It is no obligation, and the intended output is a concise responsibility map, a list of unresolved questions and the appropriate next route.
After submission, NRM will contact you to arrange the no-obligation introductory discussion.