How-To Guides

REDCap Logo

(1) Best Practices: Review recommended strategies for project planning, compliance, data quality, governance, user management, and long-term project maintenance.

(2) Project Development: Learn how to plan, build, configure, and test REDCap projects while aligning with IRB-approved study protocols and institutional requirements.

    (3) Moving-to-Production and Making Production Changes: Prepare projects for Production, safely manage post-production changes, and maintain project integrity throughout the study lifecycle.

    (4) Project Closure: REDCap Project Closure Guide

    (5) Surveys and Automated Survey Invitations (ASIs): Build and distribute surveys, automate invitations and reminders, manage survey queues, and improve participant workflows.

    (6) Logic, Calculations & Smart Variables: Use branching logic, calculated fields, action tags, and smart variables to build more dynamic and automated REDCap workflows.

     

    (7) e-Consents: The REDCap eConsent Framework supports secure electronic consent workflows for both in-person and remote research participation.

    (8) Longitudinal Projects: Build projects with multiple visits, events, repeatable instruments, and study timelines.

    (9) Identifiers & Sensitive Data: Guidance for handling identifiers, PHI, and confidentiality requirements.

    (10) Optional Modules & Customization: Extend REDCap functionality with optional modules and custom features.

     (11) NIH Data Sharing: Prepare REDCap data for NIH repositories and NDA submissions.

    (12) Citing REDCap: Recommended citation language and REDCap publication references. View Resource | View Guide 

    (14) Securing Your Project:

      1. Additional Data Management Resources. Review these guides for additional ways to help you manage your project:
      2. Project Development Strategies. These resources focus on project setup, development workflows, and testing strategies before moving projects into Production.
      3. User Access: Guideline on user access oversight, sponsor responsibilities, and project user management workflows.
      Page 2-1