About This Calculator
A REDCap end survey action can stop a survey when a rule is met. This calculator helps plan that rule before launch. It checks score cutoffs, survey outcomes, completion rates, and data quality signals. It is useful for screening surveys, consent checks, eligibility reviews, and follow up workflows.
Why End Survey Logic Matters
End survey logic protects participants and saves review time. A project may need to stop a form when consent is denied. Another project may stop the survey when an eligibility score is too low. Some teams also stop surveys when a safety score reaches a high value. The rule should be clear before data collection starts.
Key Metrics Reviewed
The calculator separates invited records, started records, completed records, partial records, and ended records. It also reviews exclusions, duplicate responses, and consent denials. These values show whether the survey flow is balanced. A high end survey rate may be correct. It may also signal a strict cutoff or confusing question design.
Score Based Decisions
The score section compares the entered score with the cutoff. You can choose whether the survey should end below the cutoff, at or above the cutoff, or only at the exact cutoff. The result explains whether the action should trigger. It also shows the score percent and the gap from the cutoff.
Completion Planning
Completion rate is a core measure for survey quality. This tool compares valid completion rate with your target rate. It also estimates total completion time and incentive cost. These values help teams plan staffing, recruitment, and monitoring needs.
Data Review Notes
Before publishing a project, compare the category totals with the started records. If the entered categories exceed starts, the tool flags the totals for review. This does not replace REDCap testing. It supports a careful prelaunch check.
Best Practice
Test several examples before enabling the survey. Try scores just below the cutoff. Try scores equal to it. Try scores above it. Confirm that the final action matches the protocol. Save the exported report with project notes. Clear documentation helps audits and later team handoffs. Use the notes during weekly checks. Update thresholds only after protocol approval, stakeholder review, and validation testing in a copy project first.