Subscribe to Our Newsletter
Get the latest updates delivered straight to your inbox.
Turning NGO Manuals into Practical eLearning Tasks in SyriaPicture a new finance assistant joining an NGO office in Damascus. On her first day, she receives a link to a shared folder holding the finance manual, the procurement manual and the HR policy, close to 200 pages in all, with a short note: ‘Please read these before you start.’ She signs a form confirming she has read them. Three weeks later, her first petty cash reconciliation comes back from the finance officer with four corrections, each one explained clearly in the manual.
The manual was not wrong, and the assistant was not careless. A manual is a reference document. It is written to be complete and correct, not to help someone practice a task. For NGO teams and teams implementing UN-funded programmes in Syria, which often onboard staff across several offices and revise procedures as programme requirements change, the gap between reading and doing shows up as rework, delayed approvals and questions that land on the same few experienced colleagues.
This article shows how to turn one section of a work manual into a practical eLearning task: choose a non-sensitive administrative task, rebuild it as a short scenario with feedback, provide a full text alternative and have it reviewed locally before release. It is general guidance. Your organization’s own policies, manual owners, and donor requirements always take precedence.
Why Uploading the Manual Is Not eLearningMany organizations take their first step toward eLearning by placing manuals on an eLearning platform or shared drive and asking staff to confirm they have read them. That creates a record of access, but it changes little. The employee still has to translate pages of rules into decisions on a real form, usually alone and under time pressure.
Practical eLearning reverses the order. The task comes first, and the manual becomes the reference the employee uses to complete it. Instead of reading eight pages about petty cash, the employee reconciles a petty cash float using fictional receipts, decides which receipts are acceptable, and receives feedback that points to the relevant clause of the manual.
That feedback is where much of the value of practical eLearning lies. In their review in Review of Educational Research, Hattie and Timperley describe feedback as one of the most powerful influences on learning and achievement, and note that its effect can be positive or negative depending on its type and how it is given. A message such as ‘Receipt 3 cannot be accepted because it has no date; see section 4.2’ teaches the rule in context. ‘Incorrect’ teaches nothing.
Step 1: Choose a Non-Sensitive Administrative TaskChoose the first eLearning task carefully. It should be frequent, rule-based, and easy to get wrong, and it must be safe to practice with entirely fictional information. Good candidates from typical NGO administrative manuals include:
If you are not sure which tasks cause the most rework, start by identifying learning and development needs across your teams, then pick one task from the top of that list for your first eLearning pilot.
Leave sensitive areas out of this format entirely. Do not build general eLearning tasks around beneficiary registration or case data, protection or safeguarding cases, security procedures, staff or vehicle movements, the locations of offices, warehouses or distribution points, partner vetting or incident reports. These subjects need specialist training channels and controls that a general eLearning library is not designed to provide.
The reason is practical as well as ethical. eLearning material tends to travel: it is downloaded to personal phones, forwarded in messaging groups and reused long after a course ends. The ICRC’s Handbook on Data Protection in Humanitarian Action states that protecting individuals’ personal data is an integral part of protecting their life, integrity and dignity. An administrative task built on fictional data avoids that risk altogether.
Step 2: Rebuild the Manual Section as a TaskSit down with the manual owner, usually the finance, logistics, or HR focal point, and break the chosen section into five elements:
Then build the eLearning task around the decisions. Give the employee a realistic case with fictional documents, ask them to make each decision or complete the output, show feedback linked to the specific manual clause, and allow a second attempt. Keep one task to about 10 to 15 minutes. If the manual section covers more, split it into several short tasks rather than one long eLearning module.
Record the manual version number inside each task. When a procedure is revised, the manual owner then knows exactly which eLearning tasks need updating. For more on updating Arabic training content when work instructions change, see our related guide.
Step 3: Provide a Text Alternative from the StartA practical eLearning task often relies on images: a scanned receipt, a screenshot of a form or a flowchart of approvals. Each needs a text alternative. Success Criterion 1.1.1 of the W3C’s Web Content Accessibility Guidelines (WCAG) 2.2 requires that non-text content presented to the user has a text alternative that serves the equivalent purpose, so that it can, for example, be read aloud by a screen reader or presented in braille. For complex images such as an approval flowchart, the guidance notes that a short description may not be enough and a longer description is needed.
For NGO teams, a second kind of text alternative is just as useful: a complete text version of the eLearning task. This is a simple document with the same case, the same documents described in words or in a table, the same questions and the feedback written out on a separate page. Colleagues can then complete the task on a basic phone, on paper, during a power cut or over a weak connection, and supervisors can work through it in a team meeting.
The text version must keep the same decisions. If the interactive eLearning task asks the employee to judge each receipt, the text version must ask the same thing, not simply summarize the rule. Otherwise, colleagues who rely on it receive a weaker form of employee learning than everyone else.
Step 4: Review the eLearning Task Locally Before ReleaseAn eLearning task written by a regional or headquarters team can look correct and still fail in a local office. Before release, ask three people to review it:
Finish with a sensitivity check. Confirm that the eLearning content contains no real names of people, organizations, suppliers, donors, or places, no amounts that could identify an actual transaction, and no fictional details that happen to match real ones.
A Hypothetical Example: Petty Cash in a Damascus OfficeThe following example is hypothetical and is included only to show how the method works.
An NGO programme office in Damascus notices that petty cash reconciliations are often returned for correction. The finance manual covers the process in eight pages. The HR and finance focal points agree to turn that section into a practical eLearning task.
The eLearning task gives the employee a fictional petty cash float, eight receipts and a cash count. The employee decides which receipts are acceptable, flags one without a date and one above the single-purchase limit set in the manual, completes the reconciliation and prepares the replenishment request. Each decision has feedback quoting the relevant clause, and the employee can try again.
The text version is a two-page document listing the same receipts in a table, with the same questions and an answer page. During local review, a finance assistant points out that many small shops issue handwritten receipts, so the team adds two handwritten-style receipts, described in words in the text version. The language reviewer replaces a literal translation of ‘float’ with the term the office already uses.
After release, the finance officer tracks two things: which feedback messages appear most often in the eLearning task, and whether real reconciliations come back with fewer corrections. Neither needs a sophisticated eLearning platform. A short monthly note is enough to decide whether to build the next task.
SummaryA manual tells staff what the rules are. A practical eLearning task lets them apply those rules safely before they meet a real case. For NGO teams in Syria, the safest and most useful starting point is a frequent, non-sensitive administrative task, rebuilt as a short scenario with feedback, supported by a full text alternative and checked by the people who do the work locally.
Start with one manual section, see whether real work improves after the eLearning, and expand from there. If you also need to reach volunteers with very limited time and devices, the design constraints change; see our guide to lightweight eLearning for volunteer training.
Click here. If you are planning to turn one of your work manuals into practical eLearning tasks, the SkillUp MENA team can talk through scope and requirements with you.




