# Biotech Project Manager Role SOP and Operating Playbook

A model operating playbook for biotech project managers covering the trigger-to-close workflow, handoffs, records, escalation and review cadence.

**Explore Professional Certificate in Biotech Management:** [Open the course and enrol](https://mtfinstitute.com/programs/biotech-management/#enroll)

**Resource type:** role sop operating playbook  
**Evidence geography:** United States  
**Evidence scope:** Evidence-derived model from 102 current U.S. biotechnology management vacancy observations and a separate 11-source review of 2026 industry changes. This purposive evidence supports a practical learning template, not a representative estimate of all employers.  
**Accepted source SHA-256:** `1a31b414ce4618fedf64056dbe3008fa0e4f5d39ea7c63cf88849097e7dd9a04`

## Coordinate an assigned biotech workstream

Use this operating playbook when you are responsible for moving an assigned biotechnology objective across people, evidence, dates and decisions. It is designed for a project manager or a colleague taking on scoped cross-functional coordination. Your usable result is a current plan, a clear owner for each dependency, an issue and resource view, and a decision record that lets the accountable person act. Adapt the model to the employer's approved procedures, systems, approval map and document controls before using it at work.

The [U.S. biotech management vacancy study](https://mtfinstitute.com/insights/us-biotech-management-102-vacancies-2026/) supports planning, risk and issue management, stakeholder alignment and decision communication as recurring work in its sampled roles. The separate [current-changes review](https://mtfinstitute.com/insights/us-biotech-management-changes-2026/) shows why a manager should record source status, evidence provenance and specialist ownership when new methods or external signals affect a plan. This playbook is a practical model derived from that evidence, not a claim that every employer uses the same cadence or gives a project manager the same authority.

### Purpose, scope and working boundary

- **Use it for:** a defined research, development, operational, product or partner workstream whose accountable owner has delegated coordination.
- **Start it when:** an objective, material change, missed dependency or decision deadline requires coordinated action.
- **Finish a cycle when:** the designated owner has accepted the decision or handoff, affected owners have a revised plan, records are stored in the approved location, and open follow-up has a named owner and date.
- **Project manager's decision space:** sequence and prioritize assigned coordination work within delegated constraints; request missing evidence; convene the right people; present options and an escalation recommendation; update the controlled plan after approval.
- **Reserved decisions:** the designated scientific lead judges method fitness and technical conclusions; qualified clinical staff own protocol and patient matters; authorized CMC and quality owners determine acceptance or disposition; regulatory specialists own filing strategy, submission content and health-authority commitments; legal counsel owns agreement and intellectual-property terms; authorized finance leaders own funding, investment and securities actions. A project manager records and routes these decisions without substituting for their owners.

### People, inputs and local controls

Name the person or function for each role that applies to the assignment. One person may hold more than one locally approved role, but do not infer approval rights from a job title alone.

| Role | Contribution and handoff |
|---|---|
| Accountable sponsor or workstream owner | Sets objective, scope, success criteria, decision deadline, delegated limits and acceptance of the final decision or handoff. |
| Project manager | Maintains the integrated plan, owner map, issue and risk log, meeting record, decision request and follow-up; checks that specialist approvals are explicit. |
| Scientific or technical owner | Supplies and judges technical evidence, method fitness and scientific feasibility. |
| Clinical, CMC, quality or regulatory owner, when applicable | Supplies discipline-specific evidence and makes decisions within assigned professional authority. |
| Finance or resource owner | Confirms capacity, budget assumptions and any proposed financial commitment. |
| Legal, data or information-security owner, when applicable | Reviews agreements, intellectual property, data rights, transfer and protection under local process. |
| External partner or vendor contact, when applicable | Confirms its deliverables, dates, dependencies and accepted communication channel; internal owners retain company approvals. |

Collect only the inputs relevant to the workstream:

- The written objective, scope, success criteria, decision date and named accountable owner.
- Current plan, milestones, previous decisions, known constraints and the employer's approved stage or change-control process.
- Evidence inventory: source, version, owner, review status, permitted use and known limits for each material input.
- Owner and dependency map, including external partner deliverables and acceptance criteria where applicable.
- Resource and cost assumptions confirmed by the appropriate owner, without treating an estimate as spending approval.
- Approved collaboration, record, security, procurement and escalation systems. **Local policy field:** identify the actual system and retention rules before entering company data.

### Trigger-to-close workflow

1. **Open and bound the request.** Record who assigned it, the objective, the decision it supports, success criteria, due date, scope exclusions and delegated limits. If any of these are unclear, request a sponsor decision before making a commitment.
2. **Map the work and authority.** Identify workstream owners, reviewers, decision makers, external interfaces and the employer's approval path. Mark any scientific, clinical, CMC, quality, regulatory, legal, data or financial question for its qualified owner.
3. **Check the evidence and baseline.** Ask each owner for the latest approved record, version, status and uncertainty. Separate confirmed facts, assumptions and missing evidence. Capture the existing schedule, capacity and cost baseline from approved sources.
4. **Build a dependency plan.** Set deliverables, accountable owners, target dates, predecessor events, acceptance criteria and a practical update rhythm. Record alternative paths when a material assumption may fail. Have the relevant owners confirm the plan before circulating it as a commitment.
5. **Run the coordination cycle.** Collect progress against each milestone, inspect new issues and risks, resolve items within delegated scope, and update the log and plan in the approved system. Send a concise status update that identifies changed dates, effects, next actions and the decision needed.
6. **Prepare and route a decision.** When a change exceeds delegated limits or needs specialist judgment, send the accountable decision maker a short package: verified evidence, uncertainty, options, effects on time/resources, specialist views, recommended next step, deadline and consequence of no decision. Record the approver's actual decision and any conditions; never turn a recommendation into an approval.
7. **Confirm the handoff and close the cycle.** Tell each affected owner what was approved, what remains open and when the next check occurs. Verify acceptance against the defined criteria, store the final record in the approved system, and retain named owners for unresolved follow-up.

### Operating cadence

This is a starting rhythm; the employer and workstream owner set the actual meetings, reporting periods and cutoffs.

| When | Project manager's check | Output or handoff |
|---|---|---|
| Daily or at the agreed check-in | Review near-term blockers, due handoffs, changed assumptions and unanswered owner requests. | Update issue/dependency records and contact the person who can unblock each item. |
| Weekly or at the agreed team cycle | Compare milestones with evidence received, capacity and partner commitments; ask owners whether dates and acceptance criteria still hold. | One short status and decision update; an updated plan with version/date. |
| Monthly or at the agreed resource review | Reconcile forecast effort and costs with the finance/resource owner; inspect recurring risks and pending sponsor decisions. | Resource assumption and decision list for authorized review. |
| At a stage, partner, trial, launch or authority event | Recheck affected evidence, interfaces, approvals and contingency before changing a controlled plan. | Event-specific question package, handoff, decision record or approved rebaseline. |

### Decisions, handoffs and escalation

Use one decision record so that discussion does not become an untraceable approval. Include the question, requested decision date, options, evidence and versions, uncertainties, affected milestones/resources, consulted specialists, decision authority, final decision, conditions and follow-up owner. Record **pending** until the authorized person decides. A change to cost, external commitment, data sharing, method acceptance or regulated work follows the employer's approval route even if a meeting attendee agrees informally.

For each handoff, state the deliverable, version, sender, receiver, acceptance check, deadline, location of the controlled record and response due date. Ask the receiver to acknowledge ownership or return a specific gap. Do not mark a handoff complete merely because a file was sent.

Escalate when a material milestone is threatened, an owner or approval is missing, evidence conflicts, an assumption changes the chosen path, resource or cost limits may be exceeded, or a specialist raises a safety, quality, data, legal or regulatory concern. Use the locally approved urgent route for urgent concerns. Send the smallest accurate summary that permits action: observed fact, source and timestamp, likely effect, immediate containment within delegated scope, required specialist or sponsor decision, and decision deadline. Avoid circulating sensitive records beyond approved recipients.

### Records and quality checks

Maintain the following in the employer's approved system, with local access and retention controls:

- Objective and authority record: versioned scope, success criteria, decision maker and delegated limits.
- Integrated milestone and dependency plan: owner, target, predecessor, acceptance check, status, assumption and last update.
- Issue and risk log: description, evidence, effect, likelihood or urgency where locally used, owner, next action, trigger and review date.
- Resource view: capacity and cost assumptions, source, owner confirmation and approval status.
- Decision log: request, specialist input, options, actual decision, approver, date, conditions and implementation owner.
- Handoff record: sender, receiver, controlled deliverable version, acceptance response and remaining actions.

Judge the coordination system by questions that can be answered from those records. Are material milestones assigned and current? Do overdue dependencies have a named next action? Were decisions made by the right owner before the plan changed? Can a reviewer trace a claim to the right evidence version? Did the receiver accept each important handoff? Did a cost or capacity change reach the authorized resource owner? Useful local indicators include overdue handoffs, aging decisions, unowned issues, milestone variance and rework caused by missing information. The employer should define thresholds and reporting periods before treating any indicator as a performance target.

### Exceptions and recovery

When evidence is missing, label the item **unverified**, assign a source owner and date, and present a bounded option or pause the affected commitment. When two approved records conflict, preserve both versions, ask their accountable owners to reconcile them and do not silently choose one. When a specialist rejects a proposed path, record the reason at the appropriate confidentiality level and revise the option with that specialist. When an external partner misses an agreed handoff, confirm the facts with the partner contact, assess downstream effect and use the contract and escalation route approved by the employer. When a decision is delayed, show the consequence and latest useful decision date; do not claim tacit approval. An urgent safety, patient, quality, data-security or legal issue follows the relevant local incident route immediately.

## Reusable blank SOP template

Copy the fields below into the employer's approved workspace, then replace each guiding prompt in the right-hand column with the assignment's actual entry. The prompts are not completed records. **Local policy field** means that the team must supply its approved owner, system, threshold or route before operational use.

| Field | Entry to complete for the assignment |
|---|---|
| Assigned objective and bounded scope | Record the sponsor's wording, success criteria, exclusions and decision deadline. |
| Sponsor and delegated limits | Record the accountable owner and what the coordinator may decide or change. **Local policy field:** approval map. |
| Workstream owner map | Record each applicable function, contact, evidence input, decision authority and handoff receiver. **Local policy field:** named approvers. |
| Evidence baseline | Record each source/version, responsible reviewer, status, permitted use and unresolved gap. **Local policy field:** controlled repository and data rules. |
| Milestone and dependency plan | Record deliverable, owner, due date, predecessor, acceptance check, assumption and contingency. **Local policy field:** planning system and change-control threshold. |
| Issue and risk view | Record fact, effect, owner, next action, escalation trigger and review date. **Local policy field:** urgent route and issue system. |
| Capacity and cost view | Record the resource owner's confirmed assumption and the status of any approval. **Local policy field:** financial authority and procurement route. |
| Decision request | Record question, options, evidence, uncertainty, specialist input, recommendation, approver and decision deadline. |
| Decision and handoff close | Record actual decision, conditions, plan version, informed owners, receiver acceptance and remaining follow-up. **Local policy field:** record retention and access. |

Before using the completed model, check that every material dependency has one accountable owner, every specialist judgment is routed to that specialist, every number has a source and date, every external commitment has the required approval, and no pending decision is represented as final.

## Worked coordination example

Fictional example for learning purposes.

An early research team has roughly six weeks, from 27 October 2026 to 4 December 2026, to decide whether to expand an external laboratory's assay-feasibility work for Program A and arrange the next evidence review. The project manager has been asked to coordinate the decision package. The scientific lead owns assay fitness; the sponsor owns the scope decision; the resource owner confirms capacity and budget; legal and the data owner control the proposed agreement and data transfer. The project manager may adjust meeting and document sequencing within the approved period but may not approve assay use, sign an agreement or authorize spending.

### Objective and scope

By **20 November 2026**, give the sponsor a reviewed recommendation on whether to fund the next bounded assay-feasibility phase. Success means a traceable evidence summary, a resource view and an approved next action. Coordinate the current laboratory data package, repeatability review, draft next-phase work plan and decision meeting. Patient, clinical and filing decisions are outside this workstream.

### Owner map

- **Scientific lead:** evaluate method fitness and data limits.
- **External lab lead:** deliver the data package and answer methods questions.
- **Resource owner:** validate staff and cost assumptions.
- **Data owner:** approve the permitted transfer route.
- **Legal:** review any revised statement of work.
- **Sponsor:** decide next-phase scope.
- **Project manager:** integrate dates, evidence, options and follow-up.

### Evidence baseline

- **Lab package v2:** received 27 October 2026; scientific review pending.
- **Internal repeatability summary v1:** stored in the controlled repository; scientific lead to confirm comparison criteria.
- **Draft partner work plan v1:** unapproved.
- **Data transfer:** data owner to check permissions before sharing.

### Milestones and dependencies

- **30 October 2026:** laboratory clarifications due to scientific lead.
- **6 November 2026:** scientific review and evidence gaps recorded.
- **10 November 2026:** resource assumption confirmed.
- **13 November 2026:** legal and data review of the proposed next-phase arrangement.
- **17 November 2026:** sponsor pre-read.
- **20 November 2026:** sponsor decision.

A late scientific review shifts the sponsor pre-read unless the sponsor approves a bounded decision on available evidence.

### Issue, resource and decision request

The laboratory package lacks a documented explanation of two discordant results. The scientific lead owns the technical question, and the external laboratory response is due **30 October 2026**. If the question remains unresolved on **6 November 2026**, the project manager escalates the schedule effect and presents a further-test option. No fitness claim is made in the meantime.

The resource owner estimates two internal scientist-weeks and one external-laboratory work package for the next phase. Cost remains an estimate pending reviewed scope, procurement and sponsor authorization.

- **Option A:** authorize a bounded repeatability step after scientific, legal, data and financial review; decide on expansion later.
- **Option B:** defer the next-phase work pending resolution of the two discordant results.
- **Recommendation for sponsor review:** prepare Option A for approval only if the scientific lead accepts the evidence threshold and the other owners complete their reviews by **17 November 2026**. The sponsor decides on **20 November 2026**.

### Decision and close

The sponsor chooses a bounded repeatability step with no expansion commitment. The scientific lead confirms the test question; legal, data and resource owners complete their respective approvals before external work is ordered. The project manager publishes plan v3 in the approved workspace, obtains the laboratory contact's acceptance of the revised handoff, and assigns the result review to the scientific lead for **4 December 2026**.

The project manager's status note can be concise: “The **20 November 2026** scope decision remains feasible if the lab clarifies the two discordant results by **30 October 2026**. The scientific lead will judge method fitness; the resource, legal and data owners will review the proposed next phase. The sponsor will receive two options on **17 November 2026**. No external work or new spending is approved yet.” This separates the observed blocker, specialist judgment, proposed path and actual authority.

## Connected role pathway

- [ats resume template](https://mtfinstitute.com/insights/biotech-management-ats-friendly-resume-template/)
- [model job description](https://mtfinstitute.com/insights/biotech-management-model-job-description/)
- [role sop operating playbook](https://mtfinstitute.com/insights/biotech-management-role-sop-operating-playbook/)
- [Vacancy evidence](https://mtfinstitute.com/insights/us-biotech-management-102-vacancies-2026/)
- [Current-practice analysis](https://mtfinstitute.com/insights/us-biotech-management-changes-2026/)

**Study Professional Certificate in Biotech Management:** [Open the course and enrol](https://mtfinstitute.com/programs/biotech-management/#enroll)

Canonical URL: https://mtfinstitute.com/insights/biotech-management-role-sop-operating-playbook/