CASRAI Dictionary

Tag: grant administration vs grant management

  • Cooperative Agreement vs Grant: What the Law Actually Requires

    Every research administrator eventually meets an award letter that does not say “grant” at the top. Understanding a cooperative agreement vs grant distinction is not academic housekeeping — it determines who signs off on your data collection plan, how often you report, and whether a federal programme officer can direct the day-to-day conduct of your funded work. The dividing line was set in US law nearly fifty years ago, and it still governs every award letter issued by NSF, NIH, DOE, USDA and dozens of other federal agencies.

    The Federal Grant and Cooperative Agreement Act of 1977 (Public Law 95-224, codified at 31 U.S.C. §§6301–6308) requires every executive agency to classify a funding relationship as one of three legal instruments before it awards money: a procurement contract, a grant agreement, or a cooperative agreement.

    The statute draws the line on two questions, applied in sequence:

    • Is the government acquiring something for its own direct benefit? If yes, the instrument must be a procurement contract under 31 U.S.C. §6303, governed by the Federal Acquisition Regulation (FAR).
    • If the purpose is instead to support or stimulate a public activity, is “substantial involvement” expected between the agency and the recipient? If no, it is a grant agreement (31 U.S.C. §6304). If yes, it is a cooperative agreement (31 U.S.C. §6305).

    Both grants and cooperative agreements are forms of federal financial assistance and sit under the Office of Management and Budget’s Uniform Guidance at 2 CFR Part 200, not the FAR. That single fact explains why grants and cooperative agreements share so much administrative machinery — standard forms, cost principles, audit requirements — while contracts follow an entirely separate acquisition regime.

    Grant vs cooperative agreement vs contract: the three-way test

    The clearest way to see the distinction is side by side. The table below reflects the statutory test as applied consistently across federal science agencies, including the framework published by the US Department of Energy’s Office of Science.

    Feature Grant Cooperative agreement Procurement contract
    Statutory basis 31 U.S.C. §6304 31 U.S.C. §6305 31 U.S.C. §6303
    Purpose Support/stimulate a public activity Support/stimulate a public activity Acquire goods/services for the government
    Federal involvement Oversight and stewardship only “Substantial involvement” expected Direction and control of delivery
    Governing rules 2 CFR Part 200 (Uniform Guidance) 2 CFR Part 200 (Uniform Guidance) Federal Acquisition Regulation
    Who owns the IP Recipient, typically Recipient, typically May transfer to government
    Scope of work Defined by applicant/PI Negotiated jointly Defined by the sponsoring agency

    A cooperative agreement therefore sits between a grant and a contract without being either. It is a financial assistance award — like a grant — but the awarding agency retains an active, defined role in carrying out the funded activity, which is the hallmark of a contract relationship without the acquisition purpose that would make it one.

    Answer-first: common questions on cooperative agreements

    What is a cooperative agreement?

    A cooperative agreement is a legal instrument of federal financial assistance used when an agency expects “substantial involvement” in a project it is funding for a public purpose. Unlike a grant, the agency actively participates — reviewing milestones, coordinating sub-awards, or contributing technical direction — rather than simply monitoring progress from a distance.

    What is the difference between a grant agreement and a contract?

    A grant transfers value to support a public purpose the recipient defines and controls; a contract acquires goods or services for the government’s direct benefit under terms the government specifies. Grants follow Uniform Guidance cost principles; contracts follow FAR-based competition, protest, and deliverable-acceptance rules.

    What is the difference between a grant and a cooperative agreement?

    Both are financial assistance instruments for public-purpose activities, but a cooperative agreement requires anticipated substantial federal involvement — joint design, resource allocation across sites, or active participation in research conduct — while a grant assumes the recipient carries out the work with only routine agency oversight.

    Is a cooperative agreement legally binding?

    Yes. A federal cooperative agreement is a binding award under 31 U.S.C. §6305 with enforceable terms, reporting obligations, and audit exposure. Do not confuse it with a private-sector “cooperation agreement” between two companies — a different, non-statutory instrument that follows ordinary contract law rather than federal assistance regulation.

    Why the distinction matters for research administrators

    The choice of instrument is not cosmetic; it changes real obligations for every principal investigator and sponsored-programmes office.

    • Reporting cadence and content. Cooperative agreements typically carry more frequent, and more detailed, progress reporting than a comparable grant, because the agency needs current information to exercise its involvement rights.
    • Prior-approval requirements. Where a grant might allow a principal investigator to reallocate budget or change key personnel within defined limits without agency sign-off, a cooperative agreement more often requires the agency’s prior approval at defined decision points.
    • Programmatic authority. Under a cooperative agreement, an agency programme officer may participate in study design, site selection, or data-sharing decisions — participation that would be inappropriate, and potentially instrument-converting, under a grant.
    • Audit and subrecipient monitoring. Both instruments sit under Uniform Guidance audit requirements, but the active federal role in a cooperative agreement often means closer scrutiny of how funds move to subrecipients and consortium partners.

    NSF cooperative agreement awards illustrate the pattern well. The National Science Foundation uses cooperative agreements — rather than grants — for its large research infrastructure programmes, including major facilities where NSF staff are directly engaged in oversight of construction, operations, and multi-institution coordination. The same NSF portfolio uses ordinary grants for the vast majority of individual investigator-led research, where the Foundation’s role is genuinely limited to stewardship.

    This is also where the distinction between grant administration vs grant management becomes practically important. Grant administration — the institutional function performed by a sponsored-programmes or research-administration office — covers pre-award compliance review, negotiation of terms, and post-award financial and regulatory oversight, and it must flex significantly for a cooperative agreement’s heavier approval and reporting load. Grant management, by contrast, is the principal investigator’s day-to-day delivery of the funded work. Bodies such as NCURA, EARMA, ARMA and INORMS increasingly treat instrument classification as a first checkpoint in research administration training precisely because misclassifying an award — or failing to staff for a cooperative agreement’s collaborative obligations — creates downstream compliance risk that a standard grant checklist will not catch.

    Institutions building out their research administration compliance frameworks should treat instrument type as a triage question at intake, not an afterthought discovered mid-project when a programme officer asks to review a dataset before publication.

    Looking ahead

    The Federal Grant and Cooperative Agreement Act has not been substantively rewritten since 1977, but its “substantial involvement” test is being tested constantly by newer funding models — public-private consortia, multi-agency infrastructure awards, and international collaborations that blend federal and non-federal sponsors. As funders experiment with more collaborative funding structures, research administrators who can correctly classify an instrument at the proposal stage — and staff accordingly — will be better placed to meet reporting obligations and protect institutional standing than those who treat “grant” as a catch-all label for any federal award. Consulting authoritative terminology resources, including a controlled research administration dictionary, helps ensure proposal teams and compliance offices are using these terms consistently across an institution.

  • 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.

  • 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.