Closeout requirements, allowable costs at end of term, and rules on equipment disposal are set by the funder and by both institutions — check them together with both research offices well before the final period, since several of them cannot be fixed retroactively.
The science is done, the papers are in progress, and the grant has three months left. This period is usually treated as administrative tidying-up.
It is also where a collaboration either closes cleanly — leaving a partner willing to work with you again — or ends with a set of small unresolved problems that the other side absorbs.
The payment timing problem
This is the most common and most damaging issue, and it is entirely predictable.
Final payments are usually released after the final report is accepted, which can be months after the project ends. Meanwhile your partner has already spent the money — on staff, on consumables, on fieldwork.
For an institution with reserves, a three-month gap is an inconvenience. For a smaller partner it can mean staff not paid on time, and it is the kind of thing that is never mentioned but is remembered.
Three things that help:
Front-load the final tranche where the rules allow, rather than holding it all to the end.
Tell them the realistic timeline early — not the contractual one but what actually happens in practice at your institution.
Submit your side of the reporting on time. A delay you cause is a delay they pay for, and they usually cannot chase it.
What the final report needs from them
Ask for it early — three months before the deadline, not three weeks:
Financial documentation in the format your funder requires. If it differs from what their institution normally produces, this takes time, and it cannot be created retroactively.
Their narrative contribution on what was done and achieved.
Confirmation of what is still in progress — papers submitted, data still being analysed.
A practical point often missed: send them the actual template, not a description of it. And if any of it requires signatures from people who will be on leave, find out when.
Equipment and materials
Agree this before the final month, because the answer is rarely automatic:
Equipment bought with project funds — who keeps it? In most cases the sensible answer is that it stays where the work happened, and where it will continue to be used. Shipping equipment back to a well-resourced lab that does not need it is a poor outcome that funder rules sometimes produce by default.
If rules require transfer or disposal, check whether donation to the partner institution is permitted — it often is, with paperwork.
Consumables and remaining stock.
Samples and specimens — returned, retained, or destroyed, and under whose authority.
Software licences and data subscriptions bought under the grant, which typically lapse at project end. If your partner's ongoing work depends on one, say so now rather than letting it stop working.
Data at project end
Four things to settle:
Both sides hold a complete copy, with enough documentation to use it independently. If your partner has never actually downloaded the data — a common situation when everything lives on your institution's systems — do it now, not later.
Long-term storage — where, for how long, who is responsible, and who pays if there is a cost.
Rights after the project — can each side use the data for new studies without asking the other? This should have been agreed at the start; if it was not, agree it now while goodwill is intact.
Any deposit obligations to a public repository, and who does it.
Unfinished outputs
Most collaborations end with papers still in progress, and this is where things most often drift.
Four agreements, in writing:
Who is responsible for finishing each paper, with a name and a target date.
Authorship, confirmed now rather than later. Memory of contributions fades, and people move on.
What happens if the lead author becomes unavailable — who takes over.
A date after which the remaining data can be used separately by either side. Without this, a dataset can sit unusable for years because one side is waiting for the other.
That last point is the single most useful clause at closeout and almost nobody writes it.
The people
Two things that cost nothing and matter a great deal:
Write for the staff whose contracts end with the grant. A reference letter, written now while you remember specifics, is worth far more than one requested in two years. Offer it rather than waiting to be asked — many will not ask.
Acknowledge the people who did the work in the final report by name, including local field staff and research assistants who are not authors. This is read by their institutions.
Leaving it usable
Three things that determine whether this becomes a one-off project or a continuing relationship:
Have the conversation about what comes next before the project formally ends, while there is still momentum. After the closing date, everyone returns to their own priorities and the window closes quickly.
Write down what worked and what did not — jointly, in a page. It is the best input to the next proposal, and doing it together surfaces things neither side would say in a solo review.
Close it explicitly. If there will be no follow-on, say so clearly and warmly rather than letting contact simply stop. A collaboration that ends with a clear conversation can be restarted; one that fades cannot.
Why is final payment timing a problem for partners?
Final tranches are usually released after report acceptance, months after the money was already spent — for a smaller partner that can mean staff not paid on time.
What should be decided about equipment?
Who keeps it — usually it should stay where the work happened and will continue; check whether donation to the partner institution is permitted.
What is the most useful clause at closeout?
A date after which remaining data can be used separately by either side — without it a dataset can sit unusable for years.
What should be done for staff whose contracts end?
Write reference letters now while you remember specifics, and offer rather than wait to be asked — many will not ask.
