Public technology procurement: specify effectively without restricting competition

Start with the public need, not a catalog

The preliminary technical study should characterize the need, current state, expected results, and alternatives. This prevents habits or preferences from becoming unjustified requirements.

Describe users, volumes, environments, integrations, constraints, timing, support, and downtime consequences. The specification should originate from — and remain traceable to — that context.

• Need and outcome
• Current state and quantities
• Interoperability
• Security and support
• Deployment and acceptance
• Lifecycle cost

Write objective, testable requirements

Prefer functional and performance requirements when sufficient. When a technical characteristic is essential, document its connection to the need and define how compliance will be proven.

Avoid vague terms such as 'high quality' or 'latest generation.' Define metrics, standards, compatibility, environmental conditions, warranty, and documentation. Every requirement needs a proportionate verification method.

Standardization requires justification, not shortcuts

References to brands, models, samples, or manufacturer letters may receive specific and exceptional treatment under applicable rules. When used, they require technical and legal grounds appropriate to the case.

Brazil’s Federal Court of Accounts procurement guidance notes that requirements capable of restricting competition require detailed technical justification. Teams should record why a requirement is necessary and which alternatives were considered.

Consider the solution’s complete lifecycle

Best value is not limited to the lowest unit price. Deployment, compatibility, training, warranty, maintenance, power, expansion, migration, and disposition can change cost and risk over time.

Define responsibilities and measurable service levels. Deadlines without a starting point, availability without a calculation method, and support without severity definitions create disputes instead of management.

Plan evidence, acceptance, and management before award

Build a matrix connecting each requirement to proof, acceptance test, and owner. This improves evaluation, acceptance, and oversight while preserving equal treatment.

At receipt, verify quantity, configuration, origin, warranty, documentation, licensing, inventory, and planned tests. Record discrepancies and remediation criteria. A procurement ends with the required outcome available — not when boxes arrive.