Imperial Recommendation Letter Example: Civil engineering student to infrastructure planning (Score 92)

Department of Civil and Environmental Engineering [Date] To the Admissions Committee, MSc Technology and Public Policy, Imperial College London I am writing in support of the applicant's candidacy for the MSc in Technology and Public Policy at Imperial College London. My basis for this recommendation is direct: over one academic term, I supervised the applicant's weekly methodology memos as part of an independent research paper in my research methods module. That sustained, close contact gave me a clearer view of their analytical development than a single coursework submission typically allows. The applicant's background is in civil engineering, and the independent paper they undertook examined infrastructure planning decisions in an urban context — specifically, how technical assessments interact with policy constraints in capital project appraisal. The topic sat at an intersection that not every engineering student navigates comfortably. What I noticed early was that the applicant did not treat the policy dimension as decorative framing around an engineering core. From the second memo onward, they were actively questioning whether the causal logic in their argument held: if a particular infrastructure standard was adopted, under what conditions would the claimed public-benefit outcome actually follow? That kind of disciplined scepticism about one's own claims is not universal at undergraduate level, and it is exactly what methods training is trying to produce. One exchange stands out. In approximately the fourth week, the applicant submitted a memo proposing a comparative analysis of two urban infrastructure schemes. The framing was confident, but the selection criteria for the comparison were not adequately justified — the two cases differed on several dimensions simultaneously, which made causal attribution difficult. I returned the memo with questions rather than corrections, asking the applicant to identify which variable they were actually trying to isolate. The revised memo, submitted three days later, had restructured the comparison around a single explanatory dimension and included an explicit acknowledgement of what the revised design could and could not claim. That response — not just fixing the problem but articulating the epistemological boundary — was the moment I began to take their analytical instincts seriously. A second scene is worth noting because it shows a different kind of readiness. During a group methods seminar, the applicant presented a section of their draft to peers working on unrelated topics. The questions they received were, predictably, from people without infrastructure knowledge. Rather than retreating into technical vocabulary, the applicant translated the planning logic into terms the group could interrogate — and then used the resulting critique to identify an assumption in their own argument they had not previously examined. That ability to hold technical content and policy-level reasoning in the same frame, and to let non-specialist challenge sharpen rather than derail the analysis, is directly relevant to the kind of interdisciplinary environment Imperial's programme involves. I want to be honest about one limitation. The applicant's prior academic record is uneven. Early in their undergraduate programme, performance in quantitative modules was inconsistent, and the analytical confidence I observed in the research paper was not always visible in earlier coursework I have seen. The independent research context — self-directed, iterative, with regular feedback — appeared to suit them better than timed, high-stakes assessment. I do not think this is a ceiling; I think it reflects a learner who develops more visibly under conditions of sustained engagement. But the admissions committee should be aware that the strongest evidence of their capability is concentrated in the latter part of their undergraduate work, and the research paper in particular. The MSc in Technology and Public Policy asks students to move between engineering evidence, economic reasoning, and governance frameworks — often within a single piece of analysis. Based on what I observed across a term of close methodological supervision, the applicant has the intellectual habits that work requires: they question causal claims, they revise in response to critique rather than around it, and they can communicate technical reasoning to non-technical audiences without losing precision. I support their application with that evidence in mind. Yours sincerely, [Title and Department] [Email]