Built for corporate training and language academies that deliver sessions to client teams: group scheduling, teacher availability, verified session attendance, contract consumption and funding compliance.
98%
Sessions verified at delivery
Teacher and learner confirmation captured at the session rather than reconstructed at month end.
3x
Faster client reporting
Delivery reports per client and per group generated from the same records used for payouts.
Zero
Contract overdelivery surprises
Hours consumed against contracted hours visible live, with alerts before a contract runs dry.
1 hour
To assemble a funding audit pack
Attendance signatures, session records and learner rolls exported per programme in one action.
The reality on the ground
Every conversation with a people team in this sector surfaces the same handful of failures. Here is what they look like and what they cost.
Teacher availability, client preferences, room capacity, platform links and level matching all sit with a single coordinator and a colour coded spreadsheet. When that person takes a week off, rescheduling stops. When a teacher cancels at short notice, finding a qualified replacement is a series of phone calls.
Cost of leaving it: Cancelled sessions, unhappy clients and a coordinator who cannot take leave.
A session was scheduled for Tuesday at a client office. Did it run? Did four learners attend or one? Was it delivered onsite or moved online? The answer arrives days later, usually from the teacher's memory, and it is the basis for both client billing and teacher payment.
Cost of leaving it: Billing disputes with clients and payment disputes with teachers, every single month.
A client buys a block of hours. Delivery happens across several groups over several months. Nobody sees the burn rate until either the contract is exhausted mid programme or hours expire unused at renewal time.
Cost of leaving it: Unbilled overdelivery on one account and lost renewal value on another.
Subsidised and funded programmes require verifiable learner attendance, signed rolls and session evidence. Collecting that from teachers across dozens of client sites, then keeping it for the retention period, is a manual archive problem.
Cost of leaving it: Rejected funding claims and clawbacks after the programme has already been delivered.
Capability deep dive
Same platform, sector specific defaults. Each capability below arrives preconfigured, so your team edits rather than builds.
A day in the life
Software only sticks when the person using it saves time on their own work. These are the three roles that make or break adoption here.
The person who currently owns the scheduling spreadsheet.
8:30 am
Reviews today's sessions and sees one teacher marked unavailable overnight.
8:45 am
Filters qualified teachers by level, language and availability, and assigns a replacement.
11:00 am
Generates the next term of sessions for three new groups from a recurring pattern.
4:00 pm
Checks which sessions from yesterday are still unverified and nudges two teachers.
Wants a clear schedule and to be paid correctly for what was delivered.
Week start
Sees the full week of sessions with client, site, level and joining link in one list.
Session start
Checks in, marks which learners attended and records the modality actually used.
Session end
Adds a short progress note that the account manager can see.
Month end
Reviews the payout sheet built from verified sessions before it is approved.
Owns the client relationship and the contract value.
Weekly
Reviews contract consumption across accounts and flags two nearing exhaustion.
Client call
Shares a delivery report showing sessions held, attendance rates and progress notes.
Mid term
Requests an extra group for a client and sees feasibility against teacher capacity immediately.
Renewal
Opens a full delivery history for the account to support the renewal conversation.
Compliance and audit
Verified attendance records
Learner presence per session captured at delivery with the responsible teacher recorded.
Session and modality log
Planned against delivered session records including reschedules, cancellations and reason codes.
Learner enrolment rolls
Enrolment, level and completion status per programme, exportable per funding claim.
Teacher qualification records
Certifications, language levels and teaching credentials stored with expiry tracking.
Contract documentation
Signed contracts, contracted volume, rate cards and amendments held against each client.
Retention and data handling
Records retained for the period your funding body requires, with role limited access to learner data.
End to end workflow
One record per person, from the day they join to the day they leave. No spreadsheet handoffs in between.
Stage 1
Contract
Client, sites, contacted volume, rates and validity period recorded with the signed document attached.
Stage 2
Group setup
Groups created with level, modality, learner enrolment and a recurring session pattern.
Stage 3
Assignment
Teachers matched by level, language, availability and travel radius, then confirmed.
Stage 4
Delivery
Sessions delivered and verified with learner attendance and modality recorded live.
Stage 5
Billing and payout
Client invoice and teacher payout generated from the same verified delivery records.
Stage 6
Closeout
Delivery report, completion status and audit pack produced for the client and any funding body.
Integrations and hardware
No rip and replace. HRMione sits alongside the systems and devices already on your floor.
Delivery platforms
Commercial systems
Communication
Rollout plan
A dedicated onboarding lead runs this with you. Nothing here needs your engineering team.
Week one
Clients and teachers
Client list, contracts, teacher roster, qualifications and availability loaded.
Week two
Groups and schedule
Active groups recreated with recurring patterns and the current term generated.
Week four
Verified delivery live
Teachers verifying sessions in the platform, first payout sheet produced from real delivery.
Day ninety
Reporting and audit
Client delivery reports, utilisation reporting and a funding audit pack validated end to end.
Commercial fit
Most providers start with clients, teachers and the current term schedule, then switch payouts to verified delivery from the following month.
Typical headcount
Providers with 10 to 400 teachers, delivering to corporate clients across onsite, online and hybrid formats.
Indicative spend
Priced per active teacher and staff member per month, billed annually. Learners and client contacts are not charged as seats.
Modules in the standard bundle
Case study
Situation
Scheduling ran on a spreadsheet owned by one coordinator. Session confirmation arrived by message after the fact, so client billing and teacher payouts were both reconstructed at month end. Funded programmes required a manual archive of signed rolls.
What we did
Teacher availability, client contracts and recurring group patterns moved into HRMione. Teachers began verifying sessions at delivery with learner attendance and modality, and payouts were generated from those records.
Result
We used to rebuild the month at the end of the month. Now delivery records itself and both the client report and the teacher payout come from the same place.
Straight answers
Our delivery mixes onsite, online and hybrid. Can one system handle all three?
Yes. Modality is a property of the session, not of the group, so a group scheduled onsite can be delivered online for one week and the record reflects what actually happened. Payout rates can differ by modality.
Teachers are freelancers, not employees. Does that work?
Yes. Teachers can be engaged on rate cards rather than salaries, with payouts generated from verified sessions. Employed staff and freelance teachers coexist in the same workspace with different payment treatment.
Will teachers actually verify every session?
Verification is two taps inside the session they already opened for the joining link, and the payout sheet is built from it. Because payment follows verification, compliance climbs quickly without policing.
What if a client changes the schedule constantly?
Reschedules and cancellations are first class actions with reason codes attached to the client, the teacher or the provider. That means the delivery report shows who caused each change, which is usually the conversation you need.
Can we report per client, per group and per learner?
Yes. Delivery, attendance and progress notes roll up from learner to group to client, so an account review and a funding claim both draw on the same underlying records.
Software Solutions
FAQ
Keep exploring
Thirty minutes, your own scenarios, a live sandbox already loaded with a workforce that looks like yours.
We use necessary cookies to run the site. With your consent, we also use analytics and marketing cookies to improve the product. Read our Privacy Policy.
