Site Operations

Research software should solve a visible operating problem

A grounded approach to evaluating site operations software, with clear workflows, accountable owners, and evidence of useful improvement.

Unlabeled task cards and an analog timer on a research operations desk.

Research sites rarely need another place to enter the same information. They need a reliable way to know what is due, who owns it, and which record can be trusted when systems disagree.

This article was originally published under a Study Catalyst title, and its original URL remains in place. The framework below applies to any operations product; it does not establish that a particular product has been clinically validated or meets every site's regulatory obligations.

Name the operating problem first

A useful problem statement describes an observable gap. “We need better efficiency” is too broad. “Completed study visits are being reconciled against payment records only at month-end, leaving discrepancies unresolved for weeks” identifies work that can be redesigned.

Write down the current trigger, owner, source record, expected result, and common exception. Estimate the effort using a defined sample period. Separate the amount of work from the proportion completed correctly; reducing clicks is not useful if errors become harder to detect.

Decide which record is authoritative

A site may use a clinical trial management system, sponsor portal, laboratory portal, finance system, scheduling tool, and local trackers. Identify the authoritative record for each important fact. A visit marked complete on a calendar may not establish that all protocol-required work or billable conditions have been met.

For payment reconciliation, distinguish completed activity, supporting evidence, invoiced amount, contractual adjustment, payment received, and unresolved difference. Combining these into one “paid” checkbox hides questions that matter to operations and finance.

The purpose is not to force all work into one application. It is to make the relationships between records explicit and maintainable.

Give exceptions an owner

Automation often handles the routine path well. Ask what happens when a visit is rescheduled, a procedure is not performed, a participant withdraws, or a sponsor disputes an invoice item.

Each exception needs an owner, status, supporting evidence, and next review date. Staff should be able to understand the next action without reconstructing a long email chain. Keep medical and financial judgments with the people qualified and authorized to make them.

Test with realistic synthetic records

Use a small set of test cases that reflect actual work without using participant information. Include a straightforward completed visit, an incomplete visit, a corrected record, a duplicate event, and a change in staff responsibility.

Confirm what users can see and edit in each role. Test exported records, history, and recovery from an interrupted task. If the product connects to another system, verify behavior when the connection fails and when information is corrected later.

Record the result of each test. A demonstration that succeeds once is a starting point, not a substitute for an implementation assessment appropriate to the system's intended use.

Measure adoption and usefulness separately

Login counts show that people accessed the system. They do not show that the work improved. Useful measures might include the age of unresolved reconciliation items, the proportion of required records complete before a visit, or the time needed to prepare a defined operational report.

Choose a baseline and use the same definitions after implementation. Note changes in study mix or workload that could explain a difference. Avoid attributing every improvement to software when staffing or process changes happened at the same time.

Plan for ownership after launch

Assign responsibility for user access, configuration changes, support requests, training, and periodic review. Confirm the process for departing staff and how the organization retrieves its information if a contract ends.

Document the workflow in a concise SOP and review the exception queue in the weekly operating meeting. Software is useful when these everyday responsibilities become clearer and easier to carry out. It cannot replace them.

Sources & further reading

  1. FDA: E6(R3) Good Clinical Practice
About this guidance

Educational information, not medical advice or a study-specific compliance determination. This article is not represented as independently clinically reviewed. Images are editorial illustrations.

KEEP YOUR PERSPECTIVE GROWING

Continue reading.