Academic and Professional Development Plan: standards review

This submission is a document, not a paper. Parts one to five go in alongside the new component, which means the marker reads six pieces written weeks apart as one thing — and the most common problem with a portfolio assembled that way is that its parts no longer agree with each other.

So the first task is not writing; it is reading what you already submitted. The specialty whose standards you review here has to be the specialty your vision and goals pointed at in part one, and the research strategies and tools you described earlier should still be plausible for it. If your thinking has moved — which over a course is entirely reasonable — the right response is to say so explicitly in the final version rather than to leave two incompatible statements sitting in the same document. A sentence acknowledging that your intended specialty narrowed, and why, reads as development. Two parts quietly naming different destinations reads as inattention, and it is the easiest thing in the world for a marker to notice. Half an hour rereading the earlier parts is the highest-value time available on this assignment, because it is the only work that improves five components at once.

The analogy the brief opens with is worth taking literally. Builders do not negotiate with building standards; they plan around them, and a plan that fails to meet one is not creative, it is non-compliant. Scope and standards of practice work the same way: they are external, published documents issued by a professional body, they state what practice in that specialty requires, and your success plan has to contain whatever steps meeting them involves. That framing tells you what the component is for. It is not an appreciation of your specialty; it is a compliance check on your own plan, run against a document you did not write. It also tells you what tone to write in: a compliance check is a plain, itemised document, not an essay about your ambitions.

Which means the word review has to be taken at full strength. A summary of what the standards say is not a review, and it is what most submissions produce. A review reads the standards against something and reports the gap. The something here is your own plan, so the shape is: name the document, its issuing body and its edition; identify the standards or competencies most relevant to where you intend to practise; then say which of them your plan as it currently stands does not yet address, and what you are adding to it as a result. That final move is the deliverable. Everything before it is setup. Doing it that way also makes the component short, which is usually a relief by the final week of a portfolio.

Two details. The brief says to review the MSN specialisations offered, which means the choice of specialty is itself under assessment rather than assumed — a sentence on why this one rather than the adjacent one it is most often confused with does real work. And standards documents are specific to a specialty and are periodically revised, so name the edition you used. Citing a superseded version of a standards document in a component whose whole subject is standards is the kind of error that undermines more than the paragraph it appears in. Naming an edition costs six words and demonstrates the habit the whole component is about.