The GCU site authorization letter: who signs it, what it must name, and why files stall on it

What does GCU mean by site authorization?

Authorization is permission from whoever controls the place, the people or the records your procedures touch. GCU's Office of Academic Research treats it as a precondition rather than an attachment: its own checklist opens by saying that site authorization is required before applying to the board. Recruit through an employer's distribution list, sit in a school library with a voice recorder, ask an administrator for a file of test scores — each of those is an activity at somebody's site, and each needs that somebody's written yes before the board will read the rest of your file.

Two routes run under the same name, and confusing them is expensive. The first is the one most candidates need: an external organisation — a district, a clinic, a company, a non-profit — grants permission by letter, and that letter travels with the IRB application. The second applies when the site is Grand Canyon University itself. That request goes to the Office of Academic Research on its own checklist, which asks for written approval from the deans concerned, the chair-approved proposal, the instruments, and a data use agreement where archival records are involved. The same checklist records a moratorium on sampling the university's own enrolled population and expects an affiliation with GCU beyond enrolment. Any design that quietly assumes access to GCU's own people should meet that page early.

Who has the authority to sign the letter?

The board is not checking for enthusiasm. It is checking that the signature belongs to someone who can bind the organisation, and the most willing helper is frequently not that person. A charge nurse, a department manager, a friendly principal — each may be delighted by your project and still lack the standing to authorise research on the organisation's behalf. GCU's template answers the commonest procedural worry directly: a wet signature is preferred, an electronic signature is sufficient. It also asks for the signer's printed name, title and signature date, which is how a board tests authority without an interrogation — a title tells the reader whether this person can grant what the page grants.

Layered settings need layered permission. GCU's template says plainly that data collected in a school requires permission from the district office and from each school, because individual schools set their own conditions on what may be collected and how staff may help. The same logic runs through health systems, correctional settings and any site that operates a review body of its own: one letter per authority, each naming what that authority actually controls. If a site runs its own IRB, expect its review to sit alongside GCU's rather than replace it.

What must the letter name, line by line?

GCU's sample is written as scaffolding in coloured instructional text, with a hard rule attached: every instruction is deleted, and the letter reaches both the site and the board in black type. What survives that deletion has to carry the following.

1. The addressee and the study. The letter is written to the board, names your study by its title, and names you as the researcher. GCU's template blocks in the university's Office of Academic Research and College of Doctoral Studies address so that the site's official can see who is being written to.
2. The purpose, in lay terms. A short statement of what the study is about, written the way you would explain it to the person signing — not the purpose statement lifted out of chapter one.
3. Every activity the site permits. This is the load-bearing paragraph. GCU's examples are unusually concrete: interviews of a named group in a named room during non-contact hours, a research presentation at a monthly staff meeting, flyers handed out at that meeting, a focus group before opening, de-identified records released by an administrator. Bullets are encouraged, and so is naming the restrictions, limitations and responsibilities the site is taking on.
4. The exact participant criteria. The template asks the site to authorise a specific population, bulleted, and states that this must align exactly with the inclusion and exclusion criteria in the consent document, the recruitment material and the application.
5. The protection undertakings. GCU's wording has the official acknowledge that the researcher will supply the approved consent document and recruitment material before recruiting anyone at the site, that the site's name will not appear in publications or presentations, and that the researcher will protect the data.
6. The workplace paragraph, when it applies. If the research runs where you work, GCU supplies a statement that complete confidentiality cannot be guaranteed, because colleagues may infer participation from your role or professional relationships. That sentence belongs in the letter and in the consent document, worded the same way in both. The template also offers an aggregate-results clause for sites that want the findings, and expects it deleted rather than softened where they do not, plus an invitation for the board to raise any concern about the permission directly with the signer.

Two mechanics decide whether a good letter survives its own formatting. The date must cover the whole period of data collection, and GCU treats authorization as something that goes stale: its checklist for doctoral files asks outright whether the site authorization or the permission to use an instrument is outdated, and expects a visible date. Ask too early and the page expires under you; ask too late and everything else sits finished, waiting.