Writing a Successful Part III Professional Case Study

What the Case Study Is For

The Professional Case Study is the largest and most demanding piece of work in the Part 3 qualification. Its purpose is not to tell the story of a project, it is to demonstrate that you possess the knowledge, understanding and professional judgement required of a qualified architect.

This distinction matters enormously. The case study uses a real project as a vehicle through which you show that you can analyse complex situations, apply professional and legal frameworks, reflect critically on your own experience, and make sound recommendations for practice. The project is the raw material; your analysis is what is being assessed.

Examiners are not interested in what your client wanted or what the contractor built. They are interested in what you understand about why decisions were made, how professional standards apply, what the risks and implications were, and what you would do differently.

Structure

A Part III case study typically follows a framework covering the full lifecycle of a construction project, divided broadly into:

Chapter 1: The Project The practice context, your role, the client, the design and construction team, appointments, fees, design development and sustainability.

Chapter 2: The Regulatory Framework Town planning, building regulations, CDM, fire and life safety, the Building Safety Act, the Equality Act, and any other relevant statutory consents or restrictions.

Chapter 3: Procurement The procurement strategy, contract form and choice rationale, tendering process, and mobilisation.

Chapter 4: Post-Mobilisation (Site) Contract administration, the architect's role, variations and change control, valuations and payments, quality control, certification and completion.

Chapter 5: Conclusions and Recommendations Themes arising from the study, ethical questions, a summary of critical analysis, and recommendations for future practice.

This structure is not a straitjacket. Projects vary enormously, and not every section will be equally rich for every case study. However, you should address all of them, even if briefly, and be ready to discuss any of them at oral examination.

The Core Method: Describe, Compare, Reflect

Every section of the case study, regardless of topic, should follow the same three-step analytical method. Applying this consistently is what separates analytical writing from descriptive writing.

Step 1: Describe the Issue

Set out the facts clearly and concisely.

• What happened?

• Who did what, and when?

• Why was that decision made?

• How was it carried out?

This step establishes the factual basis for your analysis. It should be concise, you are not writing a project diary. The goal is to give the reader enough context to follow your analysis, not to document every event.

Step 2: Identify Best Practice or a Comparator Model

Having described what happened, you now need something to measure it against.

• What does best practice look like in this situation?

• What do professional standards, guidance documents, contracts, or legislation say should happen?

• Is there an alternative approach, procurement model, or contractual arrangement that could usefully serve as a point of comparison?

• Why have you chosen this particular benchmark?

Sources for best practice include: RIBA guidance and the Plan of Work; ARB Professional Criteria; JCT and NEC contract guidance; RICS guidance notes; CDM Regulations; Planning Policy; Building Regulations Approved Documents; relevant case law; and academic or professional literature.

You should be specific. "Best practice suggests good communication" is not useful. "RIBA guidance on contract administration under JCT Standard Building Contract recommends that the Contract Administrator issues instructions in writing promptly and within the timeframes set out in the contract, to avoid ambiguity and dispute" is far more useful.

Step 3: Comparative Analysis and Reflection

This is where the real analytical work happens.

• How does what happened on your project compare with best practice?

• What were the implications of any divergence — for the project, for the client, for the design team?

• What alternative approaches could have been taken?

• What would you do differently next time, and why?

• What does this experience teach you about professional practice?

This step requires you to engage critically, not just to note that something differed from best practice, but to explore why, what the consequences were, and what a better approach would look like.

Writing Critical Analysis

Critical analysis is often misunderstood. It does not mean finding fault with everything. It means examining a situation carefully, from multiple angles, evaluating the evidence, and reaching a reasoned judgement. You can critically analyse a decision that you think was well-made just as much as one that went wrong.

What Critical Analysis Looks Like in Practice

Avoid: "The contractor submitted a variation claim. This was dealt with by the project architect."

Instead: "The contractor submitted a variation claim of £45,000 following the architect's instruction to change the cladding specification. Under the JCT Standard Building Contract, the Contract Administrator has a duty to ascertain the value of variations under clause 5.6, with reference to the contract sum analysis and current market rates where no analogous item exists. In this case, the claim was assessed against the original specification rates without adjustment for material price increases that had occurred since the contract sum was agreed. While this approach was contractually defensible, it created significant tension with the contractor and resulted in a formal dispute that delayed practical completion by three weeks. A more proactive approach, asking the contractor to provide a quotation for the changes, would have established an agreed value and avoided the dispute."

Notice what the analytical version does:

• Names the specific contractual mechanism that applies

• Identifies what the obligation was and how it was discharged

• Evaluates the quality of that discharge

• Identifies the consequences

• Proposes a better approach with reference to professional guidance

Common Failures in Critical Analysis

Describing outcomes rather than analysing decisions. "The project was delayed" tells us nothing. "The project was delayed because the employer failed to provide timely decisions on design queries, creating an entitlement to an extension of time under the contract that was not effectively managed" begins to be analytical.

Asserting without evidencing. "This was not best practice" requires you to say what best practice is and why this falls short of it.

Analysing the wrong things. Students sometimes spend significant effort analysing minor administrative processes and then treat the most significant event on the project such as a contractor insolvency, a major planning refusal, a contamination discovery, in a paragraph. The most significant events are almost always the richest sources of analysis. Give them the attention they deserve.

Staying at the surface. Many students identify that something went wrong but do not explore why, what the contributing factors were, or what a different approach would have looked like. Push yourself to go deeper.

Over-claiming. Critical analysis requires intellectual honesty. If you are not certain why a decision was made, say so, and explore the possible reasons. If the approach taken had legitimate justifications even if you would have done it differently, acknowledge them.

Writing Reflective Analysis

Reflection is not the same as self-criticism, and it is not the same as describing your feelings about a project. It is a structured process of learning from experience that informs future professional behaviour.

The Purpose of Reflection in a Case Study

You are writing as an emerging professional, not a neutral academic observer. Your direct experience of the project that is, what you observed, what you were involved in, what you understood at the time and what you understand in retrospect, is part of the evidence base for your analysis.

Reflection asks you to bring your own experience and perspective explicitly into the analysis. What did you think was happening at the time? How has your understanding of it changed since? What would you do if you encountered the same situation again?

A Model for Reflective Writing

A commonly used framework (associated with Gibbs, Schön and others) involves three moves:

Description: What happened? (concise — this overlaps with Step 1 of the analytical method above)

Interpretation: What does this mean? Why did it happen? What frameworks or models help make sense of it? What assumptions or biases might have influenced your understanding at the time?

Outcome: What does this mean for your future practice? What would you do differently? What has this experience taught you?

The 'outcome' move is critical. Reflection that ends with "I found this interesting" or "it was challenging" has not completed the reflective process. You should arrive at a concrete, defensible position: next time I encounter this situation, I will do X, because Y.

What Reflective Writing Looks Like in Practice

Avoid: "I was not very involved in the procurement process as this was handled by the senior architect. I found this frustrating as I felt I could have contributed more."

Instead: "My involvement in the procurement process was limited to administrative support during the tender period. At the time, I understood the mechanics of the process, assembling tender documents, managing the tender list, but I had not fully grasped the strategic significance of the procurement decisions that had been made earlier: why a two-stage design and build route had been chosen, what risks this transferred to the employer, and what implications it had for the architect's ongoing role and liability. In retrospect, and in the light of what I have since studied about procurement strategy, I can see that the choice of procurement route was the single decision with the greatest impact on the architect's authority and exposure on the project. Had I understood this at the time, I would have sought to understand the rationale for that choice more actively. In future projects, I will ensure I understand the procurement strategy before the contract is let, and engage with the client and lead consultant to understand the risks and implications for the architect's role."

Notice what this version does:

• Acknowledges limited involvement without making excuses

• Distinguishes between what was understood at the time and what is understood in retrospect

• Identifies a specific conceptual gap in understanding

• Draws a concrete lesson for future practice

• Connects personal experience to professional learning

Avoiding Common Pitfalls in Reflective Writing

Pseudo-reflection. Describing what happened and then saying "this taught me a lot" is not reflection. You need to say specifically what it taught you and what you would do differently.

Excessive self-criticism. Reflection is not about cataloguing your failures. It is about learning from experience, which includes identifying what worked well and why, as much as what did not.

Reflection as performance. Examiners can tell when reflection is being performed rather than genuinely undertaken. Authentic reflection is specific, intellectually honest, and arrives at conclusions that are clearly connected to the experience described.

Ignoring your own assumptions and biases. Part of reflective practice is examining not just what happened but how your own perspective shaped your understanding of it. If you had a particular relationship with a client, a colleague, or a contractor, how might that have coloured your judgement? Being explicit about this carefully, without oversharing, demonstrates a mature level of reflective practice.

Making Connections

One of the distinguishing features of higher-quality case studies is the ability to make connections — between different parts of the project, between different areas of professional knowledge, and between individual events and broader themes.

For example: a change in procurement strategy might be connected to a client's risk appetite (Chapter 1 and 3); that change might have implications for the architect's appointment scope and fee (Chapter 1); which in turn affects the architect's ability to exercise quality control on site (Chapter 4); which raises ethical questions about the architect's obligations to the end user (Chapter 5).

Tracing these connections across your study, rather than treating each chapter as a self-contained account, demonstrates the kind of sophisticated professional judgement that the qualification demands.

Similarly, look for recurring themes across your project. Do issues of communication, risk allocation, client decision-making, or fee pressure emerge repeatedly? Drawing these together in your conclusions, rather than simply listing isolated observations, shows an ability to synthesise complex experience into coherent professional learning.

Ethical Dimensions

Every case study should address the ethical dimensions of professional practice, not just as a discrete section but woven throughout the analysis.

The ethical dimension includes, but is not limited to:

• The architect's duty to the client versus obligations to third parties and the public interest

• Conflicts between commercial pressures and professional standards

• The architect's responsibility for the safety and wellbeing of building users

• Issues of sustainability and the long-term environmental impact of design decisions

• Fairness in the treatment of contractors, subconsultants and other parties

• Transparency and honesty in professional communications

Ethical analysis follows the same structure as all other analysis: describe the situation, identify the relevant ethical framework or professional standard, and analyse how the situation measures against it. The RIBA Code of Professional Conduct and the ARB Standards of Professional Conduct and Practice are the primary frameworks, but you should also engage with the broader ethical literature where relevant.

Preparing for the Oral Examination

The written case study is not the end point. It is the foundation for an oral examination in which you will need to defend, develop and extend your analysis verbally, in real time.

The most important thing you can do to prepare for the oral is to write a genuinely analytical case study rather than a descriptive one. If you have thought deeply about your project, engaged seriously with the professional and legal frameworks, and arrived at reasoned conclusions, you will have the material you need to discuss it at depth.

Frame your thinking, throughout the writing process, around the question: what would I say if an examiner asked me to explain why I think this? If you cannot answer that question for a claim you have made, revisit it.

The oral is also likely to probe beyond the specifics of your project. Examiners will explore your wider professional knowledge and judgement. The case study is the vehicle; demonstrating that you are ready to practise as a qualified architect is the destination.

A Final Note on Writing Quality

The case study requires clear, precise, professional written English. It is a formal piece of work that will be read by professional examiners, and the quality of your writing communicates your professional competence as much as its content does.

Use subject-specific language accurately. Understand the difference between a Practical Completion Certificate and a Certificate of Making Good; between a variation and a change instruction; between a programme and a schedule. Imprecise use of technical terminology undermines confidence in your professional understanding.

Write in full sentences and paragraphs. Bullet points are useful for lists, not for analysis. Analysis requires argument, and argument requires sentences.

Read your work critically before submission. Ask yourself, for every section: am I describing, or am I analysing? If the honest answer is describing, go back and push further.

The case study is, ultimately, an opportunity. It is a rare occasion in professional life to examine a complex project in depth, connect it to a wider body of knowledge, and draw out the lessons for your own practice. Approached seriously, it is one of the most valuable exercises in professional development that the qualification offers.

References for Reflective writing

Here are some key academic references for reflective practice, with brief notes on what each contributes which may of use:

Primary References

Schön, D.A. (1983). The Reflective Practitioner: How Professionals Think in Action. New York: Basic Books.

The foundational text. Schön describes reflective practice as originating in knowing-in-action — the tacit, intuitive, spontaneous knowing that enables skilful performance — and argues that reflection is prompted when a situation presents as uncertain, unique, unstable, or involves a conflict of values. He distinguishes between reflection-in-action (thinking while doing) and reflection-on-action (thinking after the event). The book examines five professions, engineering, architecture, management, psychotherapy, and town planning, to show how professionals really solve problems. Architecture features explicitly, making it particularly relevant to Part 3.

Schön, D.A. (1987). Educating the Reflective Practitioner: Toward a New Design for Teaching and Learning in the Professions. San Francisco: Jossey-Bass.

The companion volume, developing the implications of the 1983 book for professional education. More directly concerned with how reflective practice is taught and learned.

Gibbs, G. (1988). Learning by Doing: A Guide to Teaching and Learning Methods. Oxford: Further Education Unit, Oxford Polytechnic.

Gibbs created his "structured debriefing" to support experiential learning, designed as a continuous cycle of improvement. The cycle consists of six key stages: description, feelings, evaluation, analysis, conclusion, and action. The cycle can be found in section 4.3.5 of the book. Note: the book was reissued as an open-access reprint in 2013 by the Oxford Centre for Staff and Learning Development.

Kolb, D.A. (1984). Experiential Learning: Experience as the Source of Learning and Development. Englewood Cliffs, NJ: Prentice-Hall.

Kolb published his experiential learning theory in 1984, inspired by the work of gestalt psychologist Kurt Lewin, as well as John Dewey and Jean Piaget. It works on two levels: a four-stage learning cycle and four distinct learning styles. Kolb defined learning as "the process whereby knowledge is created through the transformation of experience." Gibbs's later cycle builds directly on Kolb's framework.

Important Secondary References

Boud, D., Keogh, R. and Walker, D. (eds.) (1985). Reflection: Turning Experience into Learning. London: Routledge.

A key edited collection that develops the relationship between reflection and learning. Boud and colleagues place greater emphasis than Schön on the emotional dimensions of reflection and on how personal feelings shape what is learned from experience. Widely cited alongside Gibbs.

Moon, J.A. (1999). Reflection in Learning and Professional Development. London: Routledge.

A more accessible and practically oriented text that synthesises the theoretical literature and offers clear guidance on how reflective writing works. Useful for understanding the difference between descriptive and analytical reflection.

Dewey, J. (1933). How We Think: A Restatement of the Relation of Reflective Thinking to the Educative Process. Boston: D.C. Heath.

The intellectual precursor to all of the above. Dewey established the foundational idea that learning from experience requires active, deliberate thought. Often cited as the origin of the tradition that Schön and Kolb later developed.

A Note on Using These References in a Case Study

For most Part 3 candidates, citing Schön (1983) and Gibbs (1988) is sufficient to ground the reflective methodology. Kolb (1984) is worth citing if you want to explain the broader theoretical basis of experiential learning. Boud et al. (1985) or Moon (1999) add depth if you are discussing the emotional or affective dimensions of professional experience.

You do not need to engage with the theoretical literature at length, the case study is not primarily a theory paper. A brief acknowledgement of the framework you are using, with a citation, is appropriate before getting on with the substantive analysis and reflection.