Research Ethics

What committees actually assess, why applications come back, and the ethical decisions that arrive after approval.

The short answer

Ethics approval assesses whether the benefit of your research justifies what you are asking of participants, and whether risks are understood and managed. Applications are most often returned not for serious ethical problems but for vagueness — a consent process described loosely, a data plan that does not say where data lives, or a risk section that says there are no risks. Precision is what gets applications through quickly.

What a committee is actually assessing

It helps to know what the people reading your application are looking for, because it is narrower than the word “ethics” suggests.

  1. Is the research worth doing? Asking for people’s time and information has to be justified by something. A poorly designed study is an ethical problem, not only a methodological one, because it imposes cost for no benefit.
  2. Do participants genuinely understand and agree? Not whether a form was signed — whether the person understood what they were agreeing to.
  3. Are risks identified and managed? Including risks that are not physical: distress, embarrassment, professional consequences, loss of confidentiality.
  4. Is the data handled properly? Where it lives, who sees it, how long it is kept, what happens at the end.
  5. Can people withdraw? And is it clear what withdrawal means once data is anonymised or analysed.

Requirements differ substantially by country, discipline and institution, and your own committee’s guidance is the authority. Read it before drafting rather than after, and where something is unclear, ask them — committees generally prefer a question to a resubmission.

Consent, and what makes it informed

A signature is evidence of consent, not consent itself. What matters is whether the person understood.

Information sheets are where this most often fails. They are frequently written in the register of a methods chapter — technical, long, and hard to follow — which means the participant has agreed to something they did not really follow. Write it as you would explain the study to someone outside your field, and keep it as short as accuracy allows.

What it needs to cover: what the study is about, what participation involves and how long it takes, what happens to the data, who will see it, how anonymity is handled, that participation is voluntary, how to withdraw and by when, any risks, and who to contact including someone independent if they have concerns.

Two situations that need explicit thought:

Where there is a power relationship. If you are recruiting your own students, staff you manage, or patients you treat, people may feel unable to decline. Committees look for this and expect it to be addressed — typically by having someone else recruit, or by making refusal invisible to you.

Where consent has to be ongoing. In long fieldwork or ethnography, consent given once at the start may not cover what happens six months in. Describing consent as an ongoing process rather than a single event is stronger and more honest.

Anonymity and confidentiality are different things

These are used interchangeably and mean different things, and committees notice when the distinction has not been thought through.

Anonymity means you do not know who the participant is. A truly anonymous survey has no identifying information at all — which also means you cannot remove someone’s data later, because you cannot find it.

Confidentiality means you know who they are and will not disclose it. This is what most qualitative research offers, and it is a promise about handling rather than about ignorance.

Do not promise anonymity when you mean confidentiality. It appears in information sheets constantly and it is inaccurate.

Confidentiality also has limits worth stating in advance. In small populations, a pseudonym is often not enough: a job title plus an organisation plus a described incident can identify someone to colleagues even when their name is removed. Where your sample is small or specialised, plan for it — generalising role descriptions, altering incidental detail, or aggregating findings.

And confidentiality is not absolute. If a participant discloses risk of serious harm, most frameworks require action, and your information sheet should say so plainly rather than promising something you would not keep.

Data protection, in practical terms

Data plans are returned more often than almost anything else, because they are usually written in generalities.

What a committee wants is specifics: what data you collect, where it is stored during the study, in what form, who has access, how long it is kept, and what happens at the end. “Data will be stored securely” answers none of that.

Points that recur:

  • Recordings and transcripts are separate items with separate handling, and recordings are usually destroyed earlier.
  • Keep identifiers separate from data, with a key held apart from both. This is what allows you to honour a withdrawal request without your working files carrying names.
  • Personal devices and consumer cloud services are commonly restricted by institutional policy. Check yours before you plan around them.
  • Transcription services are data processors. Sending recordings to a third party has implications your committee will ask about.
  • Retention is usually specified by your institution or funder and is often longer than the doctorate. Say what you will actually do.

Data protection law differs by jurisdiction and applies to identifiable data regardless of whether it was collected publicly — which matters if you are working with online material. Your institution will have guidance; follow it rather than general advice.

Why applications come back

Most delays are not about serious ethical problems. They are about imprecision.

  • “There are no risks.” There are always some — time, inconvenience, the possibility that a topic is uncomfortable. Saying none reads as not having thought about it.
  • An information sheet nobody could follow. Written for the committee rather than the participant.
  • Vague data handling. No location, no access list, no retention period.
  • Recruitment that dodges the power question where one plainly exists.
  • Withdrawal described without a limit. Once data is anonymised or analysed, removal may be impossible. Say by when withdrawal is possible.
  • Missing documents. Consent form, information sheet, recruitment materials, interview guide, questionnaire — committees want to see what participants will see.
  • Researcher safety not addressed. Lone interviews, home visits, sensitive topics and distressing material all carry risk to you, and committees increasingly expect this.

Two practical points. Build approval time into your schedule realistically — it takes weeks or months and is a common cause of timeline slip, particularly in sequential designs. And look at a successful application from your own department: it will tell you more about local expectations than any general guidance.

Ethics after approval

Approval is the beginning. The decisions that are genuinely difficult arrive during fieldwork and are not in the form.

A participant becomes distressed, and you have to decide whether to continue. Someone tells you something they later ask you not to use. You witness practice that concerns you. A participant tells you more than they intended because the conversation went well. None of these have a procedural answer.

What helps is deciding your principles in advance — when you would stop an interview, what you would do with a disclosure, whom you would consult — and recording these decisions as they happen, with your reasoning. That record belongs in your thesis. A methodology chapter that describes a real ethical dilemma and how it was handled is considerably more convincing than one asserting that approval was obtained and nothing further occurred.

If your design changes substantially — different participants, new questions, another site — that usually needs an amendment. Committees generally handle these quickly, and it is far better than discovering at submission that you collected outside your approval.

Questions researchers ask

What do research ethics committees look for?

Whether the research is worth what it asks of participants, whether consent is genuinely informed, whether risks are identified and managed, whether data handling is specified properly, and whether people can withdraw. Requirements differ by country, discipline and institution, so read your own committee’s guidance before drafting — and ask them where something is unclear, since most prefer a question to a resubmission.

What is the difference between anonymity and confidentiality?

Anonymity means you do not know who the participant is — which also means you cannot remove their data later. Confidentiality means you know and will not disclose it, which is what most qualitative research actually offers. Promising anonymity when you mean confidentiality is a common inaccuracy in information sheets, and committees notice it.

How long does ethics approval take?

Weeks to months, depending on your institution and whether your study involves anything requiring fuller review. It is a common cause of timeline slip and should be built into your schedule realistically — particularly in sequential designs, where a delay to the first phase moves everything after it.

Why do ethics applications get rejected or returned?

Usually for imprecision rather than serious ethical problems: stating there are no risks, an information sheet written for the committee rather than the participant, vague data handling with no location or retention period, recruitment that ignores an obvious power relationship, and missing documents. Looking at a successful application from your own department is the fastest way to learn local expectations.

Can I interview my own students or staff?

Sometimes, and committees will look closely at it because people may feel unable to decline. Expect to address it explicitly — typically by having someone else recruit, by making refusal invisible to you, or by demonstrating that participation cannot affect any assessment or employment decision. Not addressing the power relationship at all is a common reason for return.

What if something ethically difficult happens during fieldwork?

That is normal, and the form will not have covered it. Decide your principles in advance — when you would stop an interview, what you would do with a disclosure, whom you would consult — and record decisions with your reasoning as they happen. That record belongs in your thesis: a chapter describing a real dilemma and how it was handled is far more convincing than one stating that approval was obtained and nothing else occurred.

Related guides

Get the application read before you submit it

Most returns are for vagueness rather than ethical problems, and both are obvious from outside. Send your draft and a PhD in your field will tell you what a committee will query.

Discuss your application