Subscribe via E-mail

Your email:
subscribe-to-our-newsletter
alcoa-checklist

Medical Device CRO Blog

Current Articles |  RSS Feed

10 Signs That a Research Coordinator is Spread Too Thin

  
  
  

As a former research coordinator of five years, I am well aware of the extremely busy and highly demanding nature of the job. In addition to balancing multiple trials, subjects, physicians, sponsors, and monitors; coordinators are often required to perform a diverse set of tasks that go beyond the scope of subject visit conduct. This may include regulatory submission and maintenance, laboratory processing and shipping, subject recruiting, and source document creation among others. Furthermore, coordinators often work to facilitate trials across multiple locations and must ensure that studies are conducted in accordance with applicable federal regulations, the investigator agreement or 1572, the protocol, and the rules of the IRB (FAIR SHAKE). Given the multitude of responsibilities, some coordinators may be spread too thin.

10 Signs That A Research Coordinator is Spread Too Thin:

  1. Inability to maintain accurate and complete source documentation – The subject binders may be missing pages, visits, procedures, appropriate signatures, or simply are not filled out. In other cases, subject binders may lack consistency in terms of adverse events (AEs) (e.g. documented in one place but not another), concomitant medications, or other study data.
  2. Difficulty entering data and/or responding to queries in a timely manner – Data may be overdue or the coordinator may be scrambling to enter visits as the monitor is arriving on site. In more severe cases, subjects may be enrolled and complete follow up visits prior to any data being entered. This can prevent the sponsor from tracking subject enrollment and may also violate the pre-arranged time-line for data entry outlined in the agreement between the sponsor and investigator. Queries can quickly accumulate and excessive unresolved queries are often a sign of an over-worked coordinator.
  3. Failure to use correct and updated study documentation – This includes use of outdated or incorrect versions of the informed consent document, protocol, source documents, and in some cases lab kits. The coordinator may not have started using the updated versions of study materials prior to a subject visit. This is also seen at sites which fail to have currently enrolled subjects sign revised versions of informed consent documents (when instructed to do so by the IRB).
  4. Adverse events have not been properly documented, entered, or reported – AEs may not be correctly signed off by the investigator, captured on AE logs, or entered on the case report form (CRF). In addition, AEs may not be correctly reported to the sponsor and/or IRB.
  5. Study devices or investigational medication are not properly processed in terms of receipt, storage, or product log completion – Receipt of investigational devices or medication may not be properly registered or acknowledged, storage may not be adequate or secure, and product logs may not be updated to reflect on-site inventory or current subject use.
  6. Delayed response to outstanding action items or other sponsor/CRO requests – Action items which require site assistance may not addressed or completed in a timely manner. This includes regulatory issues, data issues or queries, and other miscellaneous items requiring site follow-up.
  7. Site is unprepared for monitoring visits – Outstanding items/ issues from the previous monitoring visit have not been addressed adequately or completely. Regulatory and /or subject binders may not available or up to date. In some cases, the coordinator or site staff may be unaware of the monitor’s visit or not have dedicated sufficient space or resources for the monitor.
  8. The coordinator does not have sufficient time to spend working with the monitor – The coordinator may be unavailable or not have time to address monitor questions or action items. Furthermore, the coordinator may be unable to provide the monitor with requested study documentation or materials.
  9. Salient or recurring protocol violations – Protocol violations that indicate a lack of familiarity with the protocol or insufficient time to properly conduct the study. In addition, repeated violations of the same nature may suggest a lack of oversight on the part of the research coordinator.
  10. Incomplete or missing training documentation – Training documentation may be incomplete or absent. If training has occurred, the documentation will need to be located and filed. If training was not completed, appropriate members of the study team should be notified to complete the training.

Have you ever worked with a research coordinator who was spread too thin?

Perhaps you yourself were the coordinator. Please share your thoughts below. 

Photo Credit:Tom Morris

Comments

Greetings Mr. Cobb, 
I am not a Research Coordinator, however the observations which you describe seem to be replete in every laboratory in which I have been employed. It seems as though there is a disconnect between the decision makers and the technical staff which drives the elements of insufficiency with reference to adequate allocation of resources which would allay the "spreading too thin" of the coordinator. As a management professional in the laboratory, this thesis applies also. I also think that until there is a connection between the resource allocators and the research facilities, this sort of occurance will continue to occur and the vital which benefits all of us will continue to suffer and be obstructed. I empathize with your sentiment and understand fully the primary components of you article and truly hope that one day there will be said connection so that the powerful machine that is research will move forward in a more meaningful and prolific trajectory.  
 
Thank you for this article. I sincerely hope it resonates through the research community and, perhaps makes some subtle differences in the thought processes and context of which research is viewed and comprehended.  
 
Thanks Again.....
Posted @ Tuesday, September 17, 2013 10:56 AM by John S. Voivoda
While I believe your observations are correct and definitely agree that SCs are spread way too thin, those same signs can be examples of inadequate training/experience or worse case scenario plain incompetence. I would like to hear people's thoughts on how a monitor or auditor could differentiate between those 3 root causes, i.e., being spread too thin, under trained, or incompetent.
Posted @ Tuesday, September 17, 2013 12:49 PM by Lee Truax-Bellows
The root cause of spread to thin, under-trained and/or incompetent coordinators is poor planning and management. It takes time and costs money to provide adequate resources, training and hire competent or capable coordinators. Both sponsors and site management are responsible for ensuring that the study is being run competently and in compliance. If it is not, then there should be true consequences (and not just idle threats from the sponsor). Money talks. To cut corners on competent staff should be penalized and not rewarded just because the site manages to enroll a high number - it shows shortsightedness and a "just do it" mentality.
Posted @ Tuesday, September 17, 2013 5:35 PM by jean munroe
these all sound like me at times! and episodes of under-resourced and (occasionally) quiet! It is certainly a balance between having studies up to date, new trials starting as current ones are potentially ceasing soon, successful feasibility review for both potential patients and resources. It is the operating now, and being paid 6 months later, and flexible staffing availabiltiy that cause the most angst. Monitors can be very helpful here in early education, early review of initial patients recruited, listing all required for ongoing documentation. I have always found monitoring visits most helpful in the early stages to ensure that we are on track. Maybe if these study deficiencies continue, it is a sign that a site needs much more time in education/monitoring/review of participation/processes/staffing availability
Posted @ Tuesday, September 17, 2013 8:20 PM by kate Smith
Some of the CRCs I've spoken with express that the "spread too thin" phenomenon you describe is only getting worse under some remote monitoring implementations. Tasks that an on-site monitor would typically perform are, in some cases, being handed back to the sites. Probably not the intention of a good risk-based monitoring scheme, but it's happening.
Posted @ Wednesday, September 18, 2013 10:56 AM by Laurie Meehan
As was pointed out, the signs described above can indicate poor performance or excess workload. All too often I have observed that the former conclusion is often glibly drawn without considering workload. For a site without robust data systems and workload metrics (most of us?) it is not always easy to discern causes.  
 
Competency assessments are useful during training to ensure that the coordinator is grasping basic GCP. Our coordinators worked as a group to define all of the competencies and knowledge base required for their roles. We then built an on-boarding process which included training modules and competency assessments. 
 
For example, the new coordinator completes CRFs for one of their studies. A seasoned colleague will review source and verify data entered to assess whether the new employee understands data abstraction, is in need od additional training, etc. Similarly we do reg binder checks, specimen processing, etc. if someone has a well-documented series of competency sign-offs, and can be observed to work hard, and can explain why some of these signs are present (e.g. has been focusing on another trial with a recent spate of enrollments), we know it is a workload issue. 
 
I am focused on metrics to calculate workload- my office does cancer clinical trials and it is hard to justify the need for additional staff based on observation of workload excess or stress. This is my number one priority at the moment.
Posted @ Wednesday, September 18, 2013 6:30 PM by Jennifer Clauson
Post Comment
Name
 *
Email
 *
Website (optional)
Comment
 *

Allowed tags: <a> link, <b> bold, <i> italics