Monitoring work is judgment work. These are the eight domains a CRA role turns on, what good looks like in each one, and how to build, practice and evidence them.
Each domain describes observable work, not a personality trait. A reviewer looks for these behaviors in what you produce, not in how you describe yourself.
Each one described by observable work.
Behaviors a reviewer can look for.
Learn it, practice it, prove it, put it to work.
Deciding what a visit needs to cover, in what order, and with what evidence, before arriving at the site.
What a reviewer looks forComparing what the record says with what the source shows, and knowing which differences matter.
What a reviewer looks forRecognizing a protocol deviation, classifying it honestly, and escalating on the right timeline.
What a reviewer looks forChecking that safety events were recognized, recorded, assessed and reported inside required windows.
What a reviewer looks forKeeping the trial master file and the site file current, complete and version correct.
What a reviewer looks forTurning findings into actions a site can complete, then confirming they were completed.
What a reviewer looks forWriting a report an auditor, a sponsor and the next monitor can all rely on.
What a reviewer looks forFocusing oversight where errors would harm participants or the credibility of the data.
What a reviewer looks forCapability is built in order. Each step below produces something the next step can use.
Build the underlying knowledge in BORAKA Academy, from monitoring fundamentals to safety reporting and documentation practice.
Work role-realistic monitoring situations in BORAKA Academy casebooks and simulations, where the decisions are yours to make and defend.
Submit casebook work for documented human review against a published rubric version. Only reviewed work can produce verified evidence.
Every domain has a module that teaches it, a free practice decision that exercises it, and a reviewed casebook task that evidences it.
Visit types, what each one has to cover, and how a plan is built from the protocol and the site's open issues.
Practice: Triage the site risks you would act on before the visit.
Casebook task: Rank the risks at a high-enrolling site and say why that order holds.
ALCOA expectations, what source has to show, and how a record is traced back without over-reading it.
Practice: Decide which records a targeted review has to reach.
Casebook task: Set the scope of a targeted review and defend what you left out.
How a deviation is recognized, classified honestly and escalated on the right timeline.
Practice: Choose the first action on the day a finding appears.
Casebook task: State your first action and the reasoning a reader could follow.
Reporting windows, causality and severity records, and following an unresolved event to closure.
Practice: Handle an unreported serious event inside the visit.
Casebook task: Write the findings and the corrective actions the site has to complete.
Delegation, training and version control, and what a complete site file has to hold.
Practice: Work a delegation and product accountability gap.
Casebook task: Close a filing gap with a dated, owned corrective action.
Turning a finding into an action a site can complete, with owners and dates agreed at the visit.
Practice: Decide how you close the visit with the site team.
Casebook task: Draft the communication to the investigator and the site team.
Recording what was reviewed, the sample, the method and the decision behind each query.
Practice: Judge a deviation trend from the data you were given.
Casebook task: Produce a visit report summary an auditor and the next monitor can rely on.
The principles that decide where oversight belongs when effort has to be proportionate.
Practice: Weigh participant safety against data credibility in a live call.
Casebook task: Design a proportionate monitoring plan for the rest of the study at this site.
Evidence is only useful if the person reading it can trust how it was produced.
Work is scored against criteria that are written down before the work is submitted, with the rubric version recorded on the result.
A person reviews the submission and records the reasoning behind the decision. Practice feedback is developmental and is never presented as a verified result.
A demonstrated capability keeps its date, its criteria and its review trail, so it stays readable outside the place it was earned.
