Employee training: governance and reporting before content

At the end of the quarter the quality manager asked for something simple: a list of everyone who completed the information security program, with dates. The training unit had a folder of videos, a group chat where the link was shared, an attendance sheet from one session, and an old message saying everyone had watched it. The training had genuinely happened. What was asked for was not the training but the record.

That gap is what makes choosing an employee training platform a different decision from choosing somewhere to host video. Content is the easy part. The hard part is three questions that always arrive late: who is entitled and why, who may change the material, and where the evidence sits when somebody asks six months from now. Settle those first and content becomes a matter of time. Start with content and a year later you have an archive with no record.

The reason is that internal training inverts the assumptions a public storefront is built on. A platform designed to sell courses assumes the learner picks themselves, that payment proves entitlement, and that appearing in the catalogue is the goal. Inside an organisation all three flip:

• The participant is designated in advance and does not buy, so entitlement is an administrative decision, not a transaction.
• Some material should never appear in a public catalogue, now or a year from now.
• Editing the material belongs to a known owner, not to everyone who knows the password.
• A report is requested after the program ends, so "the training ran" is not an answer.

So the first question when evaluating a platform is not the player or the page design. It is the rules around the material. Everybody likes the player during the demo; the review committee asks about the rules.

Entitlement first: who reaches what

In the organisational setup in Dwrrah, access is an entitlement you grant, not a link you circulate. You invite people by email and grant them their material, and the program stays out of the public catalogue while everyone granted access keeps working normally. The content sits in private storage that opens only for entitled accounts, through short lived signed links. Pro adds grants and invitations, limited free access for named people, and invite only coupons that work for nobody but the recipient.

But the biggest benefit of entitlement is not security. It is arithmetic. The list of people covered by the program is the denominator of every percentage you will later report. Without a list of who was supposed to be trained, a completion rate means nothing: seventy out of a hundred is a different story from seventy out of three hundred. Organisations that stumble at the report rarely stumbled at measurement. They stumbled at defining who was in scope.

That list is not a file you write once, either. New hires arrive, people transfer out, and a change of job description can move somebody from one program to another. When granting access is a real action with a named owner, all that movement becomes a one minute edit instead of an end of year investigation into why a name was on the list, or was not.

Authority: who is allowed to change the material

A shared login deletes the question "who did this", because the answer is always "everyone". In internal training that is not curiosity: a safety or compliance module has an approved version, and who changed it and when is part of the approval itself.

Five scoped roles solve this with boundaries of work rather than levels of trust. The owner holds everything. The manager runs the operation broadly and holds data export and ownership transfer. The course editor works across your content but sees no analytics, no money and no learner personal data. The landing page editor owns branding and pages only. The trainer is limited to the rows assigned to them. Roles, email invitations and ownership transfer are on every plan, and the activity log that records what changed and who changed it comes with Pro.

The operational effect is simple: the day someone moves out of the unit you withdraw their role in a minute, instead of resetting a password six people share and briefing them all again. Governance is not a document written once; it is a procedure that repeats every month. The second gain is delegating without anxiety, since whoever designs your pages never sees staff data and whoever edits content never sees your figures.

Evidence: what survives six months

Progress is recorded for each participant as they watch, so you never have to ask where they got to. Quizzes and assignments give measurement instead of impressions, and each one has a report showing who was entitled, who started, who passed and who needs a retake. A completion certificate with a verification link is issued in your identity once the rule you set is met. It is a page you share and print from the browser rather than a stored file, so anyone checking it reads the source itself. For a session or a program the certificate needs recorded attendance: a booking is not enough. Certificates are on Premium.

Aggregate numbers live in the analytics dashboard: a free dashboard on every plan alongside wallet, sales and email reports, content performance and the activity log on Pro, and CSV or JSON export on every plan so the figures join your internal reporting in the format management expects. The content view log is kept append only for teams that need traceability.

A practical way to evaluate a platform: write down the questions you will be asked after the program ends, then ask where each answer lives.

The question asked later	Where the answer lives	Note
Who was in scope at all?	Grants and invitations record	Entitlement precedes reporting
Who opened the material, and when?	The content view log	Append only
Who finished, and with what result?	The quiz or assignment report	Entitled, started, passed, needs retake
Who actually attended the session?	Attendance recorded in the meeting	A booking is not attendance
What do we hand to whoever asked?	A certificate with a verification link	Premium plan
Who changed the material, and when?	The activity log	Pro plan
How do the numbers reach our report?	CSV or JSON export	Every plan

An environment with your name on it, and a line into your systems

Participants land somewhere they recognise: your logo, your colours, and pages explaining the programs and the policies. On Pro you connect your own domain and hide the Dwrrah attribution, so nobody sees an intermediary platform between them and their employer. This is not a matter of taste: training that looks external gets treated like an advert; training that looks internal gets treated like an obligation.

For teams that need a real integration, connecting to your systems climbs with the plan. Google Calendar, WhatsApp notifications through an external provider on your own token, and the tracking tools you already run all start on Pro. The REST API, signed webhooks and the MCP server sit on Premium. Teams without a live integration stay with periodic export, which covers most first year cases, so do not buy an integration before you have proved that export falls short.

What the platform will not do, plainly

A decision reversed after six months costs far more than a no said today. These are the limits worth knowing before the signature, not after.

• It will not write your training policy. Who must be trained, how often, and what counts as passing are your decisions. The platform enforces the rule; it does not invent it.
• There is no ready made HR system connector. The API and webhooks hand you the events; the integration itself is built by your technical team or whoever you appoint.
• Live sessions run inside the platform. The room opens in the browser with nothing to install, and there is no bridge to an outside meeting tool, so if your organisation is committed to a particular one, know that on day one.
• There is no DRM and nothing prevents screen recording. Content protection is a set of layers that raise the cost of leaking: private storage, short lived links, a watermark carrying the viewer's identity, and a view log. Anyone filming their screen walks away with a copy, and the most a platform can do is make that copy attributable.
• A certificate proves your own rule was met. It is not accreditation from a regulator and not a verdict on competence.
• Reports reflect what happened inside the platform. An in person workshop whose attendance was never recorded here appears in no export.
• There is no single hub that gathers every report. The numbers live where the work happens: a report per quiz and assignment, a general dashboard, and an export you build your report on.

Four mistakes that keep repeating, and the order that avoids them

First: starting with content before the list. Twenty videos uploaded before anyone knows who the program covers means duplicated work, because grouping and grants get rebuilt anyway.

Second: one account passed around the team. It feels faster in week one, then costs you at the first review: the activity log can only say what the account says, that one person did everything.

Third: measuring attendance instead of completion. A signature on a sheet is not learning, a booking is not attendance, and watching is not understanding. Make the rule compound: recorded progress, a quiz result, and real attendance where it matters.

Fourth: leaving the export question until report day. Run an export in week one on a small set of data and check the columns you receive are the columns your report needs. A missing field found now is an adjustment; found the night before submission it is a crisis.

The order that avoids all four is short:

1. Write the list of people the program covers, and name who decides who joins and leaves.
2. Assign roles before uploading any material, and decide who owns the approved version.
3. Define the completion rule and the required evidence for each program, before the design rather than after.
4. Upload one real program and walk it end to end from a participant account: invitation, certificate, export.

Step four alone reveals more than any demo, and you can run it during the free trial: fourteen days, no card, with Pro features. What usually decides it for an organisation is the custom domain and activity log on Pro, with certificates and the API on Premium, and the pricing page shows what each plan carries today.

If you need a specific arrangement around roles, payment or participant numbers, start with a conversation from the contact page rather than a quick signup. No two organisations ask for the same thing, and a conversation is cheaper than a decision you redo.