Legal

Confidentiality & Report Limitations

Last updated: June 2026

This page explains what a Project Delivery Check report is, what it is not, and how it should be used. It also sets out how reports are kept confidential and what responsibilities rest with the people who receive them.

What a Project Delivery Check report is

A Project Delivery Check report is a structured diagnostic tool. It presents aggregated scores, role group comparisons and AI-assisted narrative based on anonymous survey responses from project stakeholders.

Reports are designed to surface delivery risks, confidence gaps and governance concerns that may not be visible in standard project reporting. They provide a structured basis for management conversation and decision-making.

Reports reflect respondent perceptions and reported conditions at the time the diagnostic was completed. They are one input into project oversight — not a replacement for direct management judgement, project plans, risk registers or governance processes.

What a Project Delivery Check report is not

A Project Delivery Check report is not:

  • An audit or formal assurance review
  • A professional opinion on project viability or commercial risk
  • A legal, financial or technical certification of any kind
  • A guarantee of project success, risk reduction or schedule performance
  • A substitute for governance processes, independent review or specialist advice

Scores and rating bands represent structured indicators at a point in time. They should not be used as the sole basis for material project decisions without corroborating evidence and direct management assessment.

AI-generated narrative

Sections of each report are generated or assisted by artificial intelligence, using submitted diagnostic responses and calculated dimension scores as inputs.

AI-generated narrative summarises patterns and signals observed in the data. It does not access external information about your project and does not have visibility of project documentation, financials or independent assessments.

AI-generated content should be reviewed in context by responsible project leaders before decisions are made. Where AI narrative appears to conflict with known project facts, project leaders should apply their own judgement.

Anonymous responses

Individual diagnostic responses are never shown in reports. All report outputs — scores, narratives, role group comparisons and confidence gap analysis — are derived from aggregated data only.

Free-text comments provided by respondents may be paraphrased in reports to preserve anonymity while retaining diagnostic value. Paraphrasing aims to preserve the substance of the feedback without identifying the individual respondent.

Role group comparisons use categories assigned by the project owner when inviting respondents (for example, Sponsor, PMO, Delivery team). These categories are not linked to individual identity in any report output.

Delivery Signal does not attempt to identify individual respondents from survey data and takes reasonable steps to prevent others from doing so.

Report confidentiality

Reports are prepared for the named project owner, sponsor, consultant or authorised recipient. They are confidential to that recipient group.

Recipients should not copy, forward, publish or distribute reports outside the authorised recipient group without appropriate permission from the project owner.

Where reports are shared with additional stakeholders as part of a governance or review process, the project owner is responsible for ensuring appropriate confidentiality obligations are communicated.

Responsibility for decisions

Any decisions, actions or communications made in response to a Project Delivery Check report remain the responsibility of the project sponsor, leadership team, consultant, PMO or organisation using the report.

Delivery Signal does not assume responsibility for project outcomes, management decisions or organisational actions arising from use of a report.

Where a report identifies significant delivery risks or confidence gaps, the appropriate response is determined by the project owner and their governance structures — not by Delivery Signal.

Limitations of the diagnostic model

The Project Delivery Check assesses 15 delivery dimensions based on respondent perceptions. The diagnostic model is designed to surface systemic patterns rather than measure objective project performance.

Results depend on the quality, honesty and representativeness of responses received. A small or unrepresentative respondent group may produce results that do not accurately reflect project conditions.

Reports are strongest when responses include perspectives from multiple role groups — sponsor or leadership, PMO or project management, and delivery team. Reports based on a single role group should be interpreted with additional caution.

Delivery Signal recommends a minimum of five respondents across at least two role groups for meaningful diagnostic output.

Contact

For questions about this page or report confidentiality: hello@delivery-signal.com

Privacy PolicyTerms of ServiceConfidentiality