Designing Arabic Training Content for Humanitarian Procedure Updates in Syria

The HR unit of a programme office in Syria revises its leave request procedure: requests now go through the line manager first, the form has two new fields, and approval moves into the HR system. An email goes out with the new procedure attached. Three weeks later, some staff still send the old form, which keeps circulating in a messaging group. Two offices use an Arabic summary that calls the HR focal point by a different title. Nobody can say with confidence which version is current.

For NGO teams and teams implementing UN-funded programmes, procedure updates are routine. The difficulty is rarely explaining the new rule. It is making sure that staff know which version applies, from when, and what each Arabic term means. Arabic training content for an update therefore needs to carry its own owner, version, and effective date, use terms that local teams recognize, and never depend on beneficiary data.

This article shows how to design that training content for a non-sensitive administrative procedure. It is general guidance only: your organization’s own policies, procedure owners, and donor requirements always take precedence.

Start the Training Content with What Changed

When a procedure is revised, the instinct is to send the full document again as the training content. Staff then have to find the changes themselves, and most will not. Start instead with a short change analysis, agreed with the procedure owner:

• Which steps, roles, forms, limits or deadlines have changed.

• Who is affected, by role and office.

• What has not changed, so staff do not relearn what they already do well.

• What a staff member must do differently from the effective date?

Then build the update package around that analysis. In most cases, four pieces of Arabic training content are enough: a one-page change brief stating what changed, from when, and what to do now; a before-and-after comparison of the steps or the form; one short practice case; and an updated job aid that replaces the old one. If the procedure is new or has been rewritten from scratch, the task is different, and our guide to turning NGO manuals into practical eLearning tasks is the better starting point.

Keep each piece of training content short enough to read on a phone between tasks, and test the package before release. Ask two staff members who have not seen the draft to complete the practice case using only the change brief and the job aid. Every question they ask points to a gap in the training content that is cheaper to fix now than after the effective date.

Make Version Ownership Visible in the Training Content

Version confusion often begins because nobody owns the training content itself. The procedure has an owner, usually in finance, logistics, or HR, who is responsible for the rule. The Arabic training content needs a named owner too, responsible for the wording, the format, and the distribution. Agree on both roles before the update is drafted, and record them on every item.

Every piece of training content in the package should show the same version label as the procedure it teaches, the date it was approved, and the owner by role title. Keep one master file for each item, and produce all other formats, such as a PDF for printing, slides for a team meeting, or a voice note for staff who mostly use phones, from that master. When a correction is needed, it is made once, and every format is regenerated.

Decide where the current version lives, and say so in the change brief. Whether that is a shared drive, an intranet page, or a learning platform, staff should know the one place to check. For setting up controlled access on a platform, see our article on access and user management in an Arabic LMS for NGOs in Syria.

Design Training Content Around the Effective Date

An update has three dates that matter: when it is approved, when staff receive the training content, and when the new rule takes effect. Put the effective date at the top of every item, in the same format, so it cannot be missed.

Ask the procedure owner for a transition rule and include it in the training content: what happens to requests, purchases, or files started before the effective date? Without this, staff will apply the new rule to old cases, or the old rule to new ones, and both will be returned.

Where possible, release the package a few working days before the effective date, so that staff can prepare and ask questions. A short live briefing can help teams spread across several offices; see our article on live virtual sessions for distributed NGO teams.

Finally, retire the old training content deliberately. Mark superseded copies clearly with the date they were replaced, remove them from shared folders, and ask office focal points to delete old files from messaging groups and post the new one. Keep one archived copy of each superseded version, so that past decisions can still be checked against the rule that applied at the time.

Review the Arabic Training Content with a Local Team

Many procedures in NGO and UN-related settings are written in English and applied in Arabic. The same concept can then appear under different Arabic names in different offices, or under an Arabic term that nobody uses in daily work, so the training content teaches a word staff never hear. Before release, ask two or three staff from different offices who do the task to review the Arabic training content for three things:

• Clarity: can a colleague understand each instruction on first reading?

• Consistency: is each key concept named the same way throughout, and on the forms and systems staff use?

• Recognition: are these the terms the team actually uses, and if not, which term should be shown alongside?

Record each decision in a short glossary that travels with the training content and with future updates. Where a procedure keeps an English term, show it once beside the Arabic term. For terms that come from UN programme documents, a public reference can help settle debates: the United Nations describes UNTERM as the multilingual database for official United Nations terminology, with a portal in the six official UN languages, including Arabic. Use it as a reference, while the local team confirms what will be understood on the ground.

Keep Beneficiary Data Out of Every Example

The practice case and any screenshots in the update package must use fictional information only: invented staff names, suppliers, amounts and reference numbers. Never use beneficiary names, case numbers, photos, lists or the locations of distributions, warehouses or offices, even in a blurred screenshot. Training content is copied, printed and forwarded far beyond its intended audience.

Data protection in humanitarian work also goes beyond names. The IASC’s Operational Guidance on Data Responsibility in Humanitarian Action, revised in 2023, addresses the safe, ethical and effective management of personal and non-personal data at all levels of the humanitarian system. For training design, the practical rule is simple: if a detail is not needed to teach the change, leave it out.

The same logic decides which procedures suit this format. Leave requests, timesheets, purchase approvals and document retention work well. Updates to beneficiary registration, protection and safeguarding, security procedures or staff movements need specialist channels and controls, not general training content.

A Hypothetical Example: A Leave Procedure Update in an Aleppo Office

The following example is hypothetical and is included only to illustrate the method.

An NGO programme office in Aleppo updates its leave request procedure, effective on the first day of next month. The HR focal point owns the procedure; the learning officer owns the training content. Their change analysis shows three differences: line manager approval now comes before HR review, the form has fields for handover arrangements and contact during leave, and requests move into the HR system.

The training content package contains a one-page Arabic change brief, a before-and-after table of the approval steps, a practice case in which a fictional finance assistant requests five days of leave that begin two days after the effective date, and a new job aid. Each item carries version 3.0, the approval date, and the effective date at the top. The transition rule states that requests submitted before the effective date follow the old route.

Three colleagues from two offices review the Arabic training content. They replace a formal term for ‘handover’ with the one staff already use, and agree on a single title for the HR focal point. The old form is marked as superseded and removed from the shared drive, and office focal points post the new job aid in their messaging groups. The HR focal point then checks the first month of requests for any that use the old route.

Summary

Procedure updates fail less often because of the rule than because of the version. Arabic training content for an update should start from what changed, show its owner, version, and effective date, include a transition rule, retire the superseded copy, and use terms that local teams have reviewed.

Keep every example free of beneficiary and operational data, and reserve this format for non-sensitive procedures. Designed this way, a small package of updated training content does more than a resent manual: staff know what changed, from when, and in which words.

Click here. If your team needs to turn procedure updates into clear Arabic training content, the SkillUp MENA team is available to discuss your corporate training requirements.