KEVOS
ArticlesServicesCase studiesAboutContact
ArticlesServicesCase studiesAboutContact
← ArticlesEthics Application Failures: What Goes WrongProject Delivery · Research ProjectsLesson 99/115← PrevNext →
GuidePublished 16 Aug 202614 min readBy KEVOS Editorialethics application rejectedethics application mistakesethics committee delaystudent ethics application supervisor
On this page

Ask about this page

KEVOS AIEthics Application Failures: What Goes Wrong

KEVOS knowledge first · trusted web sources when needed

KEVOS/Project Delivery/Research Projects/Research Ethics
Project DeliveryResearch ProjectsCoreResearch Ethics

Ethics Application Failures: What Goes Wrong

Not one of the three is a failure of ethics. Each is a failure of process — a step skipped, a category self-assigned, a relationship unrecognised — and each cost far more than the shortcut saved.

Reading time15 minutes
LevelCore
Topic streamResearch Ethics
Source materialResearch Ethics
Updated2026-08-16

In brief

  • The source supplies three case studies and states plainly that they are based on fact and that names are fictitious. Names are removed entirely here.
  • Case one: a required training video skipped, a confirmation email sent anyway, one question answered by reasoning rather than reading — application auto-routed to a higher-level committee, rejected weeks later, student withdrew.
  • Case two: a student on schedule who did everything else right chose the wrong option on one field, and the application bypassed the supervisor entirely. Weeks of delay.
  • Case three: an evaluative study on the researcher's own team. Five rounds of amendment, more than five months.
  • None of the three is an ethical failure. All three are process failures, and in two of them the trigger was an automated routing rule the applicant did not know existed.

How the source presents these

From the source

The framing, and the source's own moral

"The following case studies are based on fact; names are fictitious."

And at the end of them: "As these case studies illustrate, it is vitally important that you are familiar with University ethics requirements you need to meet before proceeding with research. Your University Supervisor is an important stakeholder in your success. Make sure you consult and heed good advice."

Read them as the source presents them: three illustrations chosen to make a point, not a sample of applications and not evidence of how often anything happens. Nothing here supports a rate, a probability or a typical outcome.

What they are unusually good for is the failure shape. Each case has a single identifiable decision point, and in each case the decision looked negligible at the time it was made.

Case one: a video, an email and an automatic routing rule

A part-time student was behind schedule. A demanding project management job and a young family had pushed study to last place — the ordinary condition of the part-time practitioner, not an unusual one.

A week-nine requirement was to view a training video on the ethics application process, then email the supervisor confirming it had been viewed. In haste, the student skipped the video and sent the email anyway. The chain that followed had no further decision points in it.

How one skipped step propagated

  1. The video is skipped

    Fifteen or twenty minutes saved, on a schedule already behind. The single decision in the whole case, and the only one that was freely made.

  2. The confirmation email is sent anyway

    The attestation is now false, and — more to the point — nobody downstream has any reason to check whether this applicant understands the process. The safety net is removed by the same act that saved the time.

  3. The online application is completed without reading the detailed information

    The material the video existed to explain went unread as well. The two omissions compound: no briefing, and no guidance notes.

  4. One question is answered by reasoning rather than by reading

    Asked whether members of an indigenous community were involved, the student answered yes — reasoning that some interviewees in the resources sector probably were. A plausible inference, made without reading what the question meant or what answering yes would do.

  5. The submission routes itself

    On submission the application was routed automatically to a higher-level ethics committee, whose requirements the student had not addressed. No human decision was involved, and no warning appeared at the moment of the answer.

  6. Weeks pass, and it is rejected

    The application came back rejected, with major amendments and lengthy timescales required. The delay was itself part of the damage — the weeks were spent believing the application was in progress.

  7. The thesis cannot proceed

    Without approval there was no lawful way forward, and the amendment timescales did not fit the remaining candidature. The student withdrew.

Caution

The attestation is the point at which the system stops helping you

Confirmations that you have read, viewed or understood something are not bureaucratic theatre. They are the moment an institution transfers responsibility from itself to you, and after which nobody checks again.

Every later step in this case assumed a briefed applicant. Skipping the briefing while asserting otherwise removed every subsequent opportunity for the error to be caught.

Source gap

What the source does not explain about the routing

The material states that the application was routed automatically to a higher-level committee and that its requirements had not been addressed. It does not describe the tier system, say what other answers trigger escalation, or set out what the higher-level committee required.

Elsewhere the same material refers to advisors who review "E2 applications" alongside the chair of an "HREC", and neither term is defined anywhere in the supplied source. No expansion or risk-tier scheme is offered, and none should be inferred.

The practical consequence is the useful part: your form almost certainly contains at least one question that silently changes where your application goes. Find out which before you answer, because the routing decision is made by software at submission, not by a person during review.

Case two: one field, wrongly self-assigned

The second case is the useful counterweight, because this student did almost everything right.

Researching social and affordable housing, she had viewed the training video and was on schedule, submitting the ethics application in week fifteen. Nothing about the preparation was careless.

The online form offered two options: submit as a student, or submit as a researcher. Considering herself a researcher — which she was — she chose that option. Student applications route automatically to the supervisor for review and authorisation before going to the committee. Choosing researcher bypassed the supervisor entirely.

The error surfaced only when the supervisor later asked where the application had got to. The blunder delayed the project by a number of weeks and affected the ability to finish on time.

Caution

Self-classification fields are routing instructions in disguise

The form was not asking how the applicant thought of herself. It was asking which workflow to use, in language that reads as an identity question.

Wherever a form asks you to categorise yourself — role, risk level, project type, whether a group is involved — assume the answer determines who sees the application and what is required of it. Where the label and the workflow could come apart, ask before you submit rather than after.

The same trap produced case one. There, a self-assessed answer about who was involved sent the application up a tier; here, a self-assessed answer about who the applicant was sent it around the supervisor.

Case three: the dependent group

The third case is different in kind. Nothing was skipped and nothing was misassigned. The study itself was simply in the hardest category: an evaluative study inside the researcher's own workplace, on the same team as the participants.

The workplace director required that colleagues be approached individually by the university supervisor rather than by the researcher, with a background information sheet sent first, and with the director notified before the researcher when a colleague agreed. The application went back and forth to the committee five times for amendments before approval, and the process took more than five months.

Source example — illustrative only

One case, and the only duration figure in the material

Five rounds and more than five months describe this application. They are not a standard, an average, a typical duration or a benchmark, and they are the only quantified statement about ethics approval timing anywhere in the supplied teaching source.

The arrangement itself, the mechanism underneath it, and how to design an equivalent for your own study are set out in Dependent Groups and Unequal Power.

Its place in this set is as the case with no mistake in it. Two of the three failures were avoidable in a few minutes. The third was structural, and the cost was borne anyway.

What the three have in common

THE THREE CASES COMPARED

CaseThe decisionWhat it costWhat would have prevented it
One — the skipped videoSkipped a required briefing and confirmed it had been viewedRejection after weeks of waiting, major amendments on long timescales, withdrawal from the degreeFifteen minutes of video, or reading the detailed information for the one question that was guessed
Two — the wrong routeChose researcher rather than student on a self-classification fieldA number of weeks' delay, and the ability to finish on time affectedOne question to the supervisor before submitting, or noticing that the field controlled routing
Three — the dependent groupNo error. An evaluative study on the researcher's own teamFive rounds of amendment and more than five months to approvalNothing removes it. Starting earlier and designing the recruitment buffer up front reduces the rounds

Case details are the source's, described as based on fact with fictitious names. The prevention column is analysis added here.

Three patterns run across the set, and they are more useful than any of the cases individually.

What the set actually shows

PATTERN 1

None of the three was an ethical failure

Nobody harmed a participant, breached a confidence, misrepresented a result or deceived anyone. All three researchers were behaving ethically throughout. What failed was process — the machinery around the ethics, not the ethics.

PATTERN 2

Every cost exceeded the saving, by orders of magnitude

Fifteen minutes bought a withdrawn candidature. One unchecked radio button bought weeks. The exchange rate between shortcut and consequence in this process is exceptionally bad, and it is bad in a way that is invisible at the moment of the shortcut.

PATTERN 3

Two of three were sprung by automated routing

In both cases an answer the applicant gave in good faith determined where the application went, without telling them. Neither error was detectable from the applicant's side until someone downstream noticed an absence.

There is a fourth observation worth adding, though it belongs to the reader rather than the source. In all three cases the loss was measured in time, and time is the resource a part-time practitioner has least of. The material's rule that research cannot proceed without approval — and that data gathered beforehand cannot be used — is what converts an administrative delay into a project-level failure. That rule is set out in Ethics Review and Approval Processes.

The failure modes, generalised

Stripped of their circumstances, the three cases contain four distinct mechanisms. Each one is easy to test for in your own application.

FOUR FAILURE MODES AND HOW TO TEST FOR EACH

Failure modeWhat it looks likeThe test
Attestation without actionConfirming you have read, viewed or understood something you have notFor every confirmation you have given, can you say what the material said? If not, that is where the process stopped protecting you
Answering by reasoning rather than by readingInferring what a question probably means and answering the inferenceFor every non-obvious question, did you read the guidance for that question specifically, or infer from the wording?
Self-classification without checking the consequenceChoosing a category for yourself, your study or your risk level without knowing what the choice triggersFor each category field, can you say who will see the application as a result of your answer?
Unread routing rulesNot knowing which answers change where the application goes or who must authorise itCan you describe the path your application will take from submit to decision, including every party in it?

The four modes are drawn from the source's three cases. The tests are synthesis added here.

Preventing all three

The source's own remedy is a single sentence and it is worth taking literally: your university supervisor is an important stakeholder in your success, so consult and heed good advice. In two of the three cases, one conversation before submitting would have been sufficient. The same pattern — a warning stated once, in a single sentence, and skipped under schedule pressure — runs through Common Mistakes in Project Management Research.

Before you press submit

  • Every required briefing, video or module has actually been completed, not just confirmed
  • The detailed guidance notes for the form have been read, not skimmed for the fields you expect
  • Every question you answered by inference has been checked against its own guidance
  • You can name every category field on the form and say what each answer triggers
  • You can describe the application's route from submission to decision, including who authorises it and in what order
  • Your supervisor has seen the application before it goes, whichever route the form says it takes
  • Where a question could plausibly be answered either way, you asked rather than chose
  • The submission date leaves room for at least one round of amendments
  • Nothing has been collected, and no participant has been approached
Check before you proceed

The routing rehearsal

Before submitting, describe out loud where your application goes next, then who sees it after that, and then what happens if it comes back.

If any step in that sequence is a guess, you are in the position both of the first two cases started from. Find the answer from your approving body or your supervisor rather than from the form's own wording — the wording is what misled both applicants.

Then set a date, in your plan, at which you will chase it if you have heard nothing. Case two was discovered because a supervisor happened to ask. That should not be the detection mechanism.

How the eight parts of the application itself are written, and which of its questions carry the strongest demands, are covered in Writing an Ethics Application. Every requirement, principle and list the ethics material sets out is indexed on one page in the Research Ethics Quick Reference.

What to carry forward

  1. The source describes these three as based on fact with fictitious names. They are illustrations of a failure shape, not evidence of how often anything happens.
  2. None of the three was an ethical failure. All three were process failures, in the machinery around the ethics.
  3. The single decision in case one was fifteen minutes of video. The consequence was a withdrawn candidature.
  4. Case two did everything else right and still lost weeks, on one field that read as an identity question and was actually a routing instruction.
  5. Case three contained no mistake at all. Some categories of study cost months regardless, which is an argument for starting them first.
  6. Attestations are where the institution stops checking and you start being responsible. Do not confirm what you have not done.
  7. Know the route your application takes before you submit it, and set a date to chase it rather than waiting to be asked.

Frequently asked questions

Are these real cases?

The supplied source states that the case studies are based on fact and that names are fictitious. Names have been removed entirely here rather than replaced. They are presented as illustrations to make a teaching point, so they support conclusions about how this kind of failure happens but not about how often it happens.

What actually triggered the rejection in the first case?

Answering yes to a question about whether members of an indigenous community were involved routed the application automatically to a higher-level committee whose requirements had not been addressed. The answer was reached by inference — some interviewees in the resources sector probably were — rather than by reading what the question meant. The source does not describe the tier system or that committee's requirements.

Why did choosing researcher instead of student cause a problem?

Student applications routed automatically to the supervisor for review and authorisation before reaching the committee. Selecting researcher bypassed that step, so the application sat outside the process with nobody expecting it. The field looked like a description of the applicant and was in fact a choice of workflow.

How much time should I allow for ethics approval?

The supplied material gives one figure — five rounds of amendment over more than five months — and it comes from the hardest category of application, insider research on a dependent group. There is no average, range or typical duration anywhere in the source. Plan on at least one round of amendments, start early, and get a realistic estimate from your own approving body.

What is the single most useful precaution?

Showing the application to your supervisor before it goes, whatever route the form says it will take. The source's own moral is that your supervisor is an important stakeholder in your success and that you should consult and heed good advice — and in two of the three cases a short conversation before submission would have prevented the whole sequence.

Can I start collecting data while approval is pending?

No. The supplied material is explicit that you cannot proceed without approval from the relevant ethics committees, and that even data gathered before clearance cannot be used in your findings. That rule is what turns a routing error into a project failure — the delay is not recoverable by working ahead.

References and source attribution

  1. Cooper, D. & Schindler, P. 2008, Business Research Methods, 10th ed., McGraw-Hill — the text the supplied source draws on for its treatment of research ethics.
  2. Quinlan, C. 2011, Business Research Methods, 1st ed., Cengage Publishing, Chapter 3 — the prescribed reading accompanying the ethics material.
  3. Swinton, J. 2009, 'Why bother with research ethics?', Journal of Community Nursing, vol. 23, no. 9, pp. 25–27.
  4. Australian Code for the Responsible Conduct of Research (2007) — named in the supplied source as the instrument behind its data retention and responsible practice requirements. The code itself is not reproduced in the supplied material.
  5. The supplied teaching source: consolidated weekly teaching notes and slide material on research ethics, which supplies the three case studies described on this page, stated there to be based on fact with fictitious names.

Suggested questions for Ask KEVOS

  • List every question on my ethics form that could change where the application is routed, and what each answer triggers.
  • Draft the questions I should put to my supervisor before I submit my ethics application.
  • Build me an ethics approval schedule that allows for at least one round of amendments.
  • I answered a form question by inference rather than by reading the guidance. Help me work out whether to correct it.
  • What should I do if my application has been submitted and nobody has acknowledged it?

Related KEVOS knowledge

Dependent Groups and Unequal PowerAdvanced · research ethicsEthics Review and Approval ProcessesCore · research ethicsWriting an Ethics ApplicationCore · research ethicsResearch Ethics Quick ReferenceFoundation · research ethicsCommon Mistakes in Project Management ResearchAdvanced · research practiceWhat Research Ethics Are and Why They MatterFoundation · research ethics
KEVOS® · Project Delivery · Research Projects Page KVS-PM-RES-0099 · v1.0.0 · content 2026.08 Last reviewed 2026-08-16

Continue learning

Dependent Groups and Unequal PowerGuide · Research ProjectsNEXT LESSON →Research Ethics Quick ReferenceGuide · Research ProjectsSponsors and Researcher IndependenceGuide · Research ProjectsThe Purpose of a Research ProposalGuide · Research Projects
KEVOS · Engineering, manufacturing and project improvement
ArticlesServicesCase studiesAboutContact
© 2026 KEVOS®