Gibbs’ Reflective Cycle: Six Stages, Examples and a Student Project Template

Gibbs’ reflective cycle is a six-stage framework for learning from experience: description, feelings, evaluation, analysis, conclusion and action plan. Developed by Graham Gibbs in 1988, it helps students examine what happened, understand their response and decide what to do next. In university industry projects, students can use it to connect client feedback, teamwork and responsible AI use with evidence of their learning.

Use the worked example and template below to build reflection into work-integrated learning in Australia or work-based learning in the UK.

What are the six stages of Gibbs’ reflective cycle?

The six stages move from an account of an experience towards an informed next action. The University of Edinburgh’s Gibbs guide provides an established explanation of the model.

• Description: What happened, and what was your role?
• Feelings: What were you thinking and feeling?
• Evaluation: What worked well, and what needed attention?
• Analysis: Why did events unfold that way?
• Conclusion: What have you learned, and what else could you have done?
• Action plan: What will you do differently, and how will you check it?

A useful reflection focuses on a specific experience. A client meeting, a disagreement over evidence or a first presentation gives students something concrete to examine.

What does a Gibbs reflective cycle example look like in an industry project?

Illustrative student-project example:

A university student team is preparing market-entry recommendations for a small business. At the draft review, the client asks the team to explain which customer evidence supports its preferred market. The team has relied heavily on general market reports and has not sufficiently tested whether the recommendation fits the client’s resources.

One student uses Gibbs’ cycle to examine their own contribution.

1. Description: establish what happened

Record the event, the relevant context, your contribution and the response you received. Keep the account specific enough that another person can understand it.

Example reflection: “I prepared the customer-research section of our first report. At the client review, I was asked why we had prioritised one market. I explained the market’s size but could not show that our proposed customers would be reachable within the client’s budget.”

Evidence to keep: the brief, the draft section, the client’s question and your research notes.

2. Feelings: examine your response

Explore how your thoughts and emotions influenced what you did. This can reveal habits to develop, such as asking for clarification or responding constructively when a recommendation is challenged.

Example reflection: “I felt confident before the presentation because our report looked complete. When the client questioned our recommendation, I became defensive and repeated our market-size figures. Afterwards, I recognised that I had treated the question as criticism rather than an invitation to explain our reasoning.”

Evidence to keep: a short contemporaneous note about your response and what you noticed during the conversation.

3. Evaluation: identify what helped and what needed attention

Look at both the strengths and the parts of the work that required a different approach. Connect the evaluation to the project’s purpose.

Example reflection: “Our presentation was clear, and the client understood the options. However, my research did not address the cost of reaching the proposed customers. We had answered which market looked attractive before establishing which market was practical for this business.”

Evidence to keep: the client feedback, assessment criteria and examples from the draft.

4. Analysis: explain why

Examine the assumptions, decisions and relevant concepts behind the event. Consider another interpretation and explain why your conclusion is reasonable.

Example reflection: “I had treated market size as the main selection criterion. Revisiting our marketing coursework helped me distinguish the total market from a segment the client could realistically serve. We also needed to test our assumptions about distribution and customer access.”

Evidence to keep: the sources you checked, the criteria you used and the alternatives you considered.

5. Conclusion: identify what you learned

Explain the insight you will carry forward and the other actions available to you.

Example reflection: “I learned to agree the decision criteria with the client before comparing markets. I could have asked about budget, distribution and existing customer relationships at the first briefing. I also learned to pause and clarify a question before defending an answer.”

Evidence to keep: the change in your reasoning and a specific example of the skill involved.

6. Action plan: make the next step testable

Set an action you can take, when you will take it and the evidence that will help you review it.

Example reflection: “Before our next submission, I will confirm three feasibility criteria with the client and rebuild the market comparison around them. I will attach the supporting sources and ask a teammate to challenge the recommendation. At the next review, I will check whether the client can see how the evidence supports our choice.”

The next client review creates a new experience to reflect on. That makes the cycle useful across a project’s milestones, as well as in a final reflective assignment.

Where can universities use Gibbs’ reflective cycle?

Universities can apply the framework to different activities while adapting prompts to their learning outcomes. La Trobe University’s reflective-writing guidance includes Gibbs alongside other approaches to reflection.

After client feedback

Ask students to identify one comment, explain how they interpreted it and show the resulting change. This connects reflection with the next piece of work.

During teamwork and cross-cultural collaboration

Ask each student to examine a decision about responsibilities, communication or disagreement. They can explain how they sought another perspective and what they would repeat or change.

During placements, internships and professional practice

Use a relevant workplace interaction as the starting point. Students should follow institutional and workplace confidentiality requirements when recording what happened.

After a presentation or research decision

Ask students to reflect on a question they could answer confidently, one that exposed an assumption and the evidence they would gather next.

For Australian WIL teams and UK work-based learning teams, these prompts can sit within existing project milestones. Reflecting before the final submission gives students an opportunity to apply their learning while the project is still underway.

A Gibbs reflection template students can reuse

Choose one event rather than summarising the entire programme. Start with the project, date, your role and the evidence you can appropriately refer to.

• Description: The event I am reflecting on was… My responsibility was… The response or outcome was…
• Feelings: Before the event I thought or felt… During it I… This affected my response by…
• Evaluation: What worked was… What needed attention was… The evidence for this is…
• Analysis: I think this happened because… A relevant concept or source is… Another possible explanation is…
• Conclusion: I learned… I could also have… The capability I want to develop is…
• Action plan: By [date or milestone], I will… I will seek feedback from… I will check progress using…

Add an evidence note: “The draft, feedback, source or decision record supporting this reflection is…”

Students can then prepare a short career example explaining the situation, their own action, the result they can substantiate and what they learned. Our career readiness skills guide shows how project activities connect with capabilities students can discuss in applications and interviews.

What do Practera programmes show about feedback, reflection and real work?

Practera’s programme examples bring this learning design into a practical setting: an authentic brief, student work, industry feedback and opportunities to explain learning.

UK: reflective tasks within an industry-project journey

The published UK partner-university case study describes a programme combining skills modules with real employer projects. Its delivery includes client briefings, feedback on team deliverables and reflective tasks through the Practera app.

This gives universities a concrete design example: place reflection beside the project activity and feedback that students need to examine. A Gibbs-based prompt can be configured around a selected milestone so students explain their response and plan the next action.

Australia: industry projects across disciplines and cohorts

Practera’s 2024 Australian partner-university case study reports 4,099 learners, 472 industry partners and 103 programmes across its delivery since March 2016. Students worked on real business challenges and received industry-client feedback.

For educators, the practical opportunity is to give each student a consistent way to examine their contribution within that wider project experience. A short reflection at the draft review and a follow-up after the final submission can make the learning journey easier to discuss and assess.

Programme evidence: using draft and final work

An evaluation of two Summer 2026 cohorts in a UK university programme delivered with Practera recorded client ratings of high or outstanding for 24 of 28 draft reports and 26 of 28 final reports. Outstanding ratings accounted for 9 drafts and 14 finals.

The results showcase client-rated work quality within a structured project programme. Universities can build on this approach by collecting students’ explanations of the feedback they used, the decisions they changed and the learning they will carry into the next task.

Student and client perspectives: what becomes visible?

In the published Study Australia Industry Experience Program case study, SAIEP participant Daina George described learning to “work effectively in a team and solve problems”. Client David Cole, Founder and CEO of FlyFreely, praised how students had “taken all feedback on board”.

Students can use these experiences to examine how they worked with others, understood the client’s needs and responded to feedback.

In a September 2026 interview with Practera, JobSmart participant Angie Su described coordinating team meetings, communicating proactively and learning through work with O-HR. She later joined the organisation as an executive operations assistant. Her account provides a useful prompt for students: which actions made your contribution visible, and how would you explain those actions to a future employer?

Fellow JobSmart participant Smriti Nagpal described researching AI-related governance and discussing bias testing and compliance with the client. In her interview, she highlighted presenting and defending research as part of the experience. This offers another reflection opportunity: explain what you investigated, how you checked your reasoning and how the conversation developed your professional judgement.

How can Gibbs reflection help students develop AI readiness?

AI readiness includes knowing when AI is appropriate, checking its outputs, protecting information and explaining the decisions that remain the student’s responsibility.

Where university and client rules permit AI use, Gibbs’ stages can help students examine it:

• Description: What task did you use AI for, and what information did you provide?
• Feelings: Did the output increase your confidence or make you uncertain?
• Evaluation: Which parts were useful, inaccurate, incomplete or unsuitable?
• Analysis: How did you verify claims, examine bias and compare alternatives?
• Conclusion: What did you learn about the tool, the task and your own judgement?
• Action plan: What will you check, disclose or do differently next time?

For example, a student might use an approved tool to generate interview-question ideas, check them against the client brief and revise questions that assume an answer. Their reflection can explain why particular questions were retained, changed or rejected.

Keep reflection grounded in the student’s experience and evidence. If AI assistance is permitted for planning or language support, students should follow disclosure requirements and retain responsibility for the account they submit. Agree information-handling boundaries before students enter client or personal information into any tool.

What is the difference between Gibbs and Kolb?

Kolb’s experiential learning cycle describes learning through experience, reflection, conceptual understanding and experimentation. Gibbs offers six prompts for examining an experience, including feelings, evaluation and an action plan.

• Use Kolb when designing the broader sequence of an experiential learning activity.
• Use Gibbs when students need a detailed structure for examining a particular event.
• Use them together where useful: a project can provide experience and experimentation, while a Gibbs-based reflection helps students examine a milestone.

For a student team, the sequence could be: undertake research, present a draft, reflect on client feedback, develop a revised approach and test it in the next submission.

How can educators assess the quality of reflection?

A useful reflection explains a specific event, connects interpretation to evidence and leads to an informed action. Educators can adapt the following review criteria to their assessment requirements.

Four criteria for reviewing a reflection

• Specific contribution: Does the student explain their own role, decisions and actions?
• Use of evidence: Do they refer to relevant work, feedback, sources or observations?
• Depth of reasoning: Do they examine why something happened, including assumptions or alternative explanations?
• Action and follow-through: Is the next action specific, relevant and reviewed at a later milestone?

For each criterion, a simple discussion scale is 0: not yet shown; 1: identified; 2: explained with relevant evidence. The four criteria give a total from 0 to 8. Educators can adapt this suggested teaching checklist to their course and assessment criteria.

Assess the quality of reasoning and evidence. Students should be able to discuss emotions at a level they are comfortable sharing; the task should not require sensitive personal disclosures to demonstrate thoughtful reflection.

Our guide to evidence-based assessment in industry projects explores how universities can connect project outputs, individual contributions and assessment.

How can Practera help universities put reflective learning into practice?

Practera helps universities design and deliver industry-linked experiential learning. Reflection becomes more useful when it connects to a real brief, scheduled feedback and an opportunity to act.

Depending on the programme, Practera can support universities with:

• Programme design: map learning outcomes to project activities, milestones and reflection prompts.
• Industry engagement: source and support suitable industry partners and project briefs.
• Structured delivery: organise content, submissions and project interactions within a clear learner journey.
• Feedback and reflection: build opportunities for client, peer and educator feedback, with prompts students can use to examine their learning.
• Programme oversight: use activity and progress information to identify where students or teams need support.

Practera’s platform features include configurable workflows, feedback, reflection-related activities and programme analytics. Design and onboarding support helps teams adapt delivery to their institution and cohort.

A university can begin with one existing project: identify the first client-feedback milestone, choose a short reflection task and give students time to apply their action plans. Academic teams retain ownership of learning outcomes, assessment criteria and grading.

Explore further examples in the Practera Case Study Hub, or talk to Practera about connecting industry projects, feedback and reflection in your programme.

Gibbs’ reflective cycle: frequently asked questions

What is Gibbs’ reflective cycle?

Gibbs’ reflective cycle is a framework developed by Graham Gibbs in 1988. It guides reflection through six stages: description, feelings, evaluation, analysis, conclusion and action plan.

What are the six stages of Gibbs’ reflective cycle?

The stages are description, feelings, evaluation, analysis, conclusion and action plan. Together, they help a learner examine an experience and decide what to do next.

How do you write a Gibbs reflection for a university project?

Choose a specific event, explain your own role and work through the six stages. Refer to relevant evidence, such as a draft, client feedback or research notes, and finish with a practical next action. Follow your institution’s assessment instructions.

What is a Gibbs reflective cycle example after client feedback?

A student might reflect on a client questioning a recommendation, examine the assumptions behind their research and plan a revised comparison using agreed criteria. The next submission provides an opportunity to apply that learning.

How is analysis different from evaluation?

Evaluation identifies what worked and what needed attention. Analysis explores why, using evidence, relevant concepts and alternative explanations.

Can Gibbs’ reflective cycle be used in group projects?

Yes. Students can examine a shared project event while explaining their own contribution, decisions and learning. Team feedback and individual reflection can be used together.

How can Gibbs reflection support AI readiness?

It can help students explain permitted AI use, evaluate outputs, check sources and bias, describe their own decisions and plan more responsible use next time.

Can universities use Gibbs’ reflective cycle with Practera?

Universities can configure reflective activities within a Practera-supported project journey, aligned to their learning outcomes and programme scope. Gibbs-based prompts can connect industry feedback with students’ explanations and next actions.