Delivery, Review, and Quality Assurance.

Conducting the work with intellectual and practical discipline.

Delivery is the stage in which the approved Commissioning Brief, provider proposal, project initiation arrangements, and ethical approvals are put into practice.

This is the point at which evidence is collected, documents are reviewed, participants are engaged, data are analyzed, interpretations are developed, and outputs begin to take shape.

Delivery should not be understood as a period in which the provider works without oversight until a final report appears. A commissioned project is a managed relationship. The commissioning body must provide timely decisions, access, institutional support, and constructive review, while the provider must preserve methodological integrity, communicate limitations, and raise risks before they undermine the work.

The purpose of project management and quality assurance is not to control the findings. It is to ensure that the work remains faithful to its purpose, ethically conducted, methodologically defensible, properly documented, and useful to its intended audiences.

The relationship between delivery and the approved brief The Commissioning Brief provides the approved basis for the project. The provider’s proposal and inception report explain how that assignment will be carried out.

During delivery, the project team should be able to answer:

• What question is this activity addressing?
• How does the activity relate to the approved design?
• What evidence will it produce?
• What limitations does it involve?
• What decision or output will it support?
• What approvals or safeguards apply?
• Who needs to know about its progress?

The brief is not a substitute for professional judgment. New evidence may reveal that a method needs to change, a question needs to be narrowed, or an assumption was unrealistic. Such changes should be discussed and recorded rather than concealed within an informal adjustment to the work plan.

Responsibilities during delivery

The Provider or Research Team

The provider is responsible for:

• Conducting the approved work.
• Applying appropriate and transparent methods.
• Maintaining research integrity.
• Protecting participants and data.
• Managing the work plan.
• Recording methodological decisions.
• Reporting progress and risks.
• Explaining limitations.
• Maintaining quality assurance.
• Producing the agreed deliverables.
• Providing complete final files and metadata.

The provider should communicate uncertainty honestly. A delay, recruitment problem, weak dataset, or unexpected finding is a project-management issue that should be reported and addressed, not hidden until the final output.

The Commissioning Body

The commissioning body is responsible for:

• Providing timely decisions.
• Facilitating access to people, data, institutions, or documents.
• Reviewing progress.
• Responding to risks.
• Approving necessary changes.
• Maintaining the boundary between legitimate oversight and interference with findings.
• Reviewing outputs against the brief.
• Supporting dissemination and use.

The commissioning body has a legitimate interest in whether the work is relevant, accurate, complete, and usable. It should not require the provider to remove valid findings or alter conclusions merely because they are inconvenient.

The Commons Coordination Team

The Commons coordination team supports:

• The Commons project workspace.
• Continuity of the project record.
• Appropriate participation and access.
• Connection to relevant Commons groups or publications.
• Documentation of key decisions.
• Preparation of final outputs for Repository deposit.
• Linking the project to follow-on work.

The Commons team is not a substitute for the commissioning body’s project management or the provider’s research responsibility.

Progress Monitoring

Progress monitoring should be proportionate to the project’s scale and risk.

A substantial project may require regular progress meetings, written reports, milestone approvals, and formal risk review. A smaller evidence synthesis may be managed through scheduled written updates and a limited number of review meetings.

Progress Reviews

Progress reviews should examine:

• Work completed since the previous review.
• Work planned for the next period.
• Progress against milestones.
• Use of budget and resources.
• Risks and dependencies.
• Access to data or participants.
• Stakeholder engagement.
• Ethical and safeguarding matters.
• Emerging findings.
• Methodological issues.
• Decisions required from the commissioning body.
• Any proposed changes to scope, method, timeline, or outputs.
• A progress review should conclude with clear actions, owners, and dates.

Project Records

The project should maintain a reliable record of:

• Progress reports.
• Meeting notes.
• Decisions.
• Approved changes.
• Risk-register updates.
• Ethics and data decisions.
• Versions of instruments or protocols.
• Draft outputs.
• Review comments.
• Responses to review.
• Approval records.

The Commons project workspace can support this record through forum topics, activity updates, shared documents, and controlled membership. The project should nevertheless identify which records are authoritative and where final versions are held.

Change control

Research projects often encounter circumstances that were not visible during commissioning. Data may be unavailable, recruitment may be slower than expected, a policy context may change, or early analysis may reveal that an original question cannot be answered as planned.

Changes should be considered in relation to:

• The purpose of the commission.
• The approved questions.
• The scope.
• The method.
• The population or evidence base.
• The timeline.
• The budget.
• The ethics and data arrangements.
• The deliverables.
• The intended users.
• A material change request should state:
• What is proposed.
• Why it is necessary.
• What prompted it.
• How it affects the approved work.
• What risks it creates.
• What additional resources it requires.
• Whether new ethical or data approval is needed.
• Who must approve it.

Minor operational adjustments may be recorded in progress notes. Changes to purpose, scope, outputs, budget, or final interpretation should be formally approved and reflected in the current project documentation.

Quality Assurance

Quality assurance should be designed during project initiation rather than added at the end.

Its purpose is to ensure that:

• The research questions are addressed.
• The evidence is appropriate and sufficiently robust.
• Data are handled responsibly.
• Analysis is transparent.
• Claims do not exceed the evidence.
• Limitations are visible.
• Outputs are accurate, accessible, and usable.
• The work can be understood and assessed by others.
• Quality assurance may involve:
• Peer review.
• Methodological review.
• Advisory-group review.
• Independent assessment.
• Data validation.
• Triangulation.
• Replication or reproducibility documentation.
• Version control.
• Editorial review.
• Accessibility review.
• Stakeholder or participant validation.

The appropriate combination depends on the nature of the commission. A qualitative study, an evidence synthesis, a programme evaluation, and a dataset will not require identical quality procedures.

Methodological Integrity

The provider should maintain a record of important methodological decisions, especially where the final design differs from the original proposal.

The record should explain:

• What decision was made.
• Why it was made.
• What evidence or constraint prompted it.
• What alternatives were considered.
• What implications it has for interpretation.
• Whether the commissioning body approved it.
• Whether ethics or data permissions were affected.

This is particularly important when:

• The sample changes.
• A data source becomes unavailable.
• A measure is revised.
• An analytical method changes.
• A comparison is removed.
• A stakeholder group cannot be reached.
• A new group or data source is added.

Methodological transparency helps future readers understand both the strengths and the limitations of the completed work.

Ethics and Safeguarding during Delivery

Ethics and safeguarding remain active responsibilities throughout the project.

Monitor:

• Consent.
• Confidentiality.
• Anonymity.
• Participant burden.
• Safeguarding.
• Changes in risk.
• Data security.
• Acces permissions.
• Incidents or complaints.
• Communication with participants.
• Compliance with approvals.

If the project changes in a way that affects participants, data, or risk, the team should determine whether additional approval is required before proceeding.

Ethical responsibilities extend through analysis, dissemination, publication, archiving, future use, and sharing. Privacy risks can arise at every stage of the research lifecycle, not only during data collection.

Data Quality and Data Management

During delivery, the team should monitor:

• Completeness.
• Accuracy.
• Consistency.
• Provenance.
• Missingness.
• Access restrictions.
• Versioning.
• Security.
• Retention.
• Documentation.

For qualitative data, this may include records of coding decisions, interview protocols, reflexive notes, and analytic development.

For quantitative data, it may include data dictionaries, cleaning records, codebooks, validation checks, and analysis scripts.

For evidence synthesis, it may include search strategies, inclusion criteria, screening decisions, extraction forms, quality assessments, and synthesis methods.

The level of documentation should be proportionate but sufficient to support confidence in the findings and later interpretation.

Draft Outputs

Draft outputs should be submitted according to the timetable in the Commissioning Brief or project plan.

A draft review should consider:

• Whether the output addresses the agreed questions.
• Whether the argument is clear.
• Whether the evidence supports the claims.
• Whether the methods are adequately explained.
• Whether limitations are visible.
• Whether recommendations are justified.
• Whether the output is appropriate for its audience.
• Whether it meets the required format and accessibility standards.
• Whether acknowledgments, citations, and licensing information are complete.

Draft review is not an opportunity to replace the approved commission with a new project. If reviewers identify a substantial new need, it should be treated as a scope-change discussion.

Distinguishing types of review comments

Reviewers should distinguish among:

• Factual correction: A statement is inaccurate and should be corrected.
• Methodological question: The reviewer needs clarification about how the work was conducted or interpreted.
• Substantive concern: The reviewer believes that the evidence does not support a claim or that an important limitation has been overlooked.
• Editorial suggestion: The wording, organization, design, or presentation could be improved.
• Accessibility improvement: The output needs adaptation for users with different language, format, or access requirements.
• Disagreement with findings: The reviewer does not agree with the conclusion but has not identified a factual or methodological error.
• Scope change: The reviewer is asking for additional work that was not included in the approved assignment.

This distinction protects the provider’s analytical independence while allowing the commissioning body to exercise proper oversight.

Interim and Emerging Findings

Interim findings may be useful for:

• Testing whether the research is addressing the right problem.
• Identifying emerging risks.
• Informing implementation decisions.
• Allowing stakeholders to respond.
• Preparing dissemination.
• Identifying a need for additional analysis.

Interim findings should be clearly marked as provisional. They should not be presented as final conclusions before the agreed review and analysis are complete.

Managing Disagreement

Disagreement may arise about:

• The interpretation of evidence.
• The significance of findings.
• The strength of recommendations.
• The appropriate audience.
• The decision to publish.
• The balance between accessibility and technical detail.

The project should have a documented route for resolving disagreement.

The record should distinguish:

• The provider’s analytical conclusion.
• The commissioning body’s institutional position.
• Advisory or stakeholder views.
• Any unresolved disagreement.

The decision about how the disagreement will be represented in the final output.

A transparent record of disagreement is preferable to an edited output that conceals the fact that a significant difference of interpretation existed.

Final Review and Acceptance

The final review should assess the complete deliverable package against the Commissioning Brief.

The commissioning body should confirm:

• The agreed outputs have been submitted.
• The research questions have been addressed.
• The method is documented.
• Limitations are included.
• Recommendations are distinguished from findings.
• Required revisions are complete.
• The output is suitable for its intended audience.
• Ethical and data obligations have been met.
• Publication and Repository requirements have been addressed.

Acceptance should be recorded with:

• The final output title.
• Version.
• Date.
• Commission reference.
• Accepted deliverables.
• Outstanding conditions, if any.
• Name and role of the approving authority.
• Date of acceptance.

The Commons Project Workspace

The project workspace may contain:

• Approved Commissioning Brief.
• Approved proposal.
• Inception report.
• Work plan.
• Risk register.
• Milestone updates.
• Meeting records.
• Methodological decisions.
• Draft outputs.
• Review discussions.
• Responses to review.
• Acceptance record.
• Links to dissemination.
• Links to Repository records.

Access should be limited according to the sensitivity of the work.

The general Commissioned Research group should not be used for:

• Confidential participant information.
• Restricted datasets.
• Draft contracts.
• Sensitive provider proposals.
• Unapproved findings.
• Internal disputes.
• Material subject to legal or institutional restrictions.

When this stage is complete

Delivery, review, and quality assurance are complete when:

• The approved work has been conducted or formally concluded.
• Material changes have been recorded.
• Required reviews have been completed.
• Final deliverables meet the acceptance criteria.
• The commissioning body has accepted the outputs.
• Remaining publication, dissemination, data, and Repository matters have been assigned.

The project then moves to the stage of making the findings available, interpretable, and useful.

See Also

Commissioned Research.

How Commissioned Research Works.

The Commissioning Brief.

Provider Engagement and Selection.

Project Initiation and Governance.

Repository Deposit and Preservation.

Project Closeout and Learning.

Commissioned Research Group.