Organising around the right players? Or the neatest schedule?

Back

You’ve agreed four groups: Tuesday and Wednesday, at 2pm and 5pm each day.

Then, before recruitment has properly started, each cohort gets assigned a specific slot.

Why?

If there’s a research or operational reason, fair enough. But if the answer is “we like to have the running order sorted”, it’s worth considering what that decision could cost you.

A suitable player can become unsuitable for your timetable

Imagine you’re recruiting two different player cohorts.

You find suitable, validated applicants for both. But players in one cohort are mainly available at 5pm, while the running order puts their group at 2pm.

They can attend an agreed session time. They meet the participant requirements. Yet they cannot be booked because their cohort has been assigned to another slot.

You’ve created an additional recruitment restriction without changing a single screener question.

The research needs their experience. The timetable needs their Tuesday afternoon. Those are different requirements.

Agree the framework. Keep the running order flexible.

There’s a straightforward alternative.

Agree the fieldwork dates, session times, group requirements and any genuine scheduling dependencies upfront. Recruit and validate against that framework, recording applicants’ availability across the agreed slots.

Then assign cohorts to sessions using the availability of suitable players.

This still requires organisation. It requires accurate availability records, clear communication and a deadline for confirming the running order.

What it avoids is treating an early scheduling preference as an immovable research requirement.

Some running orders have a purpose

There may be dependencies between sessions, different moderators, observers who need to attend particular groups or findings from one session that inform the next.

Those constraints belong in the brief because they affect recruitment.

But where sessions can run in either order, flexibility should be the starting point. A running order inherited from the last project deserves the same scrutiny as any other requirement.

Don’t pass unnecessary constraints on to participants

Players have jobs, studies, families and other commitments. Their availability is part of recruitment feasibility.

We should take those commitments seriously, particularly when someone can attend one of the sessions we’ve already agreed to run.

Otherwise, we risk rejecting suitable players, extending recruitment or asking people to rearrange their lives to protect a timetable that could have been changed.

Plan around what the research actually needs

Before fixing a cohort to a slot, ask:

What would go wrong if these groups ran in a different order?

If there’s a clear answer, plan for it.

If there isn’t, leave room to organise the sessions around the availability of the right players.

A tidy running order is useful. Filling every session with suitable participants is the objective.

Planning your next fieldwork? Share the brief and available session times with Gromotion. We’ll help identify which scheduling constraints matter and where flexibility could support recruitment.