Waiting to hear back: silence, chasing, and the applicant group chats

Between pressing submit in October and hearing anything real, there is often a gap of eight to twelve weeks in which absolutely nothing happens. No acknowledgement beyond an automated one. No indication of whether you're being considered. Nothing you can act on.

This is the part of the process nobody prepares you for, and in my experience it does more damage to people than the rejections do. Rejection at least resolves something. The silence just sits there, and it sits there through Christmas, through mock exams, and through everyone at school asking how the applications are going.

So: what's actually happening, what you can do about it, and how to use the informal intelligence networks that have grown up around all this without letting them make you worse.

Why it takes so long

It helps to understand that the delay usually isn't about you at all.

Large schemes take applications in a window and then process them in batches, because the assessment centres are booked as physical events on specific dates with a fixed number of assessors. If the January centre is full, your perfectly good application sits until the February one is scheduled. Nothing about the wait is a signal.

Recruitment teams for these schemes are also small — often a handful of people handling several thousand applications alongside their other work — and the volume is genuinely enormous. Employers also hold reserve lists. If you've been through an assessment centre and heard nothing, it's entirely possible you're on one, waiting for someone else to decline.

And the calendar has dead zones baked into it. Mid-December to early January is one. Late July and August, when half the team is on leave, is another. The application timeline maps where those fall across the year.

Track it yourself, because nobody else will

The single most useful habit: keep one spreadsheet of every application. Employer, role, date applied, stage reached, date of last contact, deadline for anything you owe them, login details for whichever portal they use.

This sounds like admin theatre. It isn't, for three reasons. It stops you missing a deadline in a portal you forgot you'd registered with, which happens more than you'd think when you're running fifteen applications across fifteen systems. It gives you something to do with the anxiety that isn't refreshing your email. And in February, when you're deciding whether to chase, it tells you at a glance who has genuinely gone quiet and who you contacted last week.

The government's Find an apprenticeship service will do part of this for you. If you create an account — it uses GOV.UK One Login — you can track applications made through the service in one place, save searches, and set up email or text alerts when matching vacancies appear. That's worth doing on day one, though be aware it only covers vacancies advertised through that service; anything you applied for directly on an employer's own site won't appear there, and plenty of the best schemes are advertised both ways or only directly.

Set the alerts up even if you've already applied everywhere you plan to. Late vacancies are real, they're covered in how to find degree apprenticeships, and an alert costs you nothing.

When chasing helps, and when it doesn't

The rule I'd give: chase when a stated deadline has passed, and not otherwise.

If the advert or the email said "we'll be in touch by the end of January" and it's the second week of February, a short polite email to the recruitment address is entirely reasonable and occasionally shakes something loose — applications do fall through cracks, especially where an agency sits between you and the employer. Keep it to three lines: which role, when you applied, and asking whether there's an update on timescales.

If no deadline was given and it's been three weeks, chasing does nothing except mildly annoy someone who has four hundred emails. It won't hurt you, but it won't help either, and the belief that it might is what keeps people awake.

What genuinely does help: if something material changes, tell them. You've got a confirmed offer elsewhere with a decision deadline, you've won an award, your predicted grades went up. That's a legitimate reason to make contact and it occasionally accelerates things, because a candidate about to accept somewhere else is a candidate they might lose.

Ghosting is normal, and it isn't personal

Some employers will simply never reply. Not a rejection, not an acknowledgement, nothing, ever.

It's poor practice and I won't defend it, but it is common enough that you should plan around it rather than wait through it. Certain parts of the market are worse than others — applications routed through third-party recruiters, and organisations where each individual department recruits separately with no central team, are the ones I'd expect least from. That last pattern is why some large public-sector and health employers develop a reputation for silence: there often isn't a single recruitment function to chase.

The practical response is to treat any application with no contact for eight weeks past its stated closing date as closed, mentally, and get on with the others. If they come back later, that's a bonus. Do not leave a slot open in your head for it.

The group chats, forums and Discords

Every application season, applicants find each other. There'll be a thread on a student forum for each big scheme, a WhatsApp group that forms after an assessment centre, a Discord for a particular sector. These are genuinely useful, and they're also the main source of avoidable misery in this process. Both things are true.

What they're good for. Timings, mostly. Knowing that other people applied in October and heard in late January tells you the silence is structural rather than about you, and that's worth a lot. They're also good for practical logistics — what the dress code actually was, how long the day ran, whether the office is walkable from the station — and for the plain fact of other people going through the same thing at the same time.

Where they mislead you. Four ways, in roughly the order they catch people out.

The people posting are not a random sample. Those who got early offers post; those who heard nothing mostly don't. Whole threads can convince you that everyone has heard back when in fact you're seeing the fastest tenth of the process.

Last year's information is confidently repeated as this year's. Processes change every cycle, and a thread from two years ago describing four stages may be describing a funnel that no longer exists.

Confidence and accuracy aren't correlated. The most assertive poster in a thread is frequently a candidate who has been through exactly one process, once, and is generalising from it. I have been that person in other contexts and I'd be wary of me too.

And they run on other people's anxiety. A rolling feed of "has anyone heard?" at 11pm in February is not information. It's a machine for turning one person's nervousness into forty people's.

Where the real risk is. When you sit an online test or attend an assessment centre, you almost always tick past terms that prohibit reproducing or sharing the content. Posting the actual questions, the case study brief, or screenshots of a test is a breach of that, and it is the kind of thing that can cost someone an offer if it's traced back to them. Reputable forums moderate this stuff off their platforms for exactly that reason, which is a large part of why the sharing has migrated to private group chats where nobody is moderating anything.

My honest advice: take the timings, take the logistics, take the company. Don't take or pass on the test content. The marginal advantage from seeing a leaked question is small, and the downside if it comes back to you is your offer.

There's a related and much more positive use for these chats later, once offers are out and a cohort starts organising housing — that's a different thing entirely and it's covered in finding housemates before day one.

Protecting your head through it

Three things I'd actually recommend, having watched a lot of people do this badly, myself included.

Batch your checking. Twice a day, at fixed times. The notifications are the problem, not the emails. Nothing in this process is so urgent that ninety minutes of delay costs you anything.

Keep something in your life that isn't this. In the December of my application year, the applications had quietly eaten everything — my weekends, my conversations, my sense of how the year was going. The thing that helped was having a part-time job that didn't care about any of it.

Don't run a public scoreboard. School turns this into a league table fast, and it's a bad one, because the person with four offers in November may have applied to less competitive schemes, and the person with none in February may be sitting on a reserve list for the best programme in the room. Tell the people you actually want to tell.

And keep the UCAS application running properly in parallel. Not as a consolation prize — as the thing that means the silence is survivable. Rejected everywhere covers what to do if it comes to that, and it's less bleak than it sounds.

The one-line version

The long silences are about assessment centre scheduling and application volume, not about you — so track everything in one spreadsheet, use the Find an apprenticeship account for alerts, chase only when a stated deadline has passed, and treat anything silent eight weeks past its closing date as closed.

Use the group chats for timings and logistics, ignore them for predictions, and never post the test content — that's the one thing in this process that can actually cost you an offer.