eLearning video built to be finished, not just uplaoded

AED 15,000 to AED 120,000 covers most of what we are asked to build. The number moves on how many modules and total runtime, whether scenarios need actors and locations, how many languages, and whether LMS packaging and knowledge checks are included. Anything quoted before those are known is a guess. We scope first, then price, and the scope document is yours whether or not you proceed. These are market ranges rather than a fixed rate card — the proposal carries the real figure.

Three to six minutes for most subjects, with a knowledge check after each. Anything past about ten minutes reliably loses people regardless of how good it is. If the material needs an hour, that is six to twelve modules rather than one long one, and the completion data will be dramatically better.

No, and we will say so. If a section is a presenter reading a policy, a well-written document is better because people can skim and search it. Video earns its cost when it shows something: a procedure, a conversation, a consequence, a piece of equipment in use.

That is how it should work. They know where people actually go wrong, which is the most valuable input into the structure. We interview them and write from that rather than asking them to produce scripts, because the constraint is always their time.

Yes, with native Arabic voice-over and subtitling rather than translation of an English recording. For safety and compliance content across a mixed UAE workforce we would usually push for more languages than a client initially budgets for, because the downside of misunderstanding is not a marketing problem.

Yes. SCORM and xAPI packaging, with the tracking configured and tested so completion and assessment data actually reaches your system. It is worth testing before launch, because tracking that silently fails is common and only discovered at reporting time.

Six to twelve weeks for a multi-module course. Structure and scripting typically take a third of that, and it is the part that determines whether the course works. Scenario filming with actors extends the schedule.

You re-record the affected module, which is the point of building it modularly. We plan for this at structure stage by isolating the content most likely to change, so an update is a day rather than a reshoot.

Knowledge check results per module, which tell you what was understood. Then the behavioural measure the training existed for: fewer incidents, fewer support tickets, faster onboarding. Completion rate is worth reporting and worth never treating as success.

Only if completion was genuinely voluntary. For mandatory training a high completion rate mostly measures how well people follow instructions. The questions that matter are whether they can answer a check afterwards and whether anything changed on the floor.

Sometimes, and it depends entirely on whether you have the source files and whether the structure is sound. If it is one long module, refreshing it usually means restructuring it, and we will be straight about that rather than patching something that will not work.