New-hire onboarding
Define the day-one basics, role expectations, app access, training tasks, practice screens, and readiness check a new hire needs before independent use.
Training
Train the team around the apps they actually use.
HospiEdge training planning follows shared identity and restaurant context, server-approved role and location access, application-owned records, local service authority, and approved online paths. Each enabled workflow needs a named audience, practice plan, readiness check, and support owner.
Rolebased paths
Appspecific refreshers
Writtentraining scope
Four training lanes
Teach the right workflow to the right person.
Training should not make a host learn finance screens or a line cook learn checkout setup. HospiEdge training follows the person, role, app access, and restaurant location.
Manager operating rhythm
Schedules, approvals, guest flow, incidents, standards, closeout review, labor, reports, and source-reviewed AI findings where eligible.
App-specific refreshers
Short practical walkthroughs for Schedule and its hiring path, HETable, POS, Ops, Finance, Labels, Marketing, and the optional Master AI review layer.
Local plus online setup
Who works from the restaurant, who can use approved online access, which routes they use, which records each app owns, and how readiness is verified.
Training by workflow
Each authorized workflow needs a practical learning path.
A restaurant can train one focused package first. The Schedule package includes Jobs, Finance, and Ops; every added workflow still needs the right role, access, practice, readiness, and support review.
Hiring + workforce
Hospi Jobs
Best when hiring follow-up is scattered across job boards, email, and texts—and the accepted candidate still has to be typed into the workforce system again.
12 highlighted functions- Branded public careers pages
- Location-specific job posts
- Mobile-friendly applications
- Candidate profile and activity history
HE Schedule
Best when managers are rebuilding the schedule from texts and spreadsheets, labor surprises arrive too late, or punch cleanup makes every payroll harder than it should be.
12 highlighted functions- Weekly schedule builder
- AI-assisted starting point with manager review
- Role, station, and coverage targets
- Availability and time-off requests
HETable
Best when reservations, walk-ins, table status, server sections, guest messages, and assistance requests need to stay together at the host stand instead of being managed across paper, memory, and separate links.
12 highlighted functions- Public reservations
- Waitlist capture
- Live host stand board
- Drag-and-drop floor map
HE POS
Best when a restaurant needs one accountable path from order entry to production, payment, server checkout, manager cashout, and end-of-day recovery instead of disconnected service and closing tools.
12 highlighted functions- Table-service ticket flow
- Quick-service register flow
- Menu, modifier, and 86 control
- KDS, expo, and bar routing
HE Ops
Best when the schedule exists but execution still depends on memory, group texts, paper checklists, and an owner asking every manager what happened.
12 highlighted functions- Daily manager desk
- Opening and closing checklists
- Line checks and culinary audits
- Custom audit forms
HE Finance
Best when closeout numbers live in different systems, managers cannot explain a variance, or the accountant spends more time rebuilding the day than reviewing it.
12 highlighted functions- Daily sales review
- Tender and cash reconciliation
- Tip and checkout review
- Labor and payroll context
HE Label AI
Best when labels are handwritten, templates drift between stations, or the restaurant needs a controlled print workflow configured for its actual devices.
12 highlighted functions- Reviewed AI-assisted item import
- Controlled prep label templates
- Date and shelf-life rule support
- Allergen label template support
HE Marketing
Best for an operator who knows the restaurant but not marketing—and needs a guided, repeatable way to bring guests back without handing the relationship to another platform.
12 highlighted functions- Guest contact database
- CSV contact import
- Tags, segments, and opt-in flags
- Email campaigns
HE Master AI
Best for an existing HospiEdge customer who needs cross-workflow answers and follow-through—not a generic chatbot and not a replacement for the apps that own the records.
12 highlighted functions- Cross-app leadership review
- Source readiness checks
- Live findings
- Daily and weekly recaps
Role-based training plan
Different users need practice and readiness checks for their roles.
The training plan should identify only the workflows, routes, and records allowed for each role, restaurant, and location, then define how the user demonstrates readiness.
Training during rollout
Confirm what is taught, practiced, accepted, and supported before go-live.
Confirm the roles, authorized apps, login paths, locations, workflows, materials, trainer, and readiness criteria included in the accepted plan.
Identify the screens and safe practice data each user will use, then record corrections before production access is accepted.
If first-shift support is included, confirm its availability window, contact route, escalation owner, rollback boundary, and response responsibility in writing.
Assign follow-up items and refresher ownership, then create a new training and readiness scope before another app or role is added.
Training resources
Use the right page for the right kind of learning.
App walkthroughsScreen-by-screen HospiEdge guides for managers evaluating or learning an enabled workflow.
Operator guidesPublic articles that explain software categories and operating workflows.
Rollout planLaunch sequence, access model, routes, app provisioning, and data setup.
Support routingWhere to go for account, billing, training, rollout, and app-specific help.
Why explicit training scope matters
Train and confirm each workflow before the team uses it in service.
- Training uses the same identity direction and approved restaurant context while keeping application records and permissions distinct.
- Focused-package customers can train the workflows included in the package they launch first.
- Managers practice only the online workflows approved for their role, restaurant, and location.
- Service teams practice the accepted local-authority workflows they use during the shift.
- Expansion requires a new training, access, data, provider, and readiness review.
- Support requests identify the app, route, role, safe account reference, expected result, and observed result.