Funding model for all apprenticeship (Standards and Framework starting from 01 )

Feconnect has been replaced by ESFA communities.

Feconnect is read only and it is not possible to create or reply to topics or posts. To search feconnect we suggest you use site specific searches. ESFA Communities is now live. Feconnect users will need to create a new ESFA communities account to post, reply or subscribe for email alerts.

Home Forums Data issues Funding model for all apprenticeship (Standards and Framework starting from 01 )

This topic contains 2 replies, has 2 voices, and was last updated by  Anonymous 3 years, 12 months ago.

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author

  • Anonymous

    Good afternoon,

    Please could you confirm which funding model we should be using for all apprenticeships starting from 1 May 2017 (both for standards and frameworks). I am a bit a confused because I am currently looking at the guidance (ILR Provider Guidance) and it states that: “For funded apprenticeships starting on or after 1 May 2017 the funding model should be recorded as code 36”

    I know the SOF is still 105, but my question is: are we no longer using funding model 35? if this is the case, should we be applying ‘funding model 36’ to both standards and frameworks?

    Apologies if I don’t make sense, but I just want to be sure that I am following the rules.

    Please let me know
    Thank you in advance.



    Martin West

    Hi Helene,
    All Apprenticeship starts prior to 1st May will remain on FM 35 but new starts from then will be recorded on FM36 for both frameworks and standards.
    The FM for any restarts would normally be recorded against the FM from their original start date although there is provision in the funding rules for a restart after a BIL to change to FM 36.



    Good afternoon Martin,

    Many thanks for your prompt reply and for your help always!
    I feel much better now: thank you again for confirming this.


Viewing 3 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic.