Getting started
Bring a protocol question, your team’s priorities and the workflow you want to improve. We’ll focus the demonstration and evaluation plan around them. Start with a non-confidential description.
A focused evaluation
Use these four steps to plan an evaluation. Access, dates, fees and what you will receive must be confirmed in a written agreement.
Start with one question: historical eligibility, assessment purpose, a visit preflight, investigator/site feedback or an amendment handoff. Choose a decision that could change after review.
Record how you handle that task today. Before starting, agree the product version, accepted files, expected documents and people involved.
Follow the proposal, supporting material, specialist response and decision using the agreed capabilities. Keep unresolved questions visible.
Compare quality and effort with the baseline. Check the agreed documents and records. Identify any remaining product, security or quality questions.
Request a proposal tailored to your review task, team and timetable, including fees, duration and support. Explore the public sample without signing up; customer evaluation access is agreed separately.
Your proposal should answer these
The pricing approach is a platform fee plus a fee based on the studies included. Your quote should clearly explain the following.
No prices, allowances, renewal terms or service levels are implied by this checklist. The signed proposal and agreements establish them.
Commercial structure
Shape the engagement around your organisation and studies. Your proposal sets out the platform fee, study scope and included services.
Agree organisation administration, user management, security requirements, evidence access and support.
Specify the studies, contributors, protocol workflow, review records and handover formats covered by the engagement.
Before your evaluation
Use these questions to prepare before speaking with us. Begin with a non-confidential description; agree file handling before sharing documents.
Choose one protocol question, such as a historical eligibility amendment or patient/site burden, and the overlapping functions responsible for examining it. Identify your current document version and the evidence or assumptions reviewers would need.
Bring your requirements for devices, accessibility, identity, hosting, permitted data routes and corporate networks. Agree supported configurations and review the relevant service evidence before introducing study data.
Start with the document handover your writing, quality and regulatory teams need. Clinical-system integrations are future scope, with availability listed on the product-scope page.
Agree the study owner, contributors, reviewers and Sponsor decision responsibilities. Set the training, support contact, response arrangements and escalation route in the engagement plan.
Record time to find and resolve the relevant decision, historical-source accuracy, required-review coverage, unnecessary flags and the effort needed to recover the rationale. Compare the same tasks during the evaluation, with your team assessing quality as well as time.
Estimate your current review effort →Agree permitted output formats, protocol documents, decision records and version history before starting. Specify ownership, access removal, data return and deletion, and who checks the handover.
Explore with your team
Explore the sample workflow, discuss your study priorities and define a focused next step.