Replies
No one has replied to this post.
How many weeks are you making your "16 month" programme? 372 sounds about right?
What I *do* know about the PDSAT calculation is that it counts SUNDAYS between start and end date, not just days divided by seven, so it can do some occasionally wacky things and, very much yes, shouldn't be using 31 hours for any starts from 1 August, should be 30 in the calc if EII = 8.
You should never make the data inaccurate just to appease a report!
Hold on, wait a minute, do you mean 23A-217 (Actual less than Plan) or 23A-215 (Plan less than notional value)?
I assumed the latter based on what you were saying.
And, in fact, the logic for 23A-215 *says* it's setting max at 30 for starts after 1 Aug:
Identify learners with ZPROG learning aims WHERE FundModel = 36, LearnStartDate >= 01/08/2019, RES <> 1 AND Phours < minimum planned hours, based on apprenticeship programme planned duration in weeks (adjusted for statutory annual leave entitlement) x least number of weekly employment hours, derived from EII (capped at 30 for starts from 01/082022) x 20%.
HI Steve
thank you , so if we have a learner whos on a 40 hr contract, we should use the employer identify as 21-30 hrs as this is the min now required , this will then reflect against the 372 we have made our plan so the reports will match?
This is incorrect fields being picked as we know they are declaring 40 hours but to satisfy the 30 hours we should do 21-30 hours and really only use this check for those on under 30 hours to identify those needing the extension to the plan.
Currently my ILR states OTJ - 372 - contracted hours field - always showing what the learner has declared and the employer intensity showing correct choice based on the actual contracted hours.
ok got it, thank you , i didnt like the idea of adding in data to match the OTJ as i can evidence my reasons if i am audited but this report is increasing each month i enrol so looks awful when i present it to SLT as supposedly wrong data my team are entering.
thanks Steve, Ill email thepDSAT helpdesk now and carry on doing it the way i have always been doing it
Key thing is to educate SLT that entries on PDSAT *aren't* errors, otherwise they'd be a Rule Violation in the ILR itself, they are *always* "Are You Sure?" reports and, if you're sure, that's fine (I always use the duplicate learner record report as an example, "look, these people are clearly twins, they're not going away").
Sharon Lillywhite
23A-217 report
Created
Hi,
Please can you advise how you now input the hours to reflect 6 hours per week as minimum please.
Our minimum OTJ hours is now set at 372 based on a 16 month practical period which is our min 6 hours per week as advised.
We are still adding the correct data in the Employment Intensity Indicator field to show correct contracted hours as some are 35-40+, but this is now throwing out the audit actions on the PDSAT to say our calculation is wrong based on this field.
Is everyone just using 21-up to 30 hours to record the employment intensity to make sure their hours work out correct to 6hours per week?
I have 200 warnings on the pdsat as we have used the correct contract data but off set the hours for otj to 372 based on a 30 hour week.
Many thanks in advance for any help