Managing Funded Research: Milestones, Risks, Deliverables and Funder Reporting

Start with the approved award

A funded project begins with a set of commitments, not just a successful proposal. Assemble the award letter, approved application, budget, conditions, partner agreements and any subsequent clarification in a controlled project folder. Identify the version that governs each commitment. A team relying on an earlier proposal may otherwise plan activities or expenditure that were changed during the award process.

Create a short obligations register recording what must be delivered, who is responsible, when it is due and which evidence will support completion. Include relevant financial, research, ethics, data and publication requirements. UKRI's award-management guidance separates matters such as award conditions, changes, spending and reporting outcomes; use the guidance relevant to the particular award rather than assuming every programme follows one procedure. ^[1]

Assign responsibilities that match authority

Identify a project lead, financial contact, research administration contact and named leads for major work packages. Explain who may authorise spending, communicate formal changes to the funder and approve deliverables internally. Participation in a project does not automatically confer authority to bind the institution.

Agree how partners will exchange progress information, supporting records and decisions. Plan for absence or staff turnover by identifying deputies and maintaining shared institutional records. Students and temporary researchers should know where to raise questions without being expected to resolve contractual or financial issues outside their role.

Build milestones around usable evidence

A milestone should describe a verifiable state, such as an approved instrument, completed recruitment assessment or validated dataset. An activity such as holding a meeting may support delivery, but it does not establish that a research objective has been achieved. Define acceptance criteria and the person responsible for reviewing the evidence.

Map dependencies between activities. Analysis may require completed data cleaning; recruitment may depend on permissions and site access. Leave room for review and correction instead of treating the first draft of every output as final. Use a simple schedule that the team can maintain consistently.

Record the difference between a deliverable, a milestone and an intended outcome. A completed report is a deliverable. Whether its recommendations influence practice is a separate question requiring appropriate evidence and, often, a longer timescale.

Review risks and changes together

Maintain a concise risk register with the risk, likely effect, early warning, owner and response. Review it when circumstances change, rather than only before formal reporting. Discuss scientific uncertainty separately from avoidable administrative delays so that management decisions remain appropriate to the problem.

For example, imagine a study whose partner schools can provide access only after a revised term schedule. The team should assess the effect on recruitment, analysis, staffing and reporting before promising a new timetable. It may need an authorised change, a revised method or a reduced scope. This is an illustrative scenario, not a record of a CARE project.

Document the options, decision, approval and communication. Do not assume that an internal decision automatically changes a funder's requirements. Check whether the specific award requires notification, prior approval or an amended agreement.

Connect technical and financial monitoring

Review expenditure beside actual progress and the forecast cost of completing the remaining work. A project that has spent little may be delayed; a project that has spent quickly may have legitimate equipment costs early in its timetable. Neither pattern can be judged responsibly without the delivery context.

Keep records that allow an authorised reviewer to understand what was purchased, why it supported the project and how it was approved. Reconcile partner expenditure and outstanding commitments before they become difficult to resolve. The NSF Proposal and Award Policies and Procedures Guide is an example of a funder-specific policy source; its applicable provisions and associated notices must be checked for an NSF award. ^[2]

Write reports from evidence

Organise a report around agreed objectives, completed work, significant findings, limitations, changes and next steps. Distinguish confirmed results from preliminary observations. If a milestone was missed, explain its consequences and the proposed response using the appropriate reporting channel.

Avoid replacing evidence with a list of meetings or publicity activities. Link claims to deliverables, records or data summaries that the institution is authorised to share. Check confidential, personal and commercially sensitive information before submitting or publishing a report.

Close the project deliberately

Begin closure planning while there is still time to resolve outstanding work. Confirm final deliverables, financial reconciliation, access arrangements, records custody and responsibilities that continue after the award. Applicable retention periods and reporting deadlines come from the award and institutional requirements, not from a universal project template.

• Confirm that the institution holds the final approved versions of essential records.
• Assign responsibility for datasets, software, equipment and unresolved partner obligations.
• Record restrictions on future access or reuse.
• Capture practical lessons for the next application and delivery team.

Successful project management makes research commitments visible and decisions traceable while leaving room for the uncertainty that responsible inquiry necessarily involves.