On 3 November 2026 I attended a continuing professional development (CPD) session facilitated by Allan Jones that was all about writing for module teams.
The session was advertised as being ‘part of the STEM Writing for Production Programme designed for colleagues who are new to writing for production or who are returning to it after a number of years and would benefit from a refresher’. What follows are some notes that I’ve made following the session.
House style points
Tone
I have to confess to say that I missed this bit (I was a few minutes late), but my own take on the university writing style has changed over the years, moving from very formal, to a more informal style (this is my own personal reflection, rather than anything that Allan has said).
Pronouns
I noted down the following:
- We, the author of the material, and the student together.
- You, referring to an individual student, rather than a collective body.
- I, the author of the learning materials, even though the material might have been a collaboratively written.
A personal reflection is that I’ve been guided to make use of ‘you’ when writing some module materials. It took me a little while to become comfortable with this, but it can be useful when guiding through activities and concept.
Abbreviation and acronyms
If you need to use university jargon, spell them out acronyms, since not only students who are familiar with the concept may be the readers of the module materials. The materials you write might, for example, find their way into OpenLearn resources.
Maths
If you present numbers, do give the units which relate to the numbers. You might want to consider guidance offered by he Royal Society.
Topicality
Do consider how your materials will look between 3 or 5 years’ time. Sometimes materials can last even longer. I once worked on a module that used a case study based around the 2012 Olympics. Whilst interesting and really relevant, topicality causes materials to age.
A simple rule of thumb: keep topicality to assignment materials, since assignments may need to change every year.
Drafting
Drafting is when the hard work really starts; correcting points that might not be clear. Be mindful of sentences that can be ambiguous. The same good advice applies to module teams as it does to students writing their TMAs. After you have written something, leave it for a few days, and then come back to it.
Etiquette should be applied. The writer should exhibit manners. If there is constant uncertainty or ambiguity in your writing, your reader may become frustrated.
Consider your commas. Be aware of the ‘comma splice’, sometimes your comma should be either a full stop or a semicolon.
Wrap-up
I asked a question about writing at different levels of study. The point was made that writing for level 1 isn’t just an introduction to the subject; it is also to the university (and to academic practice). Writing for level 1 means spelling out all the steps when making an argument. In later levels you can begin to skip steps as we begin to move to higher levels of understanding.
Reflections
I have written materials for various module teams. I started by writing assignments for an interaction design module. More recently, I’ve led a rewrite to TM354 Software Engineering, and over this last year I’ve contributed to some of the materials for TM113 Computing Fundamentals 2.
I’ve also read loads of module materials. One of Allan’s points really resonated – editors are really important. Writing module materials is a team sport.
Tags: writing, module materials, writing module materials, CPD