WRIT6000 Chap.10 Case Study Reporting and Reflection
Case Study Reporting and Reflection
A case study report turns dated weekly records into comparison, interpretation and transferable professional learning. A chronology can show that activities occurred, but it does not yet explain what the group learned about professional writing or why the learning matters beyond one exercise.
This chapter distinguishes description from reflection through a four-move sequence: describe the specific choice, evaluate its result against audience and purpose, connect the evidence to a course concept, and state how future action will change. Each move needs a record.
Draft comparisons, peer comments, task notes, sources and decision logs let writers show what changed instead of relying on retrospective claims that the group improved. Report-level synthesis then names a relationship across cases. One week may show how audience research altered a proposal, while another shows how peer review exposed an ethical assumption.
Together they can support a larger claim about evidence-based revision if the report compares them explicitly. Appendices can verify activity but cannot perform the analysis for the reader. The prose must select, interpret and connect the evidence. Reflection also needs calibrated limits: a small classroom result may demonstrate a useful practice without proving it works in every workplace.
Accurate acknowledgements, references, contribution records and file checks complete the report's accountability. The result is a case study that explains decisions and transfer, not a polished stack of weekly summaries.
What this chapter covers
- 01
Weekly records, screenshots and source details
- 02
Selection of relevant case evidence
- 03
Comparison across workplace genres
- 04
Describe, evaluate, connect and transfer
- 05
Report-level claims and visible limitations
- 06
Appendices, acknowledgements and submission verification
Worked example · free
Rebuild a generic group reflection
- 1Describe the initial writing choice accurately.
- 1Use review evidence to evaluate its result.
- 1Name the concrete revision that followed.
- 1Connect the change to a course concept.
- 1State a future team practice that transfers the lesson.
Key terms
- Case study
- A bounded account that uses specific evidence to analyse practice in context.
- Synthesis
- The explanation of a meaningful relationship across several pieces of evidence or cases.
- Reflection
- An evaluation of experience that connects evidence to concepts and changes future action.
- Transfer
- The application of a lesson from one writing situation to a new professional context.
- Evidence trail
- The records that allow a claim about process or change to be checked.
Case Study Reporting and Reflection FAQ
How does a case study differ from a weekly summary?
A weekly summary records what happened. A case study selects details to analyse a problem, choice, result and lesson in context. The final report compares cases so it can support a larger claim about professional writing practice rather than presenting a chronological stack of activities.
What makes reflection analytical?
Analytical reflection describes a specific choice, evaluates its result against audience and purpose, connects the evidence to a course concept and states how future action will change. Generic claims about learning or teamwork do not show what produced the insight or why it transfers.
What evidence should the group preserve?
Keep dated task notes, screenshots, draft comparisons, peer comments, source details, meeting decisions, role records and AI-use information. Appendices can verify activity, but the prose must still explain why the evidence matters. Remove unrelated personal information and follow the current task instructions.
Assessment move
After each tutorial, save the task record in a shared location and write four lines: what the group chose, what evidence informed the choice, what changed after feedback and what principle might transfer. Add the genre, intended audience and purpose so the later report can reconstruct context. Preserve a before-and-after excerpt for consequential revisions, along with the comment or discussion that prompted the change.
At the end of every two weeks, label each record using one or two course concepts such as rhetorical situation, higher-order revision, ethical representation, inclusion or deliberative persuasion. Do not force a connection if the evidence is weak. Midway through the unit, spread the records across a table and look for relationships rather than repeated topics.
Ask whether audience research changed later document design, whether collaboration altered how evidence was evaluated or whether revision exposed an ethical issue. Draft two possible report-level claims and test each against at least two cases and a permitted source. For every claim, write a counterexample or limit. Choose the claim that explains the evidence without erasing important differences.
Build each case paragraph through describe, evaluate, connect and transfer. Check that description is specific enough to verify, evaluation uses an audience and purpose, the concept clarifies the result and the transfer statement changes a future practice. Use appendices for supporting records, but point to the relevant evidence and interpret it in the prose.
Ask another group member to trace every synthesis claim back to its cases. Remove or qualify any claim that exceeds the record. Before submission, reconcile references, contribution information, acknowledgements, appendix labels, file names and required companion materials with the current task instructions. Save the submitted package and receipt together so the evidence trail remains complete.
