Chris Bennett

Last activity

Member since

Votes

3

Subscriptions

9

Replies

Community Reply

Chris Bennett commented,

Community Reply

Chris Bennett commented,

Community Reply

Chris Bennett commented,

My interpretation of this is I think the same as Steve Hewitt - that provided BILs are rolled over and continue to be reported as a break until they return or withdraw, they won't be treated as an overdue break (and thus withdrawal) under the QAR methodology. I actually wonder if this has always been the case...and the only change is that this has now been clarified by the addition of the reference to continuation of break records in the guidance? (aside from the changes to not use R04 data of course). Overdue breaks is the bit of the QAR that I've never quite mastered, my internal calculations are normally spot on, except for where I have expected the odd long-term break to be treated as overdue and counted as a withdrawal under QAR, but it hasn't. As a provider, we always roll ongoing breaks into the current ILR year until they return or withdraw, and if converted to a withdrawal, we would include them in the ILR data for the year when that decision took place, which is the year they then impact the QAR (reporting year becoming the hybrid year end if it's later than the planned or actual end date). I had assumed the intention of overdue breaks in the methodology was to prevent providers manipulating QAR by just leaving learners on a break instead of withdrawing them, but the AAF would now cover that, as your percentage and duration of breaks would flag you if you tried to do that, but perhaps that is no longer (or was never) the reason for it.

My interpretation of this is I think the same as Steve Hewitt - that provided BILs are rolled over and continue to be reported as a break until they return or withdraw, they won't be treated as an ...

Community Reply

Chris Bennett commented,

I've noticed the same on R10 and R09 returns, with reports taking in excess of 2 hours to be generated. This was quite common a few years ago but had been greatly improved until now, not sure why the processing has slowed down again.

I've noticed the same on R10 and R09 returns, with reports taking in excess of 2 hours to be generated. This was quite common a few years ago but had been greatly improved until now, not sure why t...