Whose signature does a WGU site permission letter actually need?
The signature has to belong to someone who can commit the organisation, not to the manager who thinks the project is a good idea. That is the whole difficulty. Everything else on the page can be drafted in an evening; the name at the bottom is the part that waits on another organisation's calendar, which is why this one sheet decides when the rest of the folder can move.
Someone with authority to grant access to the organisation's people, records or premises. Usually a facility administrator, department head or HR authority — not a peer, and not your own preceptor unless that person genuinely holds the authority. Request it first; it finishes last.
Does a WGU capstone need site permission at all?
Ask a narrower question and the answer arrives quickly: does the project reach into a facility's people, its records, its rooms or its channels? If it does, plan on written permission. If the whole project lives in publicly available material, or in a workplace you personally own and control, it may not. Everything between those poles is a judgement, and it is a judgement the board makes rather than one you announce.
WGU's published application makes the expectation plain. It closes on a reminder: any project reaching into the people of an organisation, an agency or a school district collects the relevant administrator's or workplace supervisor's signature before the application goes in — and in the published version of that form the signature is captured on the consent document itself rather than on a standalone page. Other WGU material lists a signed site authorization form among the supporting documents that travel with the application. Which shape yours takes belongs to WGU's current handbook or IRB portal. Settle it before drafting anything, because the two shapes ask different things of the person signing.
There is a second permission that catches people out, and it has nothing to do with a hospital. WGU's policy handbook puts a separate gate in front of one category of project: gathering information from the university's own learners, its employees, its graduates, or the people who employ its graduates — or reaching for university-held data about any of those groups — calls for sign-off from the Vice President of Institutional Research, or a designee, ahead of the IRB, with the capstone instructor enabling that submission. If your population is a WGU population, that gate opens first or nothing after it moves.
Who actually has authority to sign?
Authority is a property of a role, not of enthusiasm. The charge nurse who will happily hand you the unit is often not the person whose name binds the organisation, and a signature from the wrong level is not rejected unkindly — it simply is not permission, and the file waits again while the right person is found.
Three questions locate the signer faster than a phone tree. Who can authorise an outsider to speak to this organisation's people during working hours? Who can authorise release of this organisation's records? Who answers if something goes wrong and a regulator asks who allowed it? One name usually answers all three; that is your signer. Where the answers diverge — a nursing director for access, a compliance officer for records — expect either two signatures or one signature from someone senior to both.
- Hospitals and health systems: a chief nursing officer, director of nursing practice, department administrator, or the research office where one exists.
- Clinics and small practices: the practice owner, medical director or practice manager, depending on who holds the records.
- Long-term care and community agencies: the administrator of record, not the unit manager.
- Schools and districts: commonly two levels, building and district.
- Your own employer, where you are also the one asking: someone above you, always, so that the permission is not self-granted.
One trap deserves its own line. Your preceptor or practice mentor is not automatically the signer. That relationship exists for the practice hours; the permission question is an organisational one, and boards read a preceptor signature on an access request as a supervisor being helpful rather than an organisation deciding.
What must the page name?
A usable permission page is short and specific. It is not a character reference for you, and it is not a statement that the organisation finds the topic interesting. It says who is permitted to do what, where, and with which of the organisation's assets. Boards read it against the application, line for line, and the mismatch is what they find.
| The line | What it settles for the reviewer |
|---|---|
| The organisation's own letterhead and address | That an organisation is speaking, not an individual with a friendly opinion |
| Your name, and the project title as the application words it | That the permission attaches to this project rather than to a general goodwill |
| The word permission, or a phrase that cannot be read as anything softer | That access has been granted, not admired |
| Each activity: recruiting, surveying, interviewing, observing, pulling records, using internal channels | That every step in the protocol is covered, not just the visible one |
| The records named, and whether they arrive with identifiers attached | That the organisation understood what it released, which is the question a privacy officer will ask later |
| Signature, printed name, role and date | That authority is legible on the page instead of assumed |
The activity list is where most files quietly fail. A page that permits interviews while the application also describes a chart pull has not permitted the chart pull, and a reviewer who notices will say so. Write the activity list from the protocol, not from memory, and keep the two documents in step every time the protocol changes. That habit is the same one that keeps the consent document and the application from drifting apart.
Does signing make the facility part of the research?
This is the question that turns a nervous administrator into a signing one, and most candidates cannot answer it. Federal guidance from the Office for Human Research Protections draws a line it calls engagement. An organisation crosses that line, broadly, in three ways: its own people gather study data by interacting with participants, or they hand over private information that still points at someone, or they are the ones taking consent. The same guidance then lists situations that stay on the near side of the line, and one of those is an organisation — schools, nursing homes and businesses are the examples given — that lets an outside investigator use its premises to meet participants.
So the honest sentence to offer an administrator is this: allowing you in is not the same as the organisation running a study. Where its own personnel start recruiting for you, or pulling identifiable records on your behalf, that changes, and the conversation becomes a different one worth having early rather than at the signature. Some organisations will also route the request to their own board regardless; a facility with an internal review process runs it on its own schedule, and that is a fact to plan around rather than argue with.
Why is it the slowest page in the folder?
Every other document in the file answers to you. You can rewrite an aim statement tonight, redraw an instrument tomorrow, and tighten a data plan on a lunch break. This page answers to someone else's inbox, someone else's legal reading, someone else's leave calendar and, in larger systems, someone else's committee. A folder that is otherwise complete speeds none of it up.
What follows is an ordering rule rather than a trick. The permission conversation opens on the first day, alongside drafting, and it opens with a page already written. Handing a busy administrator something to check and sign is a different request from asking that person to compose something. It also leaves the activity list in your hands, which is the part that has to track the protocol.
Request it first. Expect it last. Build everything else while it travels.
Two further habits keep the page from going stale. Tell the signer what the project will do, in one paragraph, without jargon — an administrator who understands the ask signs faster than one decoding a protocol. And revisit the page whenever the protocol moves, because a permission written against an earlier design covers an earlier design.
What does an unusable page look like?
Four failures account for most of them, and none of them are dramatic.
- The warm email. A manager writes that the project sounds valuable and to let them know how it goes. Nothing has been granted, nobody with authority has spoken, and the organisation has not named itself.
- The letter of support. A real page on real letterhead that endorses the work without permitting anything. Support and permission are separate acts; boards treat them separately.
- The narrow grant. Permission for the activity the signer pictured, silent on the two the protocol also contains.
- The self-granted page. Signed by you, by your own direct report, or by a colleague at your level. Nobody above the project has agreed to it.
None of these are rejections. Each one is a return, an exchange of notes, and another wait on the same calendar you were already waiting on. That is the cost, and it is why this document leads the plan rather than closing it. If your file has already come back over a permission point, the same rule applies as elsewhere: answer the note specifically, revise every page it touches, and resubmit a file that still tells one story. The application checklist is a fast way to see whether the story holds.
What to do next
Name your signer this week, before another document is written. Draft the page for that person's letterhead with the activity list copied out of your protocol, and send it with a paragraph of plain explanation attached. Then keep building; the rest of the folder should be finished by the time the signature lands.
If you would like the page drafted and the branch read before you spend the goodwill, that is what the free application review is for. We build the permission request for signature, keep it matched to the protocol as the protocol moves, and carry the file from the determination through every reply the board sends. Your project, your data and your findings stay yours; the board's decision stays the board's. See how it works, read the questions we get most, or tell us where the capstone stands.
Request the free application review
Sources
- Western Governors University, Institutional Review Board (IRB), WGU policy handbook, WGU Knowledge Center (last updated 26 March 2026; approval requirement, submission of all proposals, the Institutional Research gate for WGU-population data, continuing review) — cm.wgu.edu
- Western Governors University Institutional Review Board, Request for Approval to Conduct Research (published application form; population and relationship questions, and the reminder to obtain an administrator or supervisor signature before submission) — aliciabatesmedlt.weebly.com/uploads/1/2/6/3/126370100/request_for_approval_to_conduct_research__1_.pdf
- Where the engagement line falls, and the facilities scenario that stays on the near side of it — Office for Human Research Protections, guidance on engagement of institutions — hhs.gov/ohrp/regulations-and-policy/guidance/guidance-on-engagement-of-institutions
- Equitable selection, and the privacy and confidentiality provision a reviewer weighs — 45 CFR 46.111(a)(3) and (a)(7) — Cornell LII, 45 CFR 46.111
- How the regulations define private information that still identifies someone — 45 CFR 46.102 — Cornell LII, 45 CFR 46.102
Routes, forms and portal wording at WGU move over time. Where this page disagrees with WGU's current handbook or IRB portal, believe the portal. This desk is an independent practice; it is not part of Western Governors University and does not speak for it.