If you have ever sat on a question for two days because you were not sure whether it belonged to the monitor, the project manager, or the medical monitor, you already understand the real cost of an unclear communication chain. The question was answerable. Finding the right inbox was the hard part.

Justin Coffeen has worked studies in orthopedics, oncology, and hepatology from his base in Lakewood Ranch, Florida. He came to research after years of clinical work and instruction, and the habit he brought with him is straightforward. Map the escalation path before the study opens, not during the first problem.

The three questions that route everything

Most site questions fall into one of three categories, and each has a different owner.

A question about how a participant should be managed clinically goes to the investigator, and if it extends past the investigator’s judgment about protocol intent, it goes to the medical monitor. A question about how the protocol should be interpreted operationally goes to the monitor or the project manager. A question about a system, a payment, a supply, or a schedule goes to whoever the sponsor assigned that function. Sorting a question into the right bucket takes seconds once you know the buckets exist.

The categories overlap more often than a clean diagram suggests, and that is fine. A question that sits between two owners gets sent to both with a note saying so. What does not work is holding it while deciding which single recipient is technically correct.

The contact list goes stale faster than anyone expects

Study staffing changes. Monitors get reassigned, project managers move to other programs, and the person listed on the site initiation slide deck may have been gone for months.

Coffeen keeps a live contact record rather than relying on a deck from activation, and he confirms it at each monitoring visit while the monitor is in the room and can correct it in real time. This is unglamorous work. It is also the difference between a safety question reaching a medical monitor in an hour and reaching them the following week.

Put it in writing even when the call was easier

Phone calls resolve things quickly, which is exactly why they are dangerous. A verbal answer from a monitor about how to handle an out-of-window visit is not documentation, and six months later nobody remembers who said what.

The fix is small. After a call that settled a question, send a short confirming message stating what was asked and what was agreed, and keep it with the study correspondence. Coffeen does this routinely, not because he distrusts the people he works with, but because the study record has to stand on its own after everyone involved has moved on to other work.

This habit also protects the person who gave the answer. A monitor who told a site something in good faith, based on what they understood at the time, is better served by a written record than by a later disagreement about recollection. Documentation is not an accusation.

Silence is a finding waiting to happen

Sites sometimes hold a problem internally while they try to solve it, hoping to bring the sponsor a resolution rather than a complication. The instinct is understandable and it consistently makes things worse.

A deviation reported the day it is identified is a managed deviation. The same deviation surfacing at a monitoring visit six weeks later is a pattern question about the site. Coffeen’s position is that the sponsor and the CRO are not an audience to perform for. They are part of the team responsible for the study, and they cannot help with a problem they have not been told about.

Communication structure sounds like an administrative topic until the moment it is not. Every escalation chain in research exists because information failed to reach someone in time, at least once, somewhere. The chain is the correction.

Coffeen has watched the timing effect play out in both directions. Sites that report early get help, and sometimes get told the issue was not a deviation at all. Sites that report late get scrutiny, regardless of how well they eventually handled the underlying problem.