ARCH9090 Chap.10 Client Reporting and Process Evaluation
Client Reporting and Process Evaluation
The Final Client Report integrates the complete public-involvement process into a professional argument. This chapter connects aims, methods, findings, recommendations and evaluation through a visible evidence chain. It organises findings around client questions rather than method silos, requires reflection on data management and method limits, and converts conclusions into actions with owners, rationales and review points.
What this chapter covers
- 01
A report opening that names the issue, decision context, timeframe and aims
- 02
Background that explains contention without overwhelming the client question
- 03
Methods sections that combine procedure, contribution, recruitment and limitation
- 04
Findings organised by decision theme with integrated evidence and graphics
- 05
Recommendations containing an actor, action, evidence reason and review point
- 06
Process evaluation and reflection linking design choices to evidence quality
Worked example · free
Write a bounded client recommendation
- 1Recommend a time-limited lighting and wayfinding pilot for the specific path. Marks used in this example are an AskSia practice allocation and not a University marking scheme.
- 1Assign the pilot and the separate reliability review to relevant client teams.
- 1Link the path action to interview and observation evidence without calling it the sole cause.
- 1State that the convenience questionnaire cannot estimate population prevalence.
- 1Set a review using movement and accessible user-feedback evidence.
Key terms
- Client report
- A professional document connecting an engagement purpose, evidence, interpretation and recommended action for a decision-maker.
- Traceability
- The visible connection from aim through method and finding to recommendation.
- Recommendation owner
- The person, team or institution responsible for implementing a proposed action.
- Process evaluation
- A reasoned assessment of whether engagement achieved its aims, promise, reach and evidence needs.
- Reflective discussion
- Analysis of how a design or data-management choice affected evidence and what should change next time.
Client Reporting and Process Evaluation FAQ
How should findings be organised?
Organise them around the client’s decision questions or meaningful themes. Within each section, compare questionnaire patterns, interview explanations and contextual evidence. A method-by-method tour makes the client perform the integration and often hides contradiction.
What makes a recommendation usable?
Name who should act, what they should do, why the evidence supports it and when the result should be reviewed. Distinguish an immediate action from a pilot or further inquiry. Broad phrases such as improve communication need a specific route and audience.
What counts as strong reflection?
Explain how a design choice affected reach, data or interpretation, then state a concrete improvement. We worked well is not analysis. Recruitment through existing lists excluded unconnected residents, so the next round needs targeted place-based routes is reflective and actionable.
How should the executive summary handle limitations?
Preserve the same public, place, time and confidence boundaries used in the full finding. Removing limitations to sound decisive creates a contradiction and may lead the client to over-apply the recommendation. A concise summary can name the strongest supported pattern, the relevant group difference, the proposed action and the principal uncertainty.
Readers who stop at the summary should still receive an accurate decision frame. Make the review trigger observable and assign an owner so the qualification governs later action instead of becoming a caution nobody must test.
Assessment move
Outline the report with a traceability table before writing prose. Give each aim an identifier, list the methods that address it, summarise the integrated finding and draft the client action. Any empty cell exposes a gap. Write findings by decision theme and place graphics only where they answer a question; a decorative visual should not displace reasoning. Audit headings and chart titles for claims broader than the sample.
For every recommendation, add an owner and review point. Build reflective notes from the project decision log, focusing on how recruitment, question design, consent or data management changed evidence quality. Complete a final reverse audit from recommendations back to findings, methods and aims.
Confirm appendices and ethical records without exposing participant identities, then check the current Canvas submission instructions. Draft the executive summary after the evidence sections and compare every statement with the full finding. Keep the same group, place, time and confidence boundaries when shortening.
Use a recommendation table with actor, action, rationale, dependency and review evidence so vague verbs become operational. Separate actions supported now from pilots and questions requiring further work. Read the methods section for both procedure and consequence: the client needs to know not only what happened but what the design allowed the team to conclude.
Perform a confidentiality search across body text, quotations, image captions, filenames and appendices. Finally, ask a reader unfamiliar with the project to trace one recommendation backward. They should locate the supporting finding, see the contributing methods and understand the original aim without verbal explanation. If the trail breaks, repair the reasoning before polishing page layout.