Business & Workplace — Unit 22, Upper-intermediate English

**Project Brief · Platform Rollout Q3**

This **cross-functional** initiative needs early **stakeholder alignment** before we commit **deliverables**. **Line managers** must confirm **headcount** — no new hires until finance signs off. We operate **remote-first**, so **onboarding** for contractors happens via the shared playbook, not ad-hoc calls. New starters should complete security training before accessing production systems.

**Meeting cadence**: daily **stand-up** at 09:00, weekly review with **stakeholders**. Log **action items** in the tracker within one hour. If **scope creep** appears, freeze requirements and **escalate an issue** to the programme lead — do not absorb extra work silently. Programme office will publish a risk register every Monday.

**KPIs**: migration uptime, support ticket volume, and customer retention. This is a **deadline-driven** quarter; **delegating tasks** without clear **accountability** will fail audits. **Streamline** the approval **workflow** before UAT — three sign-offs is the maximum. Duplicate approvals waste **bandwidth** and confuse owners.

**Bandwidth** is tight across engineering. Teams without capacity should **touch base** with their **line manager** rather than accepting shadow **deliverables**. **Cascade information** on policy changes every Friday; do not rely on chat rumours. External **stakeholders** expect written summaries after each milestone demo.

**Handover** packs must be complete before any role change. Incomplete notes caused delays last sprint. **Performance review** season starts in October — delivery metrics will be referenced. Managers should document **workflow** improvements and share examples at the town hall.

Travel is limited this quarter; **remote-first** norms apply even when visiting client sites. If partners request extra features, confirm **stakeholder alignment** in writing before rescheduling **deliverables**.

Questions: programme office · ext. 2201

**Section 6 · What this brief will not do, and the one thing it changes**

Programme briefs are read selectively, so this section states the exclusions plainly.

**No feature commitments to customers before UAT.** Sales colleagues may describe capability in general terms. Dates and named features require written sign-off from the programme lead. Three of the last four instances of **scope creep** on this platform began with a verbal commitment made in good faith at a customer meeting.

**No approval chains longer than three.** This applies to the programme office as well. Where a fourth sign-off appears to be required, the correct response is to remove one of the existing three rather than to add a fourth. Reviewers who cannot describe what they are checking for should be removed from the **workflow**.

**No overtime as a planning assumption.** A sprint that requires evening work to complete has been planned incorrectly, and reporting it as complete conceals the error from the next planning round. **Line managers** who accept such a sprint are accountable for the plan rather than the team.

**The one substantive change.** Previously, any team could raise an **action item** for any other team. From this quarter, an action item requires a named owner who has accepted it, and unaccepted items expire after five working days rather than accumulating in the tracker.

This is a smaller change than it sounds and it addresses a specific measured problem. Our tracker currently holds 1,340 open action items. Of these, 61 percent have had no activity for over ninety days, and 40 percent have no owner at all. A tracker that everyone knows is mostly dead does not fail loudly; it fails by teaching people to ignore it, which is what has happened.

**Escalation remains open to anybody, at any time, in any direction.** Nothing in this section restricts raising a problem — only assigning work.