Write a bounded project specification
6 min read
Lesson objectives
- Turn a diagnosis into a specification that can be priced, executed and checked, with explicit assumptions, exclusions and decision gates.
Please sign in to use all the tools
Once you sign in, the reading tools are yours: larger or smaller text, typeface, line spacing, focus mode, highlighting and bold, and notes saved to your account and gathered in My study.
A procurement manager requests 'the price for translating the entire website' before source files are available or anyone has agreed who approves terminology. A single figure in that situation is an estimate with hidden assumptions, not a precise quotation. The adviser's task is to develop a project specification that makes proposals comparable and exposes decisions a supplier cannot make for the client. A specification is not a long statement of intentions. It defines purpose, audience, content, delivery process, acceptance evidence and decision owners. The public abstract of ISO 11669:2024 describes project specifications as a basis for requesting, setting up, managing and evaluating translation projects, with needs analysis, risk assessment and workflows in its framework. Do not infer detailed mandatory clauses from an abstract when the full text has not been reviewed.
Begin with an observable purpose: 'An Arabic mobile user can understand the booking fees and complete confirmation without contacting support.' Define what is in scope: search and payment screens, error messages, confirmation emails, and displayed price and date values. Define what is outside it: deciding the fee policy, fixing payment logic, or certifying a specialist legal translation that was never commissioned. Exclusion does not remove responsibility to flag a risk; it routes the decision to its owner through an explicit gate. If a phrase could promise a right that has not been approved, stop its approval and obtain a ruling from the policy owner instead of polishing the wording and releasing it.
Establish a source baseline. Ask for a screen and journey inventory, exportable strings, product version, images containing words, automated messages and content generated at runtime. For each asset record its source, freeze date, owner and display context. Raw word count is not the whole workload. 'Open' might mean open a file or open an account, requiring context and a test string. Conversely, repeated paragraphs may be reusable once their contextual fit has been reviewed. Do not treat every repetition as a guaranteed saving before that check. If assets are missing at pricing time, state a conditional range and an agreed change unit rather than a final figure that implies certainty.
Now write acceptance criteria that can be tested rather than merely saying 'high quality'. For the critical journey: no conflict between displayed and checkout prices once the fee rule is approved; mixed-script interface elements read in the intended order; booking steps and confirmation email match the system's actual state; and errors that change a user's decision are corrected before launch. For information pages, review the meaning of critical terms and a distributed sample of pages, logging defects, correction and recheck. Name who approves meaning, who verifies rendering and who can stop release of a hazardous journey. Avoid a blanket pass percentage without a sampling method or severity definition. One serious payment-button error can be hidden by a high aggregate rate.
Construct a request for proposal that supports fair comparison. Send suppliers the same contextual sample and screen captures. Ask each to state whether terminology preparation, translation, linguistic revision, in-product testing and source-change handling are included in the price. Ask how queries are resolved, who decides disputed terms, what throughput assumption is used and when assets must arrive. A per-word price that includes UI testing is not directly comparable with one that excludes it. If pricing units differ, normalize offers against one scenario: a stable scope, declared change rate, and review and test costs. Do not select a supplier in the specification lesson. Produce a brief against which suppliers can later be tested without shifting the comparison rules after prices arrive.
Review the specification with a counterfactual question: What wrong decision would the delivery team make if this sentence were absent? A sentence that changes no ownership, cost, test or risk may be filler. Conversely, silence about weekly source changes can multiply effort and invalidate completed review; set a freeze point and change mechanism. The final output might be one or two pages with an asset appendix, but its value lies in clarity, not length. Give the sponsor three lists: what can be priced now, what is priced conditionally, and what cannot be published until its owner decides. This moves the engagement from diagnosing a complaint to commissioning work that can be executed and verified.
Lesson summary
Turn diagnosis into an asset, boundary, owner and acceptance specification.