GUIDED PATH · PHASE 5
Guided Japanese Course
A mastery path for complete beginners and technology professionals.
HOW THIS COURSE WORKS
Follow the path. Advance by mastery.
The primary path tells you what to do next. You can still open any available lesson, but completion is based on checkpoints rather than calendar days.
FULL TARGET CURRICULUM
Tracks 0–10
TRACK 2 · 2-19
Duration: How Long
Express how long an activity lasts and distinguish duration from a specific time point.
- Numbers, clock time, time に.
Technical work uses durations constantly: test for two hours, meeting for thirty minutes, study for one hour.
1. Time point and duration are different roles
九時に = at 9 (when). 二時間 = for two hours (how long). Basic durations often omit に.
2. Common duration units
時間 marks hours, 分 minutes, 日間 a span of days.
Natural: I study for one hour.
Structure: one-hour-duration — study.
Duration.
Natural: We have a 30-minute meeting.
Structure: 30 minutes — meeting — do.
Duration.
Natural: We test for two days.
Structure: two-day-span — test.
Multi-day duration.
3. Ask どのくらい / どれくらい
These can ask roughly how long/how much.
Natural: How long do you study?
Structure: about-how-much — study — question?
Duration question.
4. Workflow durations
Write ten realistic durations. For five, add a matching start time so you contrast に with duration.
INTERACTIVE WORKSHEET
4. Workflow durations
Write 10 duration sentences and 5 paired start-time sentences. Label WHEN vs HOW LONG.
Tip: on a foldable or tablet, use your pen directly on the page. Your strokes are saved in this browser as you work.
4. Workflow durations
Write 10 duration sentences and 5 paired start-time sentences. Label WHEN vs HOW LONG.
5. Debug when vs duration
Use same activity with different time roles.
Language IDE
Why here: It keeps time point and duration as separate semantic slots.
How to use it for this lesson: Compare 九時にテストします and 二時間テストします. Label WHEN vs DURATION.
Debug time roles →Mastery checkpoint
Answer from memory. Treat every miss as a debugging signal: inspect the explanation, repair the rule, and retry.
