At the beginning of the year, we will send out comms to all Trusts with information on the GP F2 allocation process.
We will provide deadlines for each piece of work to be completed so that we stay on track for the upcoming August rotation.
Date | Action Required | Responsibility |
Mid-March | List of approved GP sites sent to Trusts. Trusts can begin to liaise with practices to confirm allocated trainees for the year.
| HET Foundation Team / Trusts |
Mid-April
| HET to provide the Trusts with an early snapshot (ahead of the 12-week CoP deadline).This provides the Trusts with an approximate idea of the names of the trainees likely to be going into F2 GP posts. | HET Workforce team |
During April | Trusts work with General Practices and Patch ADs to allocate trainees to GP practices for the August -August Rotations.
Trainees’ allocations must be as spread evenly amongst all Practices where possible i.e., do not allocate trainees to 3 Practices for the entire year, whilst others are left empty for the entire year.
| MEMs/Foundation teams in Trusts |
May
| Trusts to notify HET of completed allocations for August – August using the template provided attached to the email sent to Trusts on March.
HET to log the allocations centrally so that invoices can be processed.
Trusts to provide HET with a list of the unused practices.
|
MEMs/Foundation admin teams in Trusts |
May (Code of Practice)
| 12 Week Deadline. Final trainee data released to trusts with confirmed names of trainees via TRoG for August placement and FRoG for the whole year view.
| HET workforce team |
May – August
| Trusts to confirm the final allocations to GP practices and trainees for the remainder of the full training year (August – December, December - April and April-August rotations). Trusts to update HET on any changes made, if necessary. | MEMs/Foundation admin teams in Trusts |
If none of the FAQs have answered your question, please submit an enquiry to the team by clicking here
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article