In REDCap, an instrument is a collection of fields organized as a form or survey. In clinical research language, an instrument is often equivalent to a CRF or eCRF. Examples include Screening Form, Enrollment Form, Medical History Form, Laboratory Results Form, Follow up Form, Adverse Event Form, and Study Completion Form. A well-designed project usually contains several focused instruments rather than one very large form.

Dividing data into instruments has practical advantages. It allows different parts of the study workflow to be completed separately. It makes forms easier for users to navigate. It supports permissions, because some users may need access to one instrument but not another. It improves monitoring, because form completion status can be reviewed by instrument. It also supports repeated forms, such as adverse events or medication logs.Each field in an instrument has a variable name, field label, field type, and optional settings.
REDCap offers several field types, including text boxes, notes boxes, calculated fields, multiple choice fields, checkboxes, dropdowns, file upload fields, sliders, descriptive text, yes/no fields, true/false fields, and section headers. Choosing the appropriate field type is one of the most important design decisions because it affects data quality and analysis.
Text fields are flexible but require validation to prevent invalid entries. They are useful for dates, numbers, short identifiers, and values that do not have fixed categories. Notes fields allow longer text but should be used carefully because long free-text entries are harder to analyze and may contain confidential information. Radio buttons are useful when only one option is allowed. Checkboxes are useful when multiple responses are allowed, but they require careful handling during analysis because each choice may export as a separate variable. Dropdown fields can save screen space when there are many options.
Descriptive text fields do not collect data but provide instructions, section explanations, or reminders. They are useful for guiding users through complex forms. Section headers divide instruments into meaningful parts, such as Eligibility, Baseline Vital Signs, Laboratory Results, and Outcome Assessment. Good use of descriptive text and section headers improves usability without adding unnecessary variables.
The field type should reflect both data entry needs and analysis needs. For example, if the study needs to calculate age from date of birth and enrollment date, these should be captured as dates rather than text. If a variable must be summarized by category, it should use coded options rather than free text. If a laboratory result has units and a plausible range, validation should be applied. A database that captures data in the correct type reduces cleaning work
later.