Managing multiple concurrent studies without drowning
Apply prioritization frameworks and triage principles to the reality of managing three, five, or eight concurrent studies -- so that participant safety is never compromised and critical deadlines do not slip.
Five studies, three sponsors, one of you
It is 8:47 AM on a Wednesday, and the coordinator's phone rings. A participant in a Phase III oncology trial is calling to report chest tightness that started during the night. This may be nothing. It may be a serious adverse event that requires reporting within 24 hours.
At the same moment, the coordinator's inbox shows 11 unread messages. One of them is from a sponsor's data management team: 14 open queries must be resolved by 5:00 PM today or the site will be placed on a data quality escalation list. Another message is a confirmation from a clinical research associate arriving tomorrow morning at 9:00 for a monitoring visit across two studies -- and the coordinator has not yet pulled the participant charts.
Five active studies. Three different sponsors. Two EDC systems. A monitoring visit in 24 hours. A participant on the phone right now who may or may not be having a cardiac event.
The math does not work unless you change how you think about prioritization.
In the previous lesson, we walked through the shape of a single CRC day -- the checkpoints, the rhythms, the cognitive weight. That lesson described what the day looks like. This one addresses a harder question: when everything is important, how do you decide what comes first? Because the defining challenge of managing multiple concurrent studies is not that you have too many tasks. It is that you have too many tasks that all feel urgent, and without a framework for distinguishing between them, every hour becomes reactive -- responding to whoever is loudest rather than to whatever matters most.
I have watched this problem destroy good coordinators. Not because they lacked skill, but because they lacked a system for making triage decisions under pressure. This lesson gives you that system.
What you will learn
By the end of this lesson, you will be able to:
1
Apply the urgency-importance matrix (Eisenhower framework) to CRC task prioritization with clinical research-specific examples
2
Implement a safety-first triage approach when competing demands arise simultaneously
3
Design a personal study tracking system that prevents critical deadlines, visit windows, and reporting requirements from slipping
4
Identify early warning signs of workload overload and apply strategies for requesting support before quality suffers
The urgency-importance matrix, adapted for clinical research
The Eisenhower matrix -- named for the U.S. president who reportedly said "What is important is seldom urgent, and what is urgent is seldom important" -- is a prioritization tool that has been applied everywhere from military operations to corporate management. Its premise is simple: every task can be classified along two dimensions (urgency and importance), and the combination determines how you should respond.
What makes this framework particularly valuable for clinical research coordination is that the CRC's daily task environment is uniquely dense with items that feel both urgent and important. A sponsor emails with "URGENT" in the subject line. An investigator asks you to pull a chart "as soon as possible." A participant calls about a headache. A query deadline is tomorrow. All of these arrive within the same hour, and without a deliberate classification system, the coordinator defaults to the most natural but least effective strategy: responding to whatever arrived most recently.
The adapted matrix for clinical research looks like this.
Figure 1: The urgency-importance matrix adapted for clinical research coordination, with CRC-specific examples and action guidance in each quadrant
Quadrant 1: urgent and important -- do immediately
These are the items that demand your attention right now and that genuinely matter for participant safety, data integrity, or regulatory compliance. A participant reporting symptoms that may constitute a serious adverse event. A safety lab result that exceeds the protocol-specified stopping rule. A protocol deviation discovered in the middle of a visit that requires real-time decision-making. An informed consent issue identified before a procedure that must not proceed without resolution.
The defining feature of Quadrant 1 items is not simply that they feel urgent -- many things feel urgent -- but that delay creates genuine risk. If the coordinator does not act on the safety call now, a reportable event may go undocumented past its reporting window. If the deviation is not addressed during the visit, the data collected afterward may be irretrievable.
Quadrant 1 items get your immediate, undivided attention. Everything else waits.
Quadrant 2: important but not urgent -- schedule and protect
This is, in my view, the most consequential quadrant for long-term CRC success, and it is the one that gets sacrificed most often. Quadrant 2 contains the tasks that do not demand action today but that, if neglected, generate Quadrant 1 crises tomorrow.
Preparing for a monitoring visit three days from now. Reviewing the IRB continuing review application due in two weeks. Completing a training module whose deadline is next Friday. Reconciling study drug accountability logs before the end of the month. Reviewing the protocol amendment that the sponsor circulated last week. None of these will cause immediate harm if you ignore them today. All of them will cause significant harm if you ignore them until they become urgent.
The discipline of Quadrant 2 is scheduling. Not "I will get to it when I have time" -- that time never materializes. Scheduling means blocking specific hours on specific days for these tasks and defending those blocks against the constant gravitational pull of Quadrant 3.
Quadrant 3: urgent but not important -- delegate or batch
This is where most coordinators lose the battle. Quadrant 3 tasks arrive with urgency cues -- a deadline, an exclamation point in the subject line, a phone call -- but they do not materially affect participant safety or data integrity if they are handled tomorrow rather than today.
A sponsor's clinical operations team sends an email requesting an updated site contact list "at your earliest convenience" -- but the email is marked high-priority, so it feels like it requires immediate action. A colleague asks whether you can cover a phone screen for their study this afternoon. The EDC system sends an automated reminder about a query that was opened 13 days ago -- the 14-day auto-escalation is tomorrow, so it feels urgent, but the query is a minor data clarification that carries no safety or compliance risk.
These items should be batched. Set aside 30 to 45 minutes during a natural break in the day -- after the last morning visit, during the afternoon administrative block -- and process them together. Batching reduces the context-switching cost that, as we discussed in the previous lesson, is one of the primary drivers of coordinator error.
Quadrant 4: neither urgent nor important -- eliminate or defer
These are the tasks that you can simply stop doing, or at least stop doing during working hours. The optional training webinar that is not required by any of your active protocols. The newsletter from a vendor you do not use. The request to update a tracking spreadsheet that no one reviews.
Every coordinator I have spoken with about time management eventually identifies at least two hours per week spent on Quadrant 4 activities that they perform out of habit, obligation, or guilt. Eliminating them does not feel heroic. But it creates the space for Quadrant 2 work that, over time, prevents the crises that make the job feel unmanageable.
The Quadrant 2 trap
Here is the pattern I see repeatedly: a coordinator who is drowning in Quadrant 1 emergencies concludes that there is no time for Quadrant 2 work. But Quadrant 2 neglect is precisely what creates Quadrant 1 emergencies. The monitoring visit that was not prepared for becomes a stressful scramble with findings. The IRB renewal that was not tracked expires, requiring a lapse-in-approval report. The training module that was deferred becomes a compliance hold on the study. The coordinator who "has no time" for Quadrant 2 is guaranteeing a future in which Quadrant 1 never stops growing. Breaking this cycle is the single most important operational change a CRC can make.
Safety-first triage: when two urgent things happen at once
The urgency-importance matrix is a planning tool. It works well when you are sitting at your desk with a task list, deciding what to do next. But it does not fully address the situation that coordinators encounter regularly: two genuinely urgent, genuinely important things happening at the same time.
The participant is on the phone with chest tightness. And the investigator has just paged you because a different participant's screening labs reveal a value that makes them ineligible, but the consent form has already been signed and the randomization call was made 20 minutes ago. Both are Quadrant 1. Both require immediate action. You cannot do both simultaneously.
This is where safety-first triage applies. The principle is straightforward, and it is grounded in the regulatory framework that governs everything we do in clinical research.
The safety-first triage rule
When two or more tasks demand immediate attention, participant safety takes absolute priority. This is not a suggestion or a cultural norm -- it is a regulatory obligation. ICH E6(R3) Annex 1, Section 2.1.3 requires the investigator (and by delegation, the coordinator) to ensure participants' "rights, safety, and well-being" are protected. When a task directly affects a participant's physical safety, it comes first. Always. No exceptions.
The triage hierarchy
When two or more Quadrant 1 items collide, apply this hierarchy.
First: direct participant safety. A participant reporting active symptoms that may constitute an adverse event. A safety lab result that exceeds the protocol-specified stopping rule. Any situation where a participant may be at immediate physical risk. This takes priority over everything else, regardless of the other demands on your time.
Second: regulatory compliance with imminent deadlines. The SAE that must be reported within 24 hours. The deviation that must be documented before the end of the business day per the sponsor's reporting requirements. The IRB reportable event that has a five-business-day submission window and this is day four. These items have deadlines imposed by regulation or contract, and missing them has defined consequences.
Third: data integrity at risk of permanent loss. The specimen that must be processed within its stability window. The source document that must be completed before the participant leaves because critical data points cannot be reconstructed from memory. The randomization error that must be documented now, while the sequence of events is still clear.
Fourth: operational commitments with stakeholder impact. The monitoring visit preparation. The query deadline. The sponsor teleconference. These are important, and they involve professional relationships and contractual obligations, but they can be rescheduled or managed with communication if participant safety or regulatory compliance requires your immediate attention.
Reference Table
Safety-first triage hierarchy for competing CRC demands
Priority level
Category
Examples
Action when lower priorities conflict
1 (highest)
Direct participant safety
Active symptom report, safety lab alert, consent integrity issue
Drop everything. Address this first. Communicate to stakeholders that other items are delayed.
Communicate proactively. Send a brief message explaining the delay. Reschedule if necessary.
Applying the hierarchy in practice
The triage hierarchy is easy to state and genuinely difficult to execute under pressure. In the scenario that opened this section -- the participant with chest tightness versus the ineligible participant who was already randomized -- the hierarchy clarifies the decision.
The participant with chest tightness takes priority. The symptoms may indicate a cardiac event, and the coordinator's immediate obligation is to ensure the participant receives appropriate medical evaluation. This means telling the participant to seek emergency medical attention if symptoms are severe, or connecting them with the investigator for a clinical assessment. It means documenting the call and initiating the adverse event reporting process.
The randomization error is serious, but it is not an immediate safety threat. The ineligible participant is not at physical risk from having been randomized -- the safety concern, if any, depends on the specific eligibility criterion that was missed. This issue can be addressed 30 minutes from now, after the safety call is handled. The coordinator should make a brief note -- date, time, nature of the issue -- so the details are not lost, and then return to it as soon as the higher-priority item is managed.
What the coordinator should not do is try to handle both simultaneously. The participant with chest tightness deserves undivided attention. Splitting focus between a safety call and a regulatory problem increases the probability of error in both.
The 30-second delay notification
When you must defer a legitimate priority to address a higher one, send a brief communication to the affected stakeholder. This takes 30 seconds and prevents hours of downstream friction. A text to the investigator: "Handling a participant safety call right now -- the randomization issue is real and I will bring it to you within the hour." An email to the sponsor: "Monitoring visit preparation is in progress; a participant safety event required my immediate attention this morning. I will have charts ready by end of day." Proactive communication about delays is a professional competency, not an admission of failure.
Building a study tracking system that prevents things from falling through
Prioritization frameworks help you decide what to do next. But they only work if you know what is on your plate. And that is a harder problem than it sounds when you are managing five concurrent studies, each with its own visit schedules, reporting deadlines, regulatory renewal dates, and participant follow-up windows.
The coordinator who relies on memory to track these obligations is not brave. The coordinator who relies on memory is taking a risk that ICH E6(R3) does not permit. Annex 1, Section 2.2.2 requires the investigator to have "sufficient time, an adequate number of available and qualified staff, and adequate facilities" to conduct the trial properly and safely. This obligation extends to ensuring that coordinators have workable systems for managing their responsibilities. A coordinator with no system for tracking deadlines across multiple studies has no mechanism for identifying when something is about to slip -- and by the time it slips, it has become a deviation, a missed reporting window, or a participant safety issue.
The goal is not a perfect system. The goal is a minimum viable tracking system -- one that takes minutes to maintain and that makes the invisible visible.
What your tracking system must show you
At a glance, without opening a single email or logging into an EDC system, you should be able to answer four questions.
What visits are coming this week, and are they on track? For each participant scheduled to visit this week, you need to know the visit type, the visit window (the acceptable date range), and whether the pre-visit preparation is complete. A visit that falls outside its protocol-defined window is a deviation. A deviation that could have been prevented by checking a calendar is, in my experience, the most frustrating kind.
What deadlines are approaching in the next 14 days? Query resolution deadlines. IRB continuing review submissions. Training module completions. Safety report follow-ups. Sponsor deliverables. These do not arrive at predictable intervals -- they accumulate unevenly across studies, and the coordinator who discovers a deadline on the day it is due has already lost the ability to manage it well.
Which participants require follow-up? The participant who reported a headache at the last visit and needs a follow-up call in five days. The participant whose labs were borderline and require investigator review before the next visit. The participant who missed the last call window and needs rescheduling. These follow-up items are not tracked by any EDC system. They live in the coordinator's head -- unless the coordinator puts them somewhere visible.
What is the status of each study right now? Not the detailed status -- just the headline. Study A: active enrollment, next monitoring visit March 28, three participants in visit windows this week. Study B: maintenance phase, database lock in six weeks, 23 open queries remaining. This kind of study-level summary prevents the coordinator from losing sight of any study for too long. When one study consumes all of your attention for three days -- and it will -- the other four studies do not stop generating obligations.
A system, not a tool
I am deliberately not recommending a specific tool -- not a spreadsheet template, not a project management application, not a particular clinical trial management system (CTMS). The reason is practical: the tool matters far less than the habit. I have seen coordinators maintain excellent tracking systems in a paper notebook. I have seen others fail to use expensive, purpose-built software because the system was more complex than the problem required. What matters is that you have a single place where all critical dates, deadlines, and follow-ups across all studies are visible, and that you consult it every morning during the inbox triage checkpoint we discussed in the previous lesson. The specific tool is a personal choice. The discipline is not optional.
Recognizing overload before quality suffers
There is a point at which no prioritization framework, no triage hierarchy, and no tracking system can compensate for the simple reality that one person has been assigned more work than one person can do well. This point arrives more often than the clinical research industry acknowledges. And it arrives silently, because the warning signs are not dramatic -- they are incremental, easy to rationalize, and visible only to the coordinator who is experiencing them.
I want to name these warning signs explicitly, because the coordinators who burn out are almost never the ones who recognized the problem early. They are the ones who kept saying "I can handle it" until the evidence proved otherwise.
Objective warning signs
These are the indicators that show up in measurable performance data -- the kind of evidence that, if you are honest with yourself, tells you that your capacity has been exceeded.
Query accumulation. Your open query count is growing faster than you can resolve them. Two weeks ago, you had 12 open queries across all studies. This week, you have 24. You are resolving queries, but new ones are arriving faster than you can close them. This is a leading indicator: the queries themselves may be minor, but the trend means documentation quality is slipping.
Documentation lag. You are entering visit data into the EDC system two or three days after the visit rather than same-day. You know you should be entering data while the details are fresh. But there are always more visits tomorrow, and today's data entry keeps getting pushed to "later." Per ICH E6(R3) Annex 1, Section 2.12.5, the investigator must ensure "the accuracy, completeness, legibility and timeliness of the data reported to the sponsor." A persistent two-day lag is not timely -- it is a pattern.
Missed deadlines. Not the dramatic kind -- not the SAE that was reported late, which would trigger an immediate investigation. The subtle kind: the IRB continuing review that was submitted on the last possible day instead of two weeks early. The training module that was completed the afternoon before the deadline. The monitoring visit preparation that was finished at 10:00 PM the night before. When every deadline becomes a last-minute scramble, the system is telling you something.
Monitoring findings increasing. The clinical research associate is identifying more issues during visits. More incomplete source documents. More unsigned pages. More queries generated from the monitoring visit itself, in addition to the queries you already had pending. This is not necessarily a reflection of your competence -- it is a reflection of your bandwidth.
Subjective warning signs
These are the internal signals that only you can detect. They are, in some ways, more reliable than the objective indicators, because they precede them.
Dread. You used to enjoy participant visits. Now, when you see a participant's name on the schedule, your first thought is not about the person -- it is about the work the visit will generate. This shift from engagement to dread is a signal that the volume of work has begun to erode the parts of the job that make it meaningful.
Avoidance. You find yourself avoiding specific tasks -- not because they are unpleasant, but because starting them feels overwhelming. The stack of 30 queries becomes a task you will "get to tomorrow." The regulatory binder update becomes something you will "catch up on this weekend." Avoidance is not laziness. It is a cognitive response to overload: the brain, when it cannot process the magnitude of remaining work, defaults to inaction.
Errors you would not normally make. You enter a date in the wrong format. You confuse two participants' visit schedules. You forget a fasting requirement for a lab draw. These are not skill deficits. These are the kind of errors that cognitive load research predicts: when working memory is saturated, details that would normally be automatic begin to slip.
Overload is not a personal failure
I want to be direct about something that the clinical research industry does not say often enough: if you are an experienced coordinator managing five concurrent studies across three therapeutic areas and you are showing signs of overload, the problem is almost certainly not you. It is the workload allocation. The solution is not to work harder, stay later, or develop better "time management skills." The solution is to communicate your capacity to site leadership and request a redistribution of work before participant safety or data quality is compromised. Asking for help is not a weakness. It is a professional obligation. ICH E6(R3) Annex 1, Section 2.1.1 requires the investigator to ensure "adequate resources" for the proper conduct of a trial. If the resources are inadequate, the responsible action is to say so -- not to quietly compensate with personal sacrifice until something breaks.
Asking for help: a competency, not a concession
Requesting support is a skill, and like any skill, it has a method. The coordinator who walks into a supervisor's office and says "I am overwhelmed" has communicated a feeling. The coordinator who walks in and says "I have 37 open queries across five studies, two monitoring visits this week, and an SAE follow-up report due tomorrow -- here is what I propose we redistribute" has communicated a problem with a solution.
How to communicate capacity
Lead with data, not emotion. Quantify the workload: number of active studies, open queries, upcoming visits, pending deadlines. This removes the conversation from the subjective realm ("I feel stressed") and places it in the operational realm ("these obligations exceed what one coordinator can complete in the available hours").
Propose a specific redistribution. Do not simply present the problem and wait for the supervisor to solve it. Identify which tasks could be transferred to another coordinator, which deadlines could be negotiated with sponsors, and which activities could be temporarily deferred without safety or compliance risk. This demonstrates that you have thought through the problem and are offering solutions, not complaints.
Frame it around quality. The most effective framing is not "I cannot handle this" but "if the current workload allocation continues, these specific quality metrics will be affected." Query resolution timelines will extend. Documentation lag will increase. Monitoring visit preparation will be incomplete. This framing aligns your request with the site's interests and the investigator's regulatory obligations -- it is not about your comfort, it is about the trial's integrity.
Set a threshold in advance. Do not wait until you are in crisis to determine what "too much" looks like. Before you reach overload, define your own capacity indicators. For instance: "If my open query count across all studies exceeds 30, or if I have more than three monitoring visits in a single week, I will initiate a workload conversation with my supervisor." Having a predefined threshold transforms the decision from an emotional judgment call into a mechanical trigger.
Case Study
"The Wednesday that tested everything"
Clinical ResearchIntermediate10-15 minutes
Scenario
Marcus Williams is a CRC II at Riverside Medical Center in Portland, Oregon, managing five concurrent studies. It is 9:15 AM on a Wednesday. In the past 30 minutes, three things have happened simultaneously.
First, a participant in the BEACON-1 Phase III oncology trial called to report that she woke up with severe abdominal pain and has been vomiting since 5:00 AM. She took her study drug last night. Marcus knows this may be a serious adverse event that requires investigator notification and initiation of the SAE reporting process within 24 hours.
Second, Marcus received an automated email from the EDC system for a cardiovascular trial: 14 data queries will auto-escalate to the sponsor's data quality committee at 5:00 PM today if they are not resolved. Three of those queries require source document verification that will take at least 20 minutes each.
Third, the clinical research associate for two of Marcus's studies confirmed she will arrive tomorrow at 9:00 AM for a two-day monitoring visit. She has requested charts for 11 participants across both studies. Marcus has prepared seven of the 11 charts. The remaining four have incomplete source documentation.
Marcus has no additional CRC support today. The investigator is in clinic until 1:00 PM.
The challenge:
How should Marcus triage these three competing demands? What should he do first, second, and third -- and what communication should he send to stakeholders about the items he cannot address immediately?
Analysis
Participant safety first: Marcus's immediate priority is the participant with abdominal pain and vomiting. He should assess the situation by asking targeted questions (onset, severity, whether she has sought medical attention), advise her to contact her physician or go to the emergency department if symptoms are severe, and leave a message for the investigator requesting an urgent callback to discuss the event and determine SAE classification. This cannot wait.
Communicate about the queries: After the safety call, Marcus should send a brief email to the sponsor's data management contact explaining that a participant safety event required his immediate attention and requesting a 24-hour extension on the query deadline. Most sponsors will grant this -- they would rather have accurate query responses one day late than rushed responses on time. If no extension is possible, Marcus should prioritize the three queries requiring source document verification (which are most time-consuming) and resolve the remaining 11 if time permits.
Monitoring visit preparation is deferrable -- with communication: Marcus should text or email the clinical research associate: "A participant safety event this morning is affecting my preparation timeline. Seven of 11 charts are ready. I will have the remaining four completed by end of day. Happy to discuss any concerns about readiness." This is professional, transparent, and acknowledges the issue without catastrophizing. The monitoring visit is tomorrow -- there is still time, and the CRA will appreciate the advance notice.
The underlying question: If this kind of morning is becoming routine rather than exceptional, Marcus should begin documenting the frequency and using it as evidence in a workload conversation with his supervisor. Five concurrent studies with active enrollment across multiple therapeutic areas may exceed what one coordinator can manage without compromising quality.
Check your understanding
1 of 3
A coordinator managing four concurrent studies is planning the week ahead. One study has a monitoring visit on Thursday, another has an IRB continuing review due in 12 days, a third has a participant visit window closing on Friday, and the fourth has a batch of 18 queries that were opened nine days ago with a 14-day resolution deadline. Using the urgency-importance matrix, which task belongs in Quadrant 2 (important but not urgent)?
What to carry forward
This lesson has given you three tools for managing the cognitive and operational demands of multiple concurrent studies. Let me be clear about what each one does and does not do.
The urgency-importance matrix gives you a language for classification. When you are staring at a task list and every item feels equally pressing, the matrix forces you to ask two questions: "Does this directly affect participant safety or data integrity?" and "Will delay cause irreversible harm?" The answers sort your tasks into a hierarchy that your instincts, under pressure, will not generate on their own.
Safety-first triage gives you a decision rule for collisions. When two urgent items arrive simultaneously -- and they will -- the hierarchy removes the need for real-time deliberation. Participant safety first. Regulatory deadlines second. Data integrity third. Operational commitments fourth. You do not have to decide in the moment. You have already decided.
A study tracking system gives you visibility. You cannot prioritize what you cannot see. The tracking system -- whatever form it takes -- ensures that the obligations of five concurrent studies are visible in one place, every morning, before the day's urgency begins to dictate your choices.
And underneath all three tools is the recognition that there are limits. That asking for help is not a sign that you are failing but a sign that you are paying attention. That the professional obligation to protect participants and maintain data quality sometimes means telling your supervisor, with evidence, that the current allocation of work is not sustainable.
The next lesson examines the administrative burden that consumes a large portion of every CRC's day -- the tracking, filing, reporting, and following up that is neither glamorous nor optional. That lesson builds directly on the prioritization principles we have discussed here, because administrative tasks are precisely the kind of important-but-not-urgent work that gets perpetually deferred unless the coordinator deliberately protects time for it.
The framework that changes everything
If you remember nothing else from this lesson, remember this: the moment you stop reacting to whatever arrives next and start triaging against a deliberate framework, you have changed the fundamental dynamics of your workday. You have moved from being controlled by your studies to managing them. The tasks do not become fewer. The deadlines do not become less demanding. But the feeling of drowning -- that persistent sense that something is being forgotten, that some deadline is slipping, that you are always one step behind -- begins to recede. Not because the workload has changed, but because your relationship to it has.
Full Preview
Free Lesson Preview
Module 1: Lesson 1
Managing multiple concurrent studies without drowning
Apply prioritization frameworks and triage principles to the reality of managing three, five, or eight concurrent studies -- so that participant safety is never compromised and critical deadlines do not slip.
Five studies, three sponsors, one of you
It is 8:47 AM on a Wednesday, and the coordinator's phone rings. A participant in a Phase III oncology trial is calling to report chest tightness that started during the night. This may be nothing. It may be a serious adverse event that requires reporting within 24 hours.
At the same moment, the coordinator's inbox shows 11 unread messages. One of them is from a sponsor's data management team: 14 open queries must be resolved by 5:00 PM today or the site will be placed on a data quality escalation list. Another message is a confirmation from a clinical research associate arriving tomorrow morning at 9:00 for a monitoring visit across two studies -- and the coordinator has not yet pulled the participant charts.
Five active studies. Three different sponsors. Two EDC systems. A monitoring visit in 24 hours. A participant on the phone right now who may or may not be having a cardiac event.
The math does not work unless you change how you think about prioritization.
In the previous lesson, we walked through the shape of a single CRC day -- the checkpoints, the rhythms, the cognitive weight. That lesson described what the day looks like. This one addresses a harder question: when everything is important, how do you decide what comes first? Because the defining challenge of managing multiple concurrent studies is not that you have too many tasks. It is that you have too many tasks that all feel urgent, and without a framework for distinguishing between them, every hour becomes reactive -- responding to whoever is loudest rather than to whatever matters most.
I have watched this problem destroy good coordinators. Not because they lacked skill, but because they lacked a system for making triage decisions under pressure. This lesson gives you that system.
What you will learn
By the end of this lesson, you will be able to:
1
Apply the urgency-importance matrix (Eisenhower framework) to CRC task prioritization with clinical research-specific examples
2
Implement a safety-first triage approach when competing demands arise simultaneously
3
Design a personal study tracking system that prevents critical deadlines, visit windows, and reporting requirements from slipping
4
Identify early warning signs of workload overload and apply strategies for requesting support before quality suffers
The urgency-importance matrix, adapted for clinical research
The Eisenhower matrix -- named for the U.S. president who reportedly said "What is important is seldom urgent, and what is urgent is seldom important" -- is a prioritization tool that has been applied everywhere from military operations to corporate management. Its premise is simple: every task can be classified along two dimensions (urgency and importance), and the combination determines how you should respond.
What makes this framework particularly valuable for clinical research coordination is that the CRC's daily task environment is uniquely dense with items that feel both urgent and important. A sponsor emails with "URGENT" in the subject line. An investigator asks you to pull a chart "as soon as possible." A participant calls about a headache. A query deadline is tomorrow. All of these arrive within the same hour, and without a deliberate classification system, the coordinator defaults to the most natural but least effective strategy: responding to whatever arrived most recently.
The adapted matrix for clinical research looks like this.
Figure 1: The urgency-importance matrix adapted for clinical research coordination, with CRC-specific examples and action guidance in each quadrant
Quadrant 1: urgent and important -- do immediately
These are the items that demand your attention right now and that genuinely matter for participant safety, data integrity, or regulatory compliance. A participant reporting symptoms that may constitute a serious adverse event. A safety lab result that exceeds the protocol-specified stopping rule. A protocol deviation discovered in the middle of a visit that requires real-time decision-making. An informed consent issue identified before a procedure that must not proceed without resolution.
The defining feature of Quadrant 1 items is not simply that they feel urgent -- many things feel urgent -- but that delay creates genuine risk. If the coordinator does not act on the safety call now, a reportable event may go undocumented past its reporting window. If the deviation is not addressed during the visit, the data collected afterward may be irretrievable.
Quadrant 1 items get your immediate, undivided attention. Everything else waits.
Quadrant 2: important but not urgent -- schedule and protect
This is, in my view, the most consequential quadrant for long-term CRC success, and it is the one that gets sacrificed most often. Quadrant 2 contains the tasks that do not demand action today but that, if neglected, generate Quadrant 1 crises tomorrow.
Preparing for a monitoring visit three days from now. Reviewing the IRB continuing review application due in two weeks. Completing a training module whose deadline is next Friday. Reconciling study drug accountability logs before the end of the month. Reviewing the protocol amendment that the sponsor circulated last week. None of these will cause immediate harm if you ignore them today. All of them will cause significant harm if you ignore them until they become urgent.
The discipline of Quadrant 2 is scheduling. Not "I will get to it when I have time" -- that time never materializes. Scheduling means blocking specific hours on specific days for these tasks and defending those blocks against the constant gravitational pull of Quadrant 3.
Quadrant 3: urgent but not important -- delegate or batch
This is where most coordinators lose the battle. Quadrant 3 tasks arrive with urgency cues -- a deadline, an exclamation point in the subject line, a phone call -- but they do not materially affect participant safety or data integrity if they are handled tomorrow rather than today.
A sponsor's clinical operations team sends an email requesting an updated site contact list "at your earliest convenience" -- but the email is marked high-priority, so it feels like it requires immediate action. A colleague asks whether you can cover a phone screen for their study this afternoon. The EDC system sends an automated reminder about a query that was opened 13 days ago -- the 14-day auto-escalation is tomorrow, so it feels urgent, but the query is a minor data clarification that carries no safety or compliance risk.
These items should be batched. Set aside 30 to 45 minutes during a natural break in the day -- after the last morning visit, during the afternoon administrative block -- and process them together. Batching reduces the context-switching cost that, as we discussed in the previous lesson, is one of the primary drivers of coordinator error.
Quadrant 4: neither urgent nor important -- eliminate or defer
These are the tasks that you can simply stop doing, or at least stop doing during working hours. The optional training webinar that is not required by any of your active protocols. The newsletter from a vendor you do not use. The request to update a tracking spreadsheet that no one reviews.
Every coordinator I have spoken with about time management eventually identifies at least two hours per week spent on Quadrant 4 activities that they perform out of habit, obligation, or guilt. Eliminating them does not feel heroic. But it creates the space for Quadrant 2 work that, over time, prevents the crises that make the job feel unmanageable.
The Quadrant 2 trap
Here is the pattern I see repeatedly: a coordinator who is drowning in Quadrant 1 emergencies concludes that there is no time for Quadrant 2 work. But Quadrant 2 neglect is precisely what creates Quadrant 1 emergencies. The monitoring visit that was not prepared for becomes a stressful scramble with findings. The IRB renewal that was not tracked expires, requiring a lapse-in-approval report. The training module that was deferred becomes a compliance hold on the study. The coordinator who "has no time" for Quadrant 2 is guaranteeing a future in which Quadrant 1 never stops growing. Breaking this cycle is the single most important operational change a CRC can make.
Safety-first triage: when two urgent things happen at once
The urgency-importance matrix is a planning tool. It works well when you are sitting at your desk with a task list, deciding what to do next. But it does not fully address the situation that coordinators encounter regularly: two genuinely urgent, genuinely important things happening at the same time.
The participant is on the phone with chest tightness. And the investigator has just paged you because a different participant's screening labs reveal a value that makes them ineligible, but the consent form has already been signed and the randomization call was made 20 minutes ago. Both are Quadrant 1. Both require immediate action. You cannot do both simultaneously.
This is where safety-first triage applies. The principle is straightforward, and it is grounded in the regulatory framework that governs everything we do in clinical research.
The safety-first triage rule
When two or more tasks demand immediate attention, participant safety takes absolute priority. This is not a suggestion or a cultural norm -- it is a regulatory obligation. ICH E6(R3) Annex 1, Section 2.1.3 requires the investigator (and by delegation, the coordinator) to ensure participants' "rights, safety, and well-being" are protected. When a task directly affects a participant's physical safety, it comes first. Always. No exceptions.
The triage hierarchy
When two or more Quadrant 1 items collide, apply this hierarchy.
First: direct participant safety. A participant reporting active symptoms that may constitute an adverse event. A safety lab result that exceeds the protocol-specified stopping rule. Any situation where a participant may be at immediate physical risk. This takes priority over everything else, regardless of the other demands on your time.
Second: regulatory compliance with imminent deadlines. The SAE that must be reported within 24 hours. The deviation that must be documented before the end of the business day per the sponsor's reporting requirements. The IRB reportable event that has a five-business-day submission window and this is day four. These items have deadlines imposed by regulation or contract, and missing them has defined consequences.
Third: data integrity at risk of permanent loss. The specimen that must be processed within its stability window. The source document that must be completed before the participant leaves because critical data points cannot be reconstructed from memory. The randomization error that must be documented now, while the sequence of events is still clear.
Fourth: operational commitments with stakeholder impact. The monitoring visit preparation. The query deadline. The sponsor teleconference. These are important, and they involve professional relationships and contractual obligations, but they can be rescheduled or managed with communication if participant safety or regulatory compliance requires your immediate attention.
Reference Table
Safety-first triage hierarchy for competing CRC demands
Priority level
Category
Examples
Action when lower priorities conflict
1 (highest)
Direct participant safety
Active symptom report, safety lab alert, consent integrity issue
Drop everything. Address this first. Communicate to stakeholders that other items are delayed.
Communicate proactively. Send a brief message explaining the delay. Reschedule if necessary.
Applying the hierarchy in practice
The triage hierarchy is easy to state and genuinely difficult to execute under pressure. In the scenario that opened this section -- the participant with chest tightness versus the ineligible participant who was already randomized -- the hierarchy clarifies the decision.
The participant with chest tightness takes priority. The symptoms may indicate a cardiac event, and the coordinator's immediate obligation is to ensure the participant receives appropriate medical evaluation. This means telling the participant to seek emergency medical attention if symptoms are severe, or connecting them with the investigator for a clinical assessment. It means documenting the call and initiating the adverse event reporting process.
The randomization error is serious, but it is not an immediate safety threat. The ineligible participant is not at physical risk from having been randomized -- the safety concern, if any, depends on the specific eligibility criterion that was missed. This issue can be addressed 30 minutes from now, after the safety call is handled. The coordinator should make a brief note -- date, time, nature of the issue -- so the details are not lost, and then return to it as soon as the higher-priority item is managed.
What the coordinator should not do is try to handle both simultaneously. The participant with chest tightness deserves undivided attention. Splitting focus between a safety call and a regulatory problem increases the probability of error in both.
The 30-second delay notification
When you must defer a legitimate priority to address a higher one, send a brief communication to the affected stakeholder. This takes 30 seconds and prevents hours of downstream friction. A text to the investigator: "Handling a participant safety call right now -- the randomization issue is real and I will bring it to you within the hour." An email to the sponsor: "Monitoring visit preparation is in progress; a participant safety event required my immediate attention this morning. I will have charts ready by end of day." Proactive communication about delays is a professional competency, not an admission of failure.
Building a study tracking system that prevents things from falling through
Prioritization frameworks help you decide what to do next. But they only work if you know what is on your plate. And that is a harder problem than it sounds when you are managing five concurrent studies, each with its own visit schedules, reporting deadlines, regulatory renewal dates, and participant follow-up windows.
The coordinator who relies on memory to track these obligations is not brave. The coordinator who relies on memory is taking a risk that ICH E6(R3) does not permit. Annex 1, Section 2.2.2 requires the investigator to have "sufficient time, an adequate number of available and qualified staff, and adequate facilities" to conduct the trial properly and safely. This obligation extends to ensuring that coordinators have workable systems for managing their responsibilities. A coordinator with no system for tracking deadlines across multiple studies has no mechanism for identifying when something is about to slip -- and by the time it slips, it has become a deviation, a missed reporting window, or a participant safety issue.
The goal is not a perfect system. The goal is a minimum viable tracking system -- one that takes minutes to maintain and that makes the invisible visible.
What your tracking system must show you
At a glance, without opening a single email or logging into an EDC system, you should be able to answer four questions.
What visits are coming this week, and are they on track? For each participant scheduled to visit this week, you need to know the visit type, the visit window (the acceptable date range), and whether the pre-visit preparation is complete. A visit that falls outside its protocol-defined window is a deviation. A deviation that could have been prevented by checking a calendar is, in my experience, the most frustrating kind.
What deadlines are approaching in the next 14 days? Query resolution deadlines. IRB continuing review submissions. Training module completions. Safety report follow-ups. Sponsor deliverables. These do not arrive at predictable intervals -- they accumulate unevenly across studies, and the coordinator who discovers a deadline on the day it is due has already lost the ability to manage it well.
Which participants require follow-up? The participant who reported a headache at the last visit and needs a follow-up call in five days. The participant whose labs were borderline and require investigator review before the next visit. The participant who missed the last call window and needs rescheduling. These follow-up items are not tracked by any EDC system. They live in the coordinator's head -- unless the coordinator puts them somewhere visible.
What is the status of each study right now? Not the detailed status -- just the headline. Study A: active enrollment, next monitoring visit March 28, three participants in visit windows this week. Study B: maintenance phase, database lock in six weeks, 23 open queries remaining. This kind of study-level summary prevents the coordinator from losing sight of any study for too long. When one study consumes all of your attention for three days -- and it will -- the other four studies do not stop generating obligations.
A system, not a tool
I am deliberately not recommending a specific tool -- not a spreadsheet template, not a project management application, not a particular clinical trial management system (CTMS). The reason is practical: the tool matters far less than the habit. I have seen coordinators maintain excellent tracking systems in a paper notebook. I have seen others fail to use expensive, purpose-built software because the system was more complex than the problem required. What matters is that you have a single place where all critical dates, deadlines, and follow-ups across all studies are visible, and that you consult it every morning during the inbox triage checkpoint we discussed in the previous lesson. The specific tool is a personal choice. The discipline is not optional.
Recognizing overload before quality suffers
There is a point at which no prioritization framework, no triage hierarchy, and no tracking system can compensate for the simple reality that one person has been assigned more work than one person can do well. This point arrives more often than the clinical research industry acknowledges. And it arrives silently, because the warning signs are not dramatic -- they are incremental, easy to rationalize, and visible only to the coordinator who is experiencing them.
I want to name these warning signs explicitly, because the coordinators who burn out are almost never the ones who recognized the problem early. They are the ones who kept saying "I can handle it" until the evidence proved otherwise.
Objective warning signs
These are the indicators that show up in measurable performance data -- the kind of evidence that, if you are honest with yourself, tells you that your capacity has been exceeded.
Query accumulation. Your open query count is growing faster than you can resolve them. Two weeks ago, you had 12 open queries across all studies. This week, you have 24. You are resolving queries, but new ones are arriving faster than you can close them. This is a leading indicator: the queries themselves may be minor, but the trend means documentation quality is slipping.
Documentation lag. You are entering visit data into the EDC system two or three days after the visit rather than same-day. You know you should be entering data while the details are fresh. But there are always more visits tomorrow, and today's data entry keeps getting pushed to "later." Per ICH E6(R3) Annex 1, Section 2.12.5, the investigator must ensure "the accuracy, completeness, legibility and timeliness of the data reported to the sponsor." A persistent two-day lag is not timely -- it is a pattern.
Missed deadlines. Not the dramatic kind -- not the SAE that was reported late, which would trigger an immediate investigation. The subtle kind: the IRB continuing review that was submitted on the last possible day instead of two weeks early. The training module that was completed the afternoon before the deadline. The monitoring visit preparation that was finished at 10:00 PM the night before. When every deadline becomes a last-minute scramble, the system is telling you something.
Monitoring findings increasing. The clinical research associate is identifying more issues during visits. More incomplete source documents. More unsigned pages. More queries generated from the monitoring visit itself, in addition to the queries you already had pending. This is not necessarily a reflection of your competence -- it is a reflection of your bandwidth.
Subjective warning signs
These are the internal signals that only you can detect. They are, in some ways, more reliable than the objective indicators, because they precede them.
Dread. You used to enjoy participant visits. Now, when you see a participant's name on the schedule, your first thought is not about the person -- it is about the work the visit will generate. This shift from engagement to dread is a signal that the volume of work has begun to erode the parts of the job that make it meaningful.
Avoidance. You find yourself avoiding specific tasks -- not because they are unpleasant, but because starting them feels overwhelming. The stack of 30 queries becomes a task you will "get to tomorrow." The regulatory binder update becomes something you will "catch up on this weekend." Avoidance is not laziness. It is a cognitive response to overload: the brain, when it cannot process the magnitude of remaining work, defaults to inaction.
Errors you would not normally make. You enter a date in the wrong format. You confuse two participants' visit schedules. You forget a fasting requirement for a lab draw. These are not skill deficits. These are the kind of errors that cognitive load research predicts: when working memory is saturated, details that would normally be automatic begin to slip.
Overload is not a personal failure
I want to be direct about something that the clinical research industry does not say often enough: if you are an experienced coordinator managing five concurrent studies across three therapeutic areas and you are showing signs of overload, the problem is almost certainly not you. It is the workload allocation. The solution is not to work harder, stay later, or develop better "time management skills." The solution is to communicate your capacity to site leadership and request a redistribution of work before participant safety or data quality is compromised. Asking for help is not a weakness. It is a professional obligation. ICH E6(R3) Annex 1, Section 2.1.1 requires the investigator to ensure "adequate resources" for the proper conduct of a trial. If the resources are inadequate, the responsible action is to say so -- not to quietly compensate with personal sacrifice until something breaks.
Asking for help: a competency, not a concession
Requesting support is a skill, and like any skill, it has a method. The coordinator who walks into a supervisor's office and says "I am overwhelmed" has communicated a feeling. The coordinator who walks in and says "I have 37 open queries across five studies, two monitoring visits this week, and an SAE follow-up report due tomorrow -- here is what I propose we redistribute" has communicated a problem with a solution.
How to communicate capacity
Lead with data, not emotion. Quantify the workload: number of active studies, open queries, upcoming visits, pending deadlines. This removes the conversation from the subjective realm ("I feel stressed") and places it in the operational realm ("these obligations exceed what one coordinator can complete in the available hours").
Propose a specific redistribution. Do not simply present the problem and wait for the supervisor to solve it. Identify which tasks could be transferred to another coordinator, which deadlines could be negotiated with sponsors, and which activities could be temporarily deferred without safety or compliance risk. This demonstrates that you have thought through the problem and are offering solutions, not complaints.
Frame it around quality. The most effective framing is not "I cannot handle this" but "if the current workload allocation continues, these specific quality metrics will be affected." Query resolution timelines will extend. Documentation lag will increase. Monitoring visit preparation will be incomplete. This framing aligns your request with the site's interests and the investigator's regulatory obligations -- it is not about your comfort, it is about the trial's integrity.
Set a threshold in advance. Do not wait until you are in crisis to determine what "too much" looks like. Before you reach overload, define your own capacity indicators. For instance: "If my open query count across all studies exceeds 30, or if I have more than three monitoring visits in a single week, I will initiate a workload conversation with my supervisor." Having a predefined threshold transforms the decision from an emotional judgment call into a mechanical trigger.
Case Study
"The Wednesday that tested everything"
Clinical ResearchIntermediate10-15 minutes
Scenario
Marcus Williams is a CRC II at Riverside Medical Center in Portland, Oregon, managing five concurrent studies. It is 9:15 AM on a Wednesday. In the past 30 minutes, three things have happened simultaneously.
First, a participant in the BEACON-1 Phase III oncology trial called to report that she woke up with severe abdominal pain and has been vomiting since 5:00 AM. She took her study drug last night. Marcus knows this may be a serious adverse event that requires investigator notification and initiation of the SAE reporting process within 24 hours.
Second, Marcus received an automated email from the EDC system for a cardiovascular trial: 14 data queries will auto-escalate to the sponsor's data quality committee at 5:00 PM today if they are not resolved. Three of those queries require source document verification that will take at least 20 minutes each.
Third, the clinical research associate for two of Marcus's studies confirmed she will arrive tomorrow at 9:00 AM for a two-day monitoring visit. She has requested charts for 11 participants across both studies. Marcus has prepared seven of the 11 charts. The remaining four have incomplete source documentation.
Marcus has no additional CRC support today. The investigator is in clinic until 1:00 PM.
The challenge:
How should Marcus triage these three competing demands? What should he do first, second, and third -- and what communication should he send to stakeholders about the items he cannot address immediately?
Analysis
Participant safety first: Marcus's immediate priority is the participant with abdominal pain and vomiting. He should assess the situation by asking targeted questions (onset, severity, whether she has sought medical attention), advise her to contact her physician or go to the emergency department if symptoms are severe, and leave a message for the investigator requesting an urgent callback to discuss the event and determine SAE classification. This cannot wait.
Communicate about the queries: After the safety call, Marcus should send a brief email to the sponsor's data management contact explaining that a participant safety event required his immediate attention and requesting a 24-hour extension on the query deadline. Most sponsors will grant this -- they would rather have accurate query responses one day late than rushed responses on time. If no extension is possible, Marcus should prioritize the three queries requiring source document verification (which are most time-consuming) and resolve the remaining 11 if time permits.
Monitoring visit preparation is deferrable -- with communication: Marcus should text or email the clinical research associate: "A participant safety event this morning is affecting my preparation timeline. Seven of 11 charts are ready. I will have the remaining four completed by end of day. Happy to discuss any concerns about readiness." This is professional, transparent, and acknowledges the issue without catastrophizing. The monitoring visit is tomorrow -- there is still time, and the CRA will appreciate the advance notice.
The underlying question: If this kind of morning is becoming routine rather than exceptional, Marcus should begin documenting the frequency and using it as evidence in a workload conversation with his supervisor. Five concurrent studies with active enrollment across multiple therapeutic areas may exceed what one coordinator can manage without compromising quality.
Check your understanding
1 of 3
A coordinator managing four concurrent studies is planning the week ahead. One study has a monitoring visit on Thursday, another has an IRB continuing review due in 12 days, a third has a participant visit window closing on Friday, and the fourth has a batch of 18 queries that were opened nine days ago with a 14-day resolution deadline. Using the urgency-importance matrix, which task belongs in Quadrant 2 (important but not urgent)?
What to carry forward
This lesson has given you three tools for managing the cognitive and operational demands of multiple concurrent studies. Let me be clear about what each one does and does not do.
The urgency-importance matrix gives you a language for classification. When you are staring at a task list and every item feels equally pressing, the matrix forces you to ask two questions: "Does this directly affect participant safety or data integrity?" and "Will delay cause irreversible harm?" The answers sort your tasks into a hierarchy that your instincts, under pressure, will not generate on their own.
Safety-first triage gives you a decision rule for collisions. When two urgent items arrive simultaneously -- and they will -- the hierarchy removes the need for real-time deliberation. Participant safety first. Regulatory deadlines second. Data integrity third. Operational commitments fourth. You do not have to decide in the moment. You have already decided.
A study tracking system gives you visibility. You cannot prioritize what you cannot see. The tracking system -- whatever form it takes -- ensures that the obligations of five concurrent studies are visible in one place, every morning, before the day's urgency begins to dictate your choices.
And underneath all three tools is the recognition that there are limits. That asking for help is not a sign that you are failing but a sign that you are paying attention. That the professional obligation to protect participants and maintain data quality sometimes means telling your supervisor, with evidence, that the current allocation of work is not sustainable.
The next lesson examines the administrative burden that consumes a large portion of every CRC's day -- the tracking, filing, reporting, and following up that is neither glamorous nor optional. That lesson builds directly on the prioritization principles we have discussed here, because administrative tasks are precisely the kind of important-but-not-urgent work that gets perpetually deferred unless the coordinator deliberately protects time for it.
The framework that changes everything
If you remember nothing else from this lesson, remember this: the moment you stop reacting to whatever arrives next and start triaging against a deliberate framework, you have changed the fundamental dynamics of your workday. You have moved from being controlled by your studies to managing them. The tasks do not become fewer. The deadlines do not become less demanding. But the feeling of drowning -- that persistent sense that something is being forgotten, that some deadline is slipping, that you are always one step behind -- begins to recede. Not because the workload has changed, but because your relationship to it has.
Enjoyed this preview?
The full CRC track covers 8 courses from study start-up to close-out — the skills sponsors actually look for.
