Chris Bennett
Last activity
Member since
Votes
3
Subscriptions
8
Replies
Chris Bennett commented,
I still have the option, a link to Upload apprentice(s) using a CSV file underneath the list of learners. Have noticed however that where an employer has given us permission to create a cohort on their behalf, you don't get the upload option straight away, after selecting the employer you are presented with the 'manual entry' screen. You only need to enter a first and last name to get past this, so pop anything in those boxes, you can then delete that dummy learner on the next screen and access the CSV upload link.
I still have the option, a link to Upload apprentice(s) using a CSV file underneath the list of learners. Have noticed however that where an employer has given us permission to create a cohort on t...
Chris Bennett commented,
We have run into this issue this week, we were able to process the change of employer against the existing stopped DAS record, but the new employer is getting an error relating to the date of birth when trying to approve the cohort request that it has generated.
We have run into this issue this week, we were able to process the change of employer against the existing stopped DAS record, but the new employer is getting an error relating to the date of birth...
Chris Bennett commented,
Sanita Roarty there are separate sub-services/roles under Submit Learner Data for these collections, you may need to request access to these via DfE Sign-In (or assign them to yourself if you are the approver for your organisation): Submit Learner Data - FE Workforce Submit Learner Data - FE Workforce Governor
Sanita Roarty there are separate sub-services/roles under Submit Learner Data for these collections, you may need to request access to these via DfE Sign-In (or assign them to yourself if you are t...
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 ...
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...
Chris Bennett commented,
Sam's solution above is the same way we have resolved these when a record has been stopped in error, ask the employer to amend the stop date to match the start date on the stopped record, then add a new record (using the original start date, etc.) to replace the stopped record. Note this applies for levy paying employers, but I would seek further advise from the helpdesk if you are working with a non-levy paying employer, as you won't be able to backdate the new record where funding reservations are involved.
Sam's solution above is the same way we have resolved these when a record has been stopped in error, ask the employer to amend the stop date to match the start date on the stopped record, then add ...
Chris Bennett commented,
Bud is frustrating in that it automatically defaults to exactly 'x' months after the apprenticeship start date (based on what is configured in the programme build) with no mechanism to confirm or alter this date through the front-end. We remove the FS aims from the ILR export when adding the learner to the ILR in Bud, and then re-activate the aim(s) and manually adjust the start and end dates accordingly once we have the first day of learning confirmed for English/maths. This ensures we don't inadvertently start drawing Functional Skills funding for a learner.
Bud is frustrating in that it automatically defaults to exactly 'x' months after the apprenticeship start date (based on what is configured in the programme build) with no mechanism to confirm or a...
Chris Bennett commented,
Yes, we have been getting the warning message appear when adding learners at the new funding band, and this is also appearing for employers, however it hasn't prevented us or the employers from approving the records at the new higher prices. The indicative ILR report is showing the correct funding band maximum and profiling the payments as expected. Despite not recognising the funding band change, the Apprenticeship service is putting all our September starts on v1.4 of the Team Leader standard, even those that started before 19th September/25th September (learners imported via CSV upload so the file had the exact start date).
Yes, we have been getting the warning message appear when adding learners at the new funding band, and this is also appearing for employers, however it hasn't prevented us or the employers from app...
Chris Bennett commented,
Just adding these bits (couldn't fit them in my original post!) Provider Support Manual The way total negotiated price (TNP 1) is calculated is changing from 1 August 2022, and will be calculated as follows: Funding band max - RPL savings - any other employer discount (e.g. large cohort) Anything over and above the funding band is dealt with off-line between the provider and employer; the DFE does not need to know about this amount or have it recorded in the ILR or apprenticeship service. The provider also does not need to record that this money was collected from the employer. Apprenticeship Funding Rules P106 When you agree a price with the employer, your starting point must be no more than the maximum of the funding band for the standard. P106.1 If the price you agree with the employer exceeds the maximum of the funding band, then you must agree off-line (outside of the ILR and apprenticeship service) how the employer will pay you any difference. We do not need to know about the amount of this difference. You may charge VAT on the difference.
Just adding these bits (couldn't fit them in my original post!) Provider Support Manual The way total negotiated price (TNP 1) is calculated is changing from 1 August 2022, and will be calculated ...
Chris Bennett commented,
Have been running into the same problem today, can create a new cohort and add the first apprentice details, but clicking 'add another apprentice' to add the 2nd+ learners threw up the error message every time. These are cohorts created today so I don't think getting your employers to resend the requests will help Gary Petley - sorry! CSV upload is working fine, and is actually a significant improvement with the changes they've made. We have 'add apprentice records' permissions with most of our employers, but previously had to create a cohort and add details for a first dummy learner manually, just to get to the upload CSV link which always felt like a clunky process. You can now upload a CSV with up to 100 new apprentice records, even if they are all from different employers. If you've got 'add apprentice records' permissions then leave CohortRef blank in the CSV file and it will create the cohorts for each employer when you import. This is really useful for our large 'group' type employers, where one cohort of learners actually sit across several levy accounts as they all belong to different businesses within the group. Unfortunately CSV import still needs dates in the YYYY-MM-DD format, so takes a bit of care to make sure you don't end up with dd/mm/yyyy dates if you are manually preparing or tweaking a CSV file with Excel, etc.
Have been running into the same problem today, can create a new cohort and add the first apprentice details, but clicking 'add another apprentice' to add the 2nd+ learners threw up the error messag...