Surveying staff or coworkers for a Walden project: consent, coercion, anonymity, and the board's questions

Is a survey of coworkers really human-subjects research?

At Walden, the scope question is settled before you ask it. The university's handbook requires IRB review of research involving data from surveys, interviews, observation, employee work products, and "records of any type," and bars anyone from beginning collection until approval exists. A short questionnaire circulated on the unit is a survey of employees; it is inside the fence. So is the informal version — the "quick poll" in a staff meeting, the pilot you meant to redo properly later. Walden's Writing Center has said it plainly about early collection: anything gathered before approval is not usable in the study. If the project will eventually touch your colleagues, the sequence in our step-by-step account of the Walden IRB process starts before the first invitation, not after.

What is the board actually worried about?

Coercion and undue influence — not as accusations, but as structural facts. The federal criteria at 45 CFR 46.111 tell a board to watch for participants "vulnerable to coercion or undue influence" and to insist on extra safeguards wherever that vulnerability exists; the consent rule at 45 CFR 46.116 wants the asking itself arranged so that pressure has no room to operate. Employment is the everyday case. A person whose schedule, evaluation, or reference you touch — or might someday touch — cannot be assumed to experience your invitation as optional, however warmly it is written. The board does not need to believe you would retaliate; it needs the design to make retaliation impossible to fear. That is a solvable problem, and it is solved with distance: between the person who asks and the person who grades, between the list of invitees and the list of respondents, between your daily role and your researcher role.

Where is the line between your role and your research?

Walden's published delay guidance names the pattern directly — a manager recruiting her own subordinates is its example of a professional role creating pressure — and tells researchers to resolve the conflict before filing rather than have the board surface it. In practice the resolutions look like this:

• Someone else holds the invitation. A neutral party — an administrator, a distribution list owner, a posted flyer — carries the request, so no one replies to you personally to say no.
• Declining is invisible. No sign-up sheets you can read, no reminders addressed to non-responders you selected, no survey handed out in a meeting you run while everyone watches who takes one.
• Your direct reports are handled explicitly. Depending on the design, they are excluded from the pool, or the data reaches you only in a form that cannot tell you who among them answered. The file says which, and why.
• The site's leadership is inside the plan. Permission comes from someone with authority over the setting — not from your own goodwill, nor a friendly peer's. What that permission letter must say is the subject of our guide to the letter of cooperation.

Whether your particular arrangement needs all of these, and in what form, is the board's call under Walden's current handbook and IRB portal — which is exactly why the dual-role answer belongs in the first draft of the file, not in the reply to a revision letter.

The board's questions, as a checklist

Before we file a staff-survey application, the desk answers these in writing, because the board will ask them in writing:

• Who sends the invitation, and does any reply pass through the researcher?
• Can anyone — researcher, supervisor, colleague — observe who participated or declined?
• Does anyone the researcher evaluates, schedules, or supervises fall inside the sample, and what protects them if so?
• Is participation on work time, and did the site agree to that?
• Where do responses live, who can open them, and what links them to people — names, emails, network accounts, or the platform's own logs?
• Could demographics re-identify a respondent in a small unit — the only per-diem nurse, the one manager over a certain age?
• What exactly did the site permit, in whose signature, and does the application claim anything the permission never mentions?

Does making the survey anonymous fix everything?

It fixes a great deal — and less than candidates hope. Anonymity means the researcher records nothing that could readily lead back to a person, and the federal exemption for survey research at 45 CFR 46.104(d)(2) leans on exactly that: identity not readily ascertainable from what is recorded, or a disclosure that could not plausibly harm someone's standing at work. But three caveats keep "it's anonymous" from being a magic sentence. First, platforms betray intentions — collection tools can log addresses and accounts unless configured not to, and the file must say how yours is configured. Second, small cells betray platforms — in a unit of nine, a handful of demographic items can name a person as surely as a signature, so the analysis plan may need to collapse categories or drop them. Third, the label is not yours to award: whether an anonymous staff survey reads as exempt, or takes another path, is a determination the board makes, as our piece on exempt, expedited and full-board review explains. Design for anonymity because it protects your colleagues; let the board say what it earns you.

What does consent look like when no one signs anything?

A staff survey usually pairs anonymity with consent that is read rather than signed: an information page ahead of the first question, with continuation serving as agreement. The regulation anticipates this — 45 CFR 46.117(c) lets a board waive the signature requirement, notably where the signature itself would be the sole record tying anyone to the study. What cannot be waived is the substance. Walden's handbook requires the application to state how participants learn of "the voluntary nature of their participation," including the right to opt out "without penalty" — and in a workplace those words carry weight only if the page also says, concretely, that participation is unconnected to employment, that no supervisor sees who answered, and what becomes of the responses. Vague reassurance reads to the board as an unanswered question. Plain mechanics read as protection.

What will the site have to put in writing?

Usually something; not always everything. Walden's guidance is explicit that written permission is not a universal requirement — the IRB tells you what it needs after reading your Form A description of the data sources and partner organizations — and equally explicit that you should not delay filing to chase paperwork the board has not asked for. When permission is required, it must come from someone with real authority over the setting and match the study the application describes: same activities, same population, same use of work time. And if your employer maintains a review board of its own, the two-boards question arises, which our article on Walden IRB review alongside a site IRB takes end to end.

What to do next

If the people in your sample are the people at your job, the file needs a separation plan before it needs anything else. Send us the outline — who you would survey, what you hold over whom, what the site knows — and a consultant reads it against the board's questions, then answers with what the file must show. We are independent of Walden University; the study stays yours, and the decision stays the board's. Request the free application review, or see how the desk carries the whole process.