Claude Team Plan for Academic Labs: Pricing and Governance

The Claude Team plan for academic labs is a promotional subscription for verified principal investigators and equivalent research-group leaders at accredited universities and nonprofit research institutes. For-profit biotechs, pharmaceutical companies, industry research and development teams, and contract research organizations are ineligible for this offer. (^[1]) (^[2]) For a qualifying group, the decision is to apply only after checking institutional arrangements and permitted data use, then allocate paid seats according to observed workload.

The headline offer is Standard at $0 and Premium at $15 per user per month. (^[3]) Verified groups can have 1 to 25 seats, and the promotional period lasts 12 months, after which the then-current plan price applies. (^[4]) Anthropic announced an initial 10,000 seats on August 27, 2026; that allocation is not a published remaining-inventory count. (^[5]) The report's calculation puts a 25-seat, all-Premium group at $4,500 for twelve months, conditional on all seats receiving the verified rate and excluding taxes and additional usage. (^[6])

Affordability does not establish suitability for unpublished research. Massachusetts Institute of Technology guidance calls for reviewing tools with institutional information technology staff and verifying AI-assisted outputs. (^[7]) (^[8]) For covered health information, the US Department of Health and Human Services describes separate business associate agreement and risk-analysis requirements. (^[9]) Institutional approval, data classification, and scientific review must therefore precede sensitive use. The recommended pilot measures total task time, reviewer acceptance, citation corrections, blocked tasks, and actual expenditure, consistent with the UK AI Security Institute's emphasis on evaluations that mirror real use. (^[10])

This guide separates the scientist subscription, ordinary commercial subscriptions, included application programming interface credits, and discretionary AI for Science grants. Its governance and pilot framework are recommendations, not additional Anthropic eligibility rules. The immediate decision is one of four: apply with approved public-data workflows; request institutional review first; use an existing university agreement; or procure a commercial plan if the organization is ineligible.

Verification note: This report carries the requested publication reference of October 13, 2026. Primary pages were actually checked on October 15, 2026. Current terms below reflect that later check, not an archived observation from October 13. In particular, the current API-credit documentation is treated as a verification update.

The scientist offer changes the budget discussion for small academic groups, but it does not remove the need to decide what the lab may put into a shared workspace. The University of Rhode Island's information technology notice directs researchers to the program and its application materials. (^[11]) That is useful institutional discovery evidence, rather than a measurement of research quality or time saved.

A lab should evaluate eligibility, licensing cost, and institutional permission separately. Harvard's guidance makes the practical point that protections must be understood for the particular tool, model, workspace, and feature being used. (^[12]) A favorable subscription price cannot answer whether a specific dataset, integration, or automated action is allowed.

IntuitionLabs approaches the subject as an adjacent life-sciences consultancy. Its own services describe guidance on AI adoption and technology roadmapping. (^[13]) That perspective informs the recommended handoff between research leadership and institutional control functions; IntuitionLabs is not presented as a competing subscription option.

The analysis focuses on decisions a principal investigator (PI), lab manager, research-computing lead, or university privacy team can make now. Oxford's research policy favors an institutional supplier agreement or an appropriate local deployment, illustrating why an existing university route deserves investigation before a separate lab purchase. (^[14]) The practical question is whether this particular workspace can support a defined workflow under the institution's rules.

Verify before applying: Reopen the official application and support pages, confirm verified prices and seat eligibility, ask about existing campus agreements, capture the renewal notice arrangements, and record approval for the proposed data and tools. Those checks are recommended procurement steps, rather than a promise that an application will be accepted.

The application should start with the PI or equivalent research-group leader, not with an assumption that every person holding a university email address qualifies independently. The eligible institutional categories and research fields are explicitly defined by the program: accredited universities and nonprofit research institutes, working in natural sciences, mathematics, computer science, engineering, and related fields. (^[15])

Table 1 translates those observed categories into a recommended eligibility decision tree. Evidence suggestions are this report's operational recommendations; Anthropic makes the verification decision.

Decision branch	Evidence to prepare	Recommended outcome
Accredited university or nonprofit research institute, eligible research field, PI or equivalent	Institutional affiliation, public group page, research description, leadership role	Proceed to institutional checks and application. ([16])
For-profit biotech, pharma, industry R&D, or contract research organization (CRO)	Organization's legal and operating identity	Use ordinary Team or Enterprise procurement; the promotion excludes this category. ([2])
University already has a Claude agreement	Campus service listing and account-administrator contact	Ask the institutional administrator before creating a separate lab workspace. ([17])
Eligible institution, but proposed data or tools lack approval	Data inventory and proposed workflow	Request institutional review first. Berkeley explicitly directs users to responsible-unit approval for new uses. ([18])

The table separates vendor qualification from local authorization. A nonprofit translational-biology institute can meet the institution branch while still needing review of a sponsored dataset. An industry collaboration also warrants careful identification of who is applying and who owns the data; participation in academic research should not be treated as a substitute for the documented organization criteria.

Application timing should be planned conservatively. The public page still displays an application route and states that most applications are reviewed within 5 to 7 business days; availability and final pricing remain conditional on verification. (^[19]) A lab should avoid scheduling a time-critical analysis on an unapproved application.

Charles University's medical faculty reports that several teams have passed verification. (^[20]) This establishes a neutral example of institutional uptake, not acceptance rates, processing guarantees, or scientific outcomes. The recommended application packet should make the group leader's affiliation and role easy to establish.

Once access is approved, the lab should keep an offer record, named billing owner, allowed-use statement, and review date. Inactivity is a financial condition: the support page says a group inactive for 90 days may be returned to standard Team pricing, with administrator notification. (^[21]) The lab should decide whether an inactive workspace should be closed, retained with a documented budget, or renewed under a different institutional arrangement.

An existing university Enterprise agreement is not something the PI should unilaterally override. Stanford's local service policy illustrates why: approval to use Stanford data depends on provisioning through its managed service, rather than an institutional email alone. (^[22]) That is Stanford's policy example, not a universal rule about every university contract.

An individual subscription can be useful for a researcher testing approved, personal workflows, but the procurement question differs from selecting a lab workspace. Claude Pro has its own individual pricing; the current official pricing page lists monthly billing and an annual subscription paid upfront. (^[23]) The comparison table below gives the observed prices alongside the group options.

The distinction should be assessed through ownership and continuity. Recommended questions are who approves the account, who pays, how project records are retained, and what happens when a researcher leaves. Berkeley's guidance asks units offering separately procured AI tools to communicate allowed uses and protection limits clearly. (^[24]) A lab should make the same expectations explicit for any reimbursed individual account.

The presence of a subscription also does not expand a researcher's rights over inputs. Yale's library guidance notes that licensed scholarly resources carry restrictions on how they may be used. (^[25]) Literature-review access should therefore be evaluated separately from permission to upload full publisher content or build a reusable corpus.

For Claude Team versus Pro for research labs, the recommended test is operational:

• Individual exploration: Use an institution-permitted account for approved material and a bounded task.
• Shared administration: Prefer a managed route when the group needs common ownership, onboarding, or institutional controls.
• Research continuity: Keep authoritative records and reviewed outputs in the institution's approved research systems.
• Departures: Define what must be transferred or preserved before reimbursement or account access ends.

These are decision criteria, not assertions that an individual account lacks every relevant control. Harvard's advice to inspect the actual workspace and feature protections is the appropriate basis for evaluating a particular arrangement. (^[12])

The lab should also distinguish permitted experimentation from an established research method. Cambridge calls for human evaluation of generated outputs before use, and Nature's editorial policy retains human scholarly judgement and responsibility. (^[26]) (^[27]) A successful writing exercise should not automatically authorize the same account for participant data, unpublished partner files, or code execution against shared infrastructure.

Regular commercial Team pricing is separate from the promotion. Its help page currently requires two members and gives Standard prices of $25 monthly or $20 per member per month billed annually, with Premium at $125 monthly or $100 per member per month billed annually, excluding applicable taxes. (^[28]) The scientist offer should not be used to estimate costs for an ineligible biotech or CRO.

Table 2 summarizes the observed US-dollar subscription prices at the October 15 verification. The promotional columns are subject to verification; annual-equivalent commercial prices involve annual billing. (^[3]) (^[23])

Route	Standard or individual cost	Premium cost	Decision boundary
Verified scientist Team promotion	$0 per user per month	$15 per user per month; $180 per year	Small verified academic or nonprofit group; promotional term. ([6])
Ordinary commercial Team	$25 monthly, or $20 per month billed annually	$125 monthly, or $100 per month billed annually	Commercial pricing; minimum two members. ([29])
Individual Pro	$20 monthly, or $200 paid annually	Not a Team seat category	Individual purchasing decision; assess permitted workspace use. ([23])
Existing university Enterprise service	Obtain the institution's allocation and charging terms	Obtain the institution's allocation and charging terms	Prefer an institutional assessment before a separate purchase. ([14])

The comparison shows why a lab should request a verified seat offer and an institutional route comparison, rather than extrapolate from a generic pricing article. It also avoids treating an unknown Enterprise contract price as zero.

Scientist seats include Claude Science, Claude Code, and Claude Cowork; Premium adds five times more usage and higher limits for long-running analyses. (^[30]) (^[31]) That multiplier is a vendor allowance description, not a promise of five times as many papers, completed experiments, or validated analyses. Model-access caveat for biology: Anthropic currently does not recommend Fable 5 or Fable 5.1 for professional biology research and drug development; blocked biology, chemistry, and life-sciences requests may fall back to Opus 5. (^[32]) Dual-use biology requests on Opus 5.5, including virology, toxicology, and molecular design, can also fall back to Opus 5. (^[33]) Affected organizations doing legitimate life-sciences research can apply to the separate Life Sciences Verification Program (LSVP). Scientist-plan eligibility should be assessed separately from LSVP verification and access-grant approval; the LSVP has its own verification and grant process. (^[34]) Evaluate these safeguards before choosing Premium: a larger usage allowance should not be treated as approval for a restricted task. The Team help page describes usage limits as per-member, so unused chat allowance should not be assumed to form a lab-wide pool. (^[35])

For access management, the dedicated setup guide supports single sign-on (SSO) on Team. (^[36]) SSO connects authentication to an identity provider; implementation still requires coordination with the people who control institutional identity settings. The provisioning guide distinguishes just-in-time (JIT) provisioning from System for Cross-domain Identity Management (SCIM), and says JIT does not automatically remove members. (^[37]) An offboarding checklist should therefore include both identity access and workspace membership. Assign the Primary Owner deliberately: the role documentation allows only one per organization, and that account consumes a license. (^[38])

Data treatment also needs a precise reading. The commercial privacy guidance says inputs and outputs are not used for training by default, with documented exceptions for affirmative permission or submitted feedback; owners can disable member feedback submission. (^[39]) This should inform configuration, not be interpreted as approval for confidential data.

Retention is another separate question. The privacy documentation describes deletion from backend systems within 30 days after chat deletion, subject to exceptions; it should not be presented as automatic deletion of all ongoing Team conversations after that interval. (^[40]) Research IT should confirm the actual workspace settings, record requirements, and available administrative features before onboarding.

An application programming interface (API) lets software call models programmatically. A lab should distinguish API expenditure from interactive subscription use, because a script, data-processing workflow, and scientist's chat session can have different budgets, permissions, and review requirements.

October 15 verification update: Current API documentation includes monthly scientist-plan credits of $20 per Standard seat and $100 per Premium seat, pooled with a $500 monthly workspace cap. Unused credits expire, and these credits do not increase Claude or Claude Code subscription limits or cover their extra usage. (^[41]) (^[42]) (^[43]) The retrieved pages do not establish that these provisions were already present on the requested publication reference date.

Activate the credits before budgeting their use: New subscribers can claim credits after seven days on an eligible plan. (^[44]) The person claiming the Team credits must be a Team Primary Owner or Owner and also hold an Owner, Admin, or Billing role in the intended Claude Console organization. In the Team workspace, open Organization settings > Billing, select the intended Console organization in the API credits section, and accept the credit-program terms by linking it. (^[45]) Choose that organization deliberately: each plan links to one Console organization, and changing the linked organization later requires contacting support.

This is distinct from AI for Science, the application-based research program. Anthropic's expansion announcement describes applications for up to $50,000 per project. (^[46]) Its program rules include discretionary selection, biosecurity assessment, and necessary institutional or employer consents. (^[47]) (^[48]) A lab should not enter that possible award as guaranteed funding.

Recommended API budget controls are:

• Separate ownership: Assign an approved Console organization and accountable budget owner.
• Bounded spending: Record included-credit terms, any additional paid allowance, and escalation rules.
• Key management: Use institution-approved credential handling and revoke access when personnel change.
• Workflow review: Approve datasets, destinations, integrations, and scientific acceptance criteria before scaling.

These controls apply the broader principle of traceability across datasets, processes, and decisions in the Organisation for Economic Co-operation and Development (OECD) AI Principles. (^[49]) They are recommendations for operating the workflow, not new credit-award conditions.

Researchers should also avoid reading model knowledge tests as proof that a particular automated research pipeline will be useful. The UK AI Security Institute (AISI) notes that knowledge-question performance does not establish an assistant's ability to help human scientists. (^[50]) A credit award or included allowance can fund evaluation; neither establishes scientific validity.

The recommended funding model therefore has separate lines for seat fees, included API allowance, paid API overage, and any independently approved grant. Grant applications should describe the research aim and required capacity, while the lab's internal approval should describe the data, responsible people, and review process.

The appropriate comparison is between a permitted, managed workflow and the lab's actual alternatives. Oxford's policy recommends institutional agreements or appropriate local models, while UNESCO's guidance discusses ethical validation in education and research. (^[14]) (^[51]) Neither framework makes a particular promotional workspace suitable for every research purpose.

Data and tool permissions before onboarding

The recommended pre-onboarding record should classify inputs and actions separately. Harvard advises checking what files, applications, accounts, and services a tool can access, and granting only necessary permissions. (^[52]) (^[53])

• Public material: Start with material the lab has permission to reuse; Berkeley permits public information in generative AI tools. (^[54])
• Unpublished research: Identify the data owner, sponsor restrictions, intellectual-property obligations, and institutional approval route. MIT explicitly addresses sensitive and controlled research inputs. (^[55])
• Human data: Confirm the approved purpose, consent constraints, ethics requirements, and data handling. Yale says existing human-data obligations continue to apply. (^[56])
• Health information: Consult the privacy office before use; relevant covered entities need the separate agreement and risk analysis described by HHS. (^[57])
• Controlled technology: Request institutional export-control advice where applicable. The Bureau of Industry and Security's fundamental-research provisions do not make all research inputs automatically unrestricted. (^[58])
• Regulated workflows: Request quality review when outputs enter regulated production or quality processes. FDA's software-assurance guidance has a defined medical-device production and quality-system scope. (^[59])
• Connectors and actions: Review source permissions, shared credentials, and read versus write authority. Claude's connector guidance describes inherited permissions and owner action controls. (^[60])
• Third parties: Review each connected service's own terms and infrastructure; approval of the chat workspace should not be extended automatically to every destination. (^[61])

For a first pilot, read-only, narrowly scoped access is a defensible recommendation. Harvard explicitly distinguishes information retrieval from actions that create, modify, delete, send, approve, or execute. (^[62]) Keep broad shared-drive access and consequential writes outside the initial scope unless separately reviewed.

A practical RACI handoff

A RACI assigns who is responsible, accountable, consulted, and informed. The following allocation is a proposed lab operating model. It reflects the National Institute of Standards and Technology (NIST) recommendation to document AI risk roles and communication lines. (^[63])

• PI: Accountable for the application, approved research scope, funding decision, and escalation to the institution.
• Workspace administrator: Responsible for membership, seat allocation, billing notices, configuration records, and workspace offboarding.
• Research IT, security, and privacy: Consulted for approval of identity, data, retention, connectors, and incident procedures; accountable for decisions within their institutional authority.
• Scientist: Responsible for permitted inputs, recording material AI assistance, checking outputs, and reporting problems.
• Scientific reviewer or task owner: Accountable for accepting the research output before it enters downstream work.

NIST distinguishes those overseeing AI systems from the people operating or interacting with them. (^[64]) In a small lab, one person may hold several roles, but each responsibility should still be named.

Scientific review and incident handling

A written approval should specify what counts as an accepted result. The International Committee of Medical Journal Editors (ICMJE) assigns humans responsibility for reviewing AI-assisted content and ensuring its accuracy. (^[65]) Code execution, a plausible citation, and fluent interpretation are not substitutes for the relevant scientific checks.

Keep confidential review duties outside ordinary experimentation. National Institutes of Health (NIH) policy prohibits generative-AI analysis and critique of its grant applications by peer reviewers; National Science Foundation (NSF) policy restricts uploads of review material to non-approved tools. (^[66]) (^[67]) These are task-specific restrictions, not blanket statements about all research assistance.

Recommended incident steps are to stop the affected workflow, restrict the implicated access, preserve relevant records under institutional policy, notify the appropriate institutional contact, and document corrective action. OECD principles support continuing lifecycle risk management rather than treating initial approval as the end of oversight. (^[68])

The 30-day duration below is this report's recommendation. It is not an Anthropic trial term or a validated universal study design. AISI argues that evaluations should mirror real use and describes human uplift studies comparing assisted work with a control condition. (^[10]) (^[69]) A lab can apply that principle proportionately without claiming to reproduce a formal benchmark.

The pilot should compare a defined workflow with the lab's existing method under comparable conditions. Record task difficulty and reviewer involvement. Where practical, alternate comparable tasks or counterbalance order so that familiarity is not mistaken for assistance. Record a result as exploratory when the small task set cannot support a broader inference. For biology tasks, review the model-access caveat above and record scientist-plan eligibility and any LSVP approval separately. Assess whether safeguards or model fallbacks affected a task before recommending a Premium upgrade.

• Days 1 to 5: Confirm institutional permission, approved inputs, owner responsibilities, and review rubrics.
• Days 6 to 10: Measure baseline effort on representative tasks using the existing method.
• Days 11 to 20: Run bounded assisted tasks, capturing usage constraints and reviewer corrections.
• Days 21 to 25: Repeat selected task types, investigate disagreement, and test required offboarding steps.
• Days 26 to 30: Compare accepted outcomes and total effort, review spending, and decide whether to continue.

Choose tasks whose outputs can be checked independently: synthesis of permitted public papers, code explanation against known tests, or drafting from approved source material. Rhode Island's notice lists literature review, coding, analysis, and writing as possible applications, rather than demonstrated productivity results. (^[70]) The lab should select its own relevant subset.

The pilot scorecard should include:

• Baseline task time: Record active scientist and reviewer time using the existing method.
• Assisted task time: Include preparation, interaction, verification, correction, and rework.
• Reviewer-accepted outputs: Report both accepted outputs and all attempted tasks.
• Citation errors: Record incorrect, unsupported, or mismatched citations and the effort needed to correct them.
• Failed or blocked tasks: Preserve these in the denominator and explain the limiting condition.
• Usage and model record: For every evaluated task, record the seat type, requested model, model that actually answered, any model-switch notice, safeguards or allowance interruptions, and additional paid consumption.
• Cost: Include seat fees, paid usage, review effort, and administration.
• Disposition: Mark each task accepted, corrected, abandoned, or outside approved scope.

Checking references and confirming accuracy are explicit recommendations in NIH's current AI research reminder. (^[71]) Human evaluation also aligns with Cambridge's guidance. (^[26]) The scorecard should count those checks as work, rather than treating them as free.

Predefine stop criteria: unauthorized data handling, inability to verify consequential output, unapproved tool access, or cost exceeding the approved allowance. Set quality thresholds by task before reviewing the assisted results. Training should cover these decisions and escalation paths, consistent with NIST's operational training guidance. (^[72])

Finally, distinguish engagement from scientific evidence. AISI cautions that model performance varies across domains. (^[73]) More sessions, longer conversations, or enthusiastic feedback do not establish a correct analysis. The continuation decision should rest on accepted work, manageable review burden, and approved operation.

The twelve-month seat calculator is arithmetic, not a forecast of future prices:

Seat cost = (Standard seats × $0 × 12) + (Premium seats × $15 × 12). The inputs come from the verified promotion; annual Premium billing is stated as $180 per user. (^[6]) Let S be Standard seats and P be Premium seats, with the verified group total within the permitted range. Additional usage and taxes are excluded.

Table 3 gives hypothetical mixes covering group sizes from a single member to the plan limit. Every row is a Hypothetical Example, calculated using the same verified rate rather than an independently quoted offer. (^[74])

Hypothetical Example	Standard seats	Premium seats	Monthly seat cost	Twelve-month seat cost
Solo, Standard	1	0	$0	$0
Small group	4	1	$15	$180
Mixed lab	8	2	$30	$360
Larger mixed lab	20	5	$75	$900
Full Standard group	25	0	$0	$0
Full Premium group	0	25	$375	$4,500

The table shows that only the Premium count changes the modeled seat fee during the promotion. It does not show the cheapest acceptable operating model, since administration and scientific review still consume resources. A recommended allocation method is to start from approved task needs, then request Premium where recorded allowance constraints impede otherwise useful work.

Renewal and inactivity exposure

The support page commits to renewal at the then-current price, rather than a specific future figure. (^[4]) A lab should therefore use variables for post-promotion budgeting: let Rₛ and Rₚ be the confirmed monthly renewal prices for its Standard and Premium seats. The modeled next-year seat budget is 12 × (S × Rₛ + P × Rₚ), assuming the same mix and a full year.

Use three explicitly hypothetical planning scenarios:

• Unconfirmed renewal: Leave both renewal prices blank and assign an administrator to obtain the offer before commitment.
• Affordable confirmed renewal: Enter the institution-approved prices, calculate the annual total, and compare with the approved spending ceiling.
• Unaffordable confirmed renewal: Model fewer seats, another approved institutional route, or closure with required record preservation.

These scenarios deliberately avoid assigning an invented future price. For a Hypothetical Example with twenty Standard seats and five Premium seats, the formula becomes 12 × (20 × Rₛ + 5 × Rₚ). The decision remains dependent on the actual renewal notice.

What the evidence establishes

The sources establish offer conditions, observed subscription prices, documented controls, and institutional expectations. They do not supply a measured productivity estimate for this lab. AISI's discussion explains why human-assistance utility must be evaluated in realistic tasks, rather than inferred from model knowledge scores. (^[75])

The recommended financial measure is total approved pilot expenditure divided by reviewer-accepted outputs, reported alongside baseline time and quality. This is an internal management calculation, not a scientific-validity score. ICMJE retains human responsibility for accuracy, regardless of how efficiently a draft was produced. (^[65])

The offer can reduce a qualifying lab's subscription line, but it also creates a decision about sustainable ownership. A good outcome is a small set of permitted workflows with documented review and a funded exit or renewal path. UNESCO's guidance places generative AI within an ethical validation process, while NIST's framework is voluntary risk-management guidance rather than a product approval. (^[51]) (^[76])

The lab should preserve enough detail to explain AI's contribution later. Oxford recommends declarations that can identify the tool, version, date, and role in the research process. (^[77]) Its policy also notes reproducibility difficulties with cloud models that change and cannot be archived. (^[78]) The recommended record is the approved input description, material prompts or procedures, checked sources, code and tests where relevant, human corrections, and final accepted output.

Disclosure rules should be checked for the actual funder and publication. ICMJE asks users to disclose the tool and purpose, while UK Research and Innovation distinguishes substantive use from minimal language or formatting assistance. (^[79]) (^[80]) NSF encourages disclosure of AI's role in proposal preparation, and NIH recommends checking institutional and journal policies. (^[81]) (^[82]) These differences favor a reusable internal record that can support the required external statement.

The recommended decision outcomes are:

• Apply now: Eligibility is clear, the institutional route is confirmed, and the initial workflows and inputs are approved.
• Request review first: The group qualifies, but data handling, identity, retention, or connector permissions remain unresolved.
• Use the university agreement: The institution directs researchers to an existing managed service.
• Choose commercial procurement: The applicant is a for-profit biotech, pharma company, industry R&D team, or CRO, or otherwise falls outside the promotion.

This operating perspective is consistent with IntuitionLabs' stated emphasis on a small portfolio of governed workflows and decisions based on observed evidence. (^[83]) It is a consultancy perspective on adoption, not a claim that a particular lab will achieve a measured benefit.

The Claude Team plan for academic labs should be evaluated as a conditional licensing opportunity within a broader institutional research workflow. Qualification, affordability, and permission answer different questions. The PI should establish eligibility, the institution should resolve the approved service and data route, the administrator should own access and billing, and scientists should retain responsibility for checked outputs.

The recommended seat decision is workload-based: request paid capacity where the pilot identifies a useful task being constrained, and retain evidence of both accepted and unsuccessful work. A low seat fee can make evaluation practical; it cannot establish that a generated interpretation, reference, or analysis is correct.

Before onboarding, the group should have named owners, an allowed-input list, reviewed tool permissions, a scientific acceptance rubric, and an offboarding process. Before continuing, it should have measured total effort, review burden, actual expenditure, and the confirmed renewal position.

The final decision need not be universal across the lab. A group can approve a narrow public-data workflow while holding sensitive work for institutional review. It can also choose an existing university service or an ordinary commercial plan where appropriate. The defensible outcome is a documented fit between the research task, the permitted environment, the human review process, and the budget.