OU blog

Personal Blogs

Christopher Douce

Preparing for your CDSA

Visible to anyone in the world

This short post presents my own take on the tutor CDSA, which is now linked to the skills audit. This post should be read from the perspective of a tutor preparing from a CDSA, rather than from the perspective of a staff tutor carrying out a tutor CDSA.

What is the CDSA all about?

The Career Development and Staff Appraisal (CDSA) meeting takes place once a year, after you have successfully passed your probation period. It is all about you and the work that you do with the university. Since everyone is working at a distance, and everyone is busy, it is best thought of a useful process that facilitates a useful conversation between yourself and your line manager. Although you and your work are the focus, it serves a number of related objectives.

Here is a list of points that have been derived from the CDSA resources. The CDSA aims to:

  • Recognise your work and your contribution.
  • Review workload and work activities.
  • Help to build an effective working relationship.
  • Determine whether there is anything you need help or support with.
  • Provide a space to discuss teaching practise.
  • Enable to share information about development opportunities and resources.
  • Set standards and expectations.
  • Share something about your future plans and career aspirations.
  • Help to align individual objectives with organisational and school objectives.

What happens and when?

You line manager will contact you and ask you to complete a CDSA form, which they will usually send to you. They may suggest a date and time for your meeting. If that date does not work for you, do suggest alternative dates. Return the form in advance of the CDSA meeting to give your line manager time to review what you have written.

Your CDSA meeting usually takes place within an MS Teams meeting room, and should last between 45 minutes and an hour.

After your CDSA meeting has taken place, your line manager will let people service know that your CDSA has taken place, or record the date in the current version of the HR system.

How to complete a CDSA form

If you have already had a CDSA, review last year’s CDSA form and revisit the objectives that you have previously set. Reflect on whether you feel they have been met. Ideally, your objectives should be SMART: Specific, Measurable, Achievable, Realistic and Timebound.

To help to prepare your CDSA document, do review your Associate Lecturer Activity Review (ALAR) which can be found on your tutor home page. This will give you the date of your last CDSA, provide a summary of your teaching history with the OU, and a summary of some of the professional development activities you have undertaken. You may also like to review the activities recorded in My Learning Centre, which is becoming more important following the introduction of the new tutor contract. It is also a good idea to review your Workload report, which is used to record how your allocated tutor time (your FTE) is being used. If you find any anomalies, or anything that you are not clear about, this could be a useful discussion point within your meeting.

Since your CDSA form is your CDSA form, it is up to you to define your objectives. It is useful to take a practical approach. If you feel that you are providing a high level of service to your students, an objective might be as simple as: ‘continuing to provide effective correspondence tuition for my tutor group’. Do reflect on areas of your practice that you feel you would like to enhance or improve.

Discussions within a CDSA meeting

Although there is no official agenda, the following simple framework is helpful when understanding what may be officially discussed:

  • Review of achievements and objectives since the last CDSA.
  • Review of skills audit.
  • Setting of new objectives.
  • Professional development planning.

The CDSA meeting can also be an informal discussion space; the most important point is to have a conversation. It is okay, for example, to share polite grumbles within your line managers. Sometimes grumbles can mask misunderstandings. It really helpful for your line manager hears about the practicalities of tutoring. Change can only get better if issues or problems are shared.

What happens to your CDSA form?

Your CDSA form is for you, and for your line manager – no one else. What is written on your form is confidential and are not shared with others. If your line manager changes, your current line manager may share your CDSA with your new line manager.

Reflections

I always tend to quite enjoy my CDSA. It is rare that I have the opportunity to talk about myself and the work that I do with someone who is actively interested.

I always think of my CDSA meeting as a friendly chat. If you are to ever come away feeling annoyed after a meeting, it is not your fault; it is the responsibility of your line manager to run a helpful and constructive meeting. My final thought is this: there should be no surprises in your CDSA, since you should be the expert in your own workload.

Permalink Add your comment
Share post
Christopher Douce

Accessibility: AL Professional Development

Visible to anyone in the world
Edited by Christopher Douce, Thursday 29 October 2026 at 12:22

On 24 April 2024 I attended an AL professional development event that was all about accessibility. What follows is a short blog summary of the event, sharing some of the key points that I found of interest. I’ve written this summary as a part of an eSTEeM writing project, which has the aim of providing useful help and guidance to tutors.

Twenty Tips for more Accessible AL practice

This first session was facilitated by Simon Ball, Associate Lecturer for the faculties of WELS and STEM. The sub-heading for his session was: quick wins and essential adaptations. Simon worked for the Jisc TechDis accessibility service. For a while, we worked together, tutoring a module about accessible online teaching.

He also made the point to me that there is a lot of detail that lies underneath each of his tips, which I’ve tried to summarise concisely as I can:

1: Set up documents. When you create, use, and share documents, always use the Word in-built headings. This makes them navigable for users of assistive technologies, such as screen readers. Plus, it makes documents easier to work with then they get bigger.

2: Images - Inline or floating? Make sure that images, tables, charts, or anything else are embed within Word document ‘inline’ rather than floating. This makes sure that the navigability of a document is clearer. You can check this using the Word Accessibility checker.

3: Punctuate bullet points. Add a full stop at the end of a bullet point. This adds a pause and will make documents more understandable if read through a screen reader.

4: Don’t convey information by visual means alone. In other words, don’t use colour to convey information. If you find that colours are useful in a diagram to share information, make sure that the information presented in the diagram is shared in another way. Screen readers won’t be able to pick up on colours.

5: Avoid relative instructions. Simply put, to use Simon’s words, ‘avoid using only phrases like ‘the box on the right’ or ‘at the bottom of the page’ as learners using a screen reader will not have a clue what is on the right or at the bottom’. This applies to both documents, and to instructions shared within tutorials.

6: Choose accessible fonts. Use sans-serif fonts, and ‘never use smaller than 12 point (RNIB recommends 14 point), or 20 point on slides’.

7: Avoid footnotes. The add complexity when trying to navigate through a document. Simon shares a clear option that they should only be used ‘for providing supplementary information that isn’t essential to the reader, so they can safely be ignored without material loss’.

8: Avoid obliques. In other words, avoid slashes, such as ‘and/or’, since this can cause screen readers to read them as ‘and slash or’. If you can, try to ‘phrase the sentence without the oblique’. It is obviously okay to use them within web addresses and within the subjects that specifically use them.

9: Alt text. Provide alt text, or alternative textual descriptions; ‘all images or graphics that contain useful information (as opposed to purely decorative images) must have alternative text (alt text)’. Give only the essential information that is needed.

10: Set up tables carefully. If you can, do prioritise rows over columns since a screen reader will read a row at a time.

11: Avoid adding textboxes. There is a simple reason for this: they are not read by screen readers. Even if a screen reader did read them, the reading order would be ambiguous.

12: Colour contrast. To ensure readability there must be a good level of contrast between foreground and background colours.. The following specific guidance is offered: ‘for body text you need a ratio of >7 to 1; for headings or isolated words you need a ratio of >4.5 to 1.’ To help, there are some useful free tools available.

13: Make feedback usable. Tell students how they can find on script comments; ‘say where it can be found, and what colour it is’ also invite feedback from students about whether the approach you use is accessible. Give dates of next events and TMA cut off dates, and provide explanations if a student has not gained full marks. Don’t say “9 out of 10, very good”, say something about what needed to be done to get the final mark.

14: Inclusive feedback. Ensure that feedback is ‘directive, constructive and clear’ whilst avoiding ‘metaphors or colloquialisms’. Offer helpful examples. Always consider how your feedback can be read.

15: Keep in touch with students. Keep an eye on which students have disability marker – ask your student about their specific needs, and be driven by them. Check in before assignments. A key point that Simon shared was that the personal touch cannot be overstated.

16: Synchronous sessions (lectures and tutorials). Give each slide a title and a number. Consider using the camera, but do check on student needs and bandwidth. Use anonymous activities such as polls, and encourage the use of raised hands. If you are making a recording do dedicate some time for some unrecorded Q&A discussions at the end of a session. Finally, consider sharing slides before a tutorial.

17: Breakout rooms. Breakout rooms are difficult. Make sure you practice before running a session that has a breakout room. Make sure that students are clear about what is going to happen before moving them into a breakout room. Ensure that there is a helpful slide that describes the task within each room. Allow time; some students may be using assistive technology. Check to make sure there are no sound issues. Give a clear warning before brining students back to a plenary room.

18: Supporting deaf students in synchronous sessions. Allow time for an interpreter to convey messages to and from a student. Ensure that your webcam is on and the pod or window that is used is as large as practically possible; this is to facilitate lip reading. Be sure to summarise any questions asked by students. Ensure that tasks are written onto text chat areas. An additional tip is do turn on any subtitling or transcription tool.

19: Ask about language. Ask students how they would like to be referred to. Different students will have different preferences.

20: Get creative, be a voice. Some subjects will require creative solutions. Consider the challenges that exist within your own discipline. Do contact module teams and line managers for advice and guidance.

20.5: Bonus tip: every tutor always does their best. Don’t worry if you get things wrong. Learn from the experience, and move on.

Proactive motivational support

The second presentation was by Annie Storkey, Associate Lecturer for the Faculty of WELS, who is also an EdD student. Her presentation had an important subtitle, ‘online students with mental health challenges’. Annie shared a number of useful recommendations, which I hope I have summarised effectively:

  • Make early contact with students, especially those who may have disclosed difficulties. Make sure that regular contact is maintained.
  • Use data analytics tools, such as OU Analyse, to find out which students are at risk of withdrawing, and make contact, especially at important points in the module such as TMA cut off dates.
  • Communicate regularly: send regular emails; this can be motivating.
  • If the module addresses sensitive subjects, make sure that students are told of these in advance. In other words, embed resilience into your teaching.
  • Remember that tutors are only able to provide academic support to students, but do feel able to signpost and refer students to the student support team and other support resources.
  • It is really important that tutors look after their own mental health and wellbeing.

I found Annie’s thought provoking. She referenced a former IET colleague, John Richardson and work carried out by Kate Lister, who wrote about barriers and enablers to student mental wellbeing.

AL Support for Dyspraxic Students

The final session was by Angela Eyre, Associate Lecturer from FASS. Angela spoke about a FASSTEST scholarship project, Dyspraxia (Developmental Coordination Disorder): Understanding students’ requirements, which carried out a survey to explore the barriers and enablers that are faced by students who are dyspraxic. 

Students who are dyspraxic face a number of barriers, which may include memory difficulties, time management, and find it difficult to find information from resources such as module websites. Other challenges may include reduced confidence about articulating thoughts and ideas, and difficulty proofreading and decoding questions.

I made a note of some key enablers, which can include the positive impact that tutors can make, the design of a module, and early access to module materials. Tutors can help by sharing direct and clear encouragement, share checklists for the completion of TMAs, and help students to decode the TMA questions through one-to-one sessions. 

I noted the following words: “give students permission to try [their study approach] their way”; everyone is likely to be an expert in their own condition. Since all students are different, seek guidance from them in terms of their needs and preferences. I also made a note about feedback: model solutions to illustrate alternative ways of forming solutions.

Towards the end of the session, I noted down a couple of resources that were specific to dyspraxia:

Resources

What follows are some useful resources which address some of the themes that were shared during this session:

Reflections

I really enjoyed Simon’s session; I liked how he shared a lot of detail in a concise way. His tips offer a useful practical framework. I’m mindful that I don’t always follow all the points that he highlighted, but I really ought to. When it comes to accessibility of teaching resources, there is always room for improvements.

Annie’s session emphasised the importance of mental health. Her session covered a lot of ground which related to her EdD research, and I took away a number of helpful suggestions. It was interesting that Angela’s presentation described research that considered the barriers and enablers, echoing Lister’s research about student wellbeing.

These three presentations have made me remember another lesson that I once learnt: positive adjustments for one group of students are also likely to help everyone.

Acknowledgements

Many thanks to all the presenters. Thanks are also extended to the ALSPD team who organised this event.

Permalink 1 comment (latest comment by Matt Raven, Monday 9 June 2025 at 23:10)
Share post
Christopher Douce

Student Interaction and Collaboration in Tutorials: Why, What and How

Visible to anyone in the world
Edited by Christopher Douce, Thursday 29 October 2026 at 12:23

On 13 June 2024 I attended a seminar that was run by three colleagues from the School of Maths and Statistics: Cath Brown, Vinay Kathotia, and Abi Kirk. The seminar was intended for ‘anyone interested in the development of online teaching’.

For anyone finding this blog post, it might be useful to view this summary alongside other posts about Adobe Connect , tutorials, and online pedagogy.

What follows are some brief notes that I made from each of the presentations. For concision, I have taken the liberty of abridging each of the titles. Some reflections and acknowledgments are shared at the end.

Why should we promote students working together?

The subtitle for this first presentation, which was facilitated by Vinay Kathotia with Cath Brown was: what are the pedagogical and broader benefits?

A useful term was introduced: student-centred pedagogy. Student adopting an active role during a tutorial can mean increases in confidence and self-efficacy. Interaction can be as simple as students making points, listening, arguing, and responding to a tutorial.

These points can be connected to ‘inquiry based mathematics education’ where collaboration has the potential to lead to higher levels of inclusion. There are some advantages of collaboration: mathematics is a collaborative activity. Through tutors demonstrating mathematical thinking, students can see that mathematics can be messy.

I noted down the phrase: “community enhances attainment”. Community can relate to the study of a module, and anything that helps to develop community, but is also useful is important.

We were asked a question: what were everyone’s experiences? How do we convince the students it is a good idea for them to come along to tutorials? Perhaps writing can be useful; asking students to write an account of what happened during a tutorial, is one approach that can facilitate sharing and suggest the benefits of tutorials.

The design and structure of collaborative tasks

The second session was facilitated by Abi Kirk. The full title of this second session was ‘some ideas and examples on the nature, design and structure of collaborative tasks’. The presenters described some collaborative tasks they have used for tutorials: small-group problem solving (which takes place on M337), and ‘pub quiz’ group work.

In the pub quiz activity, students were put into breakout rooms where they have access to five questions. In each room, students record their answers. This then leads to a plenary session which is facilitated by a tutor where all the results are shared using an Adobe Connect whiteboard.

A question was asked: how could collaboration using breakout rooms work in your context? One thought is to giving information in advance; perhaps it is important for everyone to know what is going to happen in a tutorial. There is an inherent tension of giving them too much in advance. Making a session look enticing and interesting is a skill all of its own.

Technology to enable collaborative work

The full title of this session was ‘technology to enable collaborative work - Adobe Connect and beyond’. In this session we were introduced to a variety of different Adobe Connect features and maths tools the presenters have used, such as GeoGebra, Desmos and PolyPad. Different subjects will, of course, necessitate the use of different tools. What I might use as a computing tutor will, of course, be different to what a maths tutor may use.

You can, of course, use features within Adobe Connect, such as screensharing, file sharing and polls with external tools and utilities. In some tools it is possible to create multipart activities, for example, and share URLs (web page links) with students through a text chat window.

One other idea is to open a shared Microsoft OneNote notebook. Any OU student can use it through Office 365. It can be used as a whiteboard where student can share their work. Control could be given to students, where they could interact with mathematical text.

Towards the end of the session, we returned to the topic of breakout rooms. They are pretty complex, which means that it is important to make sure you have a solid understanding of the interaction metaphors that are used. Tutors need to know how to set up and move between different layouts, how to adding and deleting breakout rooms, how to start and end breakout rooms, how to communicate to all rooms, moving between rooms, and combining results from different rooms together in a virtual plenary space.

Reflections

Quite a lot of time has elapsed between attending the seminar (June) and making these notes available (November). This means that there is risk that the sessions may not be summarised as accurately as I would have liked them to be. This said, I hope the points that I have shared are helpful, and apologies to the facilitators if I have misrepresented anything.

I went to this session since I hold the view that student interaction through online tutorials is important, but I also have the sense that it is very difficult to do well. This session was of specific interest since there are some key similarities between maths and computing: both subjects work with textual notations. With maths, there are equations (and whatever mathematicians do); within computing there are programming languages.

I do feel that there are multiple structural and technological barriers that are put in everyone’s way before interaction can become possible. More often than not, I don’t hear any student voices in tutorials, since no one really knows anyone. I remember that a book called eModeration by Gilly Salmon emphasises the importance of digital socialisation. In the currently tutorial world, where students can attend any number of different tutorials by different tutors, the tentative social connections between everyone works against interaction and collaboration. I don’t know what the solution is.

Using distance learning technology to facilitate interaction and collaboration is difficult. I don’t know where this comes from, but I’m always minded that perhaps digital educators have to become digital media producers and performers. To be good at digital performance, rehearsals are essential.

Acknowledgements

Many thanks to all facilitators.

Permalink Add your comment
Share post
Christopher Douce

Inclusive Student Engagement in Level 1 modules

Visible to anyone in the world
Edited by Christopher Douce, Thursday 29 October 2026 at 12:24

On 20 July 23 I attended a short one hour seminar that was all about inclusive student engagement in level 1 modules. The seminar had the subtitle: “a supportive framework designed by current/recent students”. The session was prepared and presented by Catriona Bergman, Olivia Brennan, Norain Imtiaz and Owen Lucas, who were also OU student virtual interns.

The seminar had a bit which shared their framework, followed by a discussion activity. I’ll begin by sharing an abridged version of the framework, and then I’ll go on to sharing a couple of points from the discussion, then concluding with a set of reflections.

Engagement framework

If I understood this correctly, their framework shared a number of themes that relate to the student/tutor relationship. There are six key points, each of which was complemented by a suggestion, or a prompt. For brevity, I’ve edited these into a form that works with my own practice.

  1. Addressing the power dynamic: address the difference in status between tutors and students. What do you do to encourage students to reach out to gain support?
  2. Consistency of communication: regular support and timely responses. How often do you communicate with your students?
  3. Proactive communication: tutors taking the initiative to interact with students. Do you contact students before their assignments are submitted?
  4. Humanising tutors: providing an opportunity to build a relationship. Do you feel comfortable in sharing your own personal experiences?
  5. Assessing communication and support needs: in the opening letter encourage disclosure. What opportunities are there for you to discuss individualised study needs with students?

Tutor and students are unknown to each other: a two-way relationship is important. What opportunities are there for icebreaking activities for students and tutors to get to know one another?

The Hidden Curriculum

There was another useful slide during the first section which was all about the notion of the hidden curriculum. I have come across the idea through the notion of academic literacies. Put another way, this is all about knowing the hidden conventions that relate to study, a discipline, and academic communication.

  • Students might not have necessary skills from their earlier education experience. Tutors can direct students to resources that can be used to develop skills (e.g. numeracy, academic writing skills, critical thinking, IT literacy, etc.).
  • Encourage students to reflect on the skills they may need to develop, and provide (or signpost students to) appropriate resources.
  • Encourage development of TMA writing skills and inform students about the importance of good academic conduct.
  • Encourage students to develop their own study habits to support their learning, and embed this within tutorial and one-to-one sessions. Consider the environment in which study takes place.
  • For the module that you are tutoring, highlight, discuss and critique ideas and practices that can contribute to the hidden curriculum.
  • Ensure students are aware of the different avenues that could be followed to gain support (from the tutor, from the module forums, or from the student support team).

Breakout rooms: what do you share, what don’t you tell them?

It was onto a breakout room discussion, where we were asked what we share with our students, and whether we share any of our own vulnerabilities. The intent behind this was to think about the extent to we may disclose something about ourselves, to engender trust and to demonstrate empathy.

Rather than focussing on sharing of vulnerabilities, the group I was assigned to primarily discussed what information we might disclose to students when we contact them for the very first time. Some key points to share include: our qualifications, whether we have been a tutor on the module before, and something about where we are based in the country. There was also some discussion about the importance of tone, and the phrase ‘professional informality’ was shared.

Reflections

I felt this session offered me some reassurance that I have been doing (roughly) the right thing. One way to formalise some of the points mentioned in the framework would be to devise some form of communication plan. This might mean a summary of what is sent to students and when. It is, of course, important to be aware of what module teams are doing, since they may well have their own communication plan, and sets of reminders and messages scheduled.

I was drawn to the session due to the mention of inclusive engagement, since I didn’t really know what this was, or how to describe it. I found it interesting that the focus lies on facilitating inclusive engagement through sharing, and putting oneself, and sharing aspects of one’s identity to others. The aim of doing this is, of course, to attempt to remove potentially perceived barriers, such as power differences between tutors and students.

Reflecting on this further, I have certainly disclosed more personal information. When tutoring on a module about accessible online learning, I have, for example, disclosed a hidden disability. My view is that context is always really important, whether context relates to the subject, or the tutor-student relationship.

Acknowledgements

Many thanks to the AP student virtual interns who facilitated the session and shared their framework. I hope that the version that appears in this blog matches with its original aims and intentions.

Permalink 1 comment (latest comment by Paul Leo Antoine Piwek, Monday 31 July 2023 at 15:36)
Share post

This blog might contain posts that are only visible to logged-in users, or where only logged-in users can comment. If you have an account on the system, please log in for full access.

Total visits to this blog: 4500841