The Personal History Profile: the form that decides your UN application

Here is the fact that changes how you apply to the United Nations: in most UN recruitment, no human being reads your CV at the screening stage. What gets read — by software first and a screening officer second — is the Personal History Profile, the structured application form you fill in on the organization’s own portal. Veterans still call it “the P11”, after the paper form it replaced; the Secretariat calls it the PHP; agencies each have their own variant. Whatever the label, it is the single document your candidacy lives or dies on, and most candidates treat it as a data-entry chore.

This guide walks through the form the way a screener reads it, section by section, and shows you how to make each field do work.

Why the PHP beats your CV

A CV is your story in your format. The PHP is your story in the organization’s format — fixed fields, fixed order, no typography, no design. That standardization exists for one reason: it lets a screening officer compare two hundred candidates against the vacancy announcement line by line, fast and defensibly. Screening in the UN system is an audit, not an impression: the officer checks whether your education field satisfies the education requirement, whether your employment entries add up to the required years of relevant experience, whether your languages match. Uploaded CVs and cover letters are, at this stage, attachments — sometimes glanced at, never decisive. The consequence is liberating once you accept it: the PHP is not paperwork after the real application; it is the real application.

The screener’s eye

Picture the reader: an HR officer or hiring manager with a stack of applications, a checklist derived from the vacancy announcement, and limited time — often only minutes per candidate on first pass. They are not looking for reasons to admire you; they are looking for the fastest defensible yes or no on each criterion. Everything that follows serves that reader: use their vocabulary, put the evidence where the checklist expects it, make every year of experience countable, and explain anything that would force them to guess. A screener who has to guess says no.

Section by section

Education

Enter degrees exactly as awarded, with the institution’s full name and the dates. Most professional posts require an advanced degree in a named set of fields, with a bachelor’s plus additional years of experience often accepted as an alternative — the vacancy text states which fields count, so if your degree title is ambiguous (“MSc in Global Studies”), use the discipline fields or the description to make the match explicit. Unfinished degrees do not count; certifications go in their own section, not here.

Employment history: achievements, not duties

This is where applications are won. Each position entry asks for a description of your functions, and the reflex — copy-pasting your old job description — is the single most common way strong candidates erase themselves. A job description says what the post was for; the screener wants to know what you did with it. Write each entry in two movements: one or two lines of scope (team size, budget or portfolio, geography, who you reported to), then three to six achievement lines that start with a verb and end with an outcome.

• Flat duty line: “Responsible for monitoring and evaluation of the country programme.”
• Achievement line: “Designed and rolled out the country programme’s M&E framework across four field offices, training 25 staff; donor reporting moved from ad hoc to quarterly with no missed deadlines in two years.”

Numbers make claims countable, but only use numbers you could defend to a reference-checker — scale, frequency and duration are usually available even when impact figures are not. Dates matter more than candidates realize: experience floors are computed from your entries, so a missing month can genuinely cost a year’s credit. And keep every relevant entry, including short contracts and consultancies — in the UN system, assembled short contracts are a normal career, not a red flag, provided each is dated and explained.

Languages

Language fields typically ask for your level in reading, writing and speaking. Report honestly against how the organization defines fluency, because language claims are the easiest thing on the form to test — panels routinely switch language mid-interview for a question or two. “Fluent” you cannot sustain in an interview does lasting damage; “confident working knowledge” that turns out solid builds trust. If the vacancy requires a language you genuinely work in, make sure it also shows up inside your employment entries (“drafted donor reports in French”), where it becomes evidence rather than assertion.

References

Choose supervisors who can verify your largest claims, warn them, and send them the vacancy text when a process reaches final stages. The strongest reference is the person who witnessed the achievement your best employment lines describe.

The cover letter field

Most portals include a free-text cover letter or motivation box. Screeners skim it; panels sometimes read it before the interview. Keep it to three or four short paragraphs mapped to the vacancy’s top requirements, and never let it repeat the form — use it to connect the dots the fields cannot: why this organization, why this duty station, why now. Plain text survives every portal; links (to work samples or a short video introduction) should be written out in full.

Mirror the vacancy announcement — honestly

Screening, whether by software or by officer, is pattern matching against the vacancy text. So write your entries in the announcement’s vocabulary wherever it is truthful: if the VA says “resource mobilization” and your entry says “fundraising”, you did the work and missed the match. Before submitting, list the announcement’s required and desirable criteria in one column and, in the other, the exact PHP line that evidences each. Where the second column is blank, either add the evidence you forgot or accept you are below the bar — grade floors are enforced mechanically, and an evening saved is worth more than a hopeless application. The line you must not cross: mirroring vocabulary is tailoring; claiming functions you did not perform is fraud against a form you sign as true, and organizations do verify.

Common disqualifiers

• Unexplained gaps. Six months of caregiving, study or job-searching is unremarkable when stated and suspicious when silent. Screeners cannot give the benefit of the doubt on a signed form.
• Unexplained acronyms. “Led CBT rollout under the RRP” means nothing outside your old office. Spell terms out once; assume an intelligent reader from a different organization.
• Duty-statement entries. Copy-pasted job descriptions with no attributable achievement give the screener nothing to score.
• Arithmetic that fails the floor. Overlapping dates, missing months, or internships counted as professional experience — screeners recalculate, and the recalculation decides.
• Inflated language levels. Tested in minutes, remembered forever.
• Missed screening questions. Many portals add yes/no eligibility questions and short essays; a blank or careless answer can auto-reject an otherwise qualified profile.

Keep a master PHP

The portals are many, the deadlines are short, and form-filling under deadline pressure produces the errors above. The fix is a master document you maintain the way an accountant maintains books: every position with full dates, scope lines and achievement bullets; every degree, certification and training with dates; language self-assessments; reference contacts; and a running list of new achievements added while they are fresh — quarterly, not on application night. Applying then becomes selection and mirroring rather than authorship: copy the relevant entries, tune the vocabulary to the vacancy, and submit hours before the deadline, not minutes. Candidates who maintain a master profile apply to twice as many genuinely matching vacancies, simply because each application costs an hour instead of a weekend — and volume against a board that shows everything live is what turns the UN’s slow arithmetic in your favour.

The PHP rewards exactly the professional habits the UN hires for: precision, honesty, and respect for the reader’s constraints. Build the master file once, keep it true, and every application after that is a tailoring exercise — which leaves your energy for the stages where a human finally looks up from the checklist: the written test and the panel.