Query management is how a trial catches and resolves bad or missing data before database lock. Capture raises a query automatically the moment a site enters a value that breaks a range or custom edit check, so data managers spend their time resolving real problems instead of hunting for them.
Free sandbox · No credit card · 21 CFR Part 11 aligned
Edit checks / auto-queries
2Type
Range High
Operator
Greater than
Value
180
Priority: High
Type
Range Low
Operator
Less than
Value
80
Priority: Normal
Query raised automatically
Value 192 violates limit (180). Please verify.
3
edit check types: range high, range low, custom value rule
Auto
query raised the moment a rule is broken, no manual review needed
Configurable
priority per rule, so the most urgent queries surface first
Field-level
audit trail on every query and its resolution
How it works
Most systems make a monitor go looking for problems. Capture’s edit checks work the other way: define a range, a comparison, or a custom rule on a field, and the moment a site enters a value that breaks it, a query is raised automatically and routed with the priority you set.
Edit checks / auto-queries
2Type
Range High
Operator
Greater than
Value
180
Priority: High
Type
Range Low
Operator
Less than
Value
80
Priority: Normal
Query raised automatically
Value 192 violates limit (180). Please verify.
The lifecycle
A site enters a value outside the range, or against a custom rule.
The query appears automatically. No one has to notice it manually.
The site corrects the value or explains it, tied to that exact field.
The audit trail keeps the original value, the new value, and the reason, permanently.
Fewer queries in the first place
Some of the most common queries are simple math done by hand: BMI, eGFR, QTc. Capture calculates fields like these automatically and shows them read-only during entry, so they never produce a transcription error and never raise a query in the first place.
BMI (Body Mass Index)
Auto-derivedHeight (cm)
172
Weight (kg)
68.5
Result
23.2 kg/m²
Reference: WHO · shown read-only during data entry
The difference
Before you switch
Edit checks, auto-queries and calculated fields are part of every plan, including the free sandbox.
Every query and its resolution is captured in the same field-level audit trail as the rest of the study.
Edit checks are set per field in the form builder. No separate query tool to configure.
Rebuild your existing edit checks the same way, whichever system you are switching from.
Email support, typically under 24 hours, plus documentation on Enterprise.
Free sandbox with every feature. No credit card, no sales call.
A range high, range low, or custom value rule you define on a field. The moment a site enters a value that breaks it, a query is raised automatically.
Yes. Each edit check has a configurable priority, so the queries that matter most surface first.
Yes. The audit trail keeps the original value, the corrected value, who made the change, and the stated reason, permanently.
No, but they are connected. Query management is what triggers and tracks the review; the audit trail is the permanent record of every change, including query resolutions.
No. Edit checks, auto-queries and resolution tracking are built into the eCRF builder, not a bolt-on module.
Yes. The free sandbox lets you build a form, set an edit check, and enter a value that breaks it, no credit card required.
Keep exploring
CRF builder for clinical trials
Where edit checks and calculated fields are configured.
Audit trail software
How every query resolution gets logged permanently.
ALCOA+ data integrity checklist
Why a clean, attributable correction matters for data integrity.
EDC with drag-and-drop CRF builder
Where edit checks sit inside the wider form builder.
eCRF software
The full form builder query management lives inside.
Free sandbox with every feature. No credit card, no sales call.