Capella IRB consent form requirements: the required elements, the reading level, and version-matching
Capella's IRB expects consent on Capella's own template, with every required element of 45 CFR 46.116 present, written so the person signing can actually understand it, and matched line for line to the research plan that Scientific Merit Review approved. The board does not waive consent itself. The consent form is the most-revised document in a Capella file, and most of those revisions are not about what it says. They are about which version was attached.
Use Capella's consent template, keep every 46.116 element, write in plain language a participant can read, and attach the one version that matches the approved research plan. Capella does not waive informed consent; a waiver of the signature is a separate question.
Does every Capella IRB application need a consent form?
If people are involved, yes. Capella's doctoral-support guidance states that informed consent must be actively obtained from participants before any data are collected, and that Capella's IRB "does not waive informed consent or allow for implied informed consent." Its Research Integrity SOPs put the same rule in regulatory terms: consent from all participants or their legal guardians, prior to any research-related interaction, under 45 CFR 46.111, 46.116 and 46.117. The application itself asks for the consent form as an upload; Capella's FAQ on completing the application lists "informed consent form using the official Capella University template" among the documents a new-data study must attach.
Two distinctions are worth getting right early. First, consent is different from documentation of consent. Capella's SOPs say the IRB may allow a waiver of documentation under 45 CFR 46.117(c), which is the rule that lets an anonymous online survey proceed on an information sheet and a "continue" click rather than a signed page, where the only link between participant and study would be the signature itself, or the research is minimal risk and involves nothing that normally needs written consent. That is a waiver of the signature, not of consent. Second, records-based research uses a different application; if you are only analysing existing records, the consent question becomes a question about how those records were originally collected and whether identifiers travel with them. Capella's current IRB portal governs both distinctions.
What elements must the form contain?
Capella's template is built around the federal elements, and the board reads the form against them. The 2018 Common Rule requires consent to begin with a concise, focused presentation of the key information a reasonable person needs to decide, to be in "language understandable to the subject," and to contain no exculpatory language that asks anyone to waive a legal right. The basic elements of 45 CFR 46.116(b) then follow, and each one has a place on the template:
- A statement that the study involves research, its purposes, the expected duration of the person's participation, the procedures, and which are experimental.
- Reasonably foreseeable risks or discomforts.
- Benefits to the participant or others that may reasonably be expected. Capella's SOPs add that an incentive may not be listed as a benefit; it is disclosed separately, with its specifics.
- Appropriate alternatives, where any exist.
- The extent to which confidentiality of identifying records will be maintained. On Capella's template this is the section headed "How will I protect your privacy and confidentiality?", and Capella's guidance on video-conferencing asks that the platform's current privacy link be placed there if interviews run on Zoom or similar.
- For more than minimal risk, compensation and treatment if injury occurs.
- Whom to contact about the research, about rights as a participant, and about research-related injury.
- That participation is voluntary, that refusal carries no penalty or loss of benefits, and that the person may withdraw at any time.
- One of two statements about identifiable information: either that identifiers might be removed and the data used for future research without further consent, or that they will not be.
The additional elements of 46.116(c) apply when they are relevant, and the ones that surface in Capella files are the approximate number of participants, the circumstances under which the researcher may end a person's participation, any costs to the participant, and what happens to data if someone withdraws. The board expects the form to say whether data collected before withdrawal are kept or destroyed, and the answer must match the data security plan.
What reading level does Capella's IRB expect?
The regulation sets the standard in words, not grade levels: information must be in language understandable to the person signing. Capella's template is written to that standard, and the board reads your insertions against it. The practical test is whether the people you are recruiting, reading alone, without you in the room, could tell a friend what they are being asked to do, what could go wrong, and how to get out. Most boards, and most plain-language guidance, work to roughly an eighth-grade reading level for the general public; Capella's current template and portal govern the expectation for your study, and a form aimed at clinicians can assume clinical vocabulary where a form aimed at patients cannot.
Three habits keep the form readable without losing the required content. Write in second person and short sentences. Name the procedures as the participant will experience them ("a recorded conversation with me, once, at a time you choose" rather than "a semi-structured qualitative data-collection session"). And resist pasting the methodology chapter into the consent; the research plan exists for the board, the consent exists for the participant, and each is written for its reader.
What does version-matching mean, and why is it the usual return?
The board reads the IRB application, the SMR-approved research plan and the consent form as one document. Every fact that appears in more than one of them must be the same fact. The consent forms that come back are rarely missing an element. They are stamped to an earlier protocol: the plan now says two interviews, the consent still says one; the plan added a second site, the consent names the first; the plan moved from in-person to video, the consent still describes a room. Each difference is a return, because the participant would be consenting to a study that is not the one approved.
| Fact | Where it also appears | Typical drift |
|---|---|---|
| Procedures and their order | Research plan; application | An interview added or dropped after SMR |
| Time required of the participant | Research plan; recruitment materials | Flyer and consent state different times |
| Sites and setting | Research plan; site permission letters | A second site named in one document only |
| Recording and transcription | Data security plan | Consent silent on audio recording the plan describes |
| Storage, access and destruction of data | Data security plan; application | Consent promises destruction on a different schedule |
| Incentive | Application; recruitment materials | Amount or timing differs between flyer and consent |
| Sample size and eligibility | Research plan; recruitment materials | Inclusion criteria tightened in one document |
The discipline that prevents this is simple and tedious: one consent file, named with its version and date in the footer, regenerated from the plan every time the plan changes, and the same file uploaded to the application, sent to the site, and used in the field. After approval the rule hardens. Policy 3.03.01 requires IRB approval before modifying approved "procedures, sites, or forms," and the SOPs carve out only typo and grammar fixes to participant-facing materials, which still have to be summarised to the IRB Office by email before the revised version is used. A consent form edited in the field without that step is a compliance problem, not a style choice.
What about signatures, copies and how consent is actually obtained?
Where consent is documented, 45 CFR 46.117 requires a written form approved by the IRB and signed, on paper or electronically, with a copy given to the person signing. The application asks how you will obtain consent, and the answer must describe a process that protects against coercion: who presents the form, where, with how much time to read and ask questions, and what happens if the person declines. If you hold any authority over the people you recruit (a manager interviewing staff, a nurse educator surveying her own unit), the consent process is where the board looks hardest for undue influence, and the wording has to make refusal visibly costless. Capella's SOPs also require the form to state incentives specifically, and forbid incentives that are coercive in nature.
Children and others who cannot consent for themselves add parental permission and assent forms under Subpart D; Capella's SOPs require both. Translation into another language needs a translated consent and a stated process for verifying it. None of these happen before approval. Capella's guidance is unambiguous that recruiting and consenting may not begin until the study reads Approved in the portal and the approval letter has issued, and that approval with conditions does not unlock either.
How does the consent form fit the rest of the file?
The consent form is one of the documents the practice builds and version-matches inside the whole process, because it is the document the board reads most closely and the one most often stamped to the wrong protocol. We build it from the approved plan rather than from a previous draft, stamp it, and keep it in step with the data security plan, the recruitment materials and the application so that every number and every promise appears identically in each. The data security plan article shows the section the consent's confidentiality paragraph must mirror, the recruitment materials article shows why the flyer's time and incentive have to agree with the consent, and the how-it-works page shows where consent sits in the three moves. The study stays yours; the board's decision is its own.
What to do next
If your consent form exists in more than one version, or was written before Scientific Merit Review finished, the useful next step is a read against the plan before the board does one. Request the free application review: send the plan and the consent, and a consultant will read the consent the way the reviewer will, element by element and fact by fact, and tell you exactly what would come back. If the form is clean, you will hear that too, and nothing is filed or billed until you say so.
Sources
- Capella University, Doctoral Support FAQ, "Do I need to obtain informed consent?" — capella.libanswers.com/doctoralsupport/faq/132846
- Capella University, Doctoral Support FAQ, "How do I complete the IRB Application?" — capella.libanswers.com/doctoralsupport/faq/132954
- Capella University, Doctoral Support FAQ, "What security issues should I know to use services like Zoom or Skype for my research?" — capella.libanswers.com/doctoralsupport/faq/301352
- Capella University, Doctoral Support FAQ, "When am I able to start recruiting, consenting, and collecting data?" — capella.libanswers.com/doctoralsupport/faq/132932
- Capella University, Research Integrity Standard Operating Procedures (RI SOPs), version 6.0: Informed Consent, Waiver of Documentation, Incentives for Participation, Notification of Modifications — capella.edu/assets/pdf/policies/HRPP-SOPs.pdf
- Capella University, Policy 3.03.01 Human Research Protections — capella.edu/content/dam/capella/PDF/policies/3.03.01.pdf
- 45 CFR 46.116, General requirements for informed consent — law.cornell.edu/cfr/text/45/46.116
- 45 CFR 46.117, Documentation of informed consent — law.cornell.edu/cfr/text/45/46.117
- 45 CFR 46.111, Criteria for IRB approval of research — law.cornell.edu/cfr/text/45/46.111
Capella's template and portal instructions change; where this article and Capella's current handbook or IRB portal differ, the portal governs. This practice is independent of Capella University.