VisitorTraining: Enterprise Visitor Compliance Management

Visitor compliance starts before arrival.
An enterprise visit involves more than a name at reception. A host needs to confirm the purpose, area owners need to authorize access, compliance and training teams need to assign the required learning, and gate staff need to verify that each person meets the conditions for entry.
VisitorTraining brings visitor appointments, business and area approvals, compliance training, assessment results, and entry and exit records into one connected workflow. Enterprises can apply configured visitor requirements consistently and retain the records needed for internal compliance reviews. Visitors prepare on their phones while internal teams manage approvals, qualifications and access through a shared workspace.
Explore the demos and source repositories
| Entry point | Address and scope |
|---|---|
| Visitor and learning frontend | visitor-training-client.blazorserver.com: explore mobile entry points, personal training lookup, and Chinese and English interfaces |
| Backend management platform | visitor-training.blazorserver.com: explore the operations dashboard and workspaces for applications, approvals, courses and training records |
| Frontend source repository | neozhu/visitor-traning-client |
| Backend source repository | neozhu/visitor-training-management |
Make enterprise visitor requirements traceable
When visit details, approval decisions and training records live in separate spreadsheets, messages and paper files, enterprises struggle to verify whether their visitor procedures were followed. Who authorized the visit and each destination? Which required courses did this person pass? Are those results still valid? Does every accompanying person meet the entry conditions? Can the team retrieve that evidence after the visit?
VisitorTraining supports enterprise visitor compliance through five connected responsibilities:
- Keep the visit together. Connect appointments, destinations, participants, vehicles and business information in one application.
- Make approval ownership visible. Record business decisions and the decisions for each selected area separately.
- Match compliance training to the visit. Use both registration type and destination areas to determine required courses, with progress and qualification validity tracked by person.
- Verify entry conditions individually. Check each participant against the visit approvals and their own current training requirements. One eligible participant can enter while another continues their learning.
- Preserve evidence for review. Keep approval decisions, training results, entry and exit times, operators and visit information together for later compliance checks.
From mobile registration to a traceable departure
1. Choose a visit type and prepare the application
Visitors, logistics drivers and contractors start with an entry point suited to their visit. The registration type determines the applicable form, notice and vehicle requirements. A guided flow collects the appointment, host, visit purpose, people and destinations.
The product workflow also supports registration by an authorized employee on someone else’s behalf. Reusable participant and vehicle profiles reduce repeated entry, while each application retains the information used for that particular visit.
2. Coordinate authorization and compliance training
After submission, business and area reviews go to their respective owners while participants receive the compliance courses required for their registration type and destinations. Separate approval decisions make responsibility for the visit purpose and requested access visible.
Time spent waiting for approval can also be time spent preparing. These activities proceed in parallel. Training can also be assigned in advance, without first creating a visit application.
3. Complete the relevant learning and preserve its validity
Courses can combine compliance training videos, supporting PDF materials, and single-choice or multiple-choice assessments. Progress, exam attempts, scores and expiry dates are associated with the person and course, giving teams a record of completed learning and current qualifications.
On a later visit, a valid passing result for the same person and course can satisfy that requirement again. Reuse preserves the original expiry date. Expired qualifications and newly required courses still need to be completed.
4. Verify entry readiness for each person
The gate workflow checks application approvals, notice acknowledgement, the appointment date, and the participant’s own current training requirements. This connects the enterprise’s configured entry conditions to the person arriving at the gate.
First entry must take place on the appointment date, evaluated in China Standard Time. The selected time slot is recorded for scheduling and display. Each participant is checked in and out separately, retaining the actual time and authorized operator.
5. Close the visit with its history intact
Participant departures, the departure of vehicles that entered, and application closure follow their applicable business conditions. Visit snapshots, approval decisions, exam attempts and entry and exit actions retain the context needed for an internal compliance review: what was requested, who approved it, which learning was completed, and when each person entered and left.
Live product screens
The mobile screenshots were captured from the local VisitorTraining client; the management dashboard was captured from the online demo. The mobile screens show the visitor entry points and personal training lookup. Both the registered name and phone number must match when finding assigned tasks; the lookup itself does not verify identity.


The management dashboard brings appointments, people on site, pending approvals, vehicles and training validity into one operational view. Area and time-period filters help teams understand upcoming demand and current readiness.

The visitor journey at a glance
The English overview connects registration, task creation, parallel approvals and learning, individual entry eligibility, departure and historical records. Question counts, passing scores and specific approval roles shown in the illustration are examples; the actual rules depend on the configured registration types, areas and courses.

View the Chinese workflow guide: registration, training, approvals and site access
Different roles, one shared visit context
| Role | Operational question | Workspace responsibilities |
|---|---|---|
| Visitors, contractors and drivers | How do I register, what must I learn, and what is complete? | Mobile registration, task lookup, videos, exams and personal results |
| Reception and operations | Who is arriving, where are they going, and who or what accompanies them? | Applications, delegated registration, appointments, participant and vehicle profiles |
| Business and area approvers | Is the purpose and requested access appropriate? | Review assigned tasks and retain separate decisions for each responsibility |
| Compliance and training teams | Which learning requirements apply, and which qualifications remain valid? | Courses, question banks, validity periods, assignments and training records |
| Gate staff | Is this person ready to enter, and when did they leave? | Individual readiness checks and recorded entry and exit operations |
Architecture and deployment
VisitorTraining separates the visitor’s mobile experience from the internal management workspace. APIs connect both experiences to shared business rules and data.
| Layer | Technology and purpose |
|---|---|
| Visitor and learning frontend | React, TypeScript, Vite, Ant Design Mobile and Tailwind CSS, designed around modern phone browsers |
| Management workspace | Blazor and CleanBlazorServerPro for business administration, users, roles, permissions and operation logs |
| Business APIs | ASP.NET Minimal APIs connecting the mobile frontend and management capabilities |
| Data and deployment | SQL Server, Docker Compose and GHCR images for deploying the frontend, backend and database together |
The product continues to evolve. This case study combines the project documentation with the current online demos; available features and integration scope depend on the deployed version and project documentation. The cover is a conceptual illustration, while the product screens are authentic browser captures.
Build a consistent enterprise visitor compliance process
Factory reception, contractor onboarding, logistics arrivals and industrial-site visits share the same compliance questions: who is coming, which areas they may access, who must authorize the visit, what training is required, and which records must be retained.
VisitorTraining connects those answers to the same visit. Participants can see their obligations, approvers can record their decisions, gate staff can verify each person’s eligibility, and enterprise teams can review the supporting records afterwards. The result is a repeatable visitor compliance process with clear ownership and traceable evidence.
Explore the visitor and learning portal · View the management platform · Frontend source · Backend source

