Managing OJT Plans and Records in One System — A Practical Guide to Standardizing Onboarding
Introduction
"We leave OJT to the trainers." You hear this answer at a great many small and mid-sized companies.
OJT (On-the-Job Training) is the single most effective method for getting new hires and transferees productive quickly — but its management is, more often than not, dependent on individuals. Each department writes its OJT plan in Excel or Word in its own format, records stay in the assigned trainer's personal notes, and the criteria for whether OJT is even complete are fuzzy. You can say you're "doing it," but not that it's "working."
This guide explains a practical, single-system approach: from designing the OJT plan, to managing daily records, to linking it all with your skill map and 1on1s.
1. The current state of OJT management
Three common problems
(1) The plan becomes a formality
Many companies are satisfied just to have produced an OJT plan, then leave it disconnected from the actual development process. "The plan says 'master product knowledge in three months,' but there's no record of what was actually taught."
(2) It resets when the trainer leaves or transfers
When OJT know-how lives only in one trainer's head, continuity of development is lost the moment that person transfers or leaves. The next new hire requires a from-scratch redesign.
(3) No criteria for complete vs. incomplete
Even if you set "OJT runs for three months," without spelling out "what counts as complete," development gets cut off at a formal end-of-period. Skill acquisition isn't reflected in evaluation, which can lead to early turnover after placement.
2. What an OJT plan should contain
A standard OJT plan structure
| Item | Content | Example |
|---|---|---|
| Trainee information | Name, start date, assigned department, assigned trainer | Taro Yamada, joined April 1, 2026, Sales Dept. Section 2 |
| OJT period | Start to planned end date | April 1 – June 30, 2026 (3 months) |
| Target skill list | Skills to acquire in the period (linked to the skill map) | Sales-meeting basics, proposal writing, CRM operation, order processing |
| Completion criteria per skill | Spelled out: "what counts as complete" | "Sales-meeting basics: can run a first meeting independently" |
| Weekly milestones | The focus theme for each week | Week 1: industry knowledge, understanding our products |
| Evaluation timing | Mid-point and final check dates | Week 6 (mid), Week 12 (final) |
"Spelling out the completion criteria" matters most
The single most important thing for making an OJT plan work is to put each skill's completion criteria (its Done condition) into words.
| Skill | Vague phrasing (NG) | Concrete criterion (OK) |
|---|---|---|
| Phone handling | Can handle phone calls | Can route, take messages, and do initial complaint handling alone, with zero errors sustained for two weeks |
| Proposal writing | Can write proposals | Created three proposals submittable without a manager's check |
| Sales-meeting shadowing | Understands sales meetings | Can submit a meeting summary the same day after shadowing |
3. Designing the daily OJT record
Choosing the record granularity
The granularity an OJT record needs depends on its purpose.
| Granularity | Use | Timing |
|---|---|---|
| Daily checklist | Confirm "what was learned today" sticks | 5 minutes before end of day |
| Weekly reflection note | Record skill progress and sticking points | Right after the weekly 1on1 |
| Skill-acquisition confirmation | Mark a plan skill complete | When the completion criterion is met |
| Trainer comment | Record the developer's observations and feedback | Monthly or at mid-point evaluation |
A weekly reflection-note template
If you record alongside the weekly 1on1, these four items make a base format that's easy to sustain:
[OJT Weekly Record]
Period: Month __, Week __
What I learned (what I can now do this week):
Where I struggled (what I haven't mastered yet):
Next week's focus theme:
Trainer comment:
Managing this format in a system accumulates progress into a development log you can still reference after OJT ends.
4. Linking with the skill map
OJT completion = skill-level update
Linking OJT management with your skill map makes the results of development visible as HR data.
Linkage flow:
- Map the "target skill list" in the OJT plan onto your skill-map items
- When the trainee meets a plan completion criterion, update the skill-map level
- The skill map at the end of OJT becomes "evidence of OJT outcomes"
| OJT completion criterion (plan) | Skill-map reflection |
|---|---|
| Three shadowed meetings + summaries submitted | "Sales-meeting basics" Lv1 → Lv2 |
| Three proposals submitted without manager check | "Proposal writing" Lv1 → Lv2 |
| Handled five initial complaints solo | "Customer handling" Lv2 → Lv3 |
This linkage accumulates OJT outcomes as data usable for evaluation, placement decisions, and promotion judgments.
5. Linking with 1on1s
Using 1on1s during the OJT period
1on1s during OJT become more effective when tied to the weekly OJT record.
Building the 1on1 agenda (during OJT):
| Agenda item | Content | Time |
|---|---|---|
| Weekly OJT review | Check progress against plan milestones | 10 min |
| Sticking-point discussion | Find the cause of skills falling behind | 10 min |
| Condition check | Adjustment to the new environment, anxiety, stress | 5 min |
| Next week's priorities | Balancing OJT and regular work | 5 min |
During OJT, it's especially important not to skip the condition check. The more dedicated the trainer is to skill acquisition, the easier it is to overlook a new hire's exhaustion or isolation.
6. The benefits of managing it in one HR system
Compared with scattered Excel files
| Comparison | Excel management | HR-system management |
|---|---|---|
| Handover | No one knows where the file is | Search instantly by trainee or trainer |
| Standardization | Format differs by department | Company-wide unified template |
| Skill-map linkage | Manual transcription needed | Reflected the moment OJT completes |
| Progress visibility | Managers tally by hand | Real-time dashboard |
| Audit / compliance | Evidence hard to gather from scattered files | Period, owner, and records managed in one place |
Benefits for managers and HR
- Detecting early-turnover risk: the system can flag new hires whose OJT progress is lagging
- Developing trainers: as records accumulate, the coaching patterns of strong trainers become visible
- Feeding hiring plans: actual OJT effort lets you plan next year's hiring and development resources
7. Common pitfalls at adoption, and how to handle them
Pitfall 1: Making the plan an end in itself
Symptom: copy-pasting the same plan every year without updating the contents Fix: tie it to skill-map items and make it a rule that "when skill requirements change, the plan updates too"
Pitfall 2: Too high a recording burden on trainers
Symptom: weekly records are mandated, but trainers give up with "I'm too busy to write them" Fix: cut record items to the minimum (four or fewer) and use a format fillable in the 5 minutes right after a 1on1
Pitfall 3: Completion criteria stay abstract
Symptom: a criterion like "has a general grasp of the work" leaves evaluation ambiguous Fix: write it with verbs ("understand" → "can do alone," "can do three or more times")
Summary
Turning OJT from "left to the trainer" into "an organizational asset" requires managing the three-piece set of plan, record, and evaluation in one HR system.
| Point | Content |
|---|---|
| Plan | Spell out target skills × completion criteria (mapped to the skill map) |
| Record | Sustain with a four-item format tied to the weekly 1on1 |
| Linkage | OJT completion → skill-map update → reflected in evaluation |
COCKPITOS provides a training-management feature that integrates OJT plans, records, and the skill map. If you want to manage everything from new-hire onboarding to mid-career skill-up in one place, reach out via our free consultation / contact form.