Technology procurement is an evidence-controlled lifecycle from need definition to accepted operation. The solicitation and contract sit between earlier feasibility work and later implementation, commissioning, handover and benefits review.
End-to-end procurement roadmap
- Frame Define the need, sponsor, governance, baseline and approval route.
- Test Complete site, technical, market, data, utility, safety and cybersecurity due diligence.
- Specify Write outcomes, mandatory requirements, response schedules, evidence and evaluation rules.
- Select Screen compliance, normalize scope and TCO, evaluate evidence and document tradeoffs.
- Contract and deliver Convert material promises into obligations, tests, remedies, change control and delivery governance.
- Accept and learn Commission, hand over, verify performance and compare actual results with the approved case.
Stage 1: Define the need and governance
Document the outcome, affected operations, urgency, budget context and decision authority. Confirm who owns the requirement, who will operate the system, who can approve the procurement and who can accept delivery.
Form a proportionate team early. Material projects may require operations, facilities, engineering, energy, finance, procurement, legal, information security, sustainability, health and safety, and executive representation. Acquisition planning is stronger when the people responsible for significant technical, financial, legal and operational aspects are involved before the solicitation is fixed.
Initial outputs
- decision statement and sponsor;
- stakeholder and responsibility map;
- initial scope and exclusions;
- approval route and delegated authority;
- conflict-of-interest process;
- high-level schedule and decision gates.
| Role | Primary responsibility | Evidence owned |
|---|---|---|
| Sponsor and decision owner | Outcome, authority, funding and decision gates | Approved need, business case and conditions |
| Operational owner | Service levels, users, operating constraints and handover | Baseline, requirements, training and acceptance input |
| Technical and specialist team | Site, design, interfaces, safety, data and performance | Surveys, specifications, reviews and test records |
| Procurement and commercial team | Route, competition, evaluation, negotiation and contract process | Solicitation, clarifications, evaluation and award file |
| Legal, cybersecurity and assurance reviewers | Risk-based review within their professional boundaries | Departures, controls, review findings and unresolved issues |
| Delivery and contract manager | Program, changes, obligations, acceptance and closeout | Progress, change, issue, test and handover records |
Stage 2: Establish the baseline and business case
Collect the evidence needed to explain the current state and required outcome. This may include utility data, load profiles, maintenance records, downtime, asset condition, fleet schedules, occupancy, production, software architecture, emissions data or planned replacement.
Develop alternatives and a proportionate business case. Use How to Build a Green Technology Business Case. Do not authorize a competitive process around a solution that has not yet been connected to a real need.
Stage 3: Test site and technical feasibility
Complete enough due diligence to avoid asking the market to price an unknown project. Depending on the technology, this may include site surveys, structural review, electrical capacity, interconnection, communications, network architecture, cybersecurity, fire and safety requirements, planning, permitting, environmental review, utility engagement and operational constraints.
Decide which information will be provided to vendors, which risks remain with the purchaser and which risks can reasonably be priced or managed by the supplier.
Stage 4: Research the market and choose a route
Market engagement can test availability, commercial models, lead times, standards, delivery capacity and whether the requirement is written in a way suppliers can answer. Use requests for information, supplier briefings, demonstrations or structured interviews consistently and without giving one supplier an unfair advantage.
Choose a procurement route that fits requirement maturity and risk. Options may include competitive quotation, request for proposals, framework or cooperative contract, direct negotiation where lawful, design-build, managed service, lease, power or service agreement, performance contract, or staged pilot followed by scale-up.
Consider whether the organization needs a product, an integrated project, an outcome-based service or a long-term performance commitment. The route affects pricing, risk allocation, financing, evaluation and contract management.
Stage 5: Write the requirement and evaluation plan
The requirement should describe outcomes, operating conditions, interfaces and acceptance—not merely repeat a preferred vendor’s specification. Use performance requirements where they allow competition and innovation, but retain prescriptive requirements where interoperability, safety or site constraints demand them.
Requirement topics
- scope, sites, quantities, duty cycle and service levels;
- technical performance and environmental conditions;
- codes, standards, safety, permits and certifications;
- interfaces, controls, data, cybersecurity and integration;
- design submissions, project management and schedule;
- testing, commissioning, acceptance and measurement;
- training, documentation, maintenance, support and spare parts;
- warranty, guarantees, remedies and end-of-life responsibilities.
Develop the evaluation plan at the same time. Define mandatory gates, weighted factors, price or TCO method, evidence requirements, scoring scale, consensus process, due diligence and approval authority. Evaluation factors should represent the important decision areas and support meaningful discrimination between proposals.
| Gate | Required evidence | Pause when |
|---|---|---|
| Need gate | Outcome, sponsor, scope, baseline and authority | The requirement is still a product preference rather than a service need |
| Feasibility gate | Material site, utility, integration, safety, data and operating constraints | Vendors would be pricing major unknowns without a commercial treatment |
| Business-case gate | Alternatives, TCO, funding, sensitivity and risk ownership | The recommendation depends on unverified savings or incentives |
| Solicitation gate | Requirement, response schedule, evaluation plan, contract basis and approvals | Criteria, weights, mandatory gates or price boundary are unsettled |
| Award gate | Compliance, evaluation, TCO, due diligence, tradeoff and negotiated terms | Material credited promises are absent from the contract position |
Stage 6: Issue the solicitation and manage communications
Provide a clear timetable, response structure, pricing schedule, contract terms, site information and rules for questions. Keep bidder communications controlled and available to all eligible participants where required.
Allow enough time for site visits, specialist input and credible pricing. A rushed response period can reduce competition or shift avoidable uncertainty into risk premiums and exclusions.
Stage 7: Evaluate proposals
Begin with conflicts and confidentiality. Check completeness and mandatory compliance before scoring weighted factors. Use the approved method consistently and record the evidence supporting material judgments.
Normalize scope and whole-life cost. Use How to Compare Vendor Proposals and the Vendor Comparison Worksheet.
Where the method permits tradeoffs, explain why the benefits of a higher-priced proposal do or do not justify the difference. Do not let the weighted total replace a reasoned decision.
Stage 8: Clarify, negotiate and complete due diligence
Resolve ambiguities, confirm assumptions and convert important proposal claims into contract-ready commitments. The rules for clarification and negotiation depend on the procurement route and jurisdiction.
Complete risk-based due diligence on the proposed supplier, product and delivery chain. Verify references, insurance, financial and operational capacity, product certification, cybersecurity, key subcontractors, service coverage, lead times and any claims that materially influenced selection.
Stage 9: Award and contract
The final agreement should preserve the evaluated scope and value. Align the statement of work, design basis, price schedule, proposal commitments, program, acceptance tests, performance measures, warranty, service levels, data rights, change control, liability, termination and remedies.
Establish governance for the delivery phase: named owners, reporting, issue escalation, document control, approval limits and change authorization. Uncontrolled changes can erode the original business case even where the procurement itself was competitive.
Stage 10: Design, implement and control change
Manage design reviews, permits, utility actions, site access, health and safety, interfaces, cybersecurity, factory testing, logistics and construction. Track decisions and changes against the approved baseline.
Require suppliers to identify deviations and consequences before work proceeds. Update the cost and benefit forecast when scope, schedule or operating assumptions change materially.
Stage 11: Commission, accept and verify
Acceptance should be based on evidence that the system was supplied, installed, integrated and tested against the agreed requirements. Commissioning may include inspection, functional testing, performance tests, controls verification, data validation, training, documentation and correction of deficiencies.
For energy or resource-saving projects, define the measurement and verification method before installation. Confirm the baseline, boundary, adjustments, meters, calculation method, reporting frequency and responsibility. Commissioning confirms that the system works as intended; measurement and verification tests whether the expected performance or savings are being realized under the agreed method.
| Evidence set | Purpose | Owner check |
|---|---|---|
| Installed and configured system | Confirms approved equipment, software, settings and interfaces | Match as-built records to the accepted design |
| Functional and performance tests | Shows operation under normal, failure and recovery conditions | Verify witnesses, pass criteria, defects and retests |
| Data and cybersecurity handover | Transfers credentials, logs, backups, exports, remote-access and recovery responsibilities | Confirm owner control and removal of temporary access |
| Operating capability | Provides training, procedures, spares, support and escalation | Confirm named owners and usable records |
| Benefits and review baseline | Defines how actual cost, service, savings or risk outcomes will be reviewed | Record method, period, source data and corrective-action process |
Stage 12: Handover, operate and learn
A project is not complete when equipment is energized or software is switched on. Confirm ownership of manuals, drawings, credentials, source data, warranties, licenses, spares, maintenance plans, training records and open defects.
Set post-implementation reviews against the business case. Compare actual cost, schedule, performance and operational effects with the approved forecast. Feed lessons into future specifications, evaluation criteria and cost models.
Decision gates
- Need gate: the outcome, sponsor and authority are defined.
- Feasibility gate: material site and technical constraints are understood.
- Business-case gate: alternatives, economics, risks and funding route support proceeding.
- Solicitation gate: requirement, evaluation method, contract basis and approvals are ready.
- Award gate: selection, due diligence, tradeoff and contract position are documented.
- Acceptance gate: tests, documentation, training and defects meet the agreed standard.
- Benefits gate: actual performance is reviewed and corrective action is assigned.
Procurement record
Maintain a proportionate file containing the need, approvals, market research, requirement, solicitation, bidder communications, proposals, evaluation records, clarifications, due diligence, decision, contract, changes, acceptance and performance evidence.
Common process failures
- Naming the product before defining the need.
- Inviting bids before site and integration risks are understood.
- Writing requirements around one vendor without a documented reason.
- Leaving the evaluation method until proposals arrive.
- Selecting on purchase price while excluding purchaser costs and operational risk.
- Awarding before important proposal commitments are reflected in the contract.
- Allowing design and scope changes without updating economics and approvals.
- Treating commissioning, data handover or measurement as optional closeout tasks.
- Failing to review actual results against the business case.
Commissioning, handover and ongoing review checklist
- Every accepted requirement is tied to an inspection, test, document or operating demonstration.
- Open defects, temporary arrangements and deferred work have owners, dates and commercial treatment.
- Credentials, source data, configurations, licenses, warranties, manuals, spares and support contacts are transferred.
- Operators and maintainers can perform the required tasks without depending on undocumented implementation knowledge.
- Actual cost, schedule, performance, service and benefits are reviewed against the approved business case.
Return to the Project Economics and Procurement hub for the full decision route and maintain the procurement record through operation, correction and eventual retirement.
Sources and evidence
Primary and authoritative references used for this page are listed below. Recheck current rules, rates, source editions and organizational requirements before a live decision.
- FAR Part 7 — Acquisition Planning — Acquisition.gov
- FAR 7.104 — General Procedures — Acquisition.gov
- FAR 7.105 — Contents of Written Acquisition Plans — Acquisition.gov
- FAR 15.304 — Evaluation Factors — Acquisition.gov
- EMIS Planning and Procurement — U.S. Department of Energy FEMP
- Measurement and Verification Options — U.S. Department of Energy FEMP
- Commissioning in Federal Buildings — U.S. Department of Energy FEMP
- Cost Estimating and Assessment Guide — U.S. Government Accountability Office
- Project Control authority: approved page map, complete page criteria, contextual-linking rules and layout matrix.
The FAR pages are current US federal acquisition references and were verified against FAC 2026-01, effective 13 March 2026. They illustrate transparent planning, evaluation and tradeoff controls; they do not govern every private, non-US or non-federal procurement.
Reviewed and updated 29 June 2026. Recheck when financial methods, procurement rules, official guidance, discount and escalation inputs, organizational governance or the page’s material claims change. Organizational author: Future Green Technology, published by Zenith Star Media.