CASRAI Dictionary

Category: Guides & Explainers

Practical how-to guides, templates, checklists, and career pathways for research administrators, authors, and institutional teams.

  • Sponsored Research Administration: A Glossary for New Research Administrators

    Every research administrator remembers the first week: a proposal deadline, an unfamiliar acronym in every email, and a sponsor budget template that assumes vocabulary nobody has explained yet. Sponsored research administration is the institutional function that turns externally funded research proposals into compliant, well-managed awards — and its terminology is not decorative. Getting a definition wrong on a budget justification or an effort report can trigger an audit finding months later. This glossary sets out the core terms a new administrator needs on day one, grounded in how US Uniform Guidance (2 CFR 200), UKRI, and Horizon Europe actually use them.

    What Is Sponsored Research Administration?

    Sponsored research administration is the set of institutional processes that manage externally funded research from proposal through closeout. “Sponsored” distinguishes this funding from an institution’s own discretionary research budget: the money comes from a sponsor — a federal agency, foundation, industry partner, or supranational funder such as the European Commission — under a formal agreement with binding terms and conditions.

    The function typically sits inside an office of sponsored programs or grants and contracts office, where research administrators act as connective tissue between principal investigators, sponsors, and the institution’s finance, legal, and audit functions.

    Research administration is a distinct professional field with its own bodies: NCURA (National Council of University Research Administrators) in the US, EARMA (European Association of Research Managers and Administrators), ARMA (Australasian Research Management Society), and the global umbrella body INORMS — each publishing glossaries and competency frameworks new administrators can use to benchmark their learning.

    The Sponsored-Project Lifecycle: Pre-Award and Post-Award

    Almost every glossary term maps to one of two lifecycle phases. Understanding which phase a term belongs to is often more useful for a new administrator than memorising the definition in isolation.

    • Pre-award covers everything before a sponsor issues funding: identifying opportunities, developing budgets, routing internal approvals, and submitting the proposal.
    • Post-award covers everything after the award is issued: setting up accounts, monitoring spending, certifying effort, filing reports, and closing the project out.
    Phase Typical activities Key terms in play
    Pre-award Proposal development, budget preparation, compliance review, sponsor guideline checks, submission Award, sponsor, cost share, direct costs
    Post-award Award setup, expenditure monitoring, subrecipient monitoring, effort certification, progress reporting F&A, effort certification, no-cost extension
    Closeout Final financial reporting, property disposition, final invoicing, records retention Closeout, final invoice, record retention

    Some institutions split pre-award and post-award into separate teams; others assign one administrator across the full lifecycle. Both models exist across US, UK, and European institutions, and the terminology below applies regardless of structure.

    Core Glossary: Terms Every New Research Administrator Should Know

    These are the terms that appear most frequently in sponsor guidelines, institutional policy, and day-to-day correspondence during a new administrator’s first year.

    • Award — the formal notice from a sponsor confirming a proposal has been funded, together with the binding terms and conditions governing how the money may be spent.
    • Sponsor — the funding organisation: a federal or national agency, a foundation, industry, or a supranational programme such as Horizon Europe.
    • Principal Investigator (PI) — the researcher with primary scientific and programmatic responsibility for the project, typically accountable to the sponsor for its conduct.
    • Direct costs — expenses specifically identifiable with a particular project, such as salaries, equipment, and travel directly attributable to the funded work.
    • Facilities and Administrative (F&A) costs — also called indirect costs or overhead; the expenses an institution incurs to support research broadly (buildings, utilities, central administration) that cannot be charged directly to one project. In the US, F&A rates are negotiated with a cognizant federal agency under the Uniform Guidance at 2 CFR 200.
    • Cost share (or matching) — the portion of project costs not covered by the sponsor. Mandatory cost share is a condition of the award; voluntary committed cost share is offered in the proposal but, once accepted, becomes equally binding.
    • Effort certification — a compliance process, required under 2 CFR 200.430 for US federal awards, confirming that salary charged to a project reflects the actual time an individual spent working on it.
    • Subrecipient / subaward — an organisation receiving a portion of the sponsored funding to carry out a defined part of the project’s scope, itself subject to monitoring by the prime recipient institution.
    • No-cost extension — an extension of a project’s end date, granted without additional sponsor funding, to complete the originally approved scope. Most US federal agencies permit institutions to approve one no-cost extension of up to 12 months under expanded authorities.
    • Closeout — the formal process of finalising a project: final financial and technical reports, expenditure reconciliation, and disposal of sponsor-funded equipment per the award terms.

    Grant Administration vs Grant Management

    New administrators often treat both phrases as synonyms — and in casual use, they usually are. But the terms carry a genuine distinction most onboarding material skips. Research administration (and its narrower cousin, sponsored programs administration) is typically used from the recipient institution’s perspective: how a university, hospital, or institute manages the funding it receives.

    Grant management is used more broadly, often from the funder’s perspective: how a foundation or agency administers its portfolio of outgoing grants and tracks compliance across grantees. UK charitable funders frequently use “grant management” in this funder-side sense, while UKRI and the research councils use “research administration” or “grants and contracts” for the recipient-side function. Knowing which side of the relationship a document is written from resolves most of the apparent inconsistency.

    Common Questions from New Research Administrators

    What is sponsored research administration?

    Sponsored research administration is the institutional function that manages externally funded research from proposal submission through award closeout. It spans pre-award activities such as budgeting and submission, and post-award activities such as compliance monitoring and reporting, ensuring projects meet sponsor terms and institutional policy.

    What is the role of a research administrator?

    A research administrator supports investigators through proposal preparation, budget development, and compliance review, then manages the awarded grant or contract through spending, reporting, and closeout. The role bridges researchers, sponsors, and institutional offices including finance, legal, and compliance.

    How do you become a research administrator?

    Most research administrators enter the profession from finance, project-management, or academic-support backgrounds rather than a dedicated degree route. Professional bodies including NCURA, EARMA, ARMA, and INORMS offer certificate programmes and community-recognised credentials that formalise skills learned on the job.

    Why Terminology Precision Matters

    Imprecise terminology is not cosmetic — it has direct compliance and financial consequences. Confusing mandatory cost share with voluntary committed cost share can leave an institution under-reporting a binding obligation, and treating F&A as a negotiable line item rather than a federally negotiated rate can misstate a budget before it reaches a sponsor.

    Effort certification errors are a recurring federal audit finding precisely because the underlying concept — that certified effort must reflect actual work performed, not budgeted intent — is easy to state and easy to get wrong in practice. New administrators who internalise precise definitions early avoid the costliest category of error: one that surfaces only at audit, long after the relevant staff have moved on.

    For institutions spanning US, UK, and EU funding environments, shared vocabulary matters even more: a research administration office managing both NIH awards and Horizon Europe grants must translate between US-specific terms like “no-cost extension” and the amendment-request processes used by European funders, without losing the underlying compliance intent.

    Building Fluency as the Profession Grows

    Sponsored research administration is professionalising quickly. Certificate programmes, competency frameworks from NCURA and EARMA, and growing recognition of research administration as a distinct career path — rather than an administrative afterthought — point toward a field with rising expectations for precise, shared terminology.

    For a new research administrator, fluency in these terms is not academic: it is the difference between a clean proposal budget and a rejected one, a routine effort report and an audit flag, a smooth closeout and a delayed final payment. Treat this glossary as a starting reference, not a substitute for institutional policy — always confirm current thresholds and rates against your own sponsor’s current guidelines, since these are periodically revised.

    CASRAI’s broader research administration resources and dictionary of standards terminology extend this glossary into adjacent areas, including researcher identification, funder metadata, and contribution reporting standards that increasingly intersect with sponsored-project compliance.

  • Electronic Research Administration: What to Evaluate in 2026

    What electronic research administration actually means

    Electronic research administration (commonly abbreviated ERA, and sometimes called eRA) refers to the digital systems and workflows that universities, hospitals, and research institutes use to manage the full lifecycle of sponsored research — from identifying a funding opportunity through proposal submission, award negotiation, compliance monitoring, and financial closeout. The term covers both the specific federal touchpoints, such as the US National Institutes of Health’s eRA Commons and ASSIST systems, and the broader category of institutional research administration software that sits between researchers, sponsors, and finance offices.

    Most research-intensive institutions no longer run these processes on spreadsheets and shared drives. They run them through a dedicated electronic research administration system, or a stack of interoperable modules, because sponsors themselves have moved to electronic submission. Grants.gov, the UK’s UKRI Funding Service, and Horizon Europe’s portal all require electronic workflows on the sponsor side; institutional ERA platforms exist largely to feed proposals into — and pull award data back out of — those sponsor systems without duplicate manual entry.

    Core modules: pre-award, post-award, compliance, effort reporting

    Despite different vendor branding, mature ERA platforms converge on a broadly consistent set of functional modules. The table below summarises what each typically covers and where it interacts with external systems.

    Module What it typically covers External touchpoints
    Pre-award Funding-opportunity discovery, proposal development, budget building, internal sign-off routing Grants.gov, UKRI Funding Service, sponsor portals
    Post-award Award setup, budget tracking, subaward management, financial reporting to sponsors Institutional finance/ERP systems
    Compliance Conflict-of-interest disclosure, IRB and IACUC protocol tracking, export-control screening, foreign-component disclosure Institutional COI registers, ORCID iDs
    Effort reporting Certifying personnel time charged to sponsored awards against actual effort HR/payroll systems, 2 CFR 200.430
    Analytics/reporting Portfolio dashboards, proposal-to-award conversion, audit-readiness reporting Institutional data warehouses

    Few institutions run all five modules from a single vendor. Chief research officers most often report assembling a stack — a proposal-routing tool from one vendor, a dedicated compliance or effort-reporting module from another — connected through system-to-system integrations rather than buying one suite outright. That reality should shape how any evaluation is scoped: interoperability matters as much as feature breadth.

    Why Uniform Guidance and audit scrutiny are reshaping ERA requirements

    US institutions receiving federal research funding operate under the Office of Management and Budget’s Uniform Guidance (2 CFR Part 200). OMB’s 2024 revisions to that guidance — effective for federal awards issued on or after 1 October 2024 — raised the Single Audit expenditure threshold from $750,000 to $1,000,000 and increased the de minimis indirect cost rate available to institutions without a negotiated rate from 10% to 15%. Both changes alter what an ERA system needs to track and report, and by when.

    • A higher Single Audit threshold shifts more institutions toward risk-based, targeted monitoring rather than a full annual audit — which means ERA compliance modules need to surface exception-based flags, not just generate end-of-year reports.
    • The revised de minimis rate changes how budget and indirect-cost calculations should populate proposal templates by default.
    • Effort reporting remains a perennial audit focus area under 2 CFR 200.430, and reviewers increasingly expect systems to certify effort against documented time-and-attendance data rather than after-the-fact estimates.

    Outside the US, UK and EU institutions face parallel pressure: UKRI’s move to its unified Funding Service and Horizon Europe’s stricter foreign-funding disclosure rules both push institutions toward systems that can evidence compliance on demand rather than reconstruct it retrospectively. An ERA platform selected in 2026 needs to be configurable against a moving regulatory baseline, not just the rules in force at implementation.

    A buyer’s framework: what to evaluate before selecting a platform

    Selection committees — typically a chief research officer, sponsored-programs staff, IT, and finance — should evaluate candidate platforms against criteria that go beyond a feature checklist:

    • Configuration versus customisation. Configurable, vendor-supported systems require less internal IT investment but less bespoke fit; heavily customised systems demand ongoing internal development capacity and are harder to keep current when a vendor ships updates.
    • Audit and compliance readiness. Ask vendors to demonstrate exception-based compliance flagging (COI, effort variance, subrecipient risk), not only static reports generated after the fact.
    • Interoperability. Confirm documented integrations with sponsor systems (Grants.gov, eRA Commons, UKRI Funding Service), identity systems (ORCID), and the institution’s own ERP/HR platforms.
    • Total cost of ownership. Homegrown and heavily customised builds frequently carry hidden maintenance costs beyond the initial development estimate; request a multi-year cost breakdown, not just licence price.
    • Vendor stability and support. Research administration software has consolidated significantly through vendor mergers and rebrands over the past decade; ask about implementation timelines, support SLAs, and product roadmap commitments in writing.

    What is electronic research administration?

    Electronic research administration is the use of digital systems to manage the sponsored-research lifecycle — proposal development, award setup, compliance tracking, and financial reporting — in place of paper-based processes. It replaces manual routing and signatures with system-based workflows that connect directly to sponsor submission portals such as Grants.gov.

    What does a research administrator do?

    A research administrator develops and oversees research proposals, awards, and financial transactions on behalf of an institution and its principal investigators. Core duties include budget development, compliance monitoring, and maintaining records that satisfy both institutional policy and sponsor requirements — increasingly through an electronic research administration system rather than paper files.

    What is the difference between eRA and NIH?

    eRA (the NIH’s Electronic Research Administration platform, including eRA Commons and ASSIST) is the online interface through which grant applicants, grantees, and NIH staff exchange administrative information about federal grants. NIH is the funding agency itself; eRA is one agency’s specific electronic system, not a synonym for the broader ERA software category institutions purchase.

    What are ERA systems?

    ERA systems are institutional software platforms — commercial or, less commonly, homegrown — that manage sponsored-research workflows end-to-end. They typically combine pre-award, post-award, compliance, and effort-reporting modules, and connect to external sponsor and identity systems such as Grants.gov and ORCID.

    Implications for institutions, funders, and publishers

    For institutions, the practical implication of tighter Uniform Guidance thresholds and rising audit scrutiny is that ERA selection is no longer purely an IT or finance-office decision — it is a compliance-risk decision that belongs on the chief research officer’s desk. Systems chosen primarily on price or user-interface polish, without a documented compliance-flagging capability, risk becoming an audit liability rather than an efficiency gain.

    For funders and publishers, the growth of ERA adoption strengthens the case for standardised metadata at the point of proposal and award creation — identifiers such as ORCID iDs and the Research Organization Registry (ROR) reduce downstream reconciliation work when award data eventually needs to map to publications, contributor roles, and institutional affiliations. Professional bodies including NCURA, ARMA, EARMA, and INORMS have each published guidance and community benchmarking on ERA adoption, reflecting how central this tooling decision has become to the research-administration profession globally.

    Outlook: ERA selection as a 2026 strategic priority

    The direction of travel is clear: sponsors are tightening disclosure and audit expectations at the same time as institutions face budget pressure to do more with fewer administrative staff. An ERA platform that cannot demonstrate compliance readiness against a moving regulatory baseline — and that cannot interoperate cleanly with sponsor and identity systems — will struggle to justify its cost within two to three budget cycles. Institutions evaluating platforms in 2026 should treat the selection process as an ongoing compliance investment rather than a one-off procurement exercise, revisiting vendor roadmaps annually against the next round of Uniform Guidance and sponsor-portal changes.

    Institutions building out their research administration function more broadly can also consult CASRAI’s research administration resources and the CASRAI Dictionary for grounded definitions of the compliance and reporting terms that ERA systems are built to track.

  • Pre-Award vs Post-Award Research Administration: Where Compliance Risk Concentrates

    Every sponsored-research office eventually asks the same operational question: where, exactly, does an audit finding get born? Pre-award research administration and post-award research administration are often treated as a single continuous job description, but they carry very different compliance profiles. Under the Office of Management and Budget’s Uniform Guidance (2 CFR 200), the two phases are governed by overlapping but distinct subparts, and institutions that blur the boundary tend to discover the gap only when a federal auditor draws attention to it.

    This guide separates the two functions, maps the specific 2 CFR 200 provisions most associated with audit findings, and flags what changed when OMB’s most recent revision took effect.

    Pre-award vs post-award: where the line falls

    Pre-award activity covers everything that happens before an institution accepts a sponsor’s terms. It is proposal-facing rather than transaction-facing, and its compliance burden is concentrated in representations made to the sponsor rather than in ongoing financial stewardship.

    • Identifying and matching funding opportunities to investigator plans
    • Budget justification and application of institutional/federal indirect cost rates
    • Compliance screening — conflict-of-interest disclosure, human/animal subject clearances, export control review
    • Internal routing, sign-off, and proposal submission
    • Award negotiation and formal acceptance of terms

    Post-award administration begins the moment an award account is set up and runs through closeout. This is where the volume and complexity of federal financial transactions live, which is also why post-award research administration generates a disproportionate share of Single Audit findings.

    • Award and general ledger account setup
    • Ongoing financial compliance monitoring — allowability, allocability, and reasonableness of costs
    • Effort certification and personnel cost justification
    • Subrecipient monitoring on any pass-through funds
    • Interim and final financial and progress reporting
    • Project closeout, equipment disposition, and unused-funds reconciliation

    Bodies such as research administration professional associations — ARMA in the UK, NCURA in the US, and EARMA across Europe — increasingly teach pre-award and post-award as a connected lifecycle rather than two silos, precisely because handoff gaps between the two are where compliance exposure accumulates.

    The compliance risk heatmap

    Not every task carries equal audit exposure. Mapping common research-administration tasks against the Uniform Guidance provisions auditors cite most often produces a practical heatmap for prioritising internal review effort.

    Phase Task Governing 2 CFR 200 provision Typical audit-finding risk
    Pre-award Budget development / indirect cost application Subpart E — Cost Principles Low–Medium
    Pre-award Conflict-of-interest and subject-protection clearance §200.112, institutional policy Medium
    Post-award Procurement of goods/services on federal funds §§200.317–200.327 High
    Post-award Subrecipient monitoring §§200.331–200.333 High
    Post-award Internal controls over federal expenditure §200.303 High
    Post-award Effort certification / salary charging Subpart E, Compensation Medium–High
    Post-award Financial and progress reporting timeliness §§200.328–200.329 Medium
    Post-award Closeout and equipment disposition §§200.344–200.345 Low–Medium

    The pattern is consistent across institutional Single Audits: pre-award weaknesses tend to surface as proposal-accuracy or disclosure gaps, while post-award weaknesses — inadequate subrecipient monitoring, undocumented internal controls, and procurement shortcuts — account for the majority of significant deficiencies reported to cognizant agencies. That imbalance is exactly why post-award teams typically carry larger headcount relative to transaction volume, even though pre-award work is more visible to investigators.

    The Uniform Guidance is changing

    OMB’s most recent revision to 2 CFR 200 took effect for federal awards issued on or after 1 October 2024, and it directly reshapes several of the risk areas above. Institutions still operating on pre-2024 assumptions are the ones most likely to generate findings against the revised text.

    • The Single Audit expenditure threshold rose from $750,000 to $1,000,000, removing some smaller institutions from mandatory audit scope but concentrating audit attention on larger, more complex programmes.
    • The de minimis indirect cost rate available to entities without a negotiated rate agreement rose from 10% to 15% of modified total direct costs.
    • The equipment and capital-asset capitalisation threshold rose from $5,000 to $10,000, changing what must be separately tracked and reported at closeout.

    Further clarifying guidance and agency-specific implementation notes continue to be issued as sponsors align their own policy manuals with the revised text, which means the compliance target for both pre-award and post-award teams is still moving. Research offices that update proposal templates and account-setup checklists only once, at the point of the original 2024 change, risk drifting out of alignment as agencies finish rolling out their own interpretations.

    Common questions on pre-award and post-award risk

    What is pre-award research administration?

    Pre-award research administration is the set of institutional functions that support a project from funding search through award acceptance — matching opportunities, building compliant budgets, screening for conflicts of interest, and routing proposals for internal sign-off before submission to a sponsor.

    What is the pre-award process?

    The pre-award process runs from identifying a funding opportunity through formal award acceptance. It typically includes proposal development, budget justification, internal institutional review, submission to the sponsor, and negotiation of final award terms before the account is established.

    What is a pre-award?

    A pre-award refers to the preparatory documentation and approvals — intent-to-apply forms, budget justifications, compliance certifications — completed before a sponsor formally commits funding. These records establish the institutional and regulatory basis the eventual award will be managed against.

    What skills do you need to be a research administrator?

    Research administrators need working knowledge of sponsor and federal regulations (including the Uniform Guidance), budget and financial analysis skills, attention to procedural detail, and the ability to translate technical compliance requirements into plain guidance for investigators.

    Implications for research offices

    The practical takeaway is not that pre-award compliance is unimportant — a flawed conflict-of-interest disclosure or an unallowable cost baked into a budget justification can still trigger scrutiny. The takeaway is that sponsored research administration teams should weight their internal review and training investment toward where findings actually concentrate: procurement, subrecipient monitoring, and documented internal controls in the post-award phase.

    Institutions that separate “grant administration” from “grant management” organisationally sometimes reproduce the same handoff risk internally — pre-award teams hand a fully compliant proposal to post-award teams who inherit responsibility for terms they did not negotiate. A shared risk register, reviewed jointly across both functions at account setup, closes that gap more reliably than siloed checklists. Institutional glossaries and shared reference material — see CASRAI’s research administration glossary — help standardise the terminology both teams use when escalating a compliance question.

    Looking ahead

    As OMB continues to refine implementation guidance around the 2024 Uniform Guidance revision, the boundary between pre-award and post-award compliance work will keep shifting rather than settling. Research offices that treat the two phases as a connected risk chain — rather than a handoff between departments — will be better positioned to absorb the next round of regulatory change without a corresponding spike in audit findings.

  • Grant Administration vs Grant Management: A Research-Office Guide

    A sponsored programmes office in a university, hospital trust, or research institute rarely has the luxury of clean job titles. Staff are asked to do “grants work” without anyone specifying which of two genuinely different functions they mean. Grant administration vs grant management is not a semantic quibble — it maps onto two distinct phases of the funding lifecycle, with different skills, different risk profiles, and different reporting lines. Getting the distinction right affects how research offices staff themselves, how they onboard new starters, and how they explain their own structure to auditors and funders.

    This explainer sets out the practical difference, shows where each function sits against the pre-award/post-award lifecycle, and answers the questions research administrators most commonly search for when trying to draw the line.

    What is grant administration?

    Grant administration is the compliance-facing, largely post-award function. It exists to make sure that once money has been awarded, it is spent, tracked, and reported exactly as the funder’s terms and conditions require. Grant administrators are the people who keep an award audit-ready from the moment funds land to the moment the final financial report is submitted.

    Typical grant administration duties include:

    • Setting up the award in the institution’s financial system and reconciling it against the signed agreement
    • Monitoring budget lines, allowable costs, and cost transfers against the approved grant budget
    • Tracking effort reporting, cost-sharing commitments, and indirect cost (overhead) recovery
    • Preparing and submitting financial and progress reports on the funder’s schedule
    • Managing award amendments, no-cost extensions, and close-out procedures

    In US institutions this work is typically anchored to the Uniform Guidance (2 CFR 200) and individual agency terms from bodies such as NIH and NSF. In the UK, the equivalent compliance backbone runs through UKRI’s grant terms and conditions, institutional TRAC (Transparent Approach to Costing) returns, and Research England reporting requirements. The regulatory vocabulary differs by jurisdiction; the underlying function — disciplined, rules-bound post-award stewardship — does not.

    What is grant management?

    Grant management is the broader, strategic function that spans the entire lifecycle: identifying funding opportunities, shaping competitive proposals, and — once an award is won — overseeing whether the funded work is actually achieving its research and institutional objectives. Where administration asks “are we compliant?”, management asks “are we winning the right grants, and are they delivering what we promised?”

    Typical grant management responsibilities include:

    • Scanning funder calls and matching them to institutional and departmental research priorities
    • Supporting principal investigators with proposal development, budget justification, and costing
    • Building and maintaining relationships with programme officers and funder liaison staff
    • Monitoring project performance against milestones, outputs, and outcomes — not just spend
    • Feeding lessons from completed awards back into future bid strategy

    A grant manager’s remit therefore extends well beyond a single award. Many sponsored programmes offices structure this as a “grants management cycle” — pre-award identification and proposal support, award negotiation, post-award delivery oversight, and closeout evaluation that feeds the next cycle.

    Pre-award vs post-award: mapping the responsibilities

    The cleanest way to separate the two functions is against the pre-award/post-award split that most research administration offices already use to structure their teams. Grant management is lifecycle-wide; grant administration is concentrated in — though not exclusively confined to — the post-award phase.

    Dimension Grant administration Grant management
    Primary lifecycle stage Post-award Pre-award through closeout
    Core question Are we compliant with the award terms? Are we funding — and delivering — the right work?
    Typical tasks Budget monitoring, cost transfers, financial reporting, audit readiness Opportunity scanning, proposal development, performance evaluation, funder relationships
    Risk focus Regulatory and financial non-compliance Strategic misalignment, missed opportunities, weak outcomes
    Reference frameworks (illustrative) Uniform Guidance (2 CFR 200), UKRI grant terms, TRAC Institutional research strategy, funder mission fit, ARMA/EARMA/NCURA practice guidance

    In practice, smaller research offices often collapse both functions into a single “research administrator” or “grants officer” role covering the full sponsored research administration remit. Larger institutions tend to separate them, with pre-award research administration and post-award research administration teams sitting either side of the award-negotiation handover point.

    Common questions on grant administration vs grant management

    What is the difference between a grant administrator and a grant manager?

    A grant administrator is primarily responsible for post-award compliance — budget monitoring, financial reporting, and adherence to funder terms. A grant manager oversees the fuller grant lifecycle, including opportunity identification, proposal strategy, and performance outcomes, though in smaller teams one person often holds both responsibilities.

    Is administration higher than management?

    Not in the grants context specifically. Generically, “administration” can refer to policy-setting and “management” to implementation, but within sponsored programmes offices the two are parallel functions — compliance-focused versus strategy-focused — rather than a strict seniority hierarchy. Either role can sit at director level depending on institutional structure.

    What is grant administration?

    Grant administration is the post-award compliance function that ensures grant funds are spent, tracked, and reported according to the funder’s contractual terms. It covers financial oversight, effort reporting, cost-transfer approval, and the preparation of interim and final reports to the awarding body.

    What is the grants management cycle?

    The grants management cycle is the recurring sequence of opportunity identification, proposal development, award negotiation, post-award delivery, monitoring, and closeout evaluation. Lessons from closeout typically feed back into the next round of opportunity identification, making it a continuous rather than linear process.

    Why the distinction matters for research offices

    Blurring grant administration and grant management has real operational costs. Institutions that treat the two as interchangeable often end up with compliance gaps — a research office focused entirely on winning new awards can miss cost-transfer deadlines or effort-reporting certifications, triggering audit findings. Conversely, an office staffed only with compliance-minded administrators can under-invest in the proposal development and funder-relationship work that keeps the award pipeline healthy.

    Professional bodies on both sides of the Atlantic reflect this split in how they organise practice guidance and training. NCURA (US) and EARMA and ARMA (UK/Europe) both maintain competency frameworks that separate pre-award and post-award skill sets, and INORMS’ Research Management and Administration career framework explicitly distinguishes strategic research management from operational research administration. This is not a CASRAI-specific taxonomy — it reflects how the wider research administration profession itself is organised, and institutions building or restructuring a sponsored programmes office should map roles against it rather than inventing local terminology from scratch.

    The distinction also matters for how institutions define career pathways. A research administration career track built purely on compliance risks losing staff who want strategic exposure; a track built purely on management risks producing officers who cannot pass an audit. The strongest sponsored programmes offices deliberately rotate staff across both functions, or pair a compliance-trained administrator with a strategy-trained manager on the same award portfolio.

    Looking ahead: convergence, not confusion

    As grant management systems increasingly automate routine compliance checks — flagging over-budget cost centres or missing certifications automatically — the administrative workload is shifting from manual reporting toward exception handling and judgement calls. That frees grant administrators to take on more of the performance-monitoring work traditionally associated with grant management, and the two functions are likely to converge further at the operational level even as they remain distinct in scope and risk ownership.

    For research offices building or auditing their own structure, the practical takeaway is not to pick one term over the other but to be explicit about which lifecycle stage — and which risk — each role is actually responsible for. That clarity, more than the job title itself, is what keeps sponsored research compliant, competitive, and well governed.

  • Grants Functional Standard: What UK Funders and Institutions Need to Know

    What Is the Grants Functional Standard (GovS 015)?

    The Grants Functional Standard — Government Functional Standard GovS 015: Grants — is the Cabinet Office document that sets mandatory expectations for how UK central government departments and their arm’s-length bodies (ALBs) design, award, monitor and close out grants. First published in December 2016 and periodically updated since, it applies to any organisation administering grants wholly or partly using Exchequer funding, which in practice includes many universities, research charities, learned societies and sector bodies that receive or pass through public grant money.

    The standard operates on a “comply or explain” basis: bodies within scope must either meet the ten Minimum Requirements or record a documented justification for departing from them. It sits alongside the wider suite of UK government functional standards (covering areas such as finance, commercial and project delivery), which exist to give civil servants and delivery partners a consistent, shared language for governance and assurance.

    The Ten Minimum Requirements

    GovS 015 is operationalised through ten numbered Minimum Requirements, each with its own supporting guidance document published by the Government Grants Management Function (GGMF). Together they cover the full grant lifecycle, from senior accountability through to reconciliation and training.

    Minimum Requirement Focus area
    1. Senior Officer Responsible for a Grant Named senior accountability for each grant scheme
    2. Governance, Approvals & Data Capture Sign-off routes and central grant-data recording
    3. Complex Grants Advice Panel (CGAP) Mandatory referral for high-risk or priority schemes
    4. Business Case Development Rationale, options appraisal and value for money
    5. Competition for Funding Fair, open, proportionate award processes
    6. Grant Agreements Terms, conditions and use of the Model Grant Agreement
    7. Risk, Controls and Assurance Fraud risk, security risk and internal controls
    8. Performance and Monitoring In-year tracking of delivery against milestones
    9. Annual Review and Reconciliation Year-end financial and delivery reconciliation
    10. Training Competency requirements for grant-making staff

    Minimum Requirement 7 — Risk, Controls and Assurance — is the section research administrators should watch most closely, because it is the one most recently amended.

    What Changed in the 21 May 2026 Update

    On 21 May 2026, the Cabinet Office published a revised version of Minimum Requirement 7: Risk, Controls and Assurance. Two substantive changes were made:

    • The language governing Fraud Risk Assessments was strengthened, tightening the expectation that grant-making bodies produce and evidence a documented fraud risk assessment as part of the standard’s risk-management requirements.
    • A new paragraph (paragraph 23) was added to provide further guidance on security risk, extending the section’s scope beyond financial and delivery risk to explicitly cover security considerations in grant-funded activity.

    This update did not change the ten-requirement structure of GovS 015 itself; it refined the assurance expectations sitting underneath Minimum Requirement 7. It follows a pattern of incremental, dated revisions the GGMF has made to individual Minimum Requirement documents over recent years — CGAP referral criteria and the Grant Agreements guidance have both been revised on a similar rolling basis. For any body already running a Grants Continuous Improvement Assessment against the standard, the May 2026 wording is the version that self-assessment evidence should now reference.

    Grant Administration, Grant Management and the Centre of Excellence

    GovS 015 sits inside a broader UK government grants ecosystem, and the terminology is often used loosely. It is worth distinguishing the parts precisely, since institutions applying the standard need to know which body owns which function.

    • Grant administration refers to the operational, transactional tasks of running a grant scheme — issuing agreements, processing claims, recording data and reconciling payments.
    • Grant management is the broader discipline: strategic design of a scheme, risk appraisal, performance oversight and continuous improvement, of which administration is one component.
    • The Government Grants Management Function (GGMF) is the cross-government function, hosted by the Cabinet Office, responsible for GovS 015 itself and for coordinating grant-making practice across departments and ALBs.
    • The Grants Centre of Excellence is the operational and advisory capability that supports departments in applying the standard consistently — providing guidance, training and shared services rather than setting the standard itself.

    What is the functional standard for grants?

    It is Government Functional Standard GovS 015, the Cabinet Office document setting mandatory requirements for how UK departments and arm’s-length bodies administer grants funded wholly or partly through the Exchequer. It exists to ensure consistency, regularity and propriety in grant-making and to promote value for money in publicly funded grant schemes.

    What are UK government functional standards?

    Functional standards are Cabinet Office-issued documents that set mandatory (“shall”) and advisory (“should”) expectations for specific government functions — finance, commercial, project delivery and grants among them. They use a shared glossary so departments and their delivery partners work to a common, auditable set of definitions and controls.

    What is the difference between grant administration and grant management?

    Grant administration is the transactional layer — agreements, claims, payments and record-keeping. Grant management is the wider strategic discipline covering scheme design, risk assessment, performance monitoring and continuous improvement, within which administration operates as one supporting activity, not a synonym for the whole function.

    What is the Grants Centre of Excellence?

    It is the cross-government advisory and capability-building resource that helps departments and arm’s-length bodies apply GovS 015 in practice, through guidance, training and shared tools. It supports implementation of the standard; it does not itself author or amend the Minimum Requirements, which remain the responsibility of the Government Grants Management Function.

    Implications for Research-Funded Institutions

    Universities, research charities and sector bodies that receive Exchequer-funded grants — directly from departments or via an ALB — sit within scope of GovS 015 even when they are not themselves a government department. The May 2026 changes to Minimum Requirement 7 have practical consequences for research administration teams:

    • Grant applications and renewals may face closer scrutiny of documented fraud risk assessments, particularly for schemes flagged as complex or high-value.
    • Institutions handling sensitive research areas — dual-use technology, critical infrastructure, or international collaboration — should expect funders to reference the new security-risk paragraph when setting due-diligence conditions.
    • Research offices that already map their processes against Minimum Requirements 1–10 for continuous-improvement self-assessment should update their MR7 evidence base to the 21 May 2026 wording.
    • Grant agreement templates and internal risk registers referencing MR7 should be checked against the current guidance rather than an earlier cached version, since the GGMF revises individual Minimum Requirement documents on a rolling basis rather than reissuing the whole standard.

    None of this changes the fundamentals of good research administration practice — due diligence, documented risk assessment and clear accountability were already core expectations. What changes is the explicitness with which fraud and security risk must now be evidenced under MR7.

    Looking Ahead

    GovS 015 has been revised incrementally rather than replaced outright since 2016, and the pattern is likely to continue: individual Minimum Requirement documents updated as risks evolve, rather than a full standard rewrite. Institutions that treat the standard as a living compliance baseline — checking dated guidance documents against their internal risk frameworks at each award cycle — will be better placed than those that rely on a static PDF saved years ago. For research administrators, the practical takeaway from the 21 May 2026 update is straightforward: fraud risk assessment and security-risk screening are no longer implicit good practice under GovS 015 — they are explicit, documented expectations under Minimum Requirement 7.

  • The De Minimis Indirect Cost Rate: When the 15% Safe Harbor Works for Your Institution

    Every proposal budget has to answer one question: how will the institution recover the overhead it spends supporting a federally funded project? For organisations without the staff or history to negotiate a formal rate, the de minimis indirect cost rate is a standing, no-negotiation alternative built directly into the federal Uniform Guidance. It lets an eligible non-federal entity recover indirect costs on a federal award without submitting a full indirect cost rate proposal — but the rate itself, and the rules around electing it, changed materially in 2024, and many summaries in circulation still cite the old figure.

    What is the de minimis indirect cost rate?

    The de minimis rate is a fixed indirect cost recovery option set out in 2 CFR 200.414(f), the cost-principles section of the OMB Uniform Guidance that governs federal grants and cooperative agreements. It exists so that organisations without a current Negotiated Indirect Cost Rate Agreement (NICRA) are not forced to either forgo indirect cost recovery entirely or undertake a formal rate negotiation with a cognizant federal agency.

    Effective 1 October 2024, OMB revised 200.414(f) and raised the rate from a flat 10% to up to 15% of Modified Total Direct Costs (MTDC). This is the single most important recent change to the rule, and it altered its character: the rate is no longer automatically 10%, nor is it automatically 15%. The “up to” language means an electing organisation should be able to justify the rate it applies, particularly if its actual indirect costs run below 15% of MTDC.

    MTDC is a defined cost base, not simply total direct costs. It includes direct salaries and wages, applicable fringe benefits, materials, supplies, services, travel, and the first $50,000 of each subaward. It excludes equipment, capital expenditures, patient care charges, rental costs, tuition remission, scholarships and fellowships, participant support costs, and the portion of any subaward beyond $50,000.

    Who qualifies to elect it

    Eligibility is narrower than the phrase “de minimis” suggests. Under 2 CFR 200.414(f):

    • The entity must be a non-federal recipient or subrecipient — a state or local government, Indian tribe, institution of higher education, or non-profit organisation.
    • The entity must not currently hold a NICRA. An organisation that has never negotiated a rate, or whose prior agreement has expired without renewal, is generally the target user.
    • For-profit entities are not eligible. Cost principles for commercial organisations sit under FAR Subpart 31.2, not 2 CFR 200 Subpart E, so the de minimis election in 200.414(f) simply does not apply to them.
    • Once elected, the rate must be applied consistently across all of the entity’s federal awards until it either negotiates a NICRA or its circumstances otherwise change; it cannot be selectively applied to some awards and not others.

    In practice, the de minimis rate is used most often by first-time federal grantees, small non-profits, and institutions with genuinely modest indirect costs — organisations for whom the administrative cost of preparing a full rate proposal would exceed the financial benefit of a more precisely calculated rate.

    De minimis rate vs a negotiated rate (NICRA)

    Choosing between the de minimis rate and a negotiated agreement is a genuine trade-off, not a formality. A NICRA requires submitting a detailed indirect cost rate proposal to a cognizant federal agency, supported by an audited or auditable cost allocation base, and typically takes months to negotiate. The de minimis rate requires no proposal and no negotiation at all.

    Factor De minimis rate (up to 15% of MTDC) Negotiated rate (NICRA)
    Documentation to elect None required; self-certified election Formal indirect cost rate proposal with supporting cost data
    Time to establish Immediate Typically several months of negotiation
    Rate accuracy Fixed ceiling, may under-recover true indirect costs Reflects the institution’s actual cost structure
    Best suited to First-time or small-scale federal recipients with modest overhead Institutions with sustained federal funding and indirect costs above 15% of MTDC
    Flexibility once set Must be applied consistently to all federal awards Rate is fixed for the negotiated period, then renegotiated

    For institutions whose actual indirect costs genuinely sit at or below 15% of MTDC, the de minimis rate is a reasonable long-term choice — it avoids the recurring administrative burden of rate renegotiation. For research-intensive institutions with substantial facilities and administrative costs, a negotiated rate almost always recovers more, because negotiated F&A rates at research universities commonly run well above 15% of MTDC.

    Documentation and compliance requirements

    The de minimis election requires no formal proposal, but it is not a documentation-free zone. Institutions should still:

    • Retain a clear internal decision record showing the rate elected and the justification, especially where the rate applied is below the full 15% ceiling.
    • Apply the cost base correctly — errors in MTDC calculation, such as including full subaward amounts above $50,000 or capital equipment, are among the most common audit findings.
    • Maintain consistency: costs charged as indirect under the de minimis rate cannot also be charged directly to the same award, and vice versa.
    • Track award-level restrictions, since some individual federal programmes cap or exclude indirect cost recovery regardless of an entity’s general de minimis election.

    Common questions

    What is a de minimis indirect cost rate?

    The de minimis indirect cost rate is a standard rate that eligible non-federal entities without a current negotiated agreement may apply to recover indirect costs on federal awards. It is capped at 15% of Modified Total Direct Costs and requires no formal rate proposal to use.

    When did the de minimis indirect cost rate change?

    OMB revised 2 CFR 200.414(f) effective 1 October 2024, raising the de minimis rate from a flat 10% to up to 15% of MTDC for new federal awards. Awards issued before that date may still reference the earlier 10% figure.

    What is the current de minimis rate?

    As of the 2024 Uniform Guidance revision, the current ceiling is 15% of MTDC. Because the regulation uses “up to” language, an organisation should be able to support the specific rate it elects rather than assume 15% applies automatically.

    How do you use the de minimis rate?

    An eligible entity elects the rate by applying it directly to its Modified Total Direct Costs base on a federal award, with no application or negotiation required. Once elected, the entity must use it consistently across all federal awards until it negotiates a formal rate.

    Implications for research administrators

    The de minimis rate should not be confused with a separate and unresolved policy debate: proposed caps on negotiated indirect cost rates. In 2025, NIH and later other federal science agencies proposed capping F&A reimbursement at 15% even for institutions that already hold a NICRA well above that figure — a distinct move from the de minimis election, which has always applied only to entities without a negotiated rate. Those cap proposals drew legal challenges from higher-education associations and remain contested in federal court as of this writing. Research administrators should track the two issues separately: one is a stable, settled recovery option for smaller or first-time recipients; the other is a live policy dispute over whether research-intensive institutions’ existing negotiated rates can be unilaterally reduced.

    For institutions building or reviewing their research administration infrastructure, the practical takeaway is to treat the de minimis election as a genuine strategic choice rather than a default. Model the actual indirect cost recovery under both the de minimis ceiling and a hypothetical negotiated rate before committing, since the consistency requirement makes switching mid-portfolio administratively costly. As federal cost-recovery policy continues to shift, institutions that document their rate rationale clearly will be best placed to adapt.

  • Indirect Cost Rate Negotiation: A Step-by-Step NICRA Guide

    Every research administrator eventually confronts the same negotiation: how to persuade a federal cognizant agency that the true overhead cost of running a laboratory, a sponsored programme, or an entire research enterprise deserves fair reimbursement. The indirect cost rate that comes out of that negotiation — formalised in a Negotiated Indirect Cost Rate Agreement, or NICRA — determines how much of an institution’s administrative and facilities burden is actually recovered on every federal award it holds. This guide walks through the mechanics: how to choose a rate type, build a defensible proposal, and manage the negotiation itself.

    This is a process guide, not a policy explainer. For background on the funding-cap debate around indirect cost recovery under the OMB Uniform Guidance, see CASRAI’s separate coverage of that policy story. Here, the focus is what a research office actually has to do — and in what order — to walk out of a negotiation with a usable rate agreement.

    What Is a NICRA, and Who Needs One?

    A NICRA is a formal, signed agreement between an organisation and its cognizant federal agency — generally whichever agency provides the largest share of that organisation’s direct federal funding — that fixes the percentage rate used to recover indirect costs on federal awards. For most US colleges and universities, cognizance sits with either the Department of Health and Human Services’ Division of Cost Allocation or the Department of the Navy’s Office of Naval Research; nonprofits and other award recipients are typically assigned a cognizant agency by whichever federal funder they draw the most direct money from.

    Once negotiated, a NICRA is binding across all federal agencies, not just the one that negotiated it — a single rate agreement travels with the organisation to every subsequent federal award. Organisations that have never held a NICRA, or whose rate has lapsed, have a fallback: 2 CFR 200.414(f) permits use of a de minimis rate of up to 15% of modified total direct costs (MTDC) without negotiation, though that rate must then be applied consistently across every federal award until a negotiated rate is obtained.

    Preparing the Indirect Cost Rate Proposal

    Before submitting anything, the research office has two decisions to make: which rate type to request, and what documentation the proposal will need to withstand review.

    Rate type Definition Adjustable later?
    Provisional Temporary rate used for interim billing pending a final rate for the same period Yes — reconciled against actual costs
    Final Rate set once actual costs for a completed fiscal year are known No
    Predetermined Fixed rate set in advance for a future period, based on a prior representative period’s actual costs No, for that period
    Fixed with carry-forward Predetermined rate with a built-in adjustment for the gap between estimated and actual costs Adjusted in the following period

    Organisations that have never negotiated a rate should generally submit their first proposal within three months of receiving a federal award; organisations with an existing NICRA must submit an updated proposal within six months of the close of each fiscal year covered by that agreement. Missing this window can force an organisation back onto the de minimis rate until a new proposal is accepted.

    A complete indirect cost rate proposal package typically includes:

    • A cover letter stating the fiscal period, rate type requested, and allocation base
    • An organisational chart and description of each unit’s functions
    • Audited financial statements or a Single Audit Report for the fiscal year under review
    • A cost policy statement setting out which costs are charged directly versus indirectly
    • The indirect cost rate calculation itself — indirect cost pool divided by the chosen direct cost base — reconciled line-by-line to the financial statements
    • A schedule of salary and wage allocation between direct and indirect functions
    • A statement of employee fringe benefits
    • A complete listing of federal grants and contracts active during the fiscal year
    • A signed Certificate of Indirect Costs and lobbying certification

    Every unallowable cost — entertainment, alcohol, lobbying, fundraising — must be scrubbed from the indirect cost pool before submission; a proposal that includes unallowable costs, even inadvertently, is the single most common reason negotiations stall.

    Negotiating With Your Cognizant Agency

    Once a proposal is accepted for review, a negotiator or auditor at the cognizant agency is assigned to check compliance with the applicable federal cost principles — 2 CFR Part 200 (the Uniform Guidance) for nonprofits, colleges, and local governments, or FAR Part 31 for commercial organisations under agencies such as the Defense Contract Audit Agency. Expect an iterative back-and-forth: requests for supporting documentation, clarification of allocation methodologies, and questions about specific cost pool line items.

    If agreement is reached, the cognizant agency issues the NICRA for signature. If it is not — because of disputed pool expenses or a disagreement over the allocation base — the agency may instead issue a unilateral rate agreement. An organisation that disagrees with a unilateral rate typically has a defined window (30 days, under NSF’s published appeal procedures) to invoke formal appeal procedures before the unilateral rate takes effect by default.

    What is the difference between direct and indirect costs?

    Direct costs are expenses specifically identifiable with a single project — a piece of equipment, a research assistant’s salary. Indirect costs, sometimes called facilities and administrative (F&A) costs, are shared expenses — utilities, general administration, facilities maintenance — that benefit multiple projects and cannot be assigned to just one.

    How do you calculate an indirect cost rate?

    An indirect cost rate is calculated by dividing the total indirect cost pool by a chosen direct cost base, typically modified total direct costs (MTDC). The resulting percentage is applied to that base on each award to determine how much indirect cost recovery the project generates.

    What percentage should indirect costs be?

    There is no single “correct” indirect cost rate — negotiated rates vary widely by institution type, facilities intensity, and cost base. Organisations without a negotiated rate may instead use the de minimis rate of up to 15% of modified total direct costs under 2 CFR 200.414(f).

    What is an example of an indirect cost?

    Common examples include administrative salaries, building depreciation, utilities, general liability insurance, and shared IT infrastructure — costs that support the whole organisation rather than any single sponsored project.

    Implications for Research Offices and What Comes Next

    Negotiating a NICRA is resource-intensive: it typically demands sustained input from finance, sponsored programmes, and facilities staff over several months, and the resulting rate directly shapes how much overhead recovery an institution can budget against every subsequent federal award. Institutions weighing whether negotiation is worth the administrative overhead should treat the de minimis 15% MTDC rate as a genuine fallback for smaller or first-time federal recipients, not a permanent compromise — most organisations with significant sustained federal funding recover meaningfully more through a negotiated rate over time.

    Because a signed NICRA binds every federal agency, not just the one that negotiated it, getting the proposal right the first time avoids repeat renegotiation cycles. As indirect cost recovery policy continues to attract political scrutiny at the federal level, research offices that maintain clean, well-documented cost pools and submit proposals on schedule will be best placed to defend their negotiated rates regardless of how the broader policy debate resolves. Robust research administration practice — accurate cost allocation, disciplined recordkeeping, and early engagement with the cognizant agency — remains the most reliable lever an institution controls in this process.

  • Writing a Data Management Plan That Satisfies NIH, NSF, and Horizon Europe

    Research administrators managing multi-funder portfolios face a recurring headache every grant cycle: no two major funders ask for a data management plan in the same way. A single investigator with an NIH R01, an NSF collaborative award, and a Horizon Europe consortium grant may need three structurally different documents that all attempt to answer the same underlying question — how will research data be generated, described, preserved, and shared? Building a reusable data management plan template that maps cleanly onto each funder’s requirements is now one of the most practical efficiency gains available to a research office.

    The stakes have risen. NIH’s 2023 Data Management and Sharing Policy is now actively enforced through award terms and conditions, UKRI’s open access policy has tightened expectations around data underlying publications, and Horizon Europe continues to treat the data management plan as a living deliverable rather than a one-off proposal attachment. Administrators who still draft a fresh plan from scratch for every submission are absorbing avoidable cost. A well-designed crosswalk — and a template built from it — turns a compliance burden into a repeatable process.

    The Funder Crosswalk: NIH, NSF, and Horizon Europe Data Management Plan Requirements Compared

    The three funders diverge on format, timing, and philosophy, even though all three now anchor their expectations in FAIR (Findable, Accessible, Interoperable, Reusable) data principles in substance if not always in name.

    • NIH: The Data Management and Sharing Plan is submitted as a distinct attachment at the time of proposal, is not subject to the page-limit rules that apply to the research strategy, and is expected to address six elements — data type, related tools and software, standards applied, oversight of data sharing, and preservation and access timelines, including where data will be deposited. NIH review does not score the plan competitively but the awarded terms make compliance a condition of funding, and lack of an approved plan can hold up an award.
    • NSF: The data management plan is a mandatory two-page supplementary document across all directorates, required since NSF’s foundational 2011 data sharing policy. NSF is comparatively brief on prescribed sections but expects coverage of the types of data produced, standards for metadata, provisions for access and sharing, and policies for reuse and redistribution. Reviewers do weigh the plan as part of the intellectual merit and broader impacts criteria, which makes NSF’s version more consequential to scoring than NIH’s.
    • Horizon Europe: The DMP is not typically required at proposal stage for most calls; instead it is a formal deliverable due within the first six months of a funded project and is explicitly framed as a “living document” to be updated at least once more during the project lifecycle, often at mid-term and final reporting. Horizon Europe’s template, aligned with its open science policy, requires explicit narrative on FAIR compliance for each dataset, plus details on cost, responsibilities, and security, including whether data will be open by default or requires a documented exception.

    The practical consequence for administrators is that the same investigator’s data description work has to be repackaged three times: NIH wants it compact and attached at submission, NSF wants it capped at two pages and reviewer-facing, and Horizon Europe wants it detailed, iterative, and post-award. A shared template only works if it separates the stable content — data types, standards, repositories, roles — from the funder-specific packaging around it.

    Where UKRI and Clinical Trial Plans Diverge Further

    Multi-funder portfolios rarely stop at the “big three.” Two further categories complicate the picture for UK-facing and clinical research offices.

    A UKRI data management plan follows UKRI’s Common Principles on Data Policy, but implementation is devolved to the individual research councils (MRC, BBSRC, ESRC, and others), each of which has its own template and level of prescriptiveness. This is a different model from Horizon Europe’s single harmonised template, and it means a UKRI-funded co-investigator on a Horizon Europe project may technically owe two structurally distinct plans for the same dataset. UKRI’s broader push on open access — extended in recent policy updates to cover monographs and underlying data alongside journal articles — has raised the profile of the DMP as a compliance artefact rather than an administrative afterthought.

    A clinical data management plan is a different instrument entirely, and administrators should not conflate the two. Where a funder DMP addresses data stewardship at the study or grant level, a clinical data management plan operationalises data collection, validation, cleaning, and quality control for a specific clinical trial, typically governed by Good Clinical Practice (GCP) principles and referenced in trial protocols. ICMJE’s data-sharing statement requirement for clinical trial registration adds a further, related but non-identical obligation: a public statement, at registration, of whether and how individual patient data will be shared after publication. A portfolio that includes clinical trials therefore needs both a funder-facing DMP and a trial-level clinical data management plan, cross-referenced but not merged.

    Building a Template Structure That Works Across Portfolios

    A functional cross-funder template separates content into modular blocks that can be recombined per submission rather than rewritten. A workable structure includes:

    • Data inventory: types, formats, and estimated volumes of data to be generated or reused, written once and reused across all funder versions.
    • Standards and metadata: discipline-specific metadata schemas and file formats, referencing recognised community standards where they exist.
    • Storage and security during the project: active storage, backup, and access-control arrangements, particularly relevant to Horizon Europe’s security section and to clinical trial data governance.
    • Preservation and repository: the named repository (disciplinary, institutional, or generalist, such as those indexed by DataCite) and expected retention period.
    • Access and reuse conditions: licensing terms, embargo periods, and any restrictions arising from participant consent, commercial sensitivity, or export control.
    • Roles and responsibilities: named individuals accountable for each stage, which Horizon Europe expects explicitly and NIH and NSF increasingly expect implicitly through institutional data stewardship policies.

    From this modular base, administrators can generate NIH’s compact attachment, NSF’s two-page version, and Horizon Europe’s fuller living document by adjusting emphasis and length rather than starting over. Tools such as DMPonline (maintained by the Digital Curation Centre) and DMPTool already offer funder-specific templates built on broadly this logic, and reviewing existing data management plan examples published through these platforms is a faster route to a working draft than starting from a blank page. The discipline is in maintaining the underlying data inventory as the single source of truth and treating each funder’s version as an export, not an independent document.

    What This Means for Research Administrators

    For research offices supporting investigators across NIH, NSF, Horizon Europe, and UKRI portfolios simultaneously, the crosswalk approach changes three things in practice. First, pre-award staff can build a standing “data profile” per investigator or dataset at the proposal-development stage, rather than waiting for each funder’s specific form to trigger the work. Second, post-award compliance monitoring becomes more tractable: Horizon Europe’s requirement for plan updates at mid-term and final reporting, and NIH’s enforcement of the terms attached at award, both depend on someone tracking which version is current and when the next revision is due. Third, offices supporting clinical research need to keep the clinical data management plan and the funder DMP as separate but cross-referenced documents, since conflating them risks under-specifying either the trial-level quality controls or the funder-level FAIR compliance narrative.

    The administrative overhead of multi-funder compliance is not going away — if anything, the direction of travel among NIH, NSF, UKRI, and Horizon Europe is toward more explicit, more frequently updated, and more publicly scrutinised data plans. Institutions that invest now in a modular, crosswalk-based template will spend less time reconciling funder idiosyncrasies later, and will be better positioned as additional funders and national mandates converge, however unevenly, on the same underlying FAIR data commitments.

  • FAIR Data Principles in 2026: A Practical Guide for Research Administrators

    The FAIR data principles — Findable, Accessible, Interoperable, Reusable — turn ten in 2026. Since Mark Wilkinson and colleagues published the framework in Scientific Data in 2016, FAIR has moved from an aspirational statement of good practice to a hard requirement embedded in funder mandates, journal policies, and institutional research data management infrastructure. UKRI’s open access policy now expects data underpinning publications to be made available in line with FAIR, the US NIH data sharing policy is actively enforced for funded projects, and Horizon Europe applicants must demonstrate FAIR-compliant data management as a condition of award.

    Yet a decade in, compliance remains uneven. Many institutions still treat FAIR as a checkbox on a data management plan template rather than a set of concrete technical and governance obligations. As the ten-year anniversary approaches and funders sharpen enforcement, research administrators need a working map from principle to practice — one that goes beyond restating the acronym and instead specifies what each letter actually requires of repositories, metadata schemas, and institutional policy.

    This article revisits the original FAIR framework as stewarded by FORCE11 and the GO FAIR initiative, and translates each element into actions that research offices, data stewards, and library services can implement now, ahead of the next REF cycle and continued tightening of funder mandates.

    What the FAIR Data Principles Actually Require

    Wilkinson et al. (2016) deliberately wrote FAIR as a set of guiding principles rather than a rigid standard, which has allowed broad adoption but also created room for superficial interpretation. FORCE11, the scholarly communication community that convened the original working group, and GO FAIR, the international support and coordination initiative, both continue to publish implementation guidance. For research administrators, the practical translation looks like this:

    • Findable — Every dataset needs a globally unique, persistent identifier (a DOI minted through DataCite is the de facto standard for research data) and rich, indexed metadata that describes the dataset independently of the data itself. Institutional repositories must expose this metadata to harvesters and search services, not bury it behind a login wall.
    • Accessible — Data (and, critically, its metadata) should be retrievable via a standardised, open communication protocol, with clear authentication and authorisation procedures where restrictions are legitimate. Accessible does not mean “open by default” — it means the access conditions are documented, discoverable, and enforced consistently, even when the data itself is restricted for ethical or commercial reasons.
    • Interoperable — Metadata and data should use formal, shared, broadly applicable vocabularies for knowledge representation, and reference other data and metadata using standard identifiers. This is where controlled vocabularies, ontologies, and cross-referencing to identifiers like ORCID (for contributors), ROR (for institutions), and CrossRef (for related publications) matter most.
    • Reusable — Data must carry a clear, accessible data usage licence, detailed provenance, and be described with enough domain-relevant metadata that a future researcher — human or machine — can understand and reuse it without contacting the original team.

    None of the four elements is optional or substitutable for another. A dataset with a DOI but no licence is findable but not reusable. A dataset described only in free-text notes is accessible but not interoperable. Institutions that treat FAIR as satisfied once a DOI is assigned are addressing roughly one letter out of four.

    Persistent Identifiers, Metadata, and Vocabularies: The Infrastructure Layer

    The technical backbone of FAIR compliance rests on three infrastructure decisions that research administrators are often best placed to influence, even without deep technical expertise.

    First, persistent identifier coverage needs to extend beyond the dataset itself. Contributor identification through ORCID, organisational identification through ROR, and publication linkage through CrossRef and DataCite together create the graph of relationships that makes data genuinely findable and interoperable — not just archived. Institutions that mandate ORCID at the point of data deposit, rather than treating it as optional metadata, see materially better linkage between datasets, grants, and outputs.

    Second, metadata schemas need to move beyond generic Dublin Core toward domain-specific standards where they exist — DataCite Metadata Schema as a baseline, supplemented by discipline-specific vocabularies (such as those maintained by biomedical, environmental, or social science data communities). Rich metadata is the single most under-invested element of FAIR compliance: it is unglamorous, resource-intensive to produce well, and rarely rewarded in the same way a publication or citation is.

    Third, standard vocabularies and licensing need institutional defaults rather than case-by-case decisions. A repository that offers a menu of Creative Commons or equivalent licences at deposit, with a sensible institutional default and clear guidance on when to deviate, removes the single most common point of friction — researchers who simply skip the licensing step because no default is presented.

    From FAIR to CARE: Data Governance Beyond Technical Compliance

    FAIR was designed primarily to solve a technical and infrastructural problem: making data machine-actionable and reusable. It says comparatively little about who benefits from that reuse, who consented to it, and who retains authority over data concerning specific communities. This gap is precisely what the CARE Principles for Indigenous Data Governance — Collective Benefit, Authority to Control, Responsibility, and Ethics — were developed to address, and the two frameworks are increasingly discussed together rather than as alternatives.

    Institutions building research data governance frameworks in 2026 need to treat FAIR and CARE as complementary rather than competing. FAIR asks “can this data be found, accessed, and reused efficiently?” CARE asks “should it be, on what terms, and who decides?” A research data management policy that only addresses FAIR risks technically excellent infrastructure applied to data — particularly Indigenous, community, or otherwise sensitive data — without adequate governance over consent, benefit-sharing, or ongoing authority. Data governance frameworks that reference both FAIR and CARE principles are becoming standard practice at institutions with significant Indigenous studies, community health, or population genomics portfolios, and reviewers increasingly expect to see both addressed in ethics and data management documentation, not just FAIR.

    Building a Research Data Management Plan That Delivers FAIR

    The research data management plan is where FAIR principles are supposed to become operational commitments, yet many plans are still written to satisfy a funder template rather than to genuinely guide the research team. A data management plan that actually delivers FAIR outcomes needs to specify, in concrete and checkable terms:

    • Which repository will host the data, and whether that repository mints persistent identifiers and supports the metadata schema required for the discipline.
    • Who is responsible for metadata creation and quality review before deposit — not left as an afterthought at project close-out.
    • Which licence will apply to the data, decided at the planning stage rather than retrofitted at submission.
    • What vocabularies or ontologies will be used to describe variables, samples, or methods, particularly where cross-study interoperability is a stated goal.
    • How access will be governed for any data subject to ethical, commercial, or CARE-relevant restrictions, including who approves access requests after the project team disbands.

    Institutions preparing for REF 2029 and equivalent national assessment exercises have a particular incentive to get this right now: data management practice is increasingly scrutinised as part of research environment statements, and a portfolio of well-governed, genuinely FAIR datasets is a defensible evidence base in a way that a folder of unlinked spreadsheets is not.

    What This Means for Research Administrators

    For research administrators, EARMA and ARMA members, and institutional research office staff, the ten-year mark for FAIR is a natural prompt to audit rather than assume compliance. Three actions stand out as immediately actionable:

    First, audit repository defaults. Check whether your institutional repository mints DOIs automatically, requires a licence selection at deposit, and exposes metadata to standard harvesting protocols. If any of these is missing, that is a findability or reusability gap regardless of how the policy documents read.

    Second, build ORCID, ROR, and DataCite/CrossRef linkage into deposit workflows as mandatory fields, not optional extras. This is the lowest-cost, highest-leverage intervention available to most institutions and directly strengthens the Findable and Interoperable pillars.

    Third, extend data governance conversations to explicitly include CARE alongside FAIR wherever research involves Indigenous communities, sensitive population data, or community-held knowledge. Reviewers, ethics committees, and increasingly funders are asking for both.

    Looking Ahead

    As FAIR approaches its tenth anniversary, the framework’s core insight — that data value compounds when it is genuinely findable, accessible, interoperable, and reusable — remains sound. What has changed is the level of scrutiny applied to claims of compliance. Funders, publishers, and institutions themselves are moving from asking “do you have a data management plan?” to asking “does your data actually behave like FAIR data?” For research administrators, closing that gap between policy and practice — with the infrastructure, governance, and plan quality to match — is the work of the next decade, not just the anniversary year.

  • No-Cost Extensions, Carryover, and Prior Approval: A Glossary for NIH Grant Administrators

    Search traffic around the NIH Grants Policy Statement no-cost extension provisions spikes every year around the same time: the final months of a project period, when a principal investigator realises the data collection is behind schedule and someone in the sponsored programs office has to explain, again, what counts as an allowable extension and what does not. The terminology in the NIH Grants Policy Statement (GPS) is precise, but it is scattered across dozens of pages, cross-referenced against 45 CFR Part 75 and the Uniform Guidance, and rarely explained in one place for the administrators who have to apply it daily.

    This glossary collects the recurring terms — no-cost extension, carryover, consortium agreements, and program income — that generate the highest volume of long-tail searches from research administrators, and sets out what each one actually means in practice. It follows the same reference format CASRAI uses across its dictionary of research-administration terms: definition first, then the operational detail that determines whether an institution stays compliant.

    The audience is deliberately broad. US-based sponsored programs offices are the primary users of NIH terminology, but institutions that hold both NIH awards and funding from UK bodies increasingly need to translate between systems — a researcher who has learned to apply for grants under UKRI’s rules and then moves onto an NIH-funded consortium project discovers quickly that “extension” and “carryover” do not mean the same thing, or follow the same approval path, on both sides of the Atlantic.

    What the NIH Grants Policy Statement Says About No-Cost Extensions

    A no-cost extension (NCE) lengthens the period of performance on an NIH award without adding funds. The NIH Grants Policy Statement recognises two routes:

    • First, unilateral NCE: the recipient institution may extend the final budget period of a grant once, for up to 12 months, without prior NIH approval, provided the award is not in its final year of a competitive segment for reasons that require agency sign-off (for example, if additional time is needed beyond the single automatic extension, or if the award carries specific terms restricting this authority). This authority sits with the institution’s authorised organisational representative, not the principal investigator alone.
    • Second, NIH prior-approval NCE: a second extension, or any extension where the unilateral authority does not apply, requires a formal request to the assigned NIH awarding component, submitted well before the current project period ends, with a justification tied to the scientific rationale — not simply “more time is needed.”

    The distinction matters because a unilateral NCE that should have gone through prior approval is a compliance finding waiting to happen. Institutions that log every NCE — automatic and approved — in a central tracking system tend to catch these errors before an NIH grants management specialist does.

    Carryover: The Companion Concept to No-Cost Extensions

    Carryover is the mechanism that lets unobligated funds from one budget period move into the next. It is distinct from a no-cost extension, though the two are frequently requested together: a project that needs more time to spend down its budget usually also needs the unspent funds to travel with it.

    Under the NIH Grants Policy Statement, carryover authority depends on the type of award:

    • Awards issued under the Streamlined Non-Competing Award Process (SNAP) generally carry automatic carryover authority, meaning unobligated balances may move forward without a separate request.
    • Non-SNAP awards, and awards with specific restrictive terms, require prior NIH approval before carryover funds can be obligated in the next budget period.

    Administrators should treat carryover and NCE requests as related but separate compliance events. A common error is assuming that approval of one automatically covers the other — it does not. Each has its own authority basis in the GPS, and each needs its own documentation trail in the institution’s grants management system.

    Consortium Agreements and Subrecipient Monitoring

    Multi-institutional NIH awards are structured through consortium agreements — legally binding documents between the prime recipient and each participating (subrecipient) institution. The NIH Grants Policy Statement requires that these agreements flow down all applicable federal terms, including the prime award’s specific conditions, and that the prime recipient carry out subrecipient monitoring consistent with the Uniform Guidance (2 CFR 200.332).

    Where searches for “nih grants policy statement” cluster most heavily around consortium terms is usually at renewal or no-cost extension time, because an NCE on the prime award does not automatically extend the subaward — each consortium agreement needs its own amendment, on its own timeline, coordinated by the prime institution’s sponsored programs office. Institutions that manage large multi-site NIH awards (common in clinical trials networks and multi-PI R01s) typically maintain a master tracking sheet cross-referencing prime award dates against every subaward’s period of performance, precisely to avoid a subrecipient continuing work after its own agreement has technically lapsed.

    Program Income: An Often-Overlooked GPS Category

    Program income is gross income earned by the recipient that is directly generated by a supported activity, or earned as a result of the award — for example, fees from clinical services delivered through a research protocol, registration fees at a conference funded by the grant, or proceeds from the sale of research-generated data or materials. The NIH Grants Policy Statement sets out three methods for handling it: deduction (reducing NIH’s contribution), addition (adding it to the project’s committed funds), or cost-sharing/matching. Which method applies is usually specified in the notice of award, and applying the wrong method is a recurring finding in post-award reviews.

    Because program income rules interact with the same budget period concept that governs carryover and no-cost extensions, administrators processing an NCE should verify whether unspent program income also needs to be reported and carried forward under the applicable method.

    What This Means for Research Administrators

    The terms in this glossary are not abstract definitions — each one triggers a distinct approval workflow, a distinct system-of-record entry, and in some cases a distinct federal reporting obligation. The practical implications for institutional research offices are:

    • Track authority levels separately. Unilateral NCE authority, prior-approval NCE, automatic carryover, and prior-approval carryover each rest on different sections of the GPS. Conflating them in institutional policy documents is a common source of audit findings.
    • Coordinate consortium timelines actively. A no-cost extension on the prime award is not self-executing across subawards; each consortium agreement needs its own amendment.
    • Build cross-training between NIH and non-NIH portfolios. Institutions managing both NIH grants and awards from bodies such as UKRI, Horizon Europe, or other funders that researchers may apply for grants through, benefit from a single internal glossary that maps equivalent-but-different terms (for example, NIH’s “no-cost extension” against a UK funder’s “extension request”) so that PIs moving between funding streams are not caught out by assuming identical rules.
    • Document the scientific justification, not just the administrative request. NIH awarding components scrutinise the rationale behind prior-approval NCE and carryover requests; a request that reads as purely administrative is more likely to be questioned or delayed.

    These distinctions also matter for research integrity and reproducibility more broadly. Standards bodies such as NISO and initiatives supported by SPARC and cOAlition S increasingly expect that data management, sharing, and reporting obligations tied to federal awards are tracked with the same rigour as the funding mechanics themselves — an NCE that extends a project’s timeline, for instance, typically extends the data-sharing and reporting deadlines tied to NIH’s data management and sharing policy as well.

    A Reference Point, Not a Substitute for the Statement Itself

    No glossary replaces a careful reading of the current NIH Grants Policy Statement, which is updated periodically and should always be consulted in its original form for the specific fiscal year and award terms in question. What a reference like this can do is give research administrators — particularly those new to federal awards, or those managing a mixed portfolio spanning NIH grants and non-US funders — a shared vocabulary for the conversations that recur every budget cycle: whether an extension is unilateral or requires approval, whether carryover is automatic or restricted, whether a consortium agreement needs its own amendment, and how program income should be handled once it appears on the books.

    As federal reporting requirements continue to tighten and data-sharing obligations extend further into the post-award period, the administrative precision this glossary describes is likely to matter more, not less. Institutions that build internal reference materials mapping these terms — and keep them current against each GPS revision — will spend less time reconciling compliance findings after the fact.