02 / Practical guide
How to prepare a technical requirement that supports decisions.
You do not need to have the solution designed. It helps to separate what is known, assumed and still needs validation. This structure reduces late questions and proposals that are difficult to compare.
Objective and current situation
Explain the decision, problem or work result you need to address and why it matters now.
- Include
- Context, process or asset, users, location and stage.
- Avoid
- Prescribing a technology without explaining the need.
Available information and sources
List available drawings, manuals, data, photographs, records, standards or systems and identify their version and owner.
- Rights
- Confirm that every source may be shared.
- Quality
- State gaps, formats, languages and currency.
Constraints and interfaces
Document regulation, safety, operational windows, budget reference, third parties, dependencies and relevant dates.
- Critical
- Separate mandatory requirements from preferences.
- Third parties
- Identify who approves, supplies or validates.
Deliverables and acceptance
Describe the evidence you expect and who can confirm that the work meets its objective.
- Format
- Document, model, software, intervention, training or dossier.
- Closure
- Testing, review, criteria and open-item treatment.
A technical conversation starts with scope
