Personal Statement for a Scholarship, Master’s or Exchange

Act as someone who has read hundreds of personal statements on a selection committee for scholarships, master's programmes and exchanges, and who knows why most of them fall at the first paragraph: they all say the same things ("ever since I was a child, I have dreamed of...", "I am a dedicated person with a passion for challenges") and none of them prove anything. A good statement answers what the committee asked, with facts that only that applicant has. Context: I am applying for [PROGRAMME - EX: a master's in environmental engineering at TU Delft; a one-semester exchange scholarship; a full undergraduate scholarship]. The application guidelines ask for [WHAT THE GUIDELINES ASK FOR - EX: paste here the questions or the part of the guidelines about the statement], in no more than [LIMIT - EX: 1 page; 500 words; 4,000 characters including spaces]. My material is this: [MY MATERIAL - EX: CV; grades; projects, research, volunteer work; what made me want this programme, as loose bullet points]. What I know about the programme: [THE PROGRAMME - EX: research areas, professors, modules, the profile the website says they are looking for]. Task: write the statement ready to send, answering the guidelines with what I actually have. Rules: 1. Before writing, list the questions the guidelines ask, explicit or implicit, in their order. The statement answers all of them, in that order, and none is left unanswered. 2. Every claim about me comes with PROOF taken from my material: a project, a number, an episode with a date or a place. A claim without proof is cut from the statement ("I am dedicated" stays out; "I redid the experiment three times until the error fell below 2%" goes in). 3. Use ONLY my material. Whatever is missing for an answer to hold together becomes "[MISSING: what it is]" in its place, never invented experience, grades or awards. 4. The "why this programme" paragraph mentions at least two things that exist only in IT (a research area, a professor, a module, a project) and connects them to what I want to do. Test: if I swap the programme's name for another one and the sentence still works, it is generic; rewrite it. 5. Open with a concrete fact from my own path, not with a catchy line. Banned: "ever since I was a child", "I have always been passionate about", "I am writing to apply for", "the dictionary defines", "in this statement I will". 6. Close with what I will do with the programme after it ends: the concrete plan, not "give back to society". 7. Respect the guidelines' limit in the unit they use (words, characters or pages) and give the count at the end. If the material does not fit, cut what proves least, never the proof. 8. First person, direct tone, no adjectives I give myself. Short sentences: the people assessing read dozens of statements a day. 9. Do not attribute anything to the programme that I did not provide: if it is not in what I pasted, do not mention it. Response format: first the list of the questions in the guidelines; then the statement, ready to send; then the count ("Words: N of 500"); then each [MISSING] with what I need to look up; and finally the two sentences of the statement most at risk of sounding generic, with an alternative for each.