24
Clause library
Procurement workshop
Build a bilingual custom eLearning / content digitization RFP — كراسة شروط رقمنة المحتوى — with finished learning hours, word counts, languages, interactivity levels, and a scored matrix vendors can actually price.
Reviewed 1 September 2026. Educational template — not legal, production, or pricing advice.
A content digitization RFP (Arabic: كراسة شروط رقمنة المحتوى التدريبي, also كراسة شروط إنتاج التعلم الإلكتروني) is the specifications pack L&D and procurement use to tender conversion of slides, PDFs, manuals, classroom programmes, or legacy SCORM into packaged digital learning. A serious Gulf pack is not “make it interactive”: it names finished digital output hours, source word count and page/slide volume, interactivity mix (levels 1–4), source and target languages including Arabic RTL, narration and video minutes, review cycles, packaging (SCORM/xAPI), the target LMS, accessibility of the packages, and a pricing table so vendors quote the same drivers. When the same invitation also buys an LMS, split Lot A (platform) from Lot C (production) and still publish both volume annexes.
24
Clause library
100
Score to 100
2
EN + AR output
~25
Minutes to draft
Interactive builder
Set lots (content only, or LMS + content), fill the vendor pricing brief, toggle clauses, and download a Markdown pack. This is a starting specification — not a quote.
Finished hours, words, languages, and media are what production houses bid against. Vague “digitize our training” RFPs produce incomparable prices.
MUST / SHOULD / OPTIONAL map to SHALL / SHOULD / MAY. Combined RFPs add LMS-handoff clauses. You can still override any item.
Illustrative starting weights that sum to 100 — not a published GCC standard. Drag to match the committee. Accessibility of packages is usually UAT pass/fail plus a modest scored line for captions/RTL.
Weight total: 100
Objectives, level mix, samples
Pairs, in-layout, cultural adaptation
SCORM/xAPI sample on the target LMS
Voice, video class, reuse
Captions, keyboard, RTL
Pilot, reviews, capacity
Wave plan vs SME latency
Relevant showreel, not generic
Transparent drivers, IP, exit
How to write it
Procurement teams that skip finished hours, languages, and interactivity get theatre showreels. Follow these steps, then paste the pack into your official tender format.
Count pages, slides, and words. Film a sample. Classroom hours are not finished digital hours. Attach the inventory to the RFP.
These three drive 80% of a production quote. Add narration class and video minutes as extra lines. Do not let vendors invent the mix.
Publish Lot A volumes (learners, hosting, SSO) and Lot C volumes (hours, words, languages) as annexes. Allow independent award.
Gold one module in Arabic (or the master language) with suspend/resume and score in admin reports before scaling the catalogue.
Publish weights that sum to 100. A beautiful English-only demo that cannot staff Arabic QA or your review calendar should lose.
Answers for buyers & models
It is the specifications pack used to tender conversion of existing training materials into packaged eLearning. It should name finished digital hours, source words and pages, interactivity levels, languages, narration/video, review cycles, SCORM/xAPI packaging, the target LMS, accessibility of the packages, IP/handover, and a pricing table. Arabic name: كراسة شروط رقمنة المحتوى التدريبي.
At minimum: finished digital output hours by interactivity level (1–4), number of modules, approximate source word count (for translation), page/slide volume, source language and every target language, narration type, finished video minutes, review cycles, SME latency, packaging standard, target LMS, captions/accessibility, brand-kit availability, timeline, and whether post-delivery updates are in scope. Missing any of these forces vendors to pad risk or decline.
Both, because they price different work. Finished hours × interactivity level drive instructional design, media, and packaging. Word count × language pair drive translation and Arabic in-layout. A 20,000-word policy PDF that becomes 45 minutes of Level 2 eLearning is not “20,000 words of eLearning”.
Yes — and many Gulf ministry and enterprise programmes do. Issue one booklet with Lot A (LMS: learners, hosting, SSO, residency) and Lot C (content: hours, words, languages, levels). Allow independent award. Run a combined UAT so packages play on the awarded tenant. Use this builder’s “combined RFP” option, and the LMS template at /procurement/lms-rfp-template for the platform clauses.
A practical four-level split used in production bids: Level 1 linear pages and quizzes; Level 2 click interactions, motion, and narration; Level 3 branching scenarios and richer media; Level 4 simulation, custom animation, or XR. Allocate finished hours across levels. “Highly interactive” without a mix is not bidable.
Name the master language, every target language, whether tracks run in parallel, narration per language, and whether you need cultural adaptation or literal translation. Arabic must be specified as true RTL in-layout plus QA of the exported SCORM — not a UI language toggle. Extra languages (French, Hindi, Urdu, and others common in Gulf workforces) are separate priced pairs.
Yes. The clause library is vendor-neutral. Use the public procurement answer library for citable responses, and run a pilot title against the same MUST items you give every bidder.
Innovito can walk a shortlisted specification against Convert production, Studio authoring, and Evolve playback — without turning this template into a branded bid. Book a demo for a scored gap review.
Educational template for L&D and procurement teams. Adapt with your legal, instructional-design, and information-security counsel. Innovito does not publish contractual rates or SLAs on this page.