A worker cannot enter the unit without a current H2S cert, and Moodle has no idea his fit test expired Tuesday

An orientation and cert-tracking core usually runs $35k to $55k, an LMS with clearance gating and mobile lands at $60k to $85k, and integration with HR and scheduling reaches $85k to $130k. Budget 15 to 20 percent of build cost yearly for support and content updates.

Because they track course completion, not plant-entry clearance. A worker can finish every course and still be barred at the gate because a fit test lapsed, and a generic LMS does not model that. Most contractors end up running a side spreadsheet next to it, which is the gap a custom LMS closes.

Yes, that is the core feature. The system knows which orientations and certs each plant requires and flags who is cleared to enter today, so a lapsed H2S or confined-space cert is caught before the gate, not at it.

Yes. H2S, confined-space, respirator fit, and site orientations are tracked with expiry dates, and the system warns before they lapse, which is what keeps a worker from being idled or an uncleared one from slipping through.

Yes. Reciprocal and site-specific orientations are modeled so a worker's cross-plant training status is clear, which a generic course-based LMS cannot represent well. This matters when crews move between Ship Channel facilities.

Yes. Mobile access lets a ramp-up crew complete required training and orientations before the turnaround starts, so clearance is ready at badging rather than becoming a bottleneck on day one.

Yes. Cleared status flows into your HR and onboarding, scheduling, and dispatch, so training, assignment, and gate access all agree on who can work.

Yes. You own the source code and your training content, so your orientations, certs, and records stay yours and portable. Put ownership and content-export rights in the contract.

If your training is generic courses with no plant-entry gating, an off-the-shelf LMS is cheaper and fine. The custom case is strong when training decides clearance, you track expiry in a spreadsheet, and ramp-ups demand fast orientation of large crews.

By designing the reporting layer first: every assignment, completion, score, and course version is stored as a point-in-time record an auditor can trust. The question audits actually ask is to show everyone certified on version 3 of a course as of March 1, and a flat completed-yes-or-no schema cannot answer it. Retrofitting that history into an LMS that never captured it is one of the most expensive fixes in this category, so name your regulator and your audit format during discovery.

Ask to speak with two past clients whose projects resemble yours in size and industry, and ask exactly who will write your code, since some agencies sell senior faces and deliver junior or subcontracted hands. Demand a written specification with acceptance criteria before any fixed price, and check that their portfolio links to products that are actually live. An instant quote given without questions about your workflows is the clearest warning sign there is.

Four repeat offenders: deciding on SCORM or xAPI after the database schema is frozen, testing with 20 users and launching to 2,000, treating reporting as a final-sprint feature, and having no answer for who authors courses after launch. The most expensive is the first, because a content-standard retrofit means rebuilding the course runtime and migrating everything already published. All four are week-one decisions, which is why a paid discovery phase is worth it.

Choosing the lowest bid, paying more than 30-40% upfront instead of on milestones, skipping a written specification, and having no maintenance plan for after launch. The most expensive of the four in Digital Heroes rescue projects is the missing spec: without written acceptance criteria, done becomes an argument instead of a checklist, and every disagreement resolves in the vendor's favor. Fix those four and you have avoided most of the ways these projects fail.

A boring, hireable one: React or Next.js on the front end, Node.js or Python on the back end, PostgreSQL for data, and a managed video service like Mux or Cloudflare Stream instead of self-hosted video. The stack matters far less than the enrollment data model and the SCORM/xAPI runtime, which is where LMS builds actually succeed or fail. The red flag is an exotic stack chosen for the agency's own interest that nobody in your market can maintain.

Four to five people is the working team size on Digital Heroes LMS builds: a project lead, a designer, two engineers, and QA, with part-time DevOps. Bigger teams do not ship an LMS faster, because the schedule is governed by decisions about roles, content standards, and reporting rather than typing speed. Be suspicious of a ten-person quote for a mid-size build, and equally suspicious of one person promising the whole thing.

Digital Heroes builds custom LMS software systems for operators who have outgrown the off-the-shelf tools in their category. The work is delivered remotely: our engineers work from Delhi and Lucknow, leadership is in New York, and some team members live in London and Sydney and work remotely from there. We have no office in Pasadena. You can chat with the team directly, and every form gets an email reply within 24 hours.