Student Support Plans in Irish
Prepare Student Support Plans in Irish with a practical routine for observations, targets, language review and collaboration.
Writing a Student Support Plan in Irish involves more than translating a finished English document. The team needs a shared understanding of the student's strengths, the priority need, the intended outcome and the classroom actions. A useful Irish-language plan should be clear to the people who will implement it and accessible to the student and family involved in the process.
For teams searching for Pleanna Tacaíochta, the practical question is how to keep the plan clear from the first observation through to review.
This guide is for school teams considering plans in Irish, including Gaelscoileanna and Gaelcholáistí. It offers a practical preparation and review routine. It is not a translation of Department guidance. Use the Department of Education's SET guidance and supporting documentation as the official reference for the relevant school setting.
Agree who needs to read the plan
Start by identifying the people who will use the document. A class teacher may work through Irish, a specialist may supply an English-language report, and a parent may prefer to discuss the plan in either language. Agree how those perspectives will be brought together. Do not assume that the language of a source report must determine the language of every subsequent conversation.
Record your practical arrangement: who prepares the draft, who checks the Irish, and who explains the agreed actions to anyone who needs clarification. If the school keeps versions in more than one language, decide which version records the agreed decision and how later changes will be reflected across both. Uncontrolled copies can drift apart during a busy term.
Gather observations in usable language
Teachers can begin with clear notes about what they observe. Include the context, the task, the support available and the student's response. Separate an observation from an interpretation. For example, “did not begin after the whole-class instruction” records an event; “does not want to work” assigns a motive that the observation alone does not establish.
When information comes from different languages, retain the intended meaning rather than matching every word. Ask whether the final wording would lead two colleagues to provide the same support. If a term is unfamiliar, explain the practical action beside it. Consistent, understandable terminology is more valuable than a document that sounds formal but leaves staff unsure what to do.
Keep targets measurable across languages
A target needs the same evidence of progress whichever language is used. Identify the action, the conditions, the support available, the success criterion and the review point before polishing the wording. This makes it easier for the language reviewer to check that the educational meaning has been preserved.
Consider a fictional target about beginning a task. The team wants the student to start the agreed first step within three minutes, using a visual prompt, in four of five observed opportunities. When preparing the Irish wording, check that “with a visual prompt” has not become “without help”, that the number of opportunities remains the same, and that the review period is still explicit. Those small differences would materially change the target.
Review drafts with an Irish-speaking colleague
Build a language check into the workflow instead of leaving it until the document is being shared. Ask an appropriately fluent colleague to check meaning, natural phrasing, names, grammar and the consistency of educational terminology. Read the target alongside the original observation. A fluent sentence can still describe the wrong outcome.
Pay particular attention to negative wording, time periods and degrees of support. Confirm that “sometimes”, “usually” and “independently” reflect what the team actually means. Where a specialist recommendation is quoted or summarised, check the source and retain relevant context. Avoid turning a tentative recommendation into a definite conclusion during translation or editing.
Make collaboration practical
The plan should help people contribute rather than create an additional language barrier. Offer a clear way for staff and families to raise questions. At a meeting, explain the intended classroom actions and ask participants to describe them back in their own words. This is a useful check on shared understanding, especially when different people use different languages in daily life.
Keep a short record of agreed changes. If feedback leads to a revised target, update the relevant versions together and identify the current plan. Give the people implementing it a clear review date and an agreed method for recording observations. The team should not have to reconstruct which version was in use when progress was recorded.
Use software as part of the whole workflow
SENScribe supports draft plans in English or Irish within its wider SEN workflow: caseloads, SMART targets, staff and parent input, actions, reviews and follow-on plans. School staff remain responsible for checking the wording and deciding what belongs in the student's plan. Language selection does not replace professional or linguistic review.
Apply for a personal 14-day trial to explore the planning workflow. Applications are reviewed, and approved applicants receive the next steps by email. For related preparation, read the Student Support Plan template walkthrough, the Student Support File guide, and the SMART targets library.