LMS Training Reports for Humanitarian Teams in Syria

Two days before a quarterly review, a programme manager asks the learning officer for ‘all the training data’. The export from the LMS software arrives as a spreadsheet with forty columns: full names, personal phone numbers, dates of birth, every quiz attempt and a folder of assignment uploads. Opening the folder, the learning officer finds that two colleagues had attached photos of real registration forms to show their work in a practice exercise.

Nobody intended any harm. The report simply had no design, so it carried everything the LMS software could export, including data that should never have entered LMS software at all. For NGO teams and teams implementing UN-funded programmes, where people’s safety can depend on how carefully information is handled, a report from LMS software needs the same discipline as any other data product.

This article shows how to design training reports from LMS software, the learning management system where staff complete their courses, around three ideas: a small set of completion indicators that answer real decisions, the minimum personal data needed to produce them, and firm rules that keep beneficiary data out of training records altogether. It is general guidance; your organization’s data protection policies and donor requirements always take precedence.

Start with the Decisions Your LMS Software Reports Must Support

‘All the data’ is not a reporting requirement. Before configuring anything in the LMS software, list who will read training reports and what each reader decides from them:

• An office manager decides who needs a reminder before a mandatory course deadline.

• HR decides whether new staff completed induction in the LMS software within their first weeks.

• A programme manager decides whether a team is ready to start using a revised procedure.

• Senior management or a donor-facing report needs an aggregated picture of mandatory training across offices.

Each decision needs a different level of detail. A manager needs names, but only for their own team. HR needs dates. A donor-facing summary needs no names at all. Design one short report per decision rather than one large export from the LMS software for everyone, and write down the purpose of each report next to its list of fields.

Then name an owner for each report, usually the learning officer, who maintains its field list and is the only person who changes it in the LMS software. Without an owner, extra columns creep back in each time someone asks for ‘just one more’ field.

Choosing Completion Indicators That Mean Something

It is tempting to report every measure the LMS software offers. A humanitarian team usually needs four or five, each defined in writing with its numerator, denominator, period, and source:

• Completion rate for each mandatory course: people who completed it divided by people assigned to it, by office and role category.

• Overdue count: assigned learners who have passed the deadline without completing.

• Induction on time: new staff who completed induction courses within an agreed number of days of their start date.

• Version coverage: people who completed the current version of a course after a procedure changed.

• Practical confirmation, where it exists: tasks confirmed by a supervisor, recorded separately from online completion in the LMS software.

Be honest about what these completion indicators show. Thalheimer’s Learning-Transfer Evaluation Model (LTEM) has eight tiers and states that its lower tiers represent methods that are inadequate to validate learning success. Completion recorded in LMS software tells you who was exposed to a course, not who can do the work. Label it as completion in every report, and keep the supervisor’s practical confirmation as a separate indicator rather than merging it into one ‘trained’ figure.

Minimum Data in LMS Software Training Reports

Once the indicators are defined, decide which personal data each one genuinely requires. The UN system’s Principles on Personal Data Protection and Privacy, written for UN System Organizations, include a principle of proportionality and necessity: processing of personal data should be relevant, limited, and adequate to what is necessary for the specified purposes. A separate retention principle adds that personal data should be retained only for the time necessary for those purposes. Even outside the UN system, it is a useful test for every column in a report.

Applied to training reports from LMS software, the minimum is usually:

• A staff number or other internal identifier instead of a full name, except in a manager’s own team view.

• Office and role category.

• Course, course version, status and completion date.

Phone numbers, dates of birth, nationality, home addresses and individual quiz answers do not belong in routine reports. If a documented requirement asks for a breakdown such as gender, report it in aggregate and only where groups are large enough. Agree how long detailed records stay in the LMS software and how long exported files may be kept, and delete old exports from shared drives and email.

Who can open each report is an access question as well; our article on access and user management in an Arabic LMS for NGOs in Syria covers the permissions side.

Where you can, let people view reports inside the LMS software, where access is controlled, rather than exporting spreadsheets that travel by email and messaging apps. When an export is unavoidable, remove unneeded columns before sharing, name the file with its purpose and date, and agree who deletes it and when.

Keeping Beneficiary Data Out of LMS Software

Staff training data is personal data, but it is not the most sensitive data a humanitarian team holds. The bigger risk is that beneficiary information enters LMS software through the side door and then appears in reports and exports. Check every route:

• Course content: exercises and screenshots loaded into the LMS software use fictional people, numbers, and places only.

• Assignment uploads: if a course does not need uploads, ask whether they can be switched off; if it does, tell learners exactly what not to upload.

• Free-text fields: comments, reflections and supervisor notes should never contain names, case details or locations of people being assisted.

• Course and group names: name groups by office and role, not by the community or site they serve.

Explain the reason to learners inside the course itself: a short note before every exercise that asks for an upload or a comment, saying that real names, photos of forms, and case details must never be entered into the LMS software.

Review a sample of uploads and free-text entries each quarter, and agree in advance what happens if real beneficiary data is found, following your organization’s data incident procedure. Prevention starts with the content itself; our guide to designing Arabic training content for humanitarian procedure updates explains how to build examples without beneficiary data.

Small Groups, Aggregated Reports and Export Tests

Removing names does not make a report anonymous. The Centre for Humanitarian Data notes in its guidance on statistical disclosure control that removing names and phone numbers is not always enough, because combining variables such as location can still allow re-identification of individuals. The guidance is written for survey data, but the same logic applies to training reports: ‘one overdue learner, finance role, small office’ points to one person.

Set a minimum group size for aggregated reports, for example five people, and merge small offices or role categories until each group reaches it. If your LMS software lets users filter a report by office, role, and course at the same time, check how small the resulting groups become. Then run export tests in the LMS software before relying on any report:

• Export each report and check every column against its agreed field list.

• Hide a field on screen and confirm it also disappears from the export.

• Check who receives scheduled reports by email, and remove anyone who no longer needs them.

• Confirm that a manager’s export contains only that manager’s team.

Checking whether the numbers themselves are right is a separate exercise; our guide to testing LMS completion reports covers it.

A Hypothetical Example: A Quarterly Report in Homs

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

A programme office in Homs uses LMS software for staff induction, finance procedures, IT basics, and a code of conduct course. Its quarterly training report used to be a full export from the LMS software. The learning officer replaces it with three reports: a team view for each manager with names and deadlines, an HR view of induction on time using staff numbers, and an office summary with completion rates for mandatory courses.

The office summary uses a minimum group size of five, so two small sub-offices are combined. Assignment uploads are switched off in the LMS software for every course that does not need them, and a review of existing uploads finds one photo containing a real form, which is deleted under the office’s incident procedure. Detailed records are kept for an agreed twelve months; the quarterly summaries are kept longer because they contain no names.

The new office summary fits on one page. Managers still see exactly who needs a reminder, and the programme manager finally has a figure everyone understands: completion of the current version, shown separately from supervisor-confirmed practice. When a donor-facing report asks how many staff were trained, the office sends the aggregated figure with its written definition, not a list of names.

Summary

Training reports from LMS software work best when they are designed, not exported. Start with the decisions each reader makes, define a few completion indicators honestly, and include only the personal data those indicators need, for only as long as they need it.

Keep beneficiary data out of content, uploads, free text, and group names, set a minimum group size for aggregated reports, and test every export from the LMS software before you rely on it. A shorter report is not a weaker report; in humanitarian work, it is usually the safer and more useful one.

Click here. If you are reviewing how your team reports training from LMS software, the SkillUp MENA team can discuss your Arabic LMS requirements with you.