CASRAI Dictionary

Tag: grant budget justification

  • Cost Sharing in Grants: Mandatory vs Voluntary

    Cost sharing on a grant is the portion of a project’s true cost that the sponsor does not pay, covered instead by the recipient institution, a third party, or in-kind contributions. It can be mandatory (a condition of the award, set out in the funding announcement) or voluntary (offered by the applicant and not required). A growing number of funders — most notably the US National Science Foundation — have moved away from requiring or even rewarding voluntary cost sharing, on the grounds that it disadvantages under-resourced institutions and adds compliance burden without improving research quality.

    What is cost sharing in a grant budget?

    Cost sharing (also called matching) is the share of a sponsored project’s total cost that is not reimbursed by the funding agency. It is contributed instead by the recipient institution, a subrecipient, or a third-party collaborator, either as cash or as an in-kind resource such as donated staff time, waived facilities-and-administration (F&A) costs, equipment, or space.

    Under the US federal Uniform Guidance (2 CFR Part 200, §200.306), cost sharing and matching are defined as the portion of project costs “not borne by the Federal Government.” Any contribution counted this way must be verifiable from the recipient’s own records, not double-counted against another federally funded project, and necessary and reasonable for the project. This is the baseline definition US sponsored programs offices apply when reviewing a proposal’s grant budget justification.

    Mandatory vs voluntary cost sharing: what’s the difference?

    The distinction between mandatory and voluntary cost sharing determines whether a commitment is legally enforceable. Mandatory cost sharing is imposed by the sponsor and stated explicitly in the funding opportunity; without it, the proposal is ineligible. Voluntary cost sharing is offered by the applicant even though the sponsor did not require it — and once quantified in a funded federal proposal, it becomes just as binding and auditable as a mandatory commitment.

    Type Who requires it Reporting obligation once awarded
    Mandatory cost sharing Sponsor, stated in the solicitation Documented, tracked and reported to the sponsor for the life of the award
    Voluntary committed cost sharing Applicant, quantified in the proposal budget or narrative Treated as binding and auditable once the award is made, on federal awards
    Voluntary uncommitted cost sharing Applicant, contributed after award but never quantified in the proposal Not tracked or reported to the sponsor

    The trap is the second row. A PI who writes “the PI will devote 20% effort at no cost to the sponsor” creates a quantified, reportable commitment — even though the sponsor never asked for one. This is why sponsored programs offices train investigators to use non-quantified language (“will provide expert consultation, as needed”) whenever cost sharing is not actually required.

    Why are funders moving away from mandatory cost sharing?

    The clearest example is the National Science Foundation. Following its own Cost Sharing Task Force review, NSF’s Proposal & Award Policies and Procedures Guide (PAPPG) states that cost sharing is not required except where a specific program solicitation invokes a statutory requirement, and that reviewers may not factor voluntary committed cost sharing into merit review. NSF’s rationale was that cost sharing had become a competitive filter favouring wealthier institutions rather than an indicator of project quality.

    Three arguments recur across funder policy statements and research-administration literature on this reform:

    • Equity between institutions. A fixed percentage match is far harder for a community college or small non-profit to absorb than for a well-endowed research university — skewing award patterns by wealth rather than merit.
    • Administrative burden. Cost sharing must be certified through effort reporting and reconciled at closeout; auditors treat under-delivered cost share as a disallowed cost, risking clawback.
    • Review integrity. A visible voluntary contribution can bias scoring toward applicants who over-promise resources they may struggle to deliver.

    Cost sharing has not disappeared. It remains common — and often mandatory — on infrastructure and construction grants, public-private partnership schemes, and Department of Justice (DOJ) Office of Justice Programs awards, where the required match varies by programme and is set out in each solicitation’s guide sheet.

    How do UK and EU funders structure cost sharing?

    US-centric discussions of cost sharing rarely mention that the UK and EU systems build an equivalent principle directly into their core funding formulas, rather than treating it as a discretionary add-on.

    UK Research and Innovation (UKRI) funds most Research Council grants at up to 80% of a project’s Full Economic Cost (fEC), calculated via the sector’s Transparent Approach to Costing (TRAC) methodology. The host university funds the remaining 20% itself — a structural, near-universal form of mandatory cost sharing built into the grant terms, not a clause institutions can negotiate away project by project.

    Under Horizon Europe, reimbursement rates differ by action type rather than a flat match: Research and Innovation Actions (RIA) are typically funded at 100% of eligible direct costs, while Innovation Actions (IA) are reimbursed at 100% for non-profit entities but only 70% for profit-making organisations — meaning commercial participants effectively cost-share 30% of their own costs as a condition of taking part.

    This is a genuinely different model from the US project-by-project mandatory/voluntary framework. A US-style “voluntary cost sharing is discouraged” mindset does not transfer cleanly to a UKRI fEC or Horizon Europe budget, where the shortfall is baked into the reimbursement rate itself, not offered or declined proposal by proposal.

    Common questions about cost sharing

    What is cost share on a grant?

    Cost share on a grant is the share of a sponsored project’s total cost that the funding agency does not pay, covered instead by the recipient institution, a subrecipient, or a third party. It can be cash (salary, direct funding) or in-kind (donated time, waived facilities-and-administration costs, equipment) and must be verifiable, allowable, and incurred within the project period.

    What are the three types of cost sharing?

    The three recognised categories are mandatory, voluntary committed, and voluntary uncommitted cost sharing. Mandatory is required by the sponsor as a condition of funding; voluntary committed is offered by the applicant and becomes binding once awarded; voluntary uncommitted is contributed after the award but never quantified in the proposal, so it carries no reporting obligation.

    What is a cost sharing requirement?

    A cost sharing requirement is a condition, stated explicitly in a funding announcement, that obliges applicants to contribute a defined percentage or dollar amount of project costs from non-sponsor sources. Requirements vary widely by programme — from a flat percentage match to a formula tied to Modified Total Direct Costs — and must be documented and reported to the sponsor if the proposal is funded.

    How does cost sharing work?

    Cost sharing works by allocating a defined portion of a project’s budget to the recipient rather than the sponsor, expressed either as a percentage of total cost or as a match ratio (for example, 1:1). Once quantified in a funded proposal’s grant budget justification, the commitment must be tracked through effort reporting or financial records and reconciled at the project’s grant closeout report.

    Implications for institutional budget commitments

    For sponsored programs offices, the decline of mandatory cost sharing at agencies like NSF does not reduce the compliance workload — it relocates it. Institutions must train investigators to recognise when descriptive language in a proposal narrative inadvertently creates a quantified, auditable commitment, distinct from genuinely required match on programmes (DOJ, construction grants, many state and foundation awards) where cost sharing is still mandatory and enforced at closeout.

    Under-delivered cost sharing is treated by auditors as a disallowed cost, triggering a proportional reduction in drawable funds regardless of whether the shortfall was mandatory or voluntary. A “decline all voluntary cost share” policy calibrated to NSF norms misfires against a UKRI fEC award, where the 20% institutional contribution is structural, not optional. A no-cost extension can buy time to complete an outstanding commitment, but it does not waive the obligation — the shortfall must still be resolved before the award can close.

    The direction of travel across US federal science funders is towards evaluating proposals on merit rather than an applicant’s ability to co-invest. Institutions that update proposal-review checklists and budget-justification templates accordingly — while keeping separate, funder-specific guidance for programmes where cost sharing remains mandatory or structural — will reduce both audit exposure and the administrative overhead cost sharing has historically imposed.

  • Grant Closeout Report: A Step-by-Step Checklist for Research Offices

    A grant closeout report is the final compliance deliverable a research office submits to a funder once a project period ends, and it must reconcile every dollar spent, document programmatic outcomes, and account for any equipment purchased with award funds. Getting these three elements wrong — not the science, not the writing — is what turns a routine closeout into an audit finding.

    A grant closeout report is the formal record confirming a recipient has completed all administrative, financial, and programmatic obligations of an award. US federal awards fall under the Uniform Guidance; UK and EU awards fall under UKRI and Horizon Europe grant terms respectively. This guide sets out what a sponsored programs office must submit, in what order, and which recurring errors turn a closeout into a finding.

    What Is a Grant Closeout Report?

    Grant closeout is the formal process by which a funder, a recipient institution, and any subrecipients confirm that all required work and administrative actions tied to an award are complete. It sits at the end of the award lifecycle, after the period of performance ends but before the file can be archived. Under US federal rules, closeout is a regulatory obligation with a fixed deadline and enforceable consequences for missing it — not optional paperwork.

    Institutions managing UKRI, Horizon Europe, and US federal awards side by side need one internal closeout workflow that flexes to each funder’s forms while never dropping the lowest common denominator: reconciled finances, a completed technical report, and a clean equipment record.

    Financial Reconciliation: What the Final Financial Report Must Show

    The final financial report reconciles every dollar drawn down or invoiced against the approved budget and general ledger. For US federal awards this is typically Standard Form 425 (the Federal Financial Report), which must tie exactly to the institution’s accounting records — any variance between the SF-425 and the ledger is one of the most common findings cited in Single Audit management letters.

    A defensible reconciliation package includes:

    • Total expenditures by budget category, matched against the approved (and any amended) budget
    • Documentation for every direct cost: receipts, invoices, and proof of payment
    • Time-and-effort or payroll certification records supporting personnel charges
    • A clear allocation methodology for indirect costs and any cost-shared or matching funds
    • Calculation and return of any unobligated balance, with the date and method of the refund recorded

    Institutions holding multiple awards from the same funder should reconcile each separately before consolidating — cross-charging between grants to smooth a shortfall is a cost-allowability violation, not a bookkeeping shortcut.

    The Final Technical or Programmatic Report

    The final technical report is the narrative counterpart to the financial reconciliation. It documents what the project achieved against the objectives in the original proposal and budget justification, and — under the Bayh-Dole framework for US federal awards — discloses any inventions arising from the work.

    Funders consistently flag two problems: outcomes that no longer match the original aims without explanation, and a narrative that cannot be reconciled with the financial report — for example, claiming a deliverable was completed while its cost category shows no spend. Principal investigators should draft the final narrative from contemporaneous progress notes kept throughout the award, not reconstructed from memory in the final weeks.

    Equipment and Property Disposition

    Equipment disposition is the step research offices most often forget, since it is invisible in the accounting system once purchased. Under 2 CFR § 200.313, equipment with a current fair-market value of $5,000 or more acquired with federal funds must be retained for use on other federally sponsored projects, disposed of per agency instructions, or sold with the federal share of proceeds remitted.

    A closeout-ready equipment record lists, for every capital asset purchased on the award: description, acquisition cost, percentage of federal participation, current location, condition, and final disposition (retained, transferred, sold, or surplused). Institutions that cannot produce this list routinely have the equipment finding flagged in their next Single Audit, sometimes years after the award closed.

    Common Pitfalls That Trigger Audit Findings

    Most closeout audit findings trace back to a small, repeatable set of failures rather than deliberate misconduct. Under 2 CFR Part 200 Subpart F, any non-federal entity that expends $750,000 or more in federal awards during its fiscal year is subject to a Single Audit, and closeout weaknesses are among the most frequently cited findings in these reviews.

    Pitfall Why it triggers a finding
    Missing or non-contemporaneous documentation Expenditure cannot be verified as allowable, allocable, or reasonable at the time it was incurred
    Charges posted after the account should have closed Costs incurred outside the period of performance are unallowable regardless of purpose
    SF-425 (or funder equivalent) inconsistent with the general ledger Reviewers reconcile the financial report against source records as a first check
    No written cost-allocation methodology for shared or indirect costs Auditors cannot test allocation decisions without a documented, consistently applied method
    Equipment inventory incomplete or disposition undocumented 2 CFR § 200.313 disposition obligations are unmet and unverifiable
    Unspent balance not calculated or returned Retention of unspent federal funds without authorisation is a direct compliance breach

    How Closeout Deadlines Differ by Funder

    Research offices managing an international award portfolio cannot apply a single closeout calendar. The deadline, required forms, and audit threshold all vary by funding framework, and missing any of them carries the same consequence: fund recovery risk and a weaker footing for renewal.

    Funding framework Final report deadline Governing rule
    US federal awards 120 calendar days after the period of performance ends 2 CFR § 200.344 (OMB Uniform Guidance)
    Horizon Europe 60 days after the end of the (final) reporting period European Commission Horizon Europe Model Grant Agreement
    UKRI Typically 3 months after the grant end date (longer where an independent examiner’s report is required) UKRI Research Grants Terms and Conditions

    Document retention obligations diverge too: under 2 CFR § 200.334, US federal award records must be kept a minimum of three years from the date the final expenditure report is submitted, longer if litigation, a claim, or an indirect cost rate negotiation is still open.

    Frequently Asked Questions

    What is the grant closeout process?

    Grant closeout is the formal process in which a funding agency, the recipient institution, and any subrecipients confirm that all required project work and administrative actions have been completed. It runs from the end of the period of performance through submission of final reports, return of unspent funds, and formal account closure in the funder’s system.

    What three things are usually included in a closeout report?

    A closeout report typically bundles three components: a final financial report reconciling budgeted against actual spend, a final technical or programmatic report describing outcomes against the original objectives, and documentation of equipment disposition or property disposal where capital assets were purchased on the award.

    How do you write a grant closeout report?

    Start from contemporaneous records kept throughout the award — progress notes, expenditure logs, and equipment purchase records — rather than reconstructing the narrative at the deadline. Reconcile the ledger first, draft the technical narrative against it so figures and outcomes agree, then assemble the equipment and retention file before submission.

    What happens if a grant closeout report is late or incomplete?

    A late or incomplete closeout can trigger an audit finding, a demand for repayment of disallowed costs, and reduced standing for future funding decisions from the same sponsor. For US federal awards subject to Single Audit under 2 CFR Part 200 Subpart F, closeout deficiencies are a recurring category of reported findings.

    What This Means for Research Offices

    Closeout is where a sponsored programs office’s record-keeping discipline over the entire award becomes visible to the funder all at once. None of the individual requirements — reconciling a ledger, writing a technical report, listing equipment — is difficult in isolation; findings happen when all three are left to the final weeks instead of maintained continuously.

    Institutions running mixed US federal, UKRI, and Horizon Europe portfolios get the most protection from a single internal closeout checklist, mapped against each framework’s deadline and audit threshold, applied from the day an award is set up rather than the day it ends. Building that discipline into standard research administration practice is what separates a routine closeout from an audit finding.

  • Grant Budget Justification: Surviving Scrutiny

    A grant budget justification is the narrative document that explains how each line-item cost in a proposal budget was calculated and why that cost is necessary to deliver the funded work. Funders reject weak justifications for three recurring reasons: unexplained cost calculations, a mismatch between the budget and the project narrative, and non-compliance with a specific funder’s format or cost-sharing rules. A budget justification that survives scrutiny is specific, arithmetically transparent, and structured to answer a reviewer’s questions before they are asked.

    A useful working definition: a budget justification is a categorical, line-by-line narrative that shows the calculation method and the programmatic rationale behind every cost category in a grant budget — personnel, travel, equipment, supplies, contractual costs, and indirect costs.

    What Is a Grant Budget Justification and Why Does It Matter?

    A budget justification (sometimes called a budget narrative) sits between the proposal narrative and the budget spreadsheet. The narrative describes what the project will do; the spreadsheet totals what it will cost; the justification explains, in words, how each figure was calculated and why it is required to carry out the activities described in the narrative.

    Reviewers use the justification as a cross-check. If a travel line reads £23,000 with no explanation, a reviewer is left to guess whether that figure is padded, under-costed, or simply unconnected to any described activity. A justification removes that guesswork by tying every number back to a specific, named project activity.

    Why Do Funders Reject Budget Justifications?

    Programme officers and peer reviewers flag budget justifications for a narrow, predictable set of faults, and most are avoidable with a structured drafting process rather than a stronger writing style.

    • Unexplained arithmetic — a total appears with no visible calculation (rate × units × time), forcing the reviewer to take the figure on faith.
    • Narrative-budget mismatch — a cost appears in the budget with no corresponding activity in the project narrative, or vice versa.
    • Wrong template or category set — the applicant uses generic categories instead of the funder’s required headings, or exceeds a stated page limit.
    • Unjustified indirect or fringe rates — a rate is applied without stating the negotiated rate agreement or the base it is applied to.
    • Ignoring cost-sharing rules — voluntary committed cost sharing is offered where the funder’s own policy discourages or disallows it, or a mandatory institutional contribution is omitted entirely.

    The National Institutes of Health (NIH) states in its grant-application guidance that personnel justification must include the name, role, and number of person-months devoted to the project for everyone charged to the award — an explicit, checkable requirement that a generic justification will not satisfy.

    How Does Budget Justification Structure Differ by Funder Type?

    The categories a justification must address, and how much narrative detail each requires, vary by funder and by national research-funding system. Applicants who reuse one template across every funder are the ones most often flagged for non-compliance.

    Funder / system Budget format Justification detail required Cost-sharing posture
    NIH (US) Modular ($25,000 increments to $250,000 direct costs/year) or detailed non-modular Full line-item narrative required above the modular threshold; modular still requires personnel justification Voluntary committed cost sharing discouraged outside statutory requirements
    NSF (US) Standard categories: senior personnel, other personnel, fringe, equipment, travel, participant support, other direct, indirect (F&A) Narrative typically capped at a set page limit per the Proposal & Award Policies and Procedures Guide (PAPPG) Voluntary committed cost sharing discouraged per PAPPG
    UKRI (UK) Full Economic Costing (fEC) submitted via the Je-S system Justification of resources statement tied to fEC cost categories (directly incurred, directly allocated, indirect) UKRI funds up to 80% of fEC; the remaining ~20% is a structural institutional contribution
    Horizon Europe (EU) Unit-cost / lump-sum funding model Cost justification aligned to work packages rather than line items Reimbursement up to 100% for research and innovation actions; lower rates apply to innovation actions for for-profit entities

    The practical implication: a UK institution submitting to both UKRI and a US federal funder in the same funding round needs two structurally different justifications, not one document with re-labelled headings.

    What Is Cost Sharing and When Is It Required?

    Cost sharing is the portion of total project cost that is not requested from the funder — met instead by the applicant institution, a third party, or an in-kind contribution. It is either mandatory (required by the funding opportunity or statute) or voluntary (offered by the applicant without being required).

    US federal guidance treats voluntary committed cost sharing as a risk factor rather than a strength: both NIH and NSF discourage it outside statutory or programme-specific requirements, because a voluntary commitment becomes an auditable, binding obligation once the award is made. The UK system works differently: UKRI’s Full Economic Costing model builds in an institutional contribution — typically the gap between the funded 80% and full cost — as a structural feature of the funding model rather than an optional pledge. Applicants should state their cost-sharing position explicitly and never imply an in-kind contribution that the institution has not formally committed.

    How Do You Write a Budget Justification, Line by Line?

    A defensible justification is drafted alongside the budget spreadsheet, not after it, and follows the same category order as the budget.

    1. Read the solicitation first and identify the funder’s required categories, page limit, and template before drafting a single line.
    2. Work through the budget category by category, writing the calculation (rate × quantity × duration) before writing the rationale.
    3. Reference the specific project-narrative activity that each cost supports, ideally by the same numbering or component label used in the narrative.
    4. State the source of every rate — a vendor quote, an institutional salary scale, a negotiated indirect-cost-rate agreement, or a government per-diem table.
    5. Have a colleague unfamiliar with the project read the draft and flag any figure they cannot immediately follow back to an activity.

    This category-by-category alignment between narrative, budget, and justification is standard practice recommended by research-administration bodies including NCURA and EARMA, and is the single most cited reason reviewers give for confidence in a proposal’s financial planning.

    Answer-First Q&A

    What does budget justification mean?

    A budget justification is a categorical narrative that explains the proposed costs in a grant budget. It documents how each cost was estimated — including any escalation or inflation factors — and lists the specific items that make up the total for each category, so a reviewer can verify the figures independently.

    Can you provide an example of a grant budget line?

    A typical travel line justification states the purpose (for example, presenting results at a named conference), the per-trip cost breakdown (airfare, lodging, per diem), the number of trips and travellers, and the total across the project period — with the arithmetic shown, not just the final figure.

    Can AI tools be used to draft a grant budget justification?

    AI drafting tools can produce a structural first draft, but every cost figure, rate source, and funder-specific compliance detail must be verified by the applicant against the actual solicitation. Funders scrutinise cost accuracy and narrative alignment, not prose quality, so an AI-generated draft with unverified numbers fails review as readily as a poorly written one.

    Implications for Research Administrators

    Institutions that standardise a category-by-category drafting workflow — rather than a single reusable template — see fewer budget-related queries and resubmission requests from programme officers. As funders including UKRI and the European Commission continue to move toward unit-cost and lump-sum models, the justification’s role is shifting from arithmetic verification toward demonstrating that proposed work packages and their costs are coherently scoped. Research offices that train investigators to draft the justification alongside the narrative, rather than after it, consistently produce more defensible — and more fundable — proposals.

  • No-Cost Extension Grant: Funder Rules Guide

    A no-cost extension grant modification lets a research team keep working past the original award end date without any additional funding from the sponsor — it changes the calendar, not the budget. A no-cost extension (NCE) is a formal amendment to a grant’s period of performance that leaves the total award amount unchanged. This guide sets out what counts as valid justification, how the major funder routes differ, and what a research office needs to document before submitting a request.

    What is a no-cost extension grant?

    A no-cost extension is an extension of a grant’s project period, budget period, or both, granted without any increase to the sponsor’s financial contribution. It exists because research timelines rarely match the calendar exactly: equipment fails, staff leave, ethics approvals slip, or a dataset takes longer to collect than planned. Rather than losing the remaining scope of work, the awardee institution requests more time to finish it.

    Crucially, an NCE is not a mechanism for spending down leftover funds more slowly. Sponsors, including UKRI and the US federal agencies operating under the Uniform Guidance (2 CFR 200.309), require a programmatic reason — a scientific or operational cause for the delay — not simply the presence of unspent money. Unspent funds alone are a common but invalid justification, and reviewers are trained to reject requests that rely on it.

    Most systems distinguish two extension types: a grantee-authorised extension, which the institution can approve internally and simply notify the sponsor of, and a sponsor-approved extension, which requires the funder’s programme officer to review and sign off before the new end date takes effect. Which route applies depends entirely on the funder and on whether the award has already used its one-time automatic allowance.

    How do funder approval routes differ?

    No two funders handle no-cost extensions identically. Duration caps, the number of extensions permitted, and who holds approval authority all vary by sponsor, and a research office managing a mixed portfolio needs to track each one separately rather than applying a single house rule.

    Funder Typical maximum duration Approval authority Source
    UKRI Up to 6 months over the grant’s lifetime for non-people-related reasons (longer for parental leave, via a separate Je-S Grant Maintenance request) UKRI review; exceptions require case-by-case approval UKRI, “Requesting a change to your project” (updated 7 May 2026)
    Wellcome Up to 12 months Wellcome, subject to sufficient unspent funds Wellcome, “Grant end dates” funding guidance
    NIH Up to 12 months (first request) Grantee-institution self-authorised for the first extension; NIH approval required thereafter NIH Grants Policy Statement; Uniform Guidance 2 CFR 200.309
    NSF Up to 12 months (first request) Grantee-institution notifies via Research.gov; NSF approval required for a second request Uniform Guidance 2 CFR 200.309
    Cancer Research UK Set by case; resets the grant end date only Cancer Research UK review before the original end date Cancer Research UK, “Grant extensions and suspensions”
    Irish Research Council Set by case IRC review via a standard NCE request form, submitted in advance with justification Irish Research Council, NCE request form
    Horizon Europe Handled as a formal grant agreement amendment Submitted through the EU Funding & Tenders Portal before the original end date Horizon Europe Model Grant Agreement

    The pattern that matters for a research office is the split between delegated authority and sponsor-approved extensions. NIH and NSF delegate the first 12-month extension to the institution itself, which is why compliance still matters even when no sponsor sign-off is required — an internally approved extension that lacks proper justification on file can still be flagged at audit. UKRI, by contrast, caps non-people-related extensions at six months over the grant’s entire lifetime, which makes early planning essential on multi-year awards nearing that ceiling.

    How should research offices document and justify the request?

    A no-cost extension request stands or falls on its documentation. Reviewers — whether an internal sponsored-programmes office or an external programme officer — need a clear, scientifically grounded account of why the work is behind schedule and a credible plan to finish it within the new timeframe.

    A complete no-cost extension request package typically includes:

    • A dated request letter or form, on institutional letterhead, stating the current end date and the proposed new end date
    • A narrative justification tied to the original aims — for example, delayed recruitment, equipment failure, supply-chain delay, or loss of key personnel
    • A progress report summarising work completed and work remaining
    • A grant budget justification showing remaining unspent funds and how they will be used during the extension period
    • Confirmation that ethics, IRB, IACUC or equivalent approvals remain valid for the extended period
    • Departmental or sponsored-programmes-office sign-off before submission to the sponsor

    The request letter and the budget justification should read as two halves of one argument: the letter explains why more time is needed; the budget justification proves the remaining funds are sufficient and appropriately allocated to finish the work. Reviewers who receive a duration request without a matching budget rationale routinely send it back for revision, which costs the research office weeks it may not have close to the original end date.

    Timing discipline matters as much as content. Most funders set a submission window — commonly 10 to 90 days before the current end date — and a late request can be rejected outright regardless of justification quality. Building the no-cost extension conversation into the grant closeout report cycle, six months ahead of the projected end date, gives the office enough runway to gather sign-offs, confirm compliance approvals, and route the request through internal review before the deadline closes.

    Frequently asked questions

    What is a no-cost extension on a grant?

    A no-cost extension is a formal amendment that extends a grant’s project period, budget period, or both, without any additional funds from the sponsor. It allows a principal investigator to finish the original scope of work when the current end date is approaching but the research is not yet complete.

    How long can a no-cost extension be?

    The permitted length varies by funder. NIH and NSF typically allow a grantee-authorised first extension of up to 12 months; Wellcome considers requests up to 12 months; UKRI caps non-people-related extensions at six months over the grant’s entire lifetime.

    What is a blanket no-cost extension?

    A blanket no-cost extension is a single authorisation that applies an identical extension period across multiple awards at once, typically issued by a funder or institution in response to a system-wide disruption. It replaces the need for a separate justification letter on each individual grant affected by the same event.

    How does a no-cost extension work?

    The principal investigator identifies that work will not finish by the current end date, and the research office prepares a justification, progress report and budget statement. Depending on the funder, the institution either self-authorises the extension internally or submits the package for sponsor approval before the award is formally amended.

    What this means for research administration offices

    No-cost extensions sit at the intersection of compliance, forecasting and research administration. An office that treats them as routine paperwork risks two failure modes: internally approved extensions with weak documentation that surface at audit, and sponsor-approved requests submitted too close to the deadline to be processed in time. Neither outcome serves the institution or the funded research.

    The more resilient approach treats the no-cost extension policy of each major sponsor as a standing reference — alongside its grant closeout report requirements and the shared terminology in the CASRAI Dictionary — rather than something looked up fresh for every request. As portfolios diversify across UKRI, US federal agencies, charitable funders and Horizon Europe, the variance in caps and approval authority documented above is exactly the kind of detail that belongs in a research office’s internal policy library, reviewed whenever a funder updates its terms and conditions.

    For institutions building or refining that internal reference, mapping each active funder’s no-cost extension terms against submission deadlines — not against the calendar year — keeps the office ahead of the six-to-twelve-month windows most sponsors actually use.