Bidding on UN Software Tenders: UNGM, the RFP Process, and the Technical Proposal

A UN software tender is a competitive solicitation through which a United Nations agency or international organization procures software development or digital services, published on the United Nations Global Marketplace (UNGM) and, in almost all cases, awarded through a Request for Proposal that is scored on technical merit before price.

Winning one is less about the lowest price than most vendors assume. Software is procured through the Request for Proposal route, where the technical proposal is opened and scored first, and price is considered only for bidders who clear the technical bar. This guide walks a software vendor through the entire process: registering on UNGM, finding opportunities, understanding which solicitation method applies, and building a technical proposal that scores well.

Atta Systems has delivered software for UN agencies and international organizations, including the Species+ platform for the Convention on International Trade in Endangered Species (CITES), built with the UN Environment Program (UNEP), and works within the UNGM and RFP processes described here.

Registering on UNGM: the entry point, not the finish line

The United Nations Global Marketplace (UNGM) is the shared procurement portal for the UN system, and registering on it is the first step to bidding on UN software tenders. Launched in 2004, UNGM is used by more than 50 UN organizations, UN-affiliated bodies, and international organizations, 32 of which use it to register suppliers. Those 32 account for roughly 98 percent of total UN procurement spend and include UNICEF, UNDP, WHO, UNOPS, WFP, and the UN Secretariat, so a single UNGM profile reaches most of the UN system’s buyers.

Registration is free and takes the form of a company profile, but three things about it are commonly misunderstood:

• Registration guarantees nothing. A completed UNGM profile makes a vendor visible in the database, but it does not automatically trigger invitations or lead to a contract. Vendors must actively seek opportunities and submit a formal bid for each. UN organizations do not push opportunities to newly registered suppliers.
• Registration has three levels, tied to contract value. UNGM uses three registration levels, and the required level increases with the monetary value of the contracts a vendor pursues: Basic (for opportunities up to US $40,000), Level 1 (US $40,000 to $500,000), and Level 2 (above US $500,000). Higher levels ask for more documentation, such as financial statements and reference letters, and a vendor can start at Basic and upgrade at any time.
• UNSPSC codes control visibility, and there is a limit. Vendors select codes from the United Nations Standard Products and Services Code (UNSPSC) to describe what they offer, and procurement officers search these codes to shortlist vendors. The UN Secretariat limits vendors to seven UNSPSC codes and considers only the first seven listed on the profile, so a software vendor should prioritize the codes that capture its core services rather than listing everything it could conceivably do.

The practical takeaway is that UNGM registration is necessary but not sufficient. It puts a vendor in the room. Winning still depends on finding the right tenders and responding to them well.

Finding UN software opportunities

Finding UN software opportunities means actively monitoring UNGM rather than waiting to be invited, because the burden of discovery sits with the vendor. There are three practical ways a software vendor finds the right tenders, and using them together is what turns a registered profile into a pipeline.

• Search UNGM directly, matched to UNSPSC codes. Published opportunities are searchable on UNGM, and the UNSPSC codes on a vendor’s profile are what match it to relevant notices. Checking the portal regularly, filtered to the vendor’s core software codes, is the manual baseline. Because the same codes drive both search and matching, accurate code selection pays off twice.
• Subscribe to the Tender Alert Service. UNGM offers an optional paid subscription, roughly US$ 250 per year, that emails a vendor tender notices matching the UNSPSC codes it has registered. For a vendor serious about UN work, it replaces manual portal checking with automatic notification and is the difference between finding an opportunity in time to bid and finding it after it has closed.
• Watch for Expressions of Interest. UN organizations often publish an Expression of Interest (EOI) before a full solicitation to gauge market capacity and build a shortlist. An EOI is often the first thing a software vendor encounters for a given need, and responding to it can be what gets a vendor invited to the subsequent RFP. Treat an EOI as an early signal, not a formality.

Discovery is not a one-time setup. The vendors that win UN work treat monitoring as an ongoing activity because the gap between a notice appearing and its deadline is often short, and a strong technical proposal cannot be assembled overnight.

Which solicitation method applies: RFQ, ITB, RFP, and EOI

UN procurement uses three main solicitation methods for awarding contracts, and software almost always falls under the Request for Proposal, with Expressions of Interest often appearing first as a pre-solicitation step. The method determines how a bid is evaluated, and reading it correctly is the difference between competing on price and on technical quality. The exact monetary thresholds differ by organization, so the ranges below are indicative rather than universal.

Software development is an RFP because its requirements cannot be reduced to a fixed specification in the same way a shipment of goods can. The agency knows the desired outcome but relies on the vendor to propose the architecture, methodology, and team. That is why the technical proposal carries most of the weight, and why a vendor who treats a software RFP like a price competition loses to one who understands it is a technical competition.

How a UN RFP is scored: the two-envelope, two-stage method

An RFP is scored in two stages, using two separately submitted envelopes: the technical and the financial. The technical proposal is opened and scored first, and the financial proposal is opened only for the bidders whose technical score clears a minimum threshold. This structure is the single most important thing a software vendor must understand before bidding.

How the two-stage evaluation works in practice:

1. Technical and financial proposals are submitted separately. The two are kept apart, often as separate files or emails, and pricing must not appear anywhere in the technical proposal. Including a price in the technical envelope commonly invalidates the bid.
2. The technical proposal is scored first, against a threshold. Evaluators score the technical proposal against pre-set criteria published in the solicitation. A common structure allocates 70 of 100 points to the technical proposal, with a pass mark around 70 percent of the technical points (for example, 49 out of 70). Proposals below the threshold are rejected, and their financial envelopes are never opened.
3. The financial proposal is opened only for technically qualified bidders. For those that pass, the financial proposal is opened and scored, commonly worth the remaining 30 points, with the lowest compliant price receiving the maximum financial score and higher prices scored in inverse proportion.
4. The award goes to the highest combined score. The technical and financial scores are combined using the published weighting (commonly 70:30), and the contract is awarded to the bidder with the highest total. A strong technical proposal at a fair price beats a cheap proposal that scores poorly on technical merit.

One caveat on the method. Not every RFP uses combined scoring. Some organizations, UNDP among them, may instead specify the lowest-priced, technically compliant method, where price decides among bidders who pass the technical threshold. The published solicitation always states which method applies, so a vendor should read it rather than assume. Even under the lowest-priced method, though, the technical threshold still gates everything: a proposal that fails it is never priced.

The consequence for a software vendor is direct: price discipline matters, but the technical proposal usually determines whether the bid wins or loses, and always determines whether the bid survives to the financial stage. A vendor cannot buy its way in with a low price if the technical proposal does not clear the threshold, because the financial envelope will never be opened.

What the technical proposal must contain

A UN technical proposal for a software tender must demonstrate three things that the evaluators score: that the vendor is capable and experienced, that the proposed team is qualified, and that the approach fits the specific requirements. These map to the criteria published in the solicitation, and a proposal that misses any of them loses points it cannot recover in the financial stage.

• Firm profile and organizational capability. A description of the company, its software delivery experience, its financial stability, and its quality and security certifications. Certifications such as ISO 9001 and ISO 27001 are evidence an evaluator can score, not just claims.
• Team composition and CVs. The proposed roles and the CVs of key personnel are mapped to the requirements. Evaluators check whether the named people have the specific skills the project needs, so a generic team list scores worse than one matched to the terms of reference.
• Methodology and technical approach. How the vendor will deliver the software, including architecture, development approach, and how it will meet or exceed the requirements in the terms of reference. This section usually carries the most points because it shows evaluators that the vendor understands the problem.
• Work plan and implementation timeline. A sequenced plan showing activities, milestones, and dependencies. Evaluators look for a plan that is realistic and logically ordered, not an optimistic list of dates.
• Project management and quality assurance. The process for managing the project, monitoring progress, and assuring quality, including testing and, where relevant, accessibility conformance. For public-sector software, accessibility is frequently a scored requirement.
• Client references for similar work. Usually two references for comparable projects, with scope, value, duration, and contactable referees. UN evaluators place heavy weight on demonstrated delivery of similar work, and unverifiable references score poorly.

Accessibility deserves particular attention. Public-sector software is frequently required to meet accessibility standards, and the technical proposal is where a vendor shows it can deliver them. For how accessibility requirements shape public-facing software, see Atta Systems on custom EdTech software, where the same accessibility discipline applies.

Atta Systems has built software for UN agencies and international organizations under this exact process, and prepares technical proposals that map directly to the published evaluation criteria rather than describing capability in general terms.

Common mistakes software vendors make on UN tenders

Software vendors lose UN tenders for a small set of avoidable reasons, most of which come from treating a UN RFP like a commercial sales process. The most common mistakes:

• Treating it as a price competition. A vendor that leads with a low price and a thin technical proposal fails the technical threshold and never has its price considered. The technical proposal is what wins the bid.
• Putting pricing in the technical proposal. Any price figure in the technical envelope can invalidate the bid outright. The separation between technical and financial content is strict.
• Submitting a generic proposal. A proposal that does not map to the specific evaluation criteria in the terms of reference loses points compared with vendors that address the criteria point by point. Evaluators score against their published grid, not against general impressiveness.
• Weak or unverifiable references. References that cannot be contacted or that do not match the scope of the tender score poorly. UN evaluators verify claimed experience.
• Missing mandatory requirements. The solicitation lists mandatory requirements, and any proposal that fails to meet any of them is rejected during screening before technical scoring even begins. Reading the mandatory list first is essential.

FAQ about bidding on UN software tenders

Atta Systems builds software for UN agencies and international organizations, preparing technical proposals that align with published evaluation criteria and delivering to the quality and accessibility standards required by public-sector work.

Atta Systems focuses on custom software development for the public sector and international organizations across health, education, and government systems, rather than on off-the-shelf product supply or goods and commodity tenders that run through the ITB and RFQ routes.