Skip to Content

What our feedback looks like

This article is part of the Iris Ethics Knowledge Base; you can find a directory of all articles here.

Most applications to Iris Ethics receive at least one round of feedback before the committee issues a formal decision. This applies to both lower risk and full HREC review. Feedback is not a sign that your application has fallen short. It is how we make sure we understand your project well enough to approve it.

This article explains why we give feedback before deciding, the three broad kinds of feedback you are likely to see, and how to respond in a way that gets you to a decision quickly. It complements Responding to feedback, which covers the portal and the response process in more detail.

Why feedback comes before a decision

Our reviews are conducted against the National Statement on Ethical Conduct in Human Research 2025 (the National Statement). The National Statement is explicit that its guidelines "are not simply a set of rules" and that their application "should not be mechanical" (NS Section 1, Application of these values and principles). Good review depends on understanding context, and an application form rarely captures every decision behind a project.

A feedback round gives the committee the opportunity to:

  • clarify points that are ambiguous or could be read more than one way;
  • understand the reasoning and context behind design choices; and
  • confirm that materials, such as participant information sheets, consent forms, and distress protocols, align with the National Statement.

This means the committee reaches its decision with the fullest available knowledge of your project. It also means far fewer applications are declined at first review. A gap that can be closed with a paragraph of explanation or a revised consent form is resolved during feedback, rather than becoming a reason to decline and asking you to start again. This reflects the National Statement's position that good review requires open communication between review bodies and applicants, and a shared commitment to a constructive process (NS 5.2.11). Where we request changes, we give reasons with reference to the National Statement (NS 5.2.7).

Feedback generally falls into three kinds, set out below. These are not formal labels, and a single item can touch on more than one. Knowing which kind you are looking at, though, helps you decide how to respond.

Requirements under the National Statement

Some feedback concerns elements that must be addressed for the project to comply with the National Statement. These are the items that stand between your application and approval.

Often this means amending documents or activities. Common examples include:

  • a participant information sheet that omits a complaints contact, or does not explain whether data can be withdrawn (NS 2.2.6);
  • recruitment through a program's own case workers, without addressing the potential for pressure or coercion in that relationship (NS 3.1.17(d)); and
  • a data management plan that does not say where interview recordings will be stored, who can access them, or when they will be destroyed (NS 3.1.44).

In other cases, nothing needs to change. What the committee needs is clarification and assurance. The National Statement requires that risks be identified, assessed, and minimised, mitigated, or managed (NS 2.1.1). If an application touches on a sensitive topic but does not show how the associated risk has been characterised, we will ask.

Example: An evaluation of a family violence prevention program plans interviews with program participants. The application includes a distress protocol but does not say who will conduct the interviews. The committee asks. The evaluation team replies that interviewers have trauma-informed practice training and sector experience, and that a referral pathway has been agreed with the service provider. No document needs amending. The committee now has assurance that the risk has been appropriately characterised and mitigated in the context of the activity.

Questions about method

Method feedback is usually about understanding why you chose a particular approach. Most evaluation and research questions can be answered in more than one way, using methods in isolation or in combination. The National Statement requires that projects use methods appropriate for achieving their aims (NS 1.1(b)), and asks applicants to explain how their design will achieve those aims (NS 3.1.1(d)). It also asks reviewers to consider the various methods by which the aims could be achieved when weighing benefits against risks (NS 2.1.3). So when we ask "why this method?", we are seeking context. We are not second-guessing your expertise.

We are also pragmatic. The ideal method for answering a question is not always feasible within the time and budget available, and the National Statement itself asks that resources be sufficient to complete the project as designed (NS 3.1.9). An alternative method may be the best practical option, and it can be acceptable where the benefits outweigh the risks.

Example: A market research agency proposes an online survey of recent users of a government service, where in-depth interviews might yield richer insight. The committee asks why. The agency explains that the client needs national findings within six weeks, and that an anonymous survey reduces both the burden on respondents and the risk of identification. That is enough. In context, the method is fit for purpose and carries lower risk than the alternative.

Suggestions that go beyond the National Statement

Our committee brings together deep expertise in policy, method, and lived experience, and many members have worked on projects similar to the ones they review. The National Statement recognises the value of this. It notes that effective review draws on expertise in the relevant methods and areas of practice (NS Chapter 3.1, Introduction), and encourages reviewers to consider advice from people with experience of a similar methodology, population, or research domain (NS 2.1.2).

Because of that experience, members are often able (and willing) to suggest ways a project could better support participants, stakeholders, or its own objectives. These suggestions go beyond what the National Statement requires, so we treat them as optional. For example, we might suggest:

  • offering an Easy Read version of the information sheet for a disability services evaluation, even where the plain language version meets requirements;
  • sharing a short summary of findings with the community organisations that helped with recruitment; or
  • adding a survey item to a social research project that would allow analysis for a subgroup of policy interest.

You are not required to adopt these suggestions, and there are sometimes very good reasons not to. We include them because we would rather give you the opportunity to consider them than keep them to ourselves. In our view, this is where review adds value beyond procedural assessment. If you decide not to take one up it will not count against your application.

Responding to feedback

The way you respond has a direct effect on how quickly the committee can reach a decision. Two practices make the biggest difference.

Use our response template (full reviews). For full HREC reviews, we provide a template to summarise your responses. It helps you organise your response and lets the committee see at a glance how each item has been addressed. It is not compulsory. A clear, point-by-point response in another format is fine.

Provide tracked-changes versions where feasible. Alongside clean copies of amended documents, a tracked-changes version lets the committee see exactly what has changed without re-reading the whole document. This is one of the most effective ways to shorten the second round of review.

It also helps to keep the three kinds of feedback in mind as you work through your response. Requirements need to be resolved, whether by amendment or by explanation. Method questions need context. Optional suggestions need only an acknowledgement. And if you disagree with any item, say so and explain why; a reasoned response is exactly what the process is for. Responding to feedback sets out the full step-by-step process.

Summary

Feedback before a decision is how we make sure the committee understands your project in full. It typically covers requirements under the National Statement, questions about method, and optional suggestions drawn from our committee's experience. Address the requirements, give context on method, and consider the suggestions on their merits. Using the template and providing tracked changes will help the committee reach a decision sooner.

If you are unsure what a piece of feedback is asking for, or which kind it is, ask us. A short question early can save a response aimed at the wrong issue.

Related resources

This page was last updated on 23 October 2026.

Was this helpful? We'd appreciate your feedback!

This article makes reference to the National Statement on Ethical Conduct in Human Research 2025. It is intended as practical guidance and does not constitute legal advice.

AI Disclosure: Resources in this library were prepared using Large Language Models with input from Iris Ethics staff who guided the scope and design. Subsequent revisions and final versions were developed and approved by Iris Ethics staff.