Flexible Working Request Conversation: Rehearse the Meeting

Statutory flexible-working request conversation is the consultation after submission, where the employee explains the proposed pattern, addresses operational concerns and tests workable alternatives before a decision. The Acas Code of Practice on requests for flexible working requires the employer to communicate a decision, including any appeal, within 2 months, alongside Employment Rights Act 1996 refusal grounds.

What should you say in a flexible working request conversation after submitting the form?

A Statutory flexible-working request conversation should start with the exact pattern, the work it protects and the decision you want: agreement, a defined alternative or a fair trial. The Acas Code of Practice on requests for flexible working expects consultation before rejection unless the employer accepts the request in full.

Say:

“I am asking for [pattern]. My proposal protects [customers, deadlines or handovers]. I have brought a coverage plan. Which operational risk would you like me to address first?”

Keep the first answer operational. Do not lead with a long personal explanation. Name the work the Friday salary review, customer queue or handover must still protect.

If your manager asks, “How will the team cover Fridays?”, answer directly:

“On Fridays, [named work] moves to [named owner or earlier handover]. Urgent work follows [escalation route]. We can review response times and missed handovers on [review dates].”

Then ask:

“Which specific business concern should we address? Is this a statutory business ground connected to my requested pattern, or a general preference for everyone to work the same pattern?”

That question creates a useful distinction. A shared office preference is not the same as evidence that your proposed hours will disrupt work. Keep your tone neutral. You are testing the operating problem, not challenging the manager personally.

The Acas decision guidance states that there is no specific statutory timeframe for holding the consultation meeting, but the employer must communicate the final decision, including any appeal, within two months unless you agree an extension.

This is general workplace information, not legal advice. Consult an employment adviser or trade union representative if the meeting raises a dispute about rights or discrimination.

What should you prepare before the consultation meeting?

A Statutory flexible-working request needs a practical operating plan. The Acas Code of Practice supports reasonable preparation, discussion of alternatives and accurate records. (Acas Code of Practice)

Keep the plan to one page. Show:

• customer demand and peak periods;
• recurring meetings and essential availability;
• handover points and named owners;
• urgent-work escalation;
• response-time or service-level commitments;
• work that remains unchanged.

Mark your requested days and hours against the calendar. Add rota history, service-level records, response-time records and recurring team meetings. Use evidence you can explain aloud. A dashboard extract is not useful if you cannot say what it measures, who owns the data or how it relates to your role.

Prepare one primary proposal and two workable alternatives. Options include a rota, job-share, compressed hours, changed core hours or a partial-Friday arrangement. Write the operational trade-off beside each option. Do not list alternatives that simply move your workload to colleagues without agreement.

Prepare a short answer to why this pattern is needed. Keep the explanation truthful and proportionate. You can state that the arrangement supports caring, health, travel or another personal need without disclosing intimate detail. Share only information needed for the discussion.

Managers often need help turning a request into workable objectives. The UK qualitative research recommends practical guidance and trial periods that scale workloads and objectives appropriately. (Flexible working qualitative analysis)

For a fast or remote meeting, keep this line beside your screen:

“I want to answer that accurately. May I take a moment to check my notes, and may I send the supporting detail after this meeting?”

Ask whether the person in the meeting has authority to decide. If not, ask who decides, what information they need and when you will receive the next update.

Which eight business grounds can support refusal, and how do you answer each one?

The Employment Rights Act 1996 lists eight statutory refusal grounds; the Acas Code says the employer should connect the stated ground to your requested pattern and its operational effect, not simply say flexible work does not suit the team. (Acas Code of Practice)

The table turns each ground into a testable question. After each answer, ask: “What evidence would show that this risk is resolved, reduced or still present?”

Eight refusal grounds: the live counter and proof to bring

Employment Rights Act 1996 ground	What the manager may say	Prepared counter-line	Evidence or trial measure (guidance)
Additional burden of cost	“Cover, overtime or equipment will cost more.”	“Let us compare the extra cost with a cost-neutral cover plan before deciding.”	Cover rota, equipment list and review of actual extra cost.
Detrimental effect on ability to meet customer demand	“The team needs everyone present on Friday.”	“Which work requires simultaneous presence, which hours are critical, and would a partial-Friday arrangement protect that demand?”	Response times, rota coverage, escalation records and missed deadlines.
Inability to reorganise work among existing staff	“Nobody else can take this on.”	“Here is the handover map. These are the named owners. No work transfers without an agreed capacity change.”	Handover checklist, owner confirmation and workload review.
Inability to recruit additional staff	“We cannot recruit someone to fill the gap.”	“This request does not depend on recruitment. Could changed core hours or partial-Friday cover address the gap?”	Coverage plan tested against the affected hours.
Detrimental effect on quality	“Quality will drop.”	“Which quality risk do you expect, and which check would show whether it is occurring?”	Quality checks, error escalation route and review point.
Detrimental effect on performance	“Your performance will suffer.”	“Let us link the arrangement to deliverables, deadlines and availability, then adjust objectives only where the pattern requires it.”	Output, deadlines, availability and agreed objective measures.
Insufficiency of work during the periods proposed	“There is not enough work at those times.”	“Does that concern the role, these hours or the proposed days? We could test compressed hours or changed days.”	Work allocation by period and comparison with an alternative pattern.
Planned structural changes	“The department is about to change.”	“What is the timetable, and would a temporary arrangement or review after the change address that concern?”	Change milestones, interim responsibilities and review date.

Source: Acas Code of Practice on requests for flexible working.

The Friday objection needs detail, not reassurance. For a fairness objection, say: “I understand the team impact. I am not asking colleagues to absorb undefined work. Let us identify each handover, owner and capacity change before deciding.” Productivity is a proposed outcome, not a promise; measure it through agreed delivery and service evidence.

Australian research found that caring or productivity framing performed better than wellbeing or autonomy framing, and that managers favoured two home-working days over four. Its 21-day response detail belongs to Australian context, not the UK statutory process. (Australian flexible-work research summary)

Why should you propose a trial period instead of asking for trust?

A Trial period turns a flexible-working proposal into a measurable operating test. This reflects research that links trial arrangements with guidance on workload and objectives. (Flexible working qualitative analysis)

The consensus position is sensible: discuss implementation, alternatives and practical effects before rejecting a request. It breaks down when “trust me” meets an untested Friday rota, unclear ownership or a manager who cannot picture how peak demand will work. Treat the consultation as an operational design review, not a test of whether your personal reason sounds persuasive.

A request becomes stronger when each concern becomes a coverage test. Do not offer a general assurance that customers will be supported. Define the pattern, start date, review dates, decision owner and measures in one sentence:

“Would you agree to a trial of this pattern, with a review after the agreed period, using response times, deadline delivery, handover failures, customer coverage and workload as the measures?”

Set failure triggers before the trial starts. Examples include one missed critical handover, unresolved cover during a known peak period, or an agreed service measure falling below its existing level. Name the person who records each event. Otherwise, the review becomes a memory contest.

Agree the review decision tree in advance. The arrangement can continue, change, extend by agreement, or return to the original pattern. A trial is evidence-gathering. It is not a certain route to approval. The Acas Code supports discussing alternatives and implementation as part of consultation. (Acas Code of Practice)

Reject an alternative that misses the need. Say, “This solves Tuesday coverage, but not the Friday caring commitment. I could test a partial-Friday arrangement instead.” Do not accept an unworkable permanent change simply because it sounds cooperative.

Separate a statutory contractual change from a non-statutory informal arrangement. Confirm hours, availability, objectives, progression, equipment and review terms in writing. A flexible pattern that quietly preserves the old workload is not a workable agreement.

How do you rehearse a manager who agrees in principle but stalls in practice?

The Acas Code of Practice requires consultation before rejection, and the employer must decide and communicate the request, including any appeal, within two months unless you agree an extension.

Use this three-round exercise before the meeting. Keep your answer short. Give the manager something specific to assess.

Round one: clarify the operational concern

Read the manager’s line aloud:

“I support flexible working in principle, but Fridays are difficult.”

Answer with your coverage plan:

“On Fridays, [named work] moves to [named owner] after [handover point]. Urgent work follows [escalation route]. I will remain available during [agreed hours]. Which specific operational risk concerns you?”

Do not defend your personal reason again. Move the discussion towards customer demand, deadlines, meetings, handovers or peak periods. Ask who owns the decision if the person in the room cannot decide:

“Who will make the decision, what information do they need, and when will I receive the next update?”

Round two: handle delay and fairness objections

Read each line separately:

• “I need to speak to the team.”
• “We will come back to you.”
• “Everyone needs to be treated fairly.”

Answer without arguing about goodwill:

“I understand. What information will you take forward, who will decide, and what date should I use for the next update?”

For a fairness objection, add:

“I am not asking colleagues to absorb undefined work. Let us identify each handover, owner and capacity change before deciding.”

This keeps the focus on the proposed arrangement. It does not require you to solve every staffing problem in the team.

Round three: pause when a new objection appears

Introduce an objection that was absent from the invitation:

“This would create a problem for a project you have not mentioned.”

Pause for a moment. Restate the point:

“I understand that the concern is the effect on [project] during [period]. I would like to check the dates and respond with relevant evidence.”

Then ask for the concern in writing if the facts are unclear:

“Could you send me the specific issue and the information you need? I will review it before responding.”

Do not treat a new concern as an immediate rejection. Offer a practical response without making an unsupported promise.

Score the rehearsal

After each round, score yourself against five checks:

Clarity: Did you state the requested pattern and the work it protects? Directness: Did you answer the objection before explaining further? Evidence: Did you name a rota, calendar, response-time record, handover or review measure? Listening: Did you accurately restate the manager’s concern? Recovery: Did you pause and return to the question after an interruption?

Save one strong line for the real meeting. For example:

“Which part of the coverage plan remains unresolved, and what evidence would address it?”

Optional tool: Razen’s voice rehearsal scenarios may support spoken practice for these three rounds. You can also rehearse without software by reading the manager’s lines from a page and recording your replies for your own review.

The Acas decision guidance states that there is no specific statutory timeframe for holding the consultation meeting, but the final decision, including any appeal, must normally be communicated within two months. The employer and employee can agree an extension.

If the employer allows a companion, agree the role beforehand. A fellow-worker companion, trade union representative or trade union official can take notes and help you recall questions. The Acas Code does not create a statutory right to accompaniment. Check the employer’s policy, and seek qualified employment advice if the meeting raises a dispute about rights or discrimination.

What should you do after the meeting if the answer is vague, alternative or negative?

The Acas Code of Practice on requests for flexible working says there is no statutory right to an appeal, but the request remains live during an agreed appeal or extension. (Acas Code of Practice)

1. Document the meeting

Send a factual note promptly. Record the requested pattern, objections raised, evidence offered, alternatives discussed, agreed actions and next date. Ask the manager to correct anything inaccurate. Your note is your account. Do not describe it as the employer’s official record.

Ask who owns the next decision and when you will receive it. If the employer permits a companion, agree their role before the meeting. A fellow-worker companion, trade union representative or trade union official can help you take notes and recall questions. The Acas Code does not create a statutory right to accompaniment, so check the employer’s policy. The Acas flexible working request response letter template provides a useful model for written confirmation.

2. Test an alternative against the original need

A proposed alternative is useful only if it addresses the problem behind your request. Ask whether it is temporary or permanent, what hours and availability it requires, and how it affects workload, pay, progression and caring responsibilities.

Use this line:

“Which part of my original need does this arrangement meet, and what changes to workload or progression would follow?”

If the manager says “yes in principle”, ask for the contractual pattern, start date, objectives, review point and person responsible for confirming the terms. Agreement without dates or workload boundaries is not a workable operating arrangement.

3. Consider appeal, discrimination and reasonable-adjustment issues

If the employer rejects the request, ask which Employment Rights Act 1996 ground applies, what facts support it and whether further evidence or an alternative could address the concern. Do not present the future Employment Rights Act 2025 reasonableness test as current law. The government response identifies that reform as intended for autumn 2027, separate from changes introduced in April 2024. (Government response on improving access to flexible working)

Use an offered appeal meeting to present overlooked evidence, a workable alternative or a process concern. Do not simply repeat the original request. If disability forms part of the reason, a reasonable adjustment issue under the Equality Act 2010 may require separate advice. Flexible-working law and discrimination law are distinct.

Share health, caring or other sensitive information only with people who need it. Check the employer’s policy and its handling of UK GDPR and data protection law before sending details to a wider workplace group.

What does this process not prove about your request?

A Statutory flexible-working request remains a decision under the Acas Code of Practice on requests for flexible working. It does not assure acceptance. Rehearsal improves precision, but it cannot remove a genuine business constraint.

The government consultation figures are rounded, self-reported responses from a consultation sample, not a national approval rate. Among 330 respondents, 58.8% reported acceptance, 15.2% reported an alternative arrangement and 26.1% reported rejection, as stated in the government response.

Current Population Survey and Bureau of Labor Statistics evidence describes US workplace changes, not UK flexible-working law (BLS evidence). The Journal of Occupational and Organizational Psychology, Workplace Gender Equality Agency and Dedoose qualitative-analysis software provide external research context, not statutory authority. The UK qualitative analysis examines four spheres of influence: individual, manager and team, organisation, and society.

Ask the Chartered Institute of Personnel and Development, a Trade union representative or a qualified employment adviser when policy, equality or contract issues exceed this guide. A flexible-working request is not a Reasonable adjustment, legal advice or sensitive-person support.

Razen Rehearsal Sandbox: The Friday Coverage Consultation

You have submitted a UK statutory flexible-working request to work Monday to Thursday, 8:00 to 18:00, with no Friday hours. Your consultation meeting is with your manager and the operations lead, who owns Friday customer cover. The outcome affects your childcare arrangement, your team’s service levels and the employer’s two-month decision deadline.

Setting. A 30-minute video meeting with Maya, her manager Simon and operations lead Leila. Maya has brought a one-page coverage plan and wants agreement, a defined alternative or a measured trial.

Cast

• Maya, Employee making the request. At stake: She needs a workable pattern without exposing private family details or accepting an undefined delay.
• Simon, Manager deciding the request. At stake: He must protect Friday coverage, workload and deadlines while giving a clear decision.
• Leila, Operations lead for Friday cover. At stake: She must not inherit unplanned work or let customer response times fall.

The Wrong Way

Maya: Thanks for meeting. I’m asking to work Monday to Thursday, eight to six, because Fridays have become impossible for me personally.

(She speaks quickly, grips a printed note and looks at Simon rather than Leila.)

Simon: I understand, but Fridays are our busiest day. How would the team cover customers?

(He leans back, taps the calendar and keeps his voice measured.)

Maya: I’ve thought about it. Nothing should really change. I’d get everything done earlier, and I’d still check messages if something urgent came up.

(She nods before finishing, then adds the last sentence in a smaller voice.)

Leila: Checking messages isn’t the same as being available. We have three client handovers on Fridays.

(She turns from her second screen and points to the rota.)

Maya: Right, yes. I could probably move those to Thursday. I don’t want this to create work for anyone.

(She crosses out a line on her paper without naming an owner.)

Simon: I need to speak to the team first. We also have to be fair to everyone.

(He closes the calendar and gives a polite half-smile.)

Maya: Of course. I’m sure we can work something out. Just let me know.

(She nods repeatedly and does not ask for a date or decision owner.)

Leila: I’d need to see what the extra Friday work actually looks like.

(She raises one hand, but Maya is already gathering her notes.)

Why it fails. Maya makes the request sound like a test of whether her personal reason deserves approval, then claims that the impact will be negligible. The key failure is the line “Nothing should really change,” which gives Simon and Leila no coverage test. Her final “Just let me know” turns a consultation into an open-ended delay with no owner or date.

The Right Way

Maya: I’m asking to work Monday to Thursday, 8:00 to 18:00, with no Friday hours. I’ve mapped the Friday work, the owners and the escalation route. Which operational risk should we test first?

(She places the one-page plan between the camera and her notes, then looks at each person.)

Simon: Friday customer demand is the concern. We can’t leave the team guessing.

(He points to the Friday column and speaks more firmly on “guessing.”)

Maya: The three scheduled client handovers move to Thursday by 16:00. Leila owns only P1 escalations, not routine tickets. Routine tickets stay with the existing Friday rota, and I’ll record every handover failure.

(She traces each line with her finger and stops after naming Leila’s boundary.)

Leila: I need the P1 definition and a response target. Otherwise I’m covering everything by default.

(She sits forward and opens the service-level dashboard.)

Maya: Agreed. P1 means a live outage or safety issue, with a 30-minute response target. We review response times, missed handovers, deadline delivery and your recorded extra hours after four weeks.

(She writes the four measures down, keeping her pen still between each item.)

Simon: What happens if the trial misses the current response level?

(He stops tapping the calendar and waits for her answer.)

Maya: We pause the trial if a critical handover is missed or response performance falls below its current level for two review periods. Then we either change the pattern, extend testing by agreement or return to the original arrangement.

(She takes one breath before listing the failure triggers and keeps her gaze on Simon.)

Leila: I’d support a four-week trial if the rota shows the named Friday owner and I receive the Thursday handover by four.

(She turns the dashboard towards Simon and taps the 16:00 deadline.)

Maya: Then may we record those terms, name Simon as the decision owner and set the review for 18 April? If approval needs another person, who is that and what date will they respond?

(She leaves both hands flat on the desk and waits without filling the silence.)

Why it lands. Maya treats the meeting as an operating-plan review, not a plea for trust. She converts Friday coverage into named owners, a boundary, measurable service levels and failure triggers. The trade-off is real: she accepts tighter Thursday handovers and the possibility that the arrangement returns to the original pattern. Leila changes from a potential blocker into a test owner because her workload has a defined limit.

<aside class="razen-coach-card" data-razen-scenario="the-friday-coverage-consultation"> <p class="razen-coach-card__title"><strong>Practice this live.</strong></p> <p><a class="razen-coach-card__button" href="https://razenai.com/coach?scenario=the-friday-coverage-consultation&amp;article=flexible-working-request-conversation&amp;utm_source=razen_blog&amp;utm_medium=rehearsal_sandbox&amp;utm_campaign=flexible-working-request-conversation">Click here to boot up the Razen AI voice coach for this exact scenario.</a></p> </aside>

Delivery playbook

Tone shifts

• Open with a practical, low-pitched delivery when stating Monday to Thursday and the requested hours; shift to a slower, more deliberate tone when naming the Friday owners and measures.
• When Simon says the team must be fair, move from explanation to precise questioning: ask which workload, service level or handover he wants tested.
• If Leila challenges the P1 boundary, stop defending the request and sound exact: define P1, the response target and what remains on the existing rota.

Pause placement

• Pause for 2 seconds after “Which operational risk should we test first?” Do not rescue Simon from answering.
• Pause for 2 seconds after naming “P1 escalations, not routine tickets” so Leila can challenge the boundary rather than silently accepting it.
• Pause for 3 seconds after asking for the decision owner and 18 April date. Keep your gaze on Simon during the silence.

Physiological cues

• Before stating the pattern, breathe out fully and loosen your jaw; avoid speeding through the private reason or adding unnecessary detail.
• Keep one finger on each coverage item as you speak, and stop tapping or crossing out notes when someone raises a workload concern.
• When the word “fair” triggers an urge to apologise, place both feet flat and replace repeated nodding with one slow nod.

Recovery moves

• If you start defending your personal reason, say: “The reason explains the need, but let’s test the work impact. The Friday plan is here.”
• If Simon says, “We’ll come back to you,” say: “What action happens next, who owns it and what date should I expect the update?”
• If a new objection appears, say: “I haven’t prepared that point accurately. Let me restate the concern, take a moment with my notes and send the supporting detail after this meeting.”
• If you agree too quickly to an undefined alternative, say: “I want to check whether that pattern meets the original need before I agree. Which hours, owners and review terms would apply?”

Frequently asked questions

Can my employer reject a statutory flexible-working request without discussing it?

Under the Acas Code, an employer should consult you before rejecting a statutory request unless it accepts the request in full. Ask which specific business ground applies, what evidence supports it and whether an alternative or trial could address the concern. The current process normally requires a final decision, including any appeal, within two months.

What should I say when my manager asks how the team will cover Fridays?

Name the Friday work, its owner, the handover point and the escalation route. Then offer measures such as response times, deadline delivery and missed handovers. Say: “Here is the coverage plan. Which part concerns you, and what result would show that the risk is controlled?”

Can I ask for a trial period during the meeting?

Yes, you can propose one as a practical option. Set the pattern, start date, review dates, measures, failure triggers and decision owner. Confirm whether the trial changes your contract or remains an informal arrangement, and do not assume a trial leads to permanent approval.

What if my manager says yes in principle but does nothing?

Ask for the decision owner, next action and date in writing. Confirm the agreed pattern, start date, objectives and review terms. If the request remains unresolved, keep a factual record and ask for the employer’s specific concerns or formal decision within the applicable process.

Does the two-month period always apply to an appeal?

The Acas guidance says the employer must decide and communicate the request, including any appeal, within two months of receiving it, unless you agree an extension. There is no statutory right to an appeal, so check the employer’s policy and seek qualified advice if handling becomes disputed.