Give written feedback to faculty as a university program coordinator

Context

A program coordinator, department chair, or academic director who has just received teaching evaluation survey results — from students or a self-assessment process — and needs to write individual, formative written feedback for one or more faculty members on their team. Use at the end of a semester, before the follow-up conversation with each faculty member.

Originally written for Chilean higher education. References to "coordinador de carrera" (program coordinator), "encuesta de evaluación docente" (teaching evaluation survey), "CNA" (Chile's National Accreditation Commission), and "Ley 19.628" (Chile's data privacy law) apply specifically to the Chilean system. Adapt role names, evaluation instruments, accreditation bodies, and privacy regulations to your local context.

Paste first

Before opening the model, have ready:

• Quantitative results from the survey: averages per dimension and, if available, comparisons with the program average or previous semester
• Anonymized qualitative comments from students
• Course name, level, and semester evaluated
• Any relevant context about the faculty member: if this is the first time they've taught the course, if the student cohort had particular characteristics, if they changed their teaching method this semester
• The improvement focus if you already have one in mind

Privacy rule: Do not paste student names or anything that could identify who said what in qualitative comments. Results must be anonymized before copying to the model — comply with your institution's data privacy policy.

Act as a higher education academic management advisor with experience supporting faculty teams at universities. I'm going to share the results from a student teaching evaluation survey and need your help writing individual, formative written feedback for a member of my faculty team.

This feedback is part of the program's internal formative coaching — it is not a summative evaluation process and will not be used for contract renewal or accreditation decisions without proper institutional review. The tone should be that of a colleague in a coordination role, not a formal performance evaluator.

**Faculty and course details:**
- Program: {{program name, e.g., "Civil Engineering" or "Nursing"}}
- Institution: {{institution name or type, e.g., "accredited regional university" or "technical institute"}}
- Course evaluated: {{course name and level, e.g., "Project Management, third year" or "Anatomy I, first year"}}
- Faculty member: {{descriptor or initials, e.g., "Prof. Herrera" or "faculty member with 7 years in the program"}}
- Period evaluated: {{semester and year, e.g., "Spring 2026" or "first semester 2026"}}
- Survey instrument used: {{brief description, e.g., "6-dimension Likert 1-5 institutional survey + open-ended question"}}

**Survey results (no identifiable student data):**
{{paste quantitative results — dimension averages — and anonymized qualitative comments as you have them}}

**What I need:**

1. An opening paragraph (3-4 sentences) that acknowledges the concrete strengths the results show: which specific aspects students valued and why they matter for learning in this discipline.
2. A development paragraph (4-5 sentences) that identifies the area with the largest gap between the current level and what the program expects, explaining its concrete pedagogical impact on the student group.
3. A practical, actionable suggestion: something the faculty member can incorporate in the next module or semester without needing additional professional development or new resources.
4. A closing paragraph (2-3 sentences) that proposes a next coaching step: a follow-up conversation, syllabus review, co-observation, or joint planning session.

The final text should be 280 to 380 words, written in second person, and sound like a professional conversation between colleagues with differentiated roles — not an administrative report.

**Important:** if the results include ambiguous data or qualitative comments that contradict each other, flag this before drafting and ask me how I'd like to address it.

**Privacy notice:** This feedback is an internal academic management input. Do not use this text as evidence in termination processes, position competitions, or any formal procedure without legal and institutional review.

Expected output

Real example (trimmed):

Before drafting, I want to flag that the two lowest dimensions —Teaching
methodology (3.4) and Feedback on assessments (3.1)— point to different
problems. I've focused the development paragraph on feedback on assessments
(the larger gap). Let me know if you'd prefer a different focus.

Strengths
Your disciplinary expertise (4.7/5) and program completion (4.8/5) build
genuine trust with the group. Your availability and approach to students
(4.5/5) reflect a healthy professional relationship — something that is
genuinely difficult to sustain with a high-workload third-year cohort.

Area to strengthen
The lowest dimension is feedback on assessments (3.1/5). In engineering, an
uncorrected mistake carries into later courses. When feedback arrives late and
without explanation, students use the grade as a signal but don't learn from
the evaluation process — exactly the opposite of what they need in a design-
and-construction program.

Suggestion for next semester
A 15-minute group debrief at the start of the next class — covering the two
or three most common mistakes before returning graded work — removes the need
for individual written comments on every assessment while still giving students
timely, meaningful feedback before they see their grade.

Watch out for

• Student teaching evaluation surveys measure student perception at a specific moment in time, not the faculty member's full performance. The model does not know the course context, the student cohort's characteristics, or the semester's conditions — verify that every claim it generates matches what you actually observe in your team.
• Avoid pasting qualitative comments that could identify specific students: overly detailed comments, references to personal situations, or descriptions of distinguishing characteristics. Paraphrase before copying to the model.
• This draft is for informal, formative coaching. Do not use it as input for termination decisions, contract non-renewal, or accreditation reports without institutional and legal review.

Suggested iteration

If the draft is too generic: "The strengths paragraph doesn't reflect our survey's specific dimensions. Rewrite it using only these concrete data points: [list the highest-scoring items and their values]."

If the faculty member has a long tenure and the tone needs to be more careful: "Keep the content but add a sentence at the start of the development paragraph that acknowledges the faculty member's experience in the program, before moving into the area to strengthen."