RFP response: running the answer, not just writing it
Most RFP responses are lost to logistics, not prose. How to split the questions, hold the deadline and stop rewriting the same answer every quarter.
Under TUPE employees move on their existing terms, and both employers carry information and consultation duties with deadlines that start before completion.
TUPE — the Transfer of Undertakings (Protection of Employment) Regulations — protects employees when the business they work in changes hands, or when a service they provide is outsourced, brought back in-house, or moved to a different contractor. Their employment does not end and restart: it transfers, with continuity of service and existing terms intact.
This is one of the areas where getting the process wrong is expensive and getting professional advice is genuinely worth it. What follows describes the shape of the obligations so that they are recognised in time — it is not legal advice, and the specifics of any transfer deserve a lawyer.
Occupational pension rights are the notable partial exception, with separate rules that do not simply carry across. And dismissal because of the transfer itself is automatically unfair, subject to defined exceptions — reorganising the workforce on day one is not a free hand.
The 28-day employee liability information deadline is often missed because the deal is still confidential at that point. Confidentiality does not extend the deadline. Where the timetable is tight, the sequencing has to be worked out early rather than discovered a fortnight before completion. The receiving side should also plan the employee onboarding checklist for people who are not new joiners.
Harmonising terms across a merged workforce is the usual commercial wish and the usual legal problem: changes for a reason connected to the transfer are generally void, even where the employee agrees, with limited exceptions. The practical answer is patience and proper process rather than a variation letter in month two.
The same caution applies to redundancies. Genuine reorganisations can happen, but the reason has to stand on its own — and it will be examined against the timing.
A transfer produces a dense set of documents in a short window: the liability information, the letters to representatives, meeting notes, the consultation responses, and the induction paperwork for people who are not new joiners. Ettex Docs keeps those with their dates and versions, so the record shows what was said and when — which is exactly what a later claim tests. What TUPE requires in a specific transfer is a legal question, and the shape above is a prompt to ask it early rather than a substitute for the answer.
It can. Service provision changes — outsourcing, insourcing and changing contractor — are covered where an organised grouping of employees is assigned to the activity and the activities remain fundamentally the same.
Dismissal where the sole or principal reason is the transfer is automatically unfair, unless it falls within the limited exceptions. Genuine reasons unconnected with the transfer are assessed on their own facts.
The details the outgoing employer must give the incoming one — identities, ages, particulars of employment, disciplinary and grievance records within defined periods, and any outstanding claims — at least 28 days before the transfer.
No, but changes for a reason connected with the transfer are generally void. Changes for unconnected reasons, or those permitted by the exceptions, follow normal contract variation rules.
Most RFP responses are lost to logistics, not prose. How to split the questions, hold the deadline and stop rewriting the same answer every quarter.
A safeguarding policy is judged on whether staff can act on it. Most failures are not missing policies — they are policies nobody could follow under pressure.
Approval steps that exist because something once went wrong pile up. Each one should name what its approver is checking, or it is only delay.