Commercial proposal
Employee request: Draft a proposal for a six-week operations review.
Current source: Service overview — The operations review runs for six weeks. The approved deliverables are an operating baseline, a prioritised improvement plan and named owners for next steps.
Approved guidance: Standard payment terms are 30 days. A proposed discount above 10% requires approval from the commercial owner. Owner: Commercial. Audience: Commercial team.
Illustrative answer: Our six-week review gives your team a clear operating baseline, a prioritised improvement plan and an owner for every next step. Weeks 1–2 · Understand the current operation. Weeks 3–4 · Design the improvement plan. Weeks 5–6 · Agree ownership and next steps. Use standard 30-day payment terms. A discount above 10% needs commercial-owner approval before the proposal is sent.
Team onboarding
Employee request: How does this team handle client handovers?
Current source: Client handover playbook — Every handover includes the current scope, open decisions, source links, the next milestone and its owner. The receiving team confirms that it can continue the work.
Approved guidance: The delivery owner is accountable for reviewing the handover. Client-sensitive material stays within its approved audience. Owner: Operations. Audience: Delivery team.
Illustrative answer: Start with the current client handover checklist. The delivery owner reviews the scope, open decisions and next milestone with the outgoing team. Prepare · Scope, decisions and source links. Review · Delivery owner confirms the next milestone. Complete · Receiving team acknowledges ownership. Keep client-sensitive material in its approved workspace. The shared checklist explains the process; it does not grant access to client files.
Product handoff
Employee request: Turn this brief into an engineering handoff.
Current source: Product brief — The brief describes a team-level reporting experience. The handoff must retain the approved audience, intended behaviour and unresolved decisions.
Approved guidance: Engineering handoffs include acceptance criteria, interface changes, permissions, failure behaviour and relevant verification. Unresolved decisions must have an owner. Owner: Engineering. Audience: Product & engineering.
Illustrative answer: Structure the handoff around the approved brief, acceptance criteria, permissions and the release checks your engineering team maintains. Define · Problem, audience and acceptance criteria. Specify · Interfaces, permissions and failure states. Verify · Functional, accessibility and release checks. Link the maintained specification. Unresolved requirements stay explicit and need an owner before implementation is approved.