MSN plan Part 5: CV, development goals, social change

Three deliverables sit inside this component and they are supposed to agree with each other, which is the requirement nobody states and most submissions miss. A curriculum vitae, a statement of professional development goals, and a statement aligning one or more of those goals with the university's emphasis on social change. Written independently they produce a document whose parts describe three different people: a CV recording where you have been, goals pointing somewhere unrelated to it, and an alignment paragraph reaching for a mission statement neither of the other two mentions. The portfolio framing in the brief's own opening is the clue — a portfolio is evidence, so the CV is what makes the goals credible rather than an administrative attachment filed alongside them. Read the three back to back before submitting and the disagreements are usually obvious inside a paragraph.

The CV is the piece most often produced carelessly, usually because it is confused with a résumé. They are different documents with different rules. A résumé is short, tailored to a particular post, and selective by design. A curriculum vitae is comprehensive and chronological: education, licensure and certifications with their numbers and dates, clinical and professional experience, memberships, presentations, publications, honours, service. It grows over a career rather than being rewritten for each application, which is exactly why it belongs in a development plan — it is the document that shows accumulation. Producing a one-page tailored résumé here answers a question the brief did not ask, and loses the record the rest of the component depends on. Length is the giveaway: a CV that fits on a single page has almost certainly been pruned like a résumé, and the pruning removed exactly the accumulation this component exists to display.

Professional development goals are the second place this goes wrong, and the problem is that most stated goals are credentials rather than development. Becoming a nurse practitioner, finishing the MSN, passing a certification exam — these are milestones with dates, and they are worth listing, but none of them describes a capability you intend to build. A development goal names something you will be able to do that you cannot do now: appraise evidence well enough to change a unit protocol, lead an interprofessional handover, design and evaluate a teaching intervention, mentor a new graduate through their first year. Goals written that way can be aligned with something; goals written as credentials can only be scheduled. The credential is usually still worth naming, but as the route to the capability rather than as the goal itself — a difference of one clause and a great deal of substance.

Which is what makes the third statement hard, and it is the one the marker will read most closely. The university's emphasis on positive social change is an institutional commitment with a stated meaning, not a decorative phrase, so the alignment has to be argued rather than asserted. That means naming the change — who is affected, in what setting, and what would be different — and then showing the mechanism by which your development goal produces it. 'I want to help people' is not an alignment; it is the absence of one. 'Building appraisal skill so I can revise our discharge teaching for low-literacy patients, who currently readmit more often' is one, because every clause in it could be checked. The test is whether somebody could tell, a year from now, whether it had happened. If they could not, nothing has actually been proposed.