Time poverty is the new hidden barrier

This week, Dr Stuart Grey discusses time poverty and student voice evidence: how low-income students lose study time through work, travel, administration, money pressure, and systems that assume spare capacity.

The episode covers time poverty as widening participation evidence, fair process in student evaluation systems, Cardiff's QER recommendation on student voice mechanisms, Advance HE's TEF analysis, and practical ways to read comments about workload, organisation, and trust as evidence about system design.

In This Episode

Why time functions as a classed resource for low-income students.
How timetable design, attendance requirements, deadline bunching, travel, and payment schedules can reproduce inequality.
Why student evaluation systems earn trust through procedural justice, not just fair-looking scores.
What Cardiff's QER recommendation says about representation, support structures, and wider student engagement.
How TEF evidence can miss the technicians, demonstrators, studio staff, and lab teams students actually experience.
A practical way to split mixed comments before turning them into action plans.

Student Voice Practice

Time poverty comments should not be filed only as individual resilience or study skills issues. They are often evidence about scheduling, workload, communications, finance, placement design, and whether the course leaves students enough room to participate. The useful question is not simply whether students are working hard, but whether the system is spending time they do not have.

Research Spotlight

Across the Sector

From the Archive

Practical Takeaway

Take one programme where work, travel, care, or placement pressure is already visible in the comments. Map the first four teaching weeks against contact hours, gaps between sessions, deadlines, attendance rules, and administrative pinch points. If the map shows the course needs spare time students do not have, that is widening participation evidence.

Full Episode Page

https://www.studentvoice.ai/podcast/episodes/015-time-poverty-is-the-new-hidden-barrier/

Subscribe to The Student Voice Weekly: https://www.studentvoice.ai/blog/newsletter/

Transcript

Hi, and welcome to Student Voice Weekly. I'm Dr Stuart Grey, founder of Student Voice, and today I'd like to talk about time poverty, and why it quietly shapes student inequality and whether feedback gets used at all.

When students talk in surveys and module evaluations, it often comes out as workload, deadline clashes, attendance rules, late timetable changes, admin delays, commuting, placements, or money stress. Staff often raise different surface concerns, like whether they trust evaluation systems, and whether it feels safe or fair to engage with them. The key thing is that underneath both is the same design assumption: that people have time or capacity to spare.

You see this in very ordinary ways. Someone misses a class because a work shift changes. Someone arrives late because transport fails and there is no buffer. Someone cannot make office hours because caring responsibilities sit right on that slot. Then we look at attendance flags, engagement dashboards, or non submission, and we treat it like an individual problem, instead of asking what our systems are doing to people with tight lives.

In the main story this week, the first research signal comes from Adi Sapir and Roni Strier's paper, "Time as privilege: exploring the intersection of social class and temporality as sources of invisible inequality in higher education". It is based on interviews with low income students. Time behaves like money. Some students have slack, and some are living in constant time debt. If you have financial buffers, you can buy time: live closer to campus, drop a shift, pay for a taxi when transport collapses, or absorb a late timetable change. If you do not have those buffers, university becomes a continuous juggling act.

That is where a lot of supposedly neutral practice stops being neutral in its impact. Timetables that move around. Deadlines that bunch up. Assessment patterns that assume evenings and weekends are available. Attendance requirements that do not recognise commuting complexity. Admin processes that require multiple steps during working hours. Each decision can sound reasonable on its own. Put together, they create friction that lands hardest on the students you most want to support.

There is also a student voice risk here that is easy to miss. When time poverty occurs, students disengage from the very things that generate the data we rely on. They do not come to focus groups. They skip mid module surveys. They cannot get to student staff committees. They do not have time to write careful evaluation comments. Then we look at thin feedback and assume things are fine, or we treat the students with the time to respond as the student voice. Make sure you notice that selection effect, because it can quietly hollow out your evidence base.

So what should a UK university do with this, in practical planning terms?

First, treat time as a resource you can increase or waste through design choices. A useful move is a time audit, similar in spirit to an accessibility audit. Pick a programme and ask: where are we spending student time that does not contribute to learning? How many platforms do they have to use each week? How many small admin steps do we create? How often do we change the timetable after teaching starts? How often do we release key information late, or shift deadlines late? These are not glamorous fixes, but they are exactly what students describe in open text.

Next, apply the same lens to staff time and to whether evaluation evidence is trusted. The issue also highlights Corrine Keke Chen's paper, "Justice and the legitimacy of student evaluation systems in higher education: a systematic review". The practical takeaway is that trust comes from procedural justice. Do staff understand the purpose of evaluation, the stakes, and what decisions it can affect? Do they understand how comments will be analysed, and what will and will not be inferred from scores? Are there safeguards against misuse? Do they have a voice in interpretation, and time to discuss what the feedback means?

If the process is clear, the use is developmental, the analysis is careful, and there is time to talk, you get very different behaviour than when the process is opaque and inconsistent. Staff either engage with feedback, or they treat it as something to defend against. Students pick up on this quickly. They can tell whether anyone is listening, whether changes are explained, and whether feedback disappears into a black box.

Across the sector, two updates connect to this theme.

One is the Quality Enhancement Review at Cardiff, where a recommendation pointed to student voice mechanisms needing clearer purpose and wider reach. That matches a pattern I see a lot. Institutions can have busy, procedural representation structures that still feel disconnected from the wider student body. The risk is that representation is treated as the whole student voice, while widespread themes in comments never quite become visible in formal decision making.

The second update is about TEF evidence. Advance HE looked at TEF submissions and found many did not reference technicians and similar delivery roles. What students are actually saying, especially in practice based subjects, often points to the real delivery model: demonstrators, lab teams, studio support, placement supervisors, and professional services. If your narrative about teaching excellence is lecturer centric, you end up telling an incomplete story about what students experience, and you miss practical levers for improvement.

Now bring this back to the day to day job of reading student comments. With time poverty in mind, I would separate three kinds of message that often get mixed together.

First, comments about time cost and friction. You will hear: I spend hours travelling, deadlines collide, the timetable changed again, recordings go up late so I fall behind, admin is impossible to reach, I have to chase basic information. Treat that as evidence about system design. It often clusters by programme, by year, by week in the term, or around specific assessment points.

Second, comments about fairness in rules. These can sound like workload complaints, but they are often about whether policies make sense given students' constraints. Attendance is an obvious one, but also extensions, penalty rules, resit timing, group work processes, and how placements are scheduled. Students are asking whether the institution understands constraint, and whether rules are applied in a way that feels legitimate.

Third, comments about trust in the process. These are the ones that sound like: we keep saying this and nothing changes, staff do not read the comments, we get asked for feedback constantly, the university only listens when it affects metrics. For staff you see the mirror image: surveys are used against us, comments are unfair, students do not understand context. Those are signals about legitimacy, and you address them through governance and communication, with visible examples of change, clear boundaries on use, and time for dialogue.

Different messages need different actions. Time cost issues often need operational fixes. Fairness issues need policy review and clearer explanations. Trust issues need clearer processes, better feedback loops, and protected time for discussion.

One practical exercise to try this week is simple. Take one programme and map student time pinch points across a four week window. Look at timetable stability, assessment bunching, required in person moments, placement travel, admin deadlines, and when key information is released. Then lay your recent free text comments alongside that map.

You are looking for where pinch points align with negative comments, because that tells you the system is creating the experience. You are also looking for where pinch points exist but comments are quiet, because that can tell you who you are not hearing from. If commuter students or students with heavy work hours are missing from the data, you may have built a feedback system that mainly hears from students with more slack.

If you want to go one step further, identify one change that reduces time cost without lowering academic standards. Spread deadlines, publish assessment briefs earlier, cut duplicate admin steps, set a threshold for timetable changes, or make office hours more reachable. Small changes can have a big equity effect when time is tight.

That's it for this week. The full set of links and summaries is in Student Voice Weekly, and you can subscribe at studentvoice.ai. If this was useful, please could you follow or subscribe to the podcast, share it with someone working on student experience, quality, or planning, or leave a quick review in your podcast app. Thanks!