break
break

‹‹ Forum

  • Collections Timetable (11 posts)

  • Avatar Image Col said 11 months, 3 weeks ago:

    Hi all,

    I've been having a look at the collections timetable for next year and it appears that the first time LR data needs to submitted is the 06/12/11 (R04). However before this date a number of returns containing 16-18 apprenticeship payments need to be made. If a provider was to submit LR data in these earlier returns (R01,R02,R03) would this cause any problems?

    Thanks!

  • Avatar Image moeszyslak said 11 months, 3 weeks ago:

    Also, is the date for the R14 correct (03/09/2012)?

    Thanks

  • Avatar Image Selvy said 11 months, 3 weeks ago:

    Hi folks

    Please carry on posting queries on the collections timetable.

    We are currently gathering feedback and will come back to you with responses in due course.

    Regards
    Selvy

  • Avatar Image Stephen Paine said 11 months, 3 weeks ago:

    It's a minor thing, but it's not very user friendly to call all the returns "R0x" – if we could revert back to LR0x, F0x, etc, that would keep some of the terminology a bit clearer. I see that the secretariat plan to issue section specific timetables in due course, which will help.

    Thanks

  • Avatar Image martinwest said 11 months, 3 weeks ago:

    It looks like I misread the March information authority board meeting minutes
    Timetable for 2011/12 ILR collections
    Where:
    Colleges funded by the Skills Funding Agency return data quarterly (four times a year plus a final return) and Training providers funded by the YPLA training make four returns annually.
    The board did make the observation that:
    YPLA reviewed the returns timetable and now only require four returns per annum rather than the previous five returns. The Skills Funding Agency will consider whether it can also reduce the number of returns required.

    What have we got?
    For College providers 19 returns, 13 for ER, 5 for LR and 1 for the YPLA

    Well no change there then, but in practice how will we produce the returns.
    We could only return ER data for R01 to R03 but after that it gets a bit complicated due to the validation rules and requirement for a full return after R03. Will the LIS for R05 ignore any validation errors in LR or the other ER datasets not required in this return? And how will we know from our previously sent batch files what return they relate to as the filename or XML no longer contains a return indicator.

    I did notice that there is no reference date for R06 (LR02) but will worry about that after R05.

  • Avatar Image simonfrance said 11 months, 2 weeks ago:

    We're a local authority adult learning provider and we currently return 13 ER, 5 LR and 5 ASL returns.

    The new timetable shows that we must now return our LR data monthly.

    What puzzles me is the relevance of the reference dates and data accuracy expectations.

    The Six Data Management Principles published by the IA sets down the fact that data should not be changed between ILRs. To what extent will this be enforced now that returns are only 4-5 weeks apart? Previously we knew that we had 3 months to make sure everything was input, all leavers recorded as withdrawn and learning aims were correct before the return went in. It can take a week to iron out all the little niggly LIS validation errors that crop up because new enrolments have been made during that time.

    If we deliver some classes in an out-centre in August we may not get the paperwork back to a main centre in time for inputting and quality checking ready for R01. Therefore, they will pop up on R02 with a start date prior to the date of the R01 return. Will we be penalised for that? Previously, it was less important as long as we got them on by the November return.

    I can see my job turning into an endless cycle of ILRs and Data Checks.

  • Avatar Image keithd said 11 months, 2 weeks ago:

    I thought things were going to be made simpler??

    As a provider of 16-18 Apprenticeships, Adult Apprenticeships, 16-18 LR (FE) and AR (FE), with data sitting in 2 systems, (1 for LR/AR the other for ER) not only are we having to await details as to what data will actually be ACCEPTED on which return, but the single Adult Budget now means for us, a merge of AR data from 2 systems AND a separation of 16-18 Apprenticeship data from Adult Apprenticeship data. If you now add the fact that our data is managed by 2 separate teams, who traditionally have submitted their own ILRs, we are now faced with the prospect of having to reorganise our structure and/or business processes to match.

    From a personal perspective, we would be much more productive by being permitted to send ALL (life is too short to work out any changes from last submission) data on a monthly basis and let the powers that be extract the data that they need as and when.

    Keith

    "Life is just one long ILR"

  • Avatar Image Paul said 11 months, 2 weeks ago:

    Hi Keith

    There will be nothing to stop you submitting all of your data monthly. The Data Service will only extract the data needed for the purposes stated in the collection timetable.

    Best wishes

    Paul

  • Avatar Image Col said 11 months, 2 weeks ago:

    Hi Paul,

    So if for example a provider submitted LR data in their R01, R02 & R03 returns does the data need to be correct? i.e. can they ignore any LIS validation errors/warnings related to LR data until they come to submit their R04 return?

    Thanks,

    Colin

  • Avatar Image Paul said 11 months, 2 weeks ago:

    Hi Colin

    Yes, you could ignore the LR validation errors / warnings for those collections. Although it'd be worth looking out for learners doing both LR and ER aims – a problem with their LR data may mean that the learner's record is rejected completely, even if the ER aspect of it is fine.

    Paul

  • Avatar Image keithd said 11 months, 2 weeks ago:

    Thanks for the reply, Paul.

    Following on from your reply to Colin, why can't we have a LIS that is told which return type it is processing (as per now) and then ignores aims which are not relevant. That way we are not going to get zillions of LIS vlaidation errors to wade through.

    Keith
    "Life is just one long ILR"

break
break
break