ignite@fenixlearning.com0 Items
FenixFoodSafety

Regulatory Portal on IgniteLMS

We run the training.
You keep the oversight.

FenixFoodSafety delivers your jurisdiction's food handler training on IgniteLMS. Your department gets its own portal, where the fee ledger, the test data, the course content, and the support queue are open to inspection at any hour, down to the individual record.

Fees held in escrow. Transferred on your schedule.

If your jurisdiction charges its own permit or program fee, those fees sit in a Stripe account in your department's name, never in our operating account, and pay out automatically on the cadence you set: daily, weekly, biweekly, or monthly. Every payout carries a batch number, a payout ID, and a reconciliation CSV identical to the file emailed with it.

Fig. 01 · The fee ledgerThe four money states, awaiting payment through confirmed, are tracked fee by fee rather than rolled up, so this ledger answers the questions a finance office asks. Which fees made up this payout? The batch lists them. Did a given learner's fee come through? It is one row, with its state. The report your office assembles by hand at month-end is this screen's resting state.

See exactly where learners need more support.

When training is delegated, the exam is usually taken on trust: the provider reports a pass rate, and the department has no practical way to look behind it. The portal changes that. Per-question results show how many learners answered each item, how many got it right, and whether the item separates learners who know the material from those who don't, with weak items flagged and the reason spelled out.

Fig. 02 · Item analysis, liveThe two flagged questions show the two ways an exam item goes wrong. The first is ambiguous: strong and weak learners miss it alike, so the wording is the problem. The second is missed by nearly everyone yet separates learners well: the material was never taught clearly, so the lesson is the problem. Large testing programs run this same psychometric review of reliability, difficulty, and discrimination. Here it runs continuously, on your jurisdiction's own learners, in view of your program staff.

Review the content inside the content.

Curriculum review in this industry is usually either a document review of an exported copy or a seat in the course: a regulator takes the training like a learner, keeps notes somewhere else, and sends them to the provider when finished. The notes live apart from the content, the history fragments, and the audit trail is whatever someone kept. Here your staff read the live course itself, every lesson and exam item as a learner sees it, in any language you offer, and comment in place.

Fig. 03 · The review readerReview access is read-only: your staff see the same lessons, videos, and transcripts a learner sees, with each lesson's version and publication date in view, and no way to disturb live content. Comments stay attached to the lesson, so a concern raised in review keeps a paper trail through to its resolution. The completion figures beside each lesson show whether learners are getting through the material or stalling in it.

Watch us support your public.

When training is outsourced, support is usually where the public's experience goes dark: complaints reach your office secondhand, and anecdotes stand in for data. The portal reports the numbers a program manager watches: response and resolution times against 4-hour and 24-hour targets, satisfaction, ticket volumes by category, and how each trends. The individual tickets are there when an audit or a complaint calls for one, not because anyone expects your staff to work a queue.

Fig. 04 · The support queueThe targets are published, and every breach lands in the numbers you see. Met and breached are running totals, never a curated sample. Any ticket is visible with its clock, like the screen-reader issue open above. When a resident calls your office about the training, your staff can see what happened and where it stands, which turns "we'll look into it" into an answer.

Training in the languages your public speaks.

Each language is versioned course content in its own right, reviewed and approved before it reaches a learner. Your team can read any version in the same review reader shown above; the Spanish thread in that screen is what sign-off looks like. The whole program runs on a phone, and the support queue treats access issues as tickets with a clock.

Read it in

Fig. 05 · One lesson, both versionsThe toggle swaps the lesson between its English and Spanish versions. Each language is its own versioned document with its own approval stamp, translated down to the progress line, and the review reader in Fig. 03 reads either one.

The public sees your brand, not ours.

The program is yours; we just operate it, and the branding should say so. Your logo, name, and colors carry through the learner portal, which can run at its own branded address, so a resident who signs up through your health department never feels handed off to a vendor.

See it in your colors

Fig. 06 · The learner portalThe header, the monogram, and the actions all take the palette you pick above. Your production portal is configured once and holds.

It doesn't stop at the portal. Your logo and colors carry inside the course player too, and the course itself can open with your own welcome: a short message from your health officer or program lead, so the first thing a learner sees is your department rather than a vendor. From there, how far the content bends to your program is a conversation.

  1. Your branding

    Logo and colors on the portal and inside the course player. Self-service.

    Included

  2. Your welcome, up front

    A message from your health officer or program lead at the start of the course.

    Easy add

  3. Your rules, added

    Local amendments and jurisdiction-specific procedures as real lessons alongside the accredited core, per group.

    Larger programs

  4. Built to your spec

    Replaced lessons, your own imagery, course development against your code. A scoping conversation, not a checkbox.

    Let's scope it

Everything on this page is a setting.

The portal, the branding, the fee schedule, and the payout cadence are all configuration on a running platform, which is why standing up a jurisdiction is a scoping conversation rather than a software project.

  1. Scope

    Your rules, your fee, your payout cadence, your look. One working session.

  2. Configure

    We set up the portal, the fee escrow, and the branding, and you review it live.

  3. Launch

    Your site and offices point the public at one link. Oversight is on from day one.

We run the training so your team can run the program.

Course delivery, translation, testing, certificates, and public support, with your fees escrowed and your oversight built in. Let's talk about what your jurisdiction needs.

Request a walkthrough →

Talk to us

ignite@fenixlearning.com

fenixfoodsafety.com

Demonstration data for a fictional jurisdiction; names and amounts are invented.