The Difference Between 工程 and 行程 | Choosing the Right Kotei, with Examples

Published:
Last Updated:
Category: Campaign Management, Marketing DX

Published:
Last Updated:
Category: Campaign Management, Marketing DX
Authors: Shusaku Yosa
You start typing kotei-hyou in Japanese, the conversion candidates offer both 工程表 and 行程表, and you stop. Both are real words, so nothing flags the wrong one as an error. This article sets out the difference in meaning between 工程 and 行程, and shows how to choose between them in the situations where people most often hesitate.
Starting with the conclusion. When you are unsure, split on this one point.
The characters themselves are the clue. If you are describing work, 工; if you are describing a path being travelled, 行. Hold onto that pairing and most cases resolve themselves.
工程 refers to the order of work leading to something being completed, each individual stage of it, and how far along it is. It is common in manufacturing and construction, but it carries the same meaning in software development and content production.
Its defining feature is that it can be counted as stages. You can say "divide it into three 工程" or "pass it to the next 工程", treating it as discrete blocks.
工程管理 (process management), 工程表 (work schedule), 工程数 (number of stages), 前工程 and 後工程 (upstream and downstream stages), 製造工程 (manufacturing process), 工程分析 (process analysis). All of these concern stages of work, and none can be swapped for 行程.
行程 refers to the route or distance to a destination, and the passage of getting there. It originally describes physical movement, and it is used in the context of travel and business trips.
Carrying distance is what separates it from 工程. You can say "the day's 行程 is about 40 kilometres", measuring it as a length of road.
As the fourth example shows, it can also be used figuratively for the course of events. Even then, the sense of having travelled a long road underlies it.
This pair causes the most hesitation. Both are in genuine use, and they mean different things.
A table setting out the sequence of work and its dates. Construction schedules, production line plans, software development schedules: the kind of document updated day to day in practice. Who does what by when is written at a concrete level of detail.
In business documents, the great majority of cases where you want to write kotei-hyou are this one.
There are two uses.
One is an itinerary for travel or a business trip: routes, times, accommodation. This follows the original sense of a route.
The other is as the Japanese rendering of roadmap. The Sanseido Kokugo Jiten defines 行程表 as a table setting out goals and methods for what will be done by when, and gives roadmap as the equivalent; Daijisen likewise directs the entry to roadmap. When you see phrases in the news like 和平の行程表 (a roadmap to peace) or 民主化の行程表 (a roadmap to democratization), this is the sense in play.
So 行程表 is used in political, diplomatic, and corporate-strategy contexts, showing the broad path toward a large goal. It is not a document listing detailed work steps.
When in doubt, try replacing the word with the katakana ロードマップ. If the sentence still works, 行程表 is right; if it does not, 工程表 is.
Situations that commonly cause hesitation, with the answer.
Refers to the allocation of dates and times. Where 行程 emphasises the route, 日程 emphasises when things happen. In travel contexts 行程表 and 日程表 are sometimes used almost interchangeably, but 行程 is natural where routes are included and 日程 where only the timing is.
A broader word for the course along which something proceeds. It is not counted in discrete blocks the way 工程 is, and it carries no distance the way 行程 does. Use it for how something came about, as in 検討の過程で方針が変わった (the direction changed during the review).
Refers to the order of what should be done. Close to 工程, but where 工程 takes in divisions of organisation and equipment, 手順 is limited to the sequence of actions. Three 工程 may involve different owners or machines; three 手順 can equally be carried out by one person in a row.
Treat it as an inconsistency in notation and standardise on one. If the document manages work steps, 工程表 is the right form, so move toward that. Adding a line to your style guide or glossary makes the decision faster next time.
For an internal memo the harm is small. But in documents going to a vendor or a client, precision of notation feeds the impression of the document's overall reliability. It is worth checking, particularly for material attached to quotations or contracts.
Yes. Any work divided into stages qualifies, regardless of industry. 入稿工程 in advertising production, テスト工程 in software development, 校正工程 in editorial work are all natural.
Try substituting 作業 (work) and see whether the sentence still holds. If it reads as 作業表 or 作業の順序, the answer is 工程. If it does not, check whether the sense of travel or of a roadmap has crept in.
The kotei-hyou you deal with in business documents is, in almost every case, 工程表. Remember it as 工程 whenever the document manages the steps and dates of work, and the situations where you hesitate drop away considerably.

A five-step method for mapping a business process, plus the three things that create key-person dependency, how to inter...

What a project manager actually does, broken down by phase from initiation to closure. Covers how the role differs from ...

How to make a project schedule readable, centred on the progress line. Covers the five steps for drawing it from the sta...