Getting through the Capella IRB as a doctoral student

When Capella IRB review is needed

IRB review is generally needed when a study involves human participants or identifiable private information, such as interviews, surveys, observations or access to identifiable records. Some quality improvement projects may be judged not to be research, but that determination is usually made through a review process rather than by the student alone.

Your faculty and mentor will tell you which review your project needs. Ask early, during the proposal stage, so the timeline includes it.

Site approval may also be required. Organizations hosting your study often have their own review or permission process in addition to Capella's.

CITI training and the Capella IRB

Capella typically requires completion of CITI training in human subjects research before IRB submission. The modules cover research ethics, informed consent, privacy and the protection of vulnerable populations, each with a quiz.

Complete the training in your own name and keep the certificate. Many students complete it during the proposal stage, which avoids delays later.

The training is also useful preparation for writing your application, because it explains the principles the IRB applies.

Check whether your site requires its own training too, since some organizations do.

What a Capella IRB application includes

An IRB application usually includes a description of the study, the research questions, the design, participant recruitment, inclusion and exclusion criteria, the consent process, data collection procedures, data storage and protection, risks and benefits, and any site permissions.

Supporting documents typically include consent forms, recruitment materials, interview guides or survey instruments, and site letters. In the DBA, DB FPX 9802 includes a participant protection plan and an ethics review narrative that prepare these materials.

Every element must match the approved proposal. Inconsistencies are the most common cause of revision requests.

Recruitment and consent in a Capella IRB application

Describe exactly how participants will be identified, contacted and invited, and by whom. Explain how you will avoid coercion, especially if you recruit from your own workplace or among people you supervise. Recruitment materials should be clear, neutral and accurate.

The consent process should explain the study's purpose, what participation involves, risks and benefits, confidentiality, voluntary participation and the right to withdraw. Use plain language and follow Capella's consent templates if provided.

If participants are employees of your organization, explain how their decision to participate will not affect their employment.

Data protection in a Capella IRB application

Explain how data will be collected, stored, accessed and eventually destroyed. Describe de-identification, such as replacing names with codes, and secure storage, such as encrypted files or password-protected systems.

State who will have access to the data and how long it will be kept. If you use transcription services or software, explain how confidentiality is protected.

The IRB looks for realistic, specific protections rather than general assurances.

For example, state that audio recordings will be stored on an encrypted drive, transcribed with names removed and deleted after a set period. That level of detail shows the board you have thought it through.

Risks and benefits in a Capella IRB application

Every study has some risk, even if minimal, such as discomfort answering questions or the risk of a confidentiality breach. Describe risks honestly and explain how you will reduce them, such as allowing participants to skip questions or providing resources if a topic is sensitive.

Describe benefits accurately. Direct benefits to participants are often limited; benefits to knowledge or practice are more common. Avoid overstating either.

Studies involving vulnerable populations, such as minors or patients, require additional protections and justification.

Common reasons for Capella IRB revisions

The most common reasons for revisions are inconsistency with the proposal, vague recruitment or consent procedures, inadequate data protection, missing site permissions and recruitment that could feel coercive.

Others include consent forms with technical language, interview questions that go beyond the study's scope and missing details about how data will be destroyed.

Reading your application against the proposal and the IRB's guidance before submission prevents most of these.

When revisions are requested, respond to each point clearly and resubmit promptly. A table listing each comment and your change helps reviewers confirm the fixes quickly.

Planning the Capella IRB timeline

IRB review takes time, and revisions add more. Plan several weeks for review, and more if revisions are needed or if site approvals must come first. Submit as early as your proposal approval allows.

Data collection cannot begin until approval is granted, so the IRB timeline shapes your project schedule. Build buffers so a delay does not push your project into extra sessions.

Keep copies of all approvals and any approved modifications. If your study changes after approval, you may need to submit a modification before making the change.

After Capella IRB approval

Once approved, follow the approved procedures exactly. Use the approved consent forms and recruitment materials, collect data as described and protect it as promised.

If something changes, such as a new site or a revised interview guide, submit a modification and wait for approval. Report any unexpected problems, such as a confidentiality breach, as the IRB requires.

At the end of the study, close it out according to the IRB's process.

Keeping a simple log of approvals, modifications and any reported issues makes this straightforward.

Getting help with the Capella IRB

Your mentor and faculty are the first source of help, and Capella's IRB office publishes guidance and templates. The participant protection plan and ethics narrative in DB FPX 9802 prepare DBA students for the application.

Some students work with doctorally qualified writers on these documents, describing their own study design and procedures. The application, CITI training and submission remain the student's responsibility, and the documents must describe the study exactly as it will be conducted.

Asking questions early, before submission, is the fastest way through review.

Capella IRB for quality improvement projects

Many DNP and some DBA projects are quality improvement projects rather than research. These may still need review to determine whether they count as research and what protections apply. Your faculty will guide you through the determination process.

Even when a project is judged not to be research, sites often require their own quality committee approval, and data protections still matter. Describe your project, data and protections as carefully as you would for full review.

Ask early which path applies, because the answer changes your timeline.