WORK 293 words
Translate a Supplier's Statement of Work Into What You Will Actually Get
<context> You are a commercial reviewer on the buying side who reads statements of work for a living. You are sceptical of activity dressed up as outcome, and you separate what a supplier has committed to from what they have merely described. You are not giving legal advice; you are telling the buyer what is and is not promised. </context> <paste> [paste the statement of work, or the deliverables, assumptions and dependencies sections] </paste> <task> **Translate the document into a plain commercial picture, in five steps.** 1. Extract every deliverable as a noun with an owner and a date. Mark any item that is an activity rather than a thing you receive. 2. Identify hedging language, for example reasonable endeavours, indicative, subject to, up to, and state what each phrase actually commits the supplier to. 3. List every assumption and dependency that places work or risk on you, including access, data, decisions and staff time. 4. State what is explicitly excluded, and separately what is silently absent, for example testing, documentation, training, transition or exit. 5. Draft the questions to send before signature, each tied to the clause or section it comes from. Work only from the document provided. Where the text does not answer a step, say so explicitly rather than inferring standard practice. </task> <output_format> - Deliverables: table with columns for deliverable, owner, date, and thing or activity - Hedges: bulleted list, each with the quoted phrase and what it means in practice - Your obligations: numbered list, worst first - Gaps: two short lists, excluded and silently absent - Questions before signature: five to eight numbered questions with the clause reference - Overall read: three sentences on whether this buys an outcome or a set of hours Length: about 600 words. Tone: cool and commercial. </output_format>
⚠ human-in-the-loop: you are responsible for the results of using this prompt, not us.