This specific tender is managed via the new supplier portal system of UNDP Quantum. If you are interested in submitting a bid for this tender, you must subscribe following the instructions in the user guide. If you have not registered a profile with this system, you can do so by following the link for Supplier Registration.
If you already have a supplier profile, please access the negotiation using quicklink or please login to the Supplier Portal, then search for the negotiation using the reference number UNDP-HQ-01568, following the instructions in the user guide.
Introduction
UNDP hereby invites prospective proposers to submit a proposal in accordance with the General Conditions of Contract and the Terms of Reference as set out in this Request for Proposal (RFP).
Scope of Work
Expected outputs (listed based on the due date):
- A banner in three languages. Design of a banner to be used on various platforms to promote the UNDP Annual Meeting on Rule of Law and Human Rights and the Annual Report, and to drive traffic to landing/home page of the Global Programme. Due 20 May 2025 (5 days approx.)
- A microsite for the Global Programme’s 2024 Annual Report. Based on the previous experience, UNDP will provide around 120 Word pages of text. In addition, the microsite will include est. 40 design elements, such as pop-up charts, infographics, graphs, etc. based on 2024 results (see last year’s Annual Report here). The microsite will be hosted on GitHub, for which UNDP already has a repository and will provide access to upload the final files and assets. The URL of the microsite will be https://rolhr.undp.org/annualreport/2024. Due 13 June 2025 (30 days approx.)
- Designed PDF version of the full report (ca. 120 pages) consisting of introduction, two forwards, ca. 40 country pages, five thematic blocks with subsections, extensive results framework and a financial summary. The financial summary has mostly tables and diagrams to provide in-depth information on our finances (see a sample here). Due 13 June 2025 (20 days approx.)
4. Highlights brochure in PDF, est. eight pages. A master copy shall be designed in English. UNDP will provide the translation in Spanish, French, Arabic and Russian to design the brochure in these languages. The file should be produced in high resolution version for printing and compressed for digital (see last year’s example here). A master copy in English is due 10 June (10 days approx.)
5. Up to 15 social media assets (mostly X and LinkedIn cards) in English, and up to five in three languages (English, Spanish and French – translation will be provided). Due 1 June – 30 June (5 days approx.)
6. Maintenance – to make updates, fix bugs, correct mistakes, etc. Due 12 December (3 days approx.).
B1. Web and UX requirements for the microsite
Design System Requirements (please, note that if you do not have access to certain pages, it will be provided later to a selected vendor).
- UNDP uses an atomic design system to support a cohesive and flexible digital presence. The system provides a library of components that must be used to ensure a consistent experience. When designing a site, the system’s components should be used when possible, and where new elements are introduced, they should consider the smaller “atoms” of the system.
- Base requirements
UNDP Brand Manual
https://brand.undp.org/
· Site header
o UNDP logo must be displayed prominently in the header following the direction UNDP’s design system provides.
o The site title should be displayed beside the logo along with an optional regional identifier as seen in UNDP’s design system.
o No additional logo should appear in the site header.
· Site footer
o Must include the UNDP logo as seen in the design system.
o The layout is flexible to adapt to content needs but should resemble the standard footer.
- Typography—Only UNDP brand typefaces should be used. Our brand fonts are Söhne Breit and Proxima Nova. Click here to find out more about UNDP’s typography.
Download individual font files from the Github repo.
Download full set of all Design System fonts.
- Responsiveness—UI must be responsive to desktop, mobile and tablet viewports. The final output must be compatible with all major browsers and OSs with UNDP web traffic share > 1%. This includes Chrome, Safari, Edge, Firefox, Samsung Internet, Android Webview, Opera. For older browsers unable to support modern techniques a “graceful degradation” approach should be taken.
- Accessibility—The site must adhere to WCAG 2.1 AA specifications
- HTTPS – site must be served via https.
- Measurement
- All publicly accessible web pages must have an option to measure outreach and user interaction. Creating a Google Analytics profile and sharing access and analytics insights (edit role) with the Digital Communication Studio is required. This will be provided.
- Output
- All required and recommended assets – images, fonts, stylesheets, script files, etc. in production quality.
- Smooth user experience even for low performance devices and restricted connectivity – lazy loading images, proper renditions for various media breakpoints, modular assets/libraries loading, etc.
- The web application must be static and will be served via GitHub pages.
- Website source code and assets should be shared via GitHub repo; If site includes build system (static site generator) repository should include all source files and configured to generate production code to either /docs subdirectory or GH-pages branch.
Documents :
Negotiation Document(s)
(Before Accessing other negotiations Document(s), please click on this link)
