Decode the specification — Technology & digital services

By the end of this lesson, you will be able to connect requirements, evidence and acceptance in a matrix.

Common to all countries

Translate the specification into testable commitments

Read the notice, instructions, specification, schedules and proposed contract together. Classify each requirement as a mandatory condition, a scored commitment, a delivery obligation or information. Keep its original reference and document version. If documents conflict, check the stated order of precedence and ask through the official channel; do not invent your own hierarchy.

Use a matrix with requirement, proposed response, evidence, dependency, acceptance test and owner. Words such as reliable, compatible, complete and sustainable need an observable meaning. Ask a precise question that explains the uncertainty and its pricing or delivery consequence. Monitor the answer and any amended files until submission; a clarification can change more than one part of the response.

Worked example — Replace a public-service booking system

This is a fictional teaching case. Quantities, prices and contractual conditions below are assumptions for the exercise, not legal requirements or market benchmarks.

The case requires importing 20,000 booking records and reconciling totals before go-live. Define field mappings, rejected-record handling, test data and rollback criteria. Do not use real personal data in an uncontrolled demonstration.

“99.9% available” is incomplete without the service hours, measurement point, exclusions and reporting period. Clarify whether planned maintenance counts and distinguish availability from the time to respond to an incident.

A useful question cites the document and paragraph, explains the two possible readings and asks which applies. Then update the affected matrix, schedule and price assumptions with the answer.

Country specific — what to verify

Determine the applicable privacy, hosting, accessibility and cybersecurity obligations for this buyer and workload. WCAG is a technical standard; the tender and applicable law determine the required version and conformity. Verify cross-border data transfers, processor terms and any AI-specific obligations for features actually supplied.

Privacy, hosting location and accessibility standards. Use the destination-country module and the actual tender pack. The sources below are references with their own scope; they do not form a single worldwide regime. For the general method, revisit the foundations.

Put it into practice

Turn the case requirement into two matrix rows, each with evidence and acceptance. Write a clarification in fewer than 80 words and identify which parts of the offer need recalculation after the answer.

Model answer

The case requires importing 20,000 booking records and reconciling totals before go-live. Define field mappings, rejected-record handling, test data and rollback criteria. Do not use real personal data in an uncontrolled demonstration. A successful matrix connects these obligations to specific records, leaving the dependency open until an official answer. Maintain a requirements-to-test matrix with expected results, observed results and an authorised decision on unresolved defects. A successful login does not prove data completeness, accessibility or performance under load.

Keep this worksheet in your working file. The quiz below checks the lesson’s decisions; passing it is neither a professional qualification nor a guarantee of an award.