Skip to main content
v2026.11,610 entries · CC-BY 4.0

Core Facility Equipment Sharing Agreements: A Practical Framework

A practical framework for the written agreement behind a shared research instrument: usage tracking, a worked recharge-rate calculation, and priority-access rules when demand from different funding sources collides.

Ask about Core Facility Equipment Sharing Agreements: A Practical Framework

Answers are drawn from this guide and the rest of the CASRAI corpus, with a link to every source.

Answers are AI-generated from CASRAI’s own published pages and can be wrong, so check the linked sources before relying on one; your question is logged without personal data — never sold, never used to train a third-party model — to show us what CASRAI is missing, so please do not type personal or confidential details. How we use this

Written and maintained by CASRAI Editorial Board

Last updated

Most institutions have a policy for what a core facility is and how its billing rates must comply with federal cost principles. Far fewer have a written answer to a narrower, more practical question: what actually goes in the agreement that governs day-to-day access to a specific shared instrument, once it’s up and running? This guide is that document’s table of contents — the usage-tracking mechanics, the rate-calculation arithmetic, and the priority-access rules a core facility (or a smaller, informal equipment-sharing arrangement between a handful of labs) needs to write down before the first scheduling conflict happens, not after.

For the underlying compliance framework — what makes something a core facility, and the federal cost-accounting rules a recharge rate must satisfy — see Core Facility (Research Core): What It Is and How Shared Research Infrastructure Is Organized. This page assumes that background and goes one level down: the practical document and the operational rules that sit underneath it.

Why a Written Agreement, Even Inside One Institution

A verbal understanding between three PIs who chipped in for a shared instrument works fine until one of them needs it during another’s grant deadline, a piece breaks and nobody agreed in advance who pays for the repair, or a fourth lab wants to join later on different terms. A written equipment-sharing agreement exists to answer those questions before they’re live disputes, and to do it in a form that survives PI turnover, a change in core-facility management, or a federal audit asking how usage is billed.

The same need exists whether the arrangement is a fully staffed, centrally administered core facility recovering cost under 2 CFR 200 cost principles, or an informal cost-share between two or three labs that never rises to the level of an institutionally recognized core. The scale differs; the list of things the agreement needs to cover does not change much.

What the Agreement Needs to Cover

A complete equipment-sharing agreement is short on legal boilerplate and specific on operations. At minimum, it should state:

  • Parties and scope. Which labs, departments, or PIs are party to the agreement, and exactly which instrument(s) or equipment set it governs — not “the imaging suite” in general if only one microscope is actually shared under this agreement.
  • Ownership and capital responsibility. Who holds title to the equipment, which award or institutional fund paid for it (relevant if it was purchased through a federal instrumentation mechanism, since award terms can constrain disposition), and what happens to the equipment if the agreement ends.
  • Usage tracking obligation. How usage is logged, by whom, and how disputes about logged time get resolved — see the next section.
  • Rate schedule and review cadence. The current recharge rate (or cost-share formula, for a non-recharge arrangement), how it was calculated, and when it gets recalculated.
  • Priority-access rules. Who gets the instrument when two users want the same slot, stated as a rule applied consistently in advance — not a case-by-case negotiation.
  • Maintenance and repair responsibility. Who schedules preventive maintenance, who pays for an unplanned repair, and what happens to billing while the instrument is down.
  • Training and competency requirements. Whether users must complete a specific training/certification before independent access, and who verifies it.
  • Exit and decommissioning terms. How a party leaves the agreement, what happens to any unspent balance or prepaid time, and — if the group dissolves — how the equipment itself gets disposed of or reallocated.
  • Dispute resolution and governance. Who has authority to resolve a scheduling or billing dispute the parties can’t settle themselves — a core-facility oversight committee, a department chair, or (for a small informal arrangement) simply a named tie-breaker.

None of this replaces the institution’s own rate-compliance review for a formally established core facility — the sponsored-programs or cost-accounting office still has to confirm a published recharge rate meets 2 CFR 200.468‘s actual-usage, non-discrimination, and break-even requirements before it’s charged to federal awards. The agreement described here is the operating document that sits on top of that compliance layer.

Usage Tracking: The Foundation Everything Else Depends On

Every other section of the agreement — the rate, the priority rules, the dispute-resolution process — depends on having an accurate, contemporaneous record of who used the equipment, for how long, and for which project. Get usage tracking wrong and the rate calculation is built on bad data, priority rules can’t be enforced because nobody can prove who was scheduled first, and a federal auditor reviewing a recharge center’s billing has nothing to test the charges against.

Three tracking approaches are common, roughly in order of how much they scale:

  • A shared logbook or spreadsheet, workable for a two- or three-lab informal arrangement with light usage, but it depends entirely on users self-reporting accurately and has no independent audit trail.
  • A calendar-based booking system (a shared institutional calendar or a lightweight scheduling tool) that at least timestamps reservations, though it still can’t distinguish a booked slot from actual instrument runtime unless someone checks in and out.
  • A dedicated core-facility management platform — the commercial category most often referenced for this is iLab Solutions and Stratocore PPMS, which combine scheduling, usage logging, and billing/chargeback in one system tied to a project or grant number at the point of use. See Core Facility Management Software: iLab, Stratocore, and How Scheduling/Billing Platforms Work for how that category works and what it automates.

Whichever method is used, the agreement should specify what counts as billable usage (scheduled time, actual runtime, or a combination), how a no-show or late cancellation is handled, and how a user disputes a charge they believe is wrong. A rate-setting methodology that satisfies 2 CFR 200.468 on paper still fails in practice if the usage data feeding it isn’t reliable.

Calculating a Recharge Rate: A Worked Example

The Uniform Guidance requirements covered on the core-facility overview page — actual-usage billing, no profit, non-discrimination between federal and internal users, periodic review with carryforward of over/under-recovery — describe what a compliant rate must do. They don’t walk through how to actually build one. A simplified worked example, using only illustrative round numbers (not a claim about any real facility’s actual costs):

  1. Identify the annual cost pool. Sum the costs the rate is meant to recover: technician/operator salary and fringe allocated to time spent on this instrument, service contracts and consumables, and the instrument’s annual depreciation. Depreciation is calculated under 2 CFR 200.436, following a capital equipment depreciation schedule — generally straight-line, acquisition cost less salvage value, over the instrument’s useful life — not its full purchase price expensed in year one.
  2. Exclude costs that can’t go in this pool. If the instrument was purchased with a federal instrumentation grant (for example, an NIH S10 Shared Instrumentation Grant award), confirm the award terms before including depreciation on the federally funded portion of the purchase price — some instrumentation mechanisms restrict charging depreciation back to federal awards on equipment the government already paid for once.
  3. Estimate annual billable hours. Realistic, not theoretical, capacity: total available hours minus planned downtime for maintenance, calibration, and the gap between reservations that any shared schedule inevitably has. Overstating billable hours is the most common way a rate ends up under-recovering cost.
  4. Divide cost pool by billable hours to get a draft $/hour (or $/sample, $/run — whatever unit matches how the instrument is actually used) rate.
  5. Apply the prior period’s carryforward. If the facility over-recovered last period, subtract that surplus from this period’s cost pool before dividing; if it under-recovered, add the deficit. This is the mechanic behind 200.468’s “no profit” and periodic-review requirements — the rate isn’t allowed to just reset to zero every cycle.
  6. Set the internal rate, and a separate external rate if applicable. The internal, federally compliant rate must be the same for federal-award and institutional non-grant usage. A higher rate for genuinely external (non-institutional) users is generally permitted, since the non-discrimination rule governs federal-vs-internal parity, not federal-vs-external pricing.

Publish the resulting rate, the review date, and — for a formally established core facility — route it through the institution’s sponsored-programs or cost-accounting office before it’s charged to a federal award. For an informal, non-recharge cost-share between a few labs with no federal-compliance obligation, the same arithmetic still produces a defensible number for splitting cost proportional to actual use, which is generally a fairer basis than an even three-way split when usage isn’t actually even.

Priority-Access Rules When Demand Exceeds Capacity

Every shared instrument eventually has more demand than open slots at the same time. The point of writing a priority-access rule into the agreement in advance is that it gets applied consistently and without a live negotiation each time it comes up — the rule decides the conflict, not whichever party argues harder in the moment.

Common approaches, which an agreement can use alone or combine:

  • First-come, scheduled-in-advance. The simplest rule: whoever books the slot first through the agreed system gets it. Works well when usage is fairly predictable and light.
  • Tiered access by funding source or membership status. Institutional/member-lab users get priority booking windows or a larger reserved block of hours than occasional or external users, reflecting that member labs typically contributed capital or ongoing subsidy to the equipment.
  • Deadline-aware override, used sparingly and defined narrowly. Some agreements allow a documented federal-grant submission or sponsor-imposed deadline to bump a routine booking, but only if the rule specifies how far in advance the override must be requested and how the bumped party is compensated (rescheduled priority next time, a fee credit, etc.) — an override rule with no limits just becomes a recurring source of disputes.
  • Rotating or block allocation. For instruments with heavy, roughly equal demand from a fixed set of labs, a rotating schedule or a pre-allocated block of hours per lab per period avoids re-litigating priority every week.
  • Waitlist with defined cancellation notice. A minimum cancellation window (so a released slot can actually be reused) paired with a waitlist that fills it automatically.

Whatever combination is chosen, write down who decides an exception (a core-facility manager, an oversight committee, or a named tie-breaker for a small informal group) and how a user who feels a rule was applied unfairly can raise it — without that, the “rule” is really just whoever runs the schedule deciding informally, which is exactly the ambiguity the written agreement is meant to remove.

Governance and Periodic Review

For a formally administered core facility, the equipment-sharing agreement and its rate schedule should sit under the same governance structure that oversees the facility generally: a facility director or manager handling day-to-day scheduling and billing, an oversight or advisory committee (drawn from user-lab PIs and institutional finance/research-administration staff) that reviews the rate and access rules at least as often as the biennial cadence 2 CFR 200.468 requires for the rate itself, and the sponsored-programs office confirming the methodology still complies before any changes take effect. See the core-facility overview for how that governance structure is typically organized.

For an informal, multi-lab equipment-sharing arrangement with no dedicated facility staff, the same review discipline still applies at a smaller scale: put a review date on the agreement itself (annually is reasonable for a low-volume arrangement), and revisit the rate and priority rules whenever a new lab joins, a major repair changes the cost picture, or usage patterns shift enough that the original priority rules no longer reflect who’s actually using the instrument.

Frequently Asked Questions

Does an informal equipment-sharing arrangement between two or three labs need to follow 2 CFR 200.468?

Only if it functions as a recharge center billing costs to federal awards. A genuinely informal cost-share (for example, three labs splitting an instrument’s service contract and consumables proportional to use, with no formal per-use billing to grant accounts) isn’t automatically subject to the same federal rate-setting rules — but it’s worth checking with the institution’s sponsored-programs office before assuming that, since the line between “informal cost-share” and “unofficial recharge center” is exactly the kind of distinction a federal audit will draw if the arrangement grows.

Who should hold the written agreement — the PIs, or the department?

Either can work, but the agreement should specify a single custodian responsible for keeping it current and for retaining usage records, since usage data may need to be produced years later in an audit or in resolving a dispute about who used what, when.

What happens to the equipment if one party leaves the agreement?

This should be answered in the agreement itself, not improvised at the time — common approaches are that the equipment stays with whichever party holds title (see “Ownership and capital responsibility” above), the departing party forfeits any prepaid but unused time, or, for jointly purchased equipment, the departing party is bought out at a depreciated value calculated the same way as the rate’s depreciation component.

How often should the recharge rate actually be recalculated?

2 CFR 200.468 requires review at least biennially, and that review must account for prior-period over- or under-recovery. Many facilities review annually in practice, since a two-year gap can let a significant under-recovery accumulate before it’s corrected.

Follow CASRAI

Research-administration guidance, standards updates and independent tool reviews.

Referenced across the research world

University of Cambridge logoColumbia University logoCrossref logoUniversity of Edinburgh logoHarvard University logoUniversity of Oxford logoPrinceton University logoStanford School of Medicine logoUniversity College London logoORCID logoUniversity of Cambridge logoColumbia University logoCrossref logoUniversity of Edinburgh logoHarvard University logoUniversity of Oxford logoPrinceton University logoStanford School of Medicine logoUniversity College London logoORCID logo
  • University of Cambridge logo
  • Columbia University logo
  • Crossref logo
  • University of Edinburgh logo
  • Harvard University logo
  • University of Oxford logo
  • Princeton University logo
  • Stanford School of Medicine logo
  • University College London logo
  • ORCID logo

View CASRAI adoption →

Regulatory Radar

Stop finding out after the fact

$29/month, cancel anytime. Daily digest updates from our analysis, a dashboard holding the same items, and a cited assistant for everything they raise.

  • Federal Register, Federal Register+, Grants.gov, Regulations.gov, NSF News, UKRI, plus CASRAI’s own published content.
  • 44,322 indexed passages, and every answer cites the ones it drew on.