Meet recruitment commitments, maintain staff readiness and manage sponsor-specific requirements with AQ Platform, from site activation through participant follow-up.

SMOs work in two ways, and many do both. Sponsors and investigators expect the same proof either way: every person on the study follows current procedures, holds valid training and works within delegated duties.
New openings and acquisitions arrive with their own habits. AQ applies your SOPs, file templates and role model to each site from day one, and shows which sites have procedures and training in force.
Your staff work inside hospitals run by someone else. AQ holds your procedures, training records, qualifications and delegation evidence for every placed person, within the arrangements agreed with each host.
For each pressure, the current approach and how AQ replaces the manual work involved.
Protocol amendments and SOP revisions pass through four stages before an SMO can show they are in force at every site. Each hand-off between unconnected systems is where a site falls behind.
Each module covers a distinct part of multi-site delivery. Users, roles, studies and sites are set once in Admin and apply across all of them.

Implementation follows the sequence agreed during onboarding.
Documents come into AQ by upload, and reports and registers export for sponsors and inspectors. Any further data exchange is scoped per study.
AQ Platformconnects with
Upload into AQ
Export from AQ
Yes. An SMO can start with the modules that address its biggest pressure, for example QMS and Digital DoA for training and delegation, or eISF for site files, then add sites and modules over time. Users, roles and sites are set once in Admin, so each new module uses the same set-up.
AQ adds the quality and evidence layer across your sites: controlled SOPs, training, delegation, site and pharmacy files, and CAPA. Your existing system keeps scheduling, finance and data capture. The implementation plan sets which records live where.
No. Sponsor-mandated systems remain the record for the purposes the sponsor defines. AQ holds the SMO’s operational record, and its eTMF holds content the sponsor has delegated.
Documents come into AQ by upload, including bulk upload. Reports, registers and audit logs export to Excel or PDF for sponsors and inspectors. Data entry into sponsor EDC and IRT stays in those systems. Any further data exchange is scoped per study during implementation.
The investigator decides and signs each delegation and keeps oversight. The SMO answers for the procedures, training and qualifications of the staff it supplies. The host institution sets local arrangements. AQ records each party’s evidence. The responsibilities themselves come from your contracts and agreements.
The central team registers the site in Admin, creates its site files from existing templates, assigns roles and allocates the controlled SOPs. Staff then complete their training in My Learnings.
Yes. CTMS shows screening and enrolment against target, visit schedules and capacity for each site, and the same view rolls up across your network.
Pick the workflow that costs your team the most time. We run it in the live platform against your operating model: owned sites, placed staff, or both.
You leave with a clear view of how AQ handles that workflow at your sites and which modules it needs.
See how the modules connect on the AQ Platform overview, read published case studies, or compare AQ for CROs and sponsors.
Pick a module, your organisation type, or both — we'll match the guides and email them to you.
Try one filter at a time, or clear to see all guides.

✓ Written for first-in-human & Phase 1 sites
✓ Inspection-ready checklists & templates
✓ Aligned to MHRA, FDA & EU Annex 11