A teaching portfolio is meant to prove how well you teach, and most portfolios fail at the only job that matters: giving a reviewer evidence they can weigh. A page of warm comments and a list of courses is a keepsake, not a case. The portfolios that survive a promotion panel are built from the same material you already generate every term. That material is student feedback, assessment results, changes you made and what came of them. This guide shows you what counts as evidence and how to bank it as you go.
Pulse is Lectimax's module for reading student feedback and evaluation data. It turns the raw comments and scores into a record you can point to. You interpret the numbers and explain what they mean.
What counts as evidence in a teaching portfolio?
Evidence is anything a reviewer can check, which rules out most of the usual padding. A student who wrote a paragraph praising your lectures is a claim about you, not proof of what the students learned. Evidence is material from your teaching record. It is the learning outcomes you set, the assessments you ran and the distribution of results. Add the feedback you got back and the change you made in response. The test for evidence is simple. Could a colleague look at it, without knowing you, and reach the same conclusion about your teaching? If yes, it belongs in the portfolio. If the item only makes sense because you are the one holding it up, it is testimony and it carries little weight.
The strongest single piece of evidence is a documented improvement loop. You ran an assignment and the results were weak. You redesigned the teaching, and the next cohort did better. An assessor can see the whole arc. That loop is harder to fake than any testimonial, which is exactly why it convinces.
How do you collect evidence instead of hunting for it?
Hunting for evidence in the week before an application is miserable, because most of it is already gone. Deadlines pass, tabs close, feedback files sit unread. The reliable way is to bank evidence as it lands, in the same rhythm as the term itself. When you brief an assignment, save a copy of the brief and the rubric. When results come back, keep the distribution and a one line note on what surprised you. When student feedback arrives, record the themes rather than the raw comments.
This is where Pulse earns its keep. Because it reads the feedback and evaluation data as it is produced, you end each term with a running record instead of a last minute archaeology project. You notice the pattern and act on it; the record is simply there when you need it.
What does the evaluation data actually show?
Evaluation scores are a snapshot of student satisfaction on the day they filled the form, not a verdict on your teaching, and it pays to read them that way. A low score on a hard, fast paced module is not the same signal as a low score on an easy one. The useful reading is in the movement: are the scores improving across the term, and where do the comments cluster? A sharp lecturer reads the data for direction, not for judgement, and writes that reading down.
Satisfaction data says little about learning on its own. Students can leave happy and learn less than a grumpy cohort that actually mastered the material. So pair the satisfaction numbers with learning evidence: results, completion rates, and whether the work met the outcomes. Together they tell a story that neither tells alone.
How do you present evidence so an assessor can read it fast?
A reviewer sits with a stack of portfolios and minutes to spend on each. Help them by structuring for speed. Open with a short claim about your teaching. Support it with three or four pieces of verifiable evidence. Each block covers what you did, the evidence it produced and what changed as a result. Keep each block to a few lines. A portfolio that reads like a memo wins over one that reads like a diary.
Name the limitations rather than hiding them. A module with stubbornly flat satisfaction scores is only a problem if you present it without context. State what the data could not tell you and what you tried. Assessors reward candour, because they are trying to predict how you will teach, and a lecturer who can name a weakness and a response is easier to trust than one who presents a perfect record.
Where does student feedback fit, and where does it not?
Student feedback earns its place in a portfolio as one thread of evidence, not as the headline. It is the students' experience of your teaching, which matters, but it is not proof of learning and not a substitute for your judgement. A review panel wants to see that you collected it, read it and acted on it, not that you collected praise. Quote a specific change you made because of what students told you: a reordered module, a worked example added, a clearer brief. That turns a sentiment into evidence.
The trap is the file of pure compliments. It comforts the writer and convinces nobody. If your feedback file is all warm words and no documented adjustments, the portfolio will read as vanity, however sincere the warmth was.
FAQ
How many items should a portfolio hold? It should cover each outcome and each course you claim. That usually means four to six strong evidence blocks, rather than thirty thin ones. Three well documented improvements outperform a shelf of testimonials.
Do I need student comments at all? You need evidence you read them and acted on them. A single specific change you made in response beats a page of praise, because it shows the loop closing.
Does Pulse replace my judgement about my own teaching? No. Pulse organises the feedback and evaluation data so you can see it clearly. You decide what the numbers mean and what to change.
The portfolio you can defend is the portfolio you bank as you teach. If you want to see how the rest of Lectimax pulls a semester together, start with what AI grading means in higher education and the feature tour. New accounts start with 200 free credits to test the workflow.