The site permission letter for Capella IRB: what it must say, who must sign it, and why it's the slow one
Capella's IRB will not accept implied permission, a verbal yes, or a supportive email from a colleague. It wants a letter on the organisation's own letterhead, signed by someone with authority to grant access, dated recently, stating in plain words that you may recruit, collect, or use records there. The letter is never the hardest document to write. It is the hardest to obtain, because someone else signs it on their own calendar, and the file cannot finish without it.
Capella requires site permission on official letterhead, signed by an authorised official, dated close to submission, and naming the permitted research activities. Implied consent does not count. Request it as soon as the research plan settles; that signature is the slowest step in the file.
When does a Capella IRB application need a site permission letter at all?
Capella's published guidance draws the line at activity, not geography. Permission is required when you will be recruiting from a site, using a site's non-publicly available data, or conducting other study-related activities there. That covers hospitals, clinics, schools, businesses, non-profits and military organisations, and it reaches further than most expect: Capella's FAQ notes that recruiting through an organisation's email lists, websites or newsletters also counts, so an "online-only" survey sent through an employer's distribution list still needs the employer's letter.
The Research Integrity SOPs say it bluntly: researchers must have written authorisation from an authorised official to recruit participants, use directory information, or conduct research involving another institution, organisation or corporation, and "implied consent does not constitute adequate site permission." If the study touches no organisation's people, premises or records, a letter is not required. For anything else, assume it is, and confirm against Capella's current IRB portal.
One category is its own process. Research that recruits Capella's own learners, alumni, faculty or staff, or uses Capella's data, needs permission through Capella's formal review, separate from IRB review and, by the SOPs' wording, granted in limited circumstances. That request goes in early, or the project is redesigned.
What must the letter actually say?
Capella publishes the requirements and a template, with a warning: the template is a guide to what a sufficient letter looks like, not a form to download and fill in. Capella's FAQ on the template spells out four things and the SOPs add the fifth. A usable letter is:
- On the organisation's official letterhead. A letter on plain paper, or a forwarded email, is not a site permission letter to this board.
- Signed by an authorised official. The SOPs name "an IRB Chair (if applicable) or other official within the organization." The FAQ calls for a hand signature; whether the organisation's own electronic signature practice is accepted is for the portal's current wording to say.
- Dated close to submission. Capella's published guidance has set a window of six months between the letter's date and the IRB submission. A letter obtained long before the file is ready has to be re-issued, which is the second reason to time the request carefully. Confirm the current window in Capella's IRB portal.
- Explicit that you have permission to conduct the research at the organisation, in those words or words that cannot be read any other way. A letter that says the organisation "supports" the project, or "looks forward to the findings," has not granted anything.
- Specific about which research activities are authorised. The FAQ asks the letter to state what the site is permitting: recruiting its employees or clients, distributing a survey through its channels, interviewing on premises, accessing a named set of records, or some combination. If the application says you will pull chart data and the letter only mentions interviews, the letter does not cover the study.
Beyond those five, the letters that move without comment name the study title as it appears on the approved research plan, name you as the researcher, and, where records are involved, name the records and whether they arrive with identifiers or de-identified. Each line is something the board would otherwise have to infer, and boards do not infer.
Who must sign it, and how do you know they have the authority?
The signatory question sinks more letters than the wording does. The manager who is glad to help is rarely the person who can authorise research on the organisation's behalf. The SOPs place the burden on you: it is "incumbent on the researcher to determine who has the authority to issue permission," and where that is unclear the IRB may ask for organisational charts or policies, or contact the site directly. A letter signed by the wrong person is not rejected rudely; it is simply not permission.
Three settings almost always need more than one signature. Capella's guidance singles out schools (district and building), Veterans Affairs facilities, and military sites (commander plus research office); its doctoral "research red flags" page adds correctional systems, where each facility runs its own layered approval. Any site with its own IRB will usually require that IRB's approval as well as Capella's, and the red-flags page cautions that a study needing more than two or three separate IRB processes may not be feasible at all. Find that out before the plan is stamped.
Then there is the contract. Some sites only grant access under an affiliation agreement, memorandum of understanding or data-use agreement. If it names Capella University as a party, or asks a mentor or chair to agree to conditions, it goes to the IRB Office for Capella's legal review before anyone signs, and neither you nor your mentor may sign on Capella's behalf; Policy 3.03.01 repeats the rule, and some data-use agreements Capella cannot sign at all. Even an agreement that binds only you is uploaded with the application, signed or not, so the board can check its conditions against Capella's practices.
Why is it the slow one?
Every other document in the file is under your control; you can rewrite a consent form tonight. The letter depends on an organisation's internal routing: a legal or compliance reading, a signature authority who is away, a committee on its own schedule, a site IRB with its own queue. None of that moves because your file is ready, which is why site permission is drawn on this site as a tributary that joins the route at the IRB gate but starts much earlier, and why the most common note in a free review is not "rewrite this" but "request this now."
The delay compounds with the dating rule. Ask too early and the letter goes stale; ask too late and the file sits complete, waiting on one signature. So open the conversation early, tell the site what the letter must contain, and have it issued once the research plan is through Scientific Merit Review and the application is being assembled. We draft the letter for signature so the site's official is approving a page, not composing one.
What happens to the file if the letter is missing or unusable?
Capella's SOPs list "documentation of site permission" among the examples of a study being approved with conditions rather than approved. That sounds gentle. It is not an approval: Capella's FAQ is explicit that a study approved with conditions may not begin recruitment or data collection until the status reads Approved and the approval letter is in the portal. A missing letter holds the whole study at the last gate with every other document done, and an unusable letter (wrong signatory, wrong activities, stale date) does the same after a round trip.
| What arrived | Why it fails | What replaces it |
|---|---|---|
| An email from a unit manager saying "happy to help" | Not on letterhead, not from an authorised official, grants nothing specific | A letter on letterhead from the official with authority, naming the permitted activities |
| A warm letter of support for the project | Support is not permission; it never says you may recruit or collect there | One sentence stating the organisation permits the research, plus the activities it covers |
| A letter that permits interviews when the plan also pulls records | The authorised activities do not match the application | A letter that names every activity in the approved plan, including the records and their identifiers |
| A letter dated long before the submission | Outside Capella's dating window | A re-issued letter dated close to the filing |
| A data-use agreement the site insists on, not yet reviewed | Contracts naming Capella need legal review first | The agreement sent through the IRB Office early, then uploaded with the application |
What does the letter have to agree with?
The board reads the file as one document. The sites named in the approved research plan, the IRB application, the consent form, the recruitment materials and the letter must all be the same sites doing the same things. A plan approved for one clinic and a letter from a different clinic is drift between the stamped plan and the file, and drift is the most common reason a Capella file comes back, as the step-by-step walk through the Capella IRB route explains. If the site changes after Scientific Merit Review, the plan is amended first and the letter follows; if it changes after approval, Policy 3.03.01 requires IRB approval before the change. And if a study is approved but never started, the SOPs note that resuming it may need updated site permission.
How we handle the letter, from request to upload
The letter is one of the documents we build inside the whole process, because it is the one most often missing when a file reaches us. We list every site and activity that needs authorisation, identify who can sign, draft each letter for signature with the activities and records matched to the plan, follow up with the signatories, and upload the letters with the complete file. The how-it-works page shows where that sits in the three moves; the application checklist shows the letter's place among the other documents. The research and the relationship with the site stay yours; the board's decision is its own.
What to do next
If you are past topic approval and have not yet asked your site for a letter, start now, and start by knowing exactly what it must say. Request the free application review and tell us which organisations your study touches. A consultant will tell you whether each needs a letter, who should sign it, and whether a contract will need Capella's legal review; if you do not need one, we will say so. Nothing is filed until you say so, and the FAQ covers what happens after.
Sources
- Capella University, Doctoral Support FAQ, "Do I need site permission to conduct my study?" — capella.libanswers.com/doctoralsupport/faq/132841
- Capella University, Doctoral Support FAQ, "Is there a template for site permissions?" — capella.libanswers.com/doctoralsupport/faq/132861
- Capella University, Research Integrity Standard Operating Procedures (RI SOPs), version 6.0, sections on Site Permissions, Site Permission that Requires a Research Contract, and IRB Review Outcomes — capella.edu/assets/pdf/policies/HRPP-SOPs.pdf
- Capella University, Policy 3.03.01 Human Research Protections, Researcher Responsibilities — capella.edu/content/dam/capella/PDF/policies/3.03.01.pdf
- Capella University doctoral colloquia, "Research Red Flags" — campustools.capella.edu (Research Red Flags)
- Capella University, Doctoral Support FAQ, "When am I able to start recruiting, consenting, and collecting data?" — capella.libanswers.com/doctoralsupport/faq/132932
- 45 CFR 46.111, Criteria for IRB approval of research (equitable selection; setting of the research) — law.cornell.edu/cfr/text/45/46.111
Capella's templates 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.