Skip to main content

Automation and Agents

How to Manage a High-Risk LSVP Grant Without Losing Its Scope

Keep a project-specific LSVP grant aligned with its work, people and tools. Understand retention, monitoring, renewal and the decisions access does not replace.

A project description stays within its scope folder through an owner handoff.
On this page
  1. Key program facts
  2. 1. Keep the grant separate from the work it supports
  3. 2. Make the project understandable to the next person
  4. 3. Check the person, surface and grant together
  5. 4. Separate vendor retention from your own records
  6. 5. Prepare to respond to a flag with context
  7. 6. Treat a changed task as a new decision
  8. 7. Make renewal and closure about current work
  9. 8. Report the evidence that helps someone act
  10. Questions about safeguards and retention
  11. Does High-risk Use remove every safeguard?
  12. Is 30-day retention only for High-risk projects?

A project can outgrow its original AI access plan without anyone making a formal decision to expand it. A researcher leaves, a new colleague takes over, an assistant gains another tool, or a document-review task becomes part of a larger workflow. The account still works. The reason it was approved may no longer describe the work.

That is the operating challenge behind Anthropic’s project-specific High-risk Use grants in its Life Sciences Verification Program, or LSVP. The grant concerns model access for an approved project. It does not establish that an institution has approved every use of the resulting answers, or that those answers are scientifically correct.

This guide proposes a way to keep the project, people and product surface aligned. It draws on current official program material, checked October 8, 2026. We have not tested LSVP or observed an incident in the program. The examples are hypothetical operating decisions, not lab instructions, legal requirements or claims that a particular control prevents misuse.

Key program facts

  • A High-risk Use grant applies to one project and renews every six months.
  • It removes life-sciences request blocks; safeguards such as cyber classifiers remain.
  • The program requires 30-day retention across LSVP traffic and uses pre-agreed incident response windows.

1. Keep the grant separate from the work it supports

The original program announcement defines High-risk Use as an add-on for a single project, renewed every six months. Standard Use can apply to a team and renews annually. High-risk grants remove safeguards that block life-sciences requests; other safeguards remain, including cyber classifiers. Broader access therefore changes one part of the operating arrangement, rather than making every request universally unrestricted.

It helps to distinguish three decisions. Anthropic decides access under its program. Your organization decides what work it permits in its own setting. A qualified reviewer decides whether a model’s answer is suitable for the intended use. One decision does not do the work of the other two. A grant can be valid while an output remains unfit to use.

Model access, organizational permission and output review remain separate decisions. View image detail

Choose Actual size to read the graphic closely.

Consider a hypothetical project using Claude to compare public documents for an internal analysis. Its owner wants useful drafting support. The organization still decides which inputs and uses it permits, while reviewers check the completed analysis.

When someone says “approved AI,” name the approved object: the account, use case, submission or completed analysis. That wording helps a successor understand what the decision actually covers.

High-risk Use is the name of an Anthropic grant. Legal classifications and physical research requirements depend on the actual work and relevant institutional authorities. Refer those decisions to the people responsible for them. Keep the model-access record clear about the permission it addresses.

If the team has not yet decided whether to pursue LSVP, start with our guide to evaluating the program against a real workload. The operating process here begins with a defined project. It cannot compensate for a weak adoption case by adding more paperwork.

2. Make the project understandable to the next person

A usable project record should answer a basic question: what work does this access support? Anthropic asks for high-level use-case descriptions without sensitive information or intellectual property. Follow that level of explanation when creating the shared record. The aim is to preserve meaning through a handoff, not to collect every confidential detail in one convenient place.

For the hypothetical document-analysis project, the record could name the intended source material, the internal deliverable and the role that reviews it. It could also distinguish activities that are outside that description. For example, an internal draft for review and an automated message sent to an external partner are different uses, even when they begin with the same documents.

Keep the actual grant details alongside the description: its reference, confirmed model and surface, renewal state and responsible people. These are proposed fields for your own record. Use them in the project system your team already understands; the inspected program material does not prescribe a specific form or app.

Write for someone who did not attend the original conversation. “Research support” is broad enough to hide several different tasks. “Prepare source-linked comparisons of the approved public document set for internal expert review” gives a successor something to recognize. A short description can be specific without revealing the research itself.

A project description carries its intended work through an owner handoff. View image detail

Choose Actual size to read the graphic closely.

Record important unanswered questions as questions. If the team is waiting for clarification about a changed use, keep that state visible. Do not quietly turn an old assumption into a confirmed permission when rewriting the record. A handoff is useful partly because it shows what the incoming owner still has to resolve.

Put the record where staff can find it during ordinary work, under existing access rules. The useful check is whether a person can connect today’s task to its current description.

3. Check the person, surface and grant together

People often think of access as attached to a person or account. LSVP adds a project-grant question to that picture. The announcement describes native grant switching in API and Claude Science, while Claude.ai and Claude Code initially use a preselected default. Claude Code using API authentication is an exception. A permission available in one route should not be assumed to travel with the person into every other route.

For a project handoff, have the incoming owner confirm the actual route they will use. Name the account or organization, product surface and selected grant in the team’s record. The point is to inspect the current setup, not to guess interface controls from a guide. A documented product distinction is not proof of what someone has configured in their account.

The hypothetical analyst might begin in a workspace and later ask an engineer to automate part of the document review through an API. That is a change in the work path. The engineer needs to establish which grant applies to that route, what inputs will be submitted and where results will go. Copying a prompt alone does not reproduce the previous arrangement.

A workspace route and an API route require their grant selection to be checked. View image detail

Choose Actual size to read the graphic closely.

Give a new researcher the current project explanation and relevant access. Transfer a departing owner’s decisions and unresolved questions as well as files. Use existing account processes for this proposed handoff; the source does not establish a special LSVP transfer feature.

Model names need confirmation too. The September announcement names Opus 5, while the current official interest page names Opus 5.5 alongside Mythos 5.1 and Sonnet 5. Keep the dated sources distinct and confirm what the actual grant supports. Do not update an operating record simply because a newer model name appears elsewhere.

Ask the incoming owner to explain the route in ordinary words: this person uses this surface and grant for this project’s task. If the answer names the wrong account or omits the selected grant, the handoff has exposed a question to resolve before the new route is used.

4. Separate vendor retention from your own records

The announcement requires 30-day retention for LSVP traffic. That applies across the program, not just to a High-risk grant. Anthropic says these data are compartmentalized, cannot be used for training and cannot be accessed by its life-sciences research teams. Those statements do not specify every detail of account-specific storage, review or deletion arrangements.

Your project also has its own records: source documents, work assignments, drafts, reviewer decisions and communications about access. Decide what each record is for before deciding how to store it. A note explaining the current grant serves a different purpose from an input file or a complete model transcript. Keeping all of them indefinitely is not automatically the best operating choice.

Source documents, grant notes and drafts serve different purposes in a project record. View image detail

Choose Actual size to read the graphic closely.

A reviewer may need a source version and the reasoning behind a conclusion. An admin may need the grant reference and an unresolved vendor question. Give each person the records relevant to that job.

Use applicable policies and account terms to decide where records belong and how long to retain them. Ask the responsible owner to resolve uncertainty about sensitive material. The announcement does not specify your organization’s archive schedule or all details of vendor deletion. Confirm those arrangements separately.

The separate Enterprise Frontier Safeguards announcement describes customer-controlled storage and customer review in a phased rollout. LSVP says integration is being explored for qualifying organizations. If that arrangement matters to your project, ask what is actually available to the account. It remains a separate product and availability question until confirmed.

The beta excludes BAA-enabled organizations. BAA means Business Associate Agreement, as explained in Anthropic’s help documentation. That condition should be part of the workload decision, not treated as an invitation to move restricted material into another account. A project owner who understands the source material and a data owner who understands the permitted use can resolve that question together. The grant name alone cannot resolve it.

5. Prepare to respond to a flag with context

Anthropic describes monitoring usage across requests and sessions against the stated use case. If unauthorized activity occurs, it can flag cases to organization admins, with pre-agreed windows for triage and remediation. The public announcement does not establish a universal response deadline, mandatory session freeze or automatic escalation to a particular job title.

Before relying on the program, establish who receives relevant notices in your organization and how they reach the people who can understand the work. Confirm the response arrangement with the account team. A deadline agreed for one organization should not be copied into another organization’s process merely because it sounds decisive.

The useful first response to a flag is a clear account of the activity. What task was intended? Who or what submitted the requests? Which sources and tools were involved? Did the work fit the project description? These questions support triage without treating every flag as proof of misconduct or every researcher’s explanation as proof that nothing went wrong.

An owner examines the intended task and actual activity behind a flag. View image detail

Choose Actual size to read the graphic closely.

Suppose an assistant produces requests unlike its ordinary document-review task. The owner needs to inspect the context and explain the departure. This planning example says nothing about how LSVP would classify the activity or how often its monitoring makes mistakes.

Avoid reconstructing the case through memory alone. Use the relevant records the organization is permitted to retain and share. Keep the response focused on the activity under review. Do not attach unrelated sensitive documents just to make the explanation look thorough. More information is not necessarily better evidence for the question being resolved.

After the responsible people agree what happened, record the decision and any change to the arrangement. A confusing handoff may need a clearer project description. An account issue may need a different response. Link the finding to the action and its owner, so the next person can see what was resolved.

6. Treat a changed task as a new decision

A project can change without changing its title. The document set may become confidential, the output may go to an external audience, or an assistant may gain permission to act in another application. These changes affect the work even if everyone still calls it “research analysis.” Ask whether the original project description and arrangements still fit.

Anthropic’s announcement names access compromise, insider threats and agent misuse among the concerns its program addresses. That makes the behavior around the model relevant, not just the contents of a single answer. It does not establish that a particular local control will prevent those risks. Your operating choices should be tied to the actual task and tools.

Consider the hypothetical analyst who wants the assistant to email its completed summary to a partner. Drafting a summary and sending it outside the organization are separate actions. The proposed addition changes the audience and destination. Before enabling it, decide who may authorize the send, which material may leave and how the completed output will be checked.

An internal draft and sending it to a partner are separate actions. View image detail

Choose Actual size to read the graphic closely.

Or consider an assistant that moves from answering questions to running a recurring multi-step job. It may now use credentials, choose documents and pass results to other systems. A project owner should understand those capabilities. Approval for a model-access use case should not be silently stretched into permission for every tool action the assistant can perform.

Capture the change in plain language. State the old task, proposed addition, affected material and person who can decide the next step. When the change may affect the grant, ask the account team what is needed. The public material does not provide a universal self-service amendment process, so do not invent one.

Distinguish work that remains within the agreed arrangement from the unresolved addition. When applicable policies allow that separation, the team can continue appropriate work while seeking an answer about the change. For the email example, that may mean preparing the internal draft while keeping external delivery undecided.

7. Make renewal and closure about current work

High-risk grants renew every six months; Standard Use grants renew annually. Keep those cycles separate. A team’s daily access and a project-specific add-on can have different states. The inspected announcement does not establish a fixed renewal dossier, a universal thirty-day preparation window or a particular automatic suspension mechanism.

Use the actual grant details and account guidance to plan renewal. Name what is due, who will handle it and which questions remain open. Schedule preparation around the confirmed process. Keep a local reminder distinct from a deadline specified by the vendor.

Renewal is a good moment to compare the current work with the project description. Is the original task still active? Have the inputs, people, product surface or connected tools changed? Is the output still reviewed in the way the team intended? These questions can reveal whether the record needs clarification before somebody repeats an old description in a new request.

Renewal compares today’s project with its recorded scope. View image detail

Choose Actual size to read the graphic closely.

If the analyst has left or the brief now serves another audience, explain the changed work at renewal. The team can describe the difference accurately without guessing what Anthropic will decide.

Project closure needs a concrete handoff. Decide what work ends, which people or automated processes no longer need access and which records remain useful under applicable policies. Use the organization’s existing processes for accounts, information and archives. Record who owns any remaining action.

Also consider unfinished work. A successor may need to know which drafts were reviewed, which questions remain unresolved and where the supporting sources live. Label the state of those materials clearly. Closing a grant does not make an unfinished analysis correct, and retaining an output does not imply that the project still has permission for new requests.

8. Report the evidence that helps someone act

Leadership needs a view of how the arrangement is working, not a decorative compliance score. Report the project’s current scope, actual access route, unresolved questions and relevant changes. Add evidence of usefulness when the team has it. A status memo can be short while still explaining what a decision-maker needs to do next.

For the document-analysis project, report what was produced and how reviewers handled it. Were drafts usable? Which errors needed repair? Did changed source material affect the process? Investigate these questions locally; no universal success percentage follows from the program.

Keep product access, operating behavior and content quality separate in that report. A successful request proves that an answer arrived under the tested conditions. It does not prove that the project stayed within every applicable rule or that the analysis was correct. Conversely, a poor draft can reveal a quality problem without establishing an access violation.

A report distinguishes access, operating behavior and content quality. View image detail

Choose Actual size to read the graphic closely.

If a flag or unusual event occurred, describe its current disposition and remaining action. Do not publish a count of warnings as if it were a count of confirmed misuse. Explain what the responsible people found. A small number with clear context can be more useful than a large dashboard whose labels hide what was actually investigated.

Model Current’s reporting reinforces the difference between permission and sound scientific answers. Its account of safeguards is reporting on vendor design, not an independent test of effectiveness. The same evidence standard applies to your own memo: say what was documented, what was observed and what remains an interpretation.

The project record, handoff and change decisions should help people do the work, rather than become a substitute for it. If an owner cannot explain the current task and access route, improve that explanation first. If the record is clear but an important question is unresolved, name the person who can answer it and the work that depends on it.

Broader access is most useful when the team can carry its meaning through ordinary changes. Keep the project description current, inspect the route people actually use and make changed work a visible decision. That gives the next owner a practical starting point without pretending that a grant guarantees either correct science or complete institutional approval.

Questions about safeguards and retention

Does High-risk Use remove every safeguard?

The announcement says it removes safeguards that block life-sciences requests. Other safeguards, including cyber classifiers, remain. That model-access change does not decide what your organization permits or whether an answer is scientifically sound.

Is 30-day retention only for High-risk projects?

No. Anthropic’s published condition applies to LSVP traffic across the program. Your own project records have a separate purpose and should follow applicable account terms and organizational policies. The announcement does not specify a universal local archive schedule.

Checked for this article

Sources

  1. Introducing the Life Sciences Verification ProgramAnthropic
  2. Life Sciences Verification Program interest pageClaude by Anthropic
  3. Developing Enterprise Frontier Safeguards with our customersAnthropic
  4. Anthropic opens broader biology AI access to vetted research teamsModel Current
  5. Business Associate Agreements for Commercial CustomersClaude Help Center

Keep reading

All articles