UCL Recommendation Letter Example: Kayak guide to coastal access and safety policy (Score 93)

I am writing in my capacity as community research partner lead for a coastal access initiative, a role through which I co-designed a field protocol with the applicant over roughly ten months. That relationship gives me a specific and, I think, useful vantage point: I watched this person work not as a student completing an assignment but as a collaborator who had to earn the trust of local stakeholders while simultaneously managing real methodological constraints. We began working together when our organisation was trying to build a usable evidence base for a coastal access and safety policy memo — the kind of document that needs to hold up to scrutiny from both community members and local authority officers. The applicant came in with a background in coastal guiding operations, which I initially assumed would mean practical instincts but limited analytical range. That assumption did not survive the first few weeks. In our early protocol meetings, the applicant pushed back on a data-collection approach I had proposed, pointing out that the sampling intervals we had planned would systematically undercount access events at low tide. The correction was technically sound and, more importantly, was presented with enough supporting reasoning that I could take it to the wider team without having to reframe it myself. We revised the protocol. The final dataset was stronger for it. The second setting I want to describe is less tidy, and I think it is more revealing. About five months in, we ran a community consultation session with a mixed group — recreational paddlers, a commercial operator, and two representatives from a coastal landowner body whose interests were not straightforwardly aligned with expanded access. The applicant facilitated part of that session. What I observed was not a polished performance; there were moments where the applicant was visibly uncertain how to hold competing framings in the same conversation. But the instinct was right: rather than defaulting to the guiding-operations perspective that would have been the path of least resistance, the applicant kept returning the group to the shared evidence and asking clarifying questions. By the end of the session we had a working agreement on three contested access points that had been stalled for months. I do not attribute that outcome solely to the applicant's facilitation, but their restraint and methodological anchoring contributed meaningfully. On the analytical side, the applicant produced a coastal and access analysis that fed directly into the policy memo. The quantitative sections were competent and clearly documented, with appropriate caveats on data limitations. I would not describe the work as technically ambitious beyond what the task required, and I think the applicant would agree. Where the analysis was strongest was in the translation layer — connecting the numbers to the governance questions the memo was actually trying to answer. That translation skill is not universal, and it is directly relevant to postgraduate work in environmental governance. One honest observation I want to offer: the applicant's written motivation for moving from operational practice into policy work was, at least in our conversations, not always fully articulated. The practical commitment was evident; the conceptual framing of why governance rather than, say, continued operational advocacy was sometimes less clear. I raise this not as a disqualifying concern but because I think it is something a rigorous programme will probe, and the applicant would benefit from having a sharper answer ready. MSc Environmental Governance at UCL asks students to work across disciplinary and stakeholder boundaries under genuine uncertainty. Based on what I observed over ten months of field protocol work, the applicant has demonstrated the methodological care, community engagement ethics, and analytical translation ability that this kind of programme demands. I support this application and am happy to discuss my observations directly if that would be useful to the admissions committee.