UN applications are screened against the criteria in the vacancy, often by more than one reviewer working through a checklist. That means completeness and alignment beat flair. The goal is to make it effortless for a screener to tick every box.
The personal history form (P-11 / PHP)
Most UN systems ask for a structured candidate profile, sometimes still called the P-11 or personal history profile. This is frequently the first thing a screener reads, so fill in every field. Give your full employment history with start and end dates, with no unexplained gaps, and describe each role in terms of what you actually did and achieved.
Your CV
Keep the CV concise and achievement-focused, and align it to the vacancy. Lead each role with results rather than duties, and quantify them: budgets managed, people supervised, programmes delivered, percentage improvements. A reviewer should see your fit in the first half page.
The cover letter or motivation statement
Address each required qualification in turn and give evidence for it. If the post asks for five years of experience in monitoring and evaluation and fluency in French, say explicitly where you gained that experience and state your French level. Mirror the language of the vacancy so the match is obvious.
Tailor to the criteria
Before you submit, line up your application against the vacancy’s requirements, education, years and type of experience, languages and competencies, and check that each one is clearly evidenced somewhere a screener will look. Do not make them hunt for it.
Deadlines and final checks
Submit before the closing date, which is usually set in the duty station’s local time. Re-read for accuracy of dates and facts, make sure your contact details are correct, and keep a copy of exactly what you submitted.
Common reasons applications are screened out
- Generic applications not tailored to the specific role.
- Unexplained gaps or missing dates in the employment history.
- A required qualification that is met but never clearly stated.
- Submitting after the deadline.
Worked example: mapping your experience to the stated requirements
The fastest way to lose a recruiter is to make them search for proof you meet a requirement. Do that work for them. Open the vacancy, copy each line from the responsibilities and required competencies into a two-column note, and write next to each one the single most relevant thing you have actually done. Then make sure that exact wording surfaces in your personal history profile and your motivation statement.
Suppose the vacancy says 'experience coordinating project activities across multiple stakeholders' and 'drafting reports for senior management'. A weak profile says 'responsible for various projects'. A strong one says 'coordinated a four-partner field project across two government counterparts and an implementing NGO, and drafted the quarterly progress reports submitted to the country representative'. Same role, but now the reviewer can tick both boxes without guessing.
- List every required and desired qualification as its own line before you write anything.
- Against each line, name one concrete task, deliverable, or outcome you owned.
- If a requirement has no honest match, leave it blank rather than stretching the truth, then decide whether the gap is small enough to still apply.
- Reuse the vacancy's own nouns and verbs so a keyword scan and a human reviewer both find what they expect.
Quantifying achievements without inflating them
Numbers make a claim checkable, which is exactly why they are persuasive. The goal is not the biggest number but the most defensible one. Describe the size of what you handled (a team, a budget you administered, a caseload, a number of districts or partners), the change you contributed to, and the period over which it happened. If you only influenced a result rather than delivered it alone, say 'contributed to' or 'supported', because an interview panel will probe anything that sounds inflated.
When you do not have a clean figure, give scale and frequency instead of a fake precision. 'Processed a high volume of procurement requests on a weekly cycle' is honest and still informative. Avoid rounding a soft estimate into a confident statistic you could not reproduce if asked, and never quote an organisation-wide result as if it were personally yours.
- Prefer ranges and approximate scale you can stand behind over a false exact figure.
- Pair every number with its timeframe so growth or volume is interpretable.
- Use 'contributed to' or 'supported' when the outcome was a team or institutional result.
- Be ready to explain in an interview how any figure you used was measured.
Writing a focused motivation statement
A motivation statement is not a summary of your profile in prose. It answers three questions: why this role, why this organisation's mandate, and why you specifically can do the work now. Keep it tight and structured. A workable shape is one short opening that states the post and your core fit, two middle paragraphs that each take a central requirement and prove it with a specific example, and a brief close on why the mandate matters to you and your availability.
Lead with substance, not enthusiasm. 'I am passionate about development' tells a recruiter nothing they can score. 'My three years administering community grant disbursements in a low-resource setting map directly to the financial monitoring this post requires' does. Name the duty station or programme area if it is fixed, and avoid generic praise of the organisation that could be pasted into any application.
Final consistency and proofreading pass
Most rejections at the screening stage come from avoidable errors, not weak experience. Before you submit, read the whole package once only for internal consistency. Your employment dates must line up across the profile, the CV, and anything you state in the cover letter, and they must not imply two full-time roles running at the same time unless one was clearly part-time or a secondment, which you should label. Job titles must match what your references and any certificate of employment would confirm.
Then check the things screeners verify directly: claimed degrees and their award years, language levels stated honestly against the role's working-language requirement, and every number you used. Confirm you answered each mandatory question in the application system, since a blank required field can auto-disqualify you regardless of how strong the rest is. Save the vacancy text and your final answers, because postings are often taken down once the deadline passes.
- Cross-check all start and end dates across every document for overlaps that do not add up.
- Verify degree titles, institutions, and graduation years exactly as on your certificates.
- State language proficiency truthfully against the post's working-language requirement.
- Confirm no mandatory field in the application system was left empty before final submission.
- Keep a saved copy of the vacancy and your submitted answers for interview preparation.