Project Closeout and Learning

Completing the commission responsibly

Project closeout is the stage at which the commissioning body, provider, Commons coordination team, and other responsible participants confirm that a commissioned project has been completed and that its intellectual, ethical, administrative, and preservation obligations have been addressed.

Closeout is not simply the moment when the final report is delivered or the final payment is made. A project is not complete if its outputs have not been reviewed, its publication conditions remain unresolved, its data obligations are incomplete, its Repository record has not been prepared, or its lessons have not been captured.

The purpose of closeout is to bring the research relationship to a responsible conclusion while preserving the possibility of future use.

The relationship between completion and closeout

A project may reach several different forms of completion:

• The provider has completed the research activity.
• The provider has submitted the final deliverables.
• The commissioning body has accepted the outputs.
• The outputs have been disseminated.
• The outputs have been deposited in the Repository.
• The project record has been closed.
• Lessons have been recorded.
• Follow-up work has been identified.

These are related but distinct events.

The project should distinguish between:

• Work completed
• Outputs submitted
• Outputs accepted
• Outputs disseminated
• Outputs preserved
• Project closed
• Future use and follow-up

This sequence prevents the project from being treated as complete merely because a file has been delivered.

Conditions for Closeout

Before closing the commission, confirm that:

• The agreed deliverables have been completed.
• Required revisions have been addressed.
• Final outputs meet the acceptance criteria.
• The commissioning body has formally accepted the outputs.
• Contractual and administrative matters are resolved.
• Required payments or financial reports are complete.
• Publication arrangements are confirmed.
• Licensing and attribution are recorded.
• Dissemination has been completed or scheduled.
• Repository deposit has been completed or scheduled.
• Data-management obligations have been fulfilled.
• Access restrictions and embargoes are documented.
• Lessons learned have been recorded.
• Follow-up work has been identified.
• The Commons project workspace has been retained, restricted, or archived appropriately.

Where one of these matters remains outstanding, the project may be marked as substantially complete but should not be represented as fully closed without an explanation.

Final Acceptance

The final acceptance decision belongs to the commissioning body or the authority identified in the Commissioning Brief.

Acceptance should confirm:

• What deliverables were submitted.
• Which version was accepted.
• Whether the outputs address the agreed questions.
• Whether required revisions were completed.
• Whether the outputs satisfy the agreed format and quality requirements.
• Whether publication and Repository arrangements can proceed.
• Whether any outstanding conditions remain.

The acceptance record should include:

• Commission title.
• Commission reference.
• Commissioning body.
• Provider.
• Accepted deliverables.
• Version numbers.
• Date of acceptance.
• Name and role of approving authority.
• Conditions or limitations.
• Follow-up responsibilities.

Acceptance does not necessarily mean that every participant agrees with every finding. It means that the work has been assessed against the agreed assignment and is accepted as the completed output of the commission.

The Closeout Record

The closeout record should provide a concise but complete account of the project.

It should include:

• Commission title.
• Commission reference.
• Commissioning body.
• Provider or delivery team.
• Project start date.
• Completion date.
• Approved Commissioning Brief.
• Final deliverables.
• Acceptance decision.
• Publication status.
• Repository location.
• Persistent identifier, where available.
• Licence.
• Access conditions.
• Dissemination activities.
• Data and confidentiality arrangements.
• Outstanding restrictions.
• Follow-up actions.
• Lessons learned.
• Final project status.

The closeout record should be linked to the Commission Request, Commissioning Brief, project workspace, and Repository record.

Assessing whether the need was addressed

Closeout should return to the original need.

Ask:

• Did the project address the problem or opportunity that gave rise to it?
• Were the primary questions answered?
• Were some questions only partially answered?
• Did the work produce evidence that can support the intended decision or action?
• Did the context change during the project?
• Were the original objectives still appropriate?
• Did the final outputs reach the intended users?
• What remains uncertain?
• What should happen next?

A project can be competently delivered and still fail to meet its intended use if the need changed, the scope was unrealistic, the outputs were inaccessible, or the commissioning body was not prepared to act on the findings.

The closeout record should therefore distinguish between:

• Quality of delivery.
• Achievement of objectives.
• Usefulness of outputs.
• Evidence of uptake.
• Unresolved needs.
• New questions generated by the work.

Retrospective Review

A retrospective review allows the commissioning body, provider, Commons team, and relevant participants to examine how the commission worked.

It should consider:

Commission design

• Was the need clearly framed?
• Was the purpose sufficiently specific?
• Were the questions appropriate?
• Was the scope realistic?
• Were intended users identified accurately?
• Were the outputs proportionate?

Provider engagement

• Was the selection route appropriate?
• Were the criteria clear?
• Did the selected provider have the required capability?
• Were conflicts of interest identified and managed?
• Did the proposal provide a realistic basis for delivery?

Project Initiation

• Were roles and decision rights clear?
• Were the budget and timetable realistic?
• Were ethics and data requirements addressed?
• Was the inception process useful?
• Were the risks identified early enough?

Delivery

• Was communication effective?
• Were decisions made in time?
• Were changes managed appropriately?
• Did the method remain suitable?
• Were participants and stakeholders treated responsibly?
• Did quality assurance identify and address problems?

Outputs and Use

• Were the outputs useful to their intended audiences?
• Were they accessible?
• Were they disseminated effectively?
• Did the findings influence decisions, policy, practice, or further research?
• Were there unexpected uses or consequences?

Preservation and Reuse

• Was the Repository deposit complete?
• Is the provenance clear?
• Are the outputs discoverable?
• Are access conditions appropriate?
• Can the work be cited and reused?
• What future work may build on it?

Learning from the Project

A retrospective should not be treated as a performance exercise designed to assign blame. Its purpose is institutional learning.

The project may have revealed:

• That a question needed to be narrowed.
• That a different method would have been more appropriate.
• That stakeholder engagement began too late.
• That the budget did not reflect the actual complexity.
• That data access required earlier negotiation.
• That dissemination should have been designed with users.
• That Repository and licensing requirements should have been agreed earlier.
• That a new research question now requires attention.

The lessons learned should be translated into improvements in:

• Future Commissioning Briefs.
• Provider-selection criteria.
• Project initiation.
• Ethics and data planning.
• CBOX workspace design.
• Output planning.
• Dissemination.
• Repository workflows.

Dissemination and Follow-Up

Closeout should confirm not only what has been published but also what remains to be done.

Follow-up may include:

• A public or professional presentation.
• A stakeholder workshop.
• A practice or policy brief.
• A training activity.
• A Journal Publication.
• A new Collaborative.
• A follow-up evaluation.
• A new Commission Request.
• A Repository collection.
• Monitoring of implementation.
• Review of early impact.

The project should identify who is responsible for each follow-up activity and when it will be reviewed.

Closing the Commons Project Workspace

The request-specific Commons workspace may be:

• Retained as an active public knowledge space.
• Converted into a public project record.
• Made read-only.
• Restricted to project members.
• Archived.
• Linked to the Repository record.
• Retained for a defined period and then reviewed.

The decision should consider:

• Public interest.
• Ongoing stakeholder activity.
• Confidentiality.
• Participant expectations.
• Intellectual property.
• Data restrictions.
• Future research value.
• Institutional records requirements.

The workspace should not be deleted simply because the project has ended if it contains essential provenance, decisions, or links to the final knowledge record.

Archiving Working Material

Not all working material should remain publicly available.

The project should determine what happens to:

• Draft reports.
• Review comments.
• Internal correspondence.
• Provider proposals.
• Contracts.
• Meeting records.
• Risk registers.
• Data-management documentation.
• Instruments.
• Research data.
• Sensitive participant information.

Some materials may be preserved in restricted access. Others may be destroyed according to the agreement, ethics approval, data-management plan, or institutional records policy.

The decision should be documented rather than assumed.

Final Project Status

Use a clear final status that communicates what has happened.

Possible statuses include:

• Completed — outputs accepted.
• Completed — outputs published.
• Completed — Repository deposit pending.
• Completed — restricted outputs preserved.
• Closed — redirected.
• Closed — deferred.
• Closed — not proceeding.
• Closed — superseded by a subsequent project.

The status should be recorded in the project workspace and, where appropriate, in the public Commons record.

Reuse and Continuation

A completed commission may provide the foundation for:

• Further research.
• A longitudinal study.
• A new evaluation.
• A Journal Publication.
• A policy or practice resource.
• A professional standard.
• A teaching or training resource.
• A Collaborative.
• A dataset or evidence map.
• A new Commission Request.
• A partnership or programme of work.

The Commons should make these relationships visible. A future project should be able to identify the earlier work on which it builds, even when the question, provider, or commissioning body has changed.

The Final Knowledge Record

The completed commission should leave behind a connected record:

• Commissioning need.
• Commission Request topic.
• Concept Note.
• Commissioning Brief.
• Provider engagement and selection record.
• Project initiation documentation.
• Delivery and review record.
• Final deliverables.
• Dissemination record.
• Repository record.
• Closeout and lessons-learned record.
• Future reuse or follow-up.

This record provides accountability to the commissioning body, provider, stakeholders, participants, and future users.

It also makes the commissioned research layer cumulative. Each completed project contributes not only an output but also experience, methods, relationships, and documented knowledge that can improve later work.

Project Closeout and Learning are complete when:

• The outputs have been accepted.
• Administrative and contractual matters are resolved.
• Publication and dissemination are complete or responsibly scheduled.
• Repository preservation is complete or documented.
• Access, licensing, and data conditions are recorded.
• The Commons workspace has been appropriately retained or archived.
• Lessons learned have been recorded.
• Follow-up responsibilities are assigned.
• The final status is confirmed.

The lifecycle is complete, but the knowledge may continue through dissemination, Repository discovery, future research, new Collaboratives, Journal Publications, or subsequent Commission Requests.

Continue to Explore

Commissioned Research Group

Commissioned Research.

How Commissioned Research Works.

How to Submit a Commission Request.

The Commissioning Brief.

Provider Engagement and Selection.

Project Initiation and Governance.

Delivery, Review, and Quality Assurance.

Outputs, Dissemination, and Use.

Repository Deposit and Preservation.