GuidesFor CRCs & site directors
Managing a Multi-Study Portfolio Without a Single Source of Truth
Jul 1, 2026GuideStudy Lifecycle TrackerAdministrative reference · Zero-PHI examples only
study portfoliolifecycleenrollmentsite opsZero-PHI
Why study status fragments across sheets and chat threads, what “stage” should mean at the portfolio level, and how Study Lifecycle Tracker keeps Pipeline→Closed visible without subject lists.
The problem on the clinic floor
Ask three people where Study X stands and you may get three answers: “still startup,” “IRB approved but not activated,” “we’re enrolling.” The truth is fragmented across a startup checklist, an email from the CRA, a shared sheet with half-updated status columns, and someone’s memory of the last SIV.
Portfolio meetings then become status archaeology. Directors want a board; coordinators want not to maintain a second CTMS. Shared cloud sheets raise the privacy concern sites keep repeating: even de-identified notes in a widely shared doc sit outside the access model people assume for clinic tools.
Without a single administrative view, kit, deviation, and deadline tools get opened without context — you fix a closet issue on a study that is already Closed in practice, or you miss that a Pipeline study still needs regulatory dates entered somewhere else.
Staff turnover makes fragmentation worse. A new coordinator inherits five protocols and five different “status” locations — none of them updated the week the previous lead left. The first portfolio huddle becomes a guessing game.
Aggregate enrollment targets drift from reality when nobody updates the board after a slow month. Leadership plans staffing from stale numbers; coordinators get asked why “actual” does not match the sheet nobody was assigned to maintain.
Practice context
Site leadership needs study-level stage and aggregate enrollment progress, not per-subject lists, to prioritize staff time. Pipeline → activation → enrollment → follow-up → Closed is enough structure for most portfolio huddles. Item-level IRB dates and training still belong in a deadline tracker; kit lots belong in kit tools.
A Zero-PHI portfolio board stores protocol/study IDs, stages, optional IRB/activation dates, aggregate target/actual counts, milestone labels, and short status notes — never subject names or IDs.
CTMS and sponsor portals hold subject-level detail under their own access controls. The site portfolio board is deliberately lighter: enough to allocate coordinator time, prep for SIV/SOV, and decide which Protocol Ops tool to open next.
Closed studies should stay visible for history, not deleted. Auditors and internal QA sometimes ask when a study left active enrollment — a stage board with archive dates answers that without reopening email threads.
How to use Study Lifecycle Tracker for this
Use Study Lifecycle Tracker as the portfolio front door, then drill into Protocol Ops tools for a specific study. Update stage and aggregate counts when something material changes — activation, enrollment pause, last-subject-in, close-out — so the board reflects this week, not last quarter.
- Open Study Lifecycle Tracker and add each protocol with stage (Pipeline through Closed), optional IRB/activation dates, and aggregate enrollment counts only. Never enter subject-level rows — target versus actual at study level is enough for portfolio view.
- Filter Active vs Closed vs All when preparing a site meeting so Closed studies do not dominate the board. Use Active for staffing decisions; use All when QA asks for a historical snapshot.
- Update next milestone labels and short status notes when something material changes — keep notes administrative (“awaiting amendment approval,” “SIV scheduled”). Avoid free-text that could resemble subject detail.
- Export CSV for leadership distribution, or Export Session Backup (.json) to move the board between clinic PCs. Date-stamp exports before director meetings.
- Archive to Closed when appropriate instead of deleting history; use Regulatory Deadline Tracker for item-level due dates on a given study. Kit and deviation tools should reference the same protocol ID labels you use here.
Portfolio chaos is usually a visibility problem. One stage board beats five optimistic status emails. When everyone reads the same Pipeline→Closed view before opening item-level tools, coordinators spend less time translating status and more time running visits.