What a proofreader notices in a bilingual wedding transport plan

A wedding with guests flying in from Japan produces one document that everybody reads and nobody proofreads: the transport plan. It lists who is collected where, at what time, and how they get back, usually in English with a Japanese version prepared late the night before. If you're researching wedding limos in Denver, start with the timetable you will hand to guests, because the vehicle is only as useful as the sentence that tells people when to stand outside.

Most of what I read is translation, and a wedding schedule is a compact test of every habit a second reader needs. Names, numbers, places and omissions all appear within a single page. What follows is the order in which I would check one, comparing the English and Japanese versions line by line.

First pass: names, in both directions

Names come first because they are the hardest to fix once printed. A Japanese guest's name may appear in kanji on the invitation list, in rōmaji on a passport and in a slightly different rōmaji spelling on the hotel booking. Long vowels are the usual culprit: the same family can appear as Satō, Sato, Satoh or Satou depending on who typed it. None of these is wrong in itself. The problem is using two of them in one document.

Name order is the second issue. Japanese gives the family name first; English documents usually give it last. A transport list that mixes the two will have a driver or coordinator looking for the wrong person. Choose one order for the English version and keep to it, and consider writing family names in capitals, which many travellers will recognise from official documents.

Galley proof

Before: "Pickup for Mr Sato's party."

After: "Pickup for the SATŌ family (four people), booked at the hotel under 'Sato'."

Why: the coordinator needs the name as it appears on the hotel booking, and the guests need to recognise their own name on the list.

Check the same way for the couple's names, the venue names and the hotel names. A venue that is called one thing on the invitation and another on the transport plan will cause at least one anxious phone call.

Second pass: times, dates and headcounts

Numbers are where translation errors hide best, because they look identical in both languages. A time written as 2:00 sits happily in English and Japanese alike, yet one reader may assume afternoon and the other may not.

Japanese uses 午前 (gozen) for morning and 午後 (gogo) for afternoon, and many Japanese travellers are comfortable with the 24-hour clock. The awkward hour is twelve. Expressions such as 午前12時 and 午後12時 are genuinely ambiguous to many readers, in both languages. The cleanest fix is to avoid them: write 12:00 noon as 正午 (shōgo) in Japanese, and give every other time in the 24-hour form alongside the English am and pm.

Galley proof

Before: "Shuttle leaves 12:00."

After: "Shuttle leaves the hotel at 12:00 noon (正午, shōgo)."

Why: "12:00" alone asks the reader to guess between noon and midnight, and a wedding guest should not have to guess.

Dates need the same care. Japanese writes year, month, day; American English writes month, day, year. A transport plan for a weekend wedding may span three dates, so spell the month in English and use 月 and 日 in Japanese. Then count the headcounts: if the English version says a group of twelve and the Japanese version says 10名 (jū mei, "ten people"), one of them was edited and the other was not.

Third pass: places, pickup points and loanwords

A pickup point is a place, and places need to be described so that someone new to the city can find them. "Meet at the hotel" is fine for the person who wrote it, and not much use for a guest who has just landed. Which entrance? Inside or outside? Which side of the building, if it is large?

Write the description from the guest's point of view rather than the planner's. "The usual spot" means nothing to someone who has never been there. Name the entrance as the hotel names it, say whether guests should wait in the lobby or on the pavement outside, and say how long the vehicle will wait. Then read the Japanese version and check that it describes the same door, the same side of the road and the same waiting time, not a tidier summary of them.

Loanwords help and hinder here. Japanese readers will recognise リムジン (rimujin, limousine) and シャトルバス (shatoru basu, shuttle bus) without trouble. 送迎 (sōgei) is the natural word for a pick-up and drop-off service, and 送迎バス (sōgei basu) for a shuttle that does it. The risk is in mixing them: if the English says "limo" for one leg and "shuttle" for another, the Japanese should keep that difference rather than flattening both into one word.

Galley proof

Before: ホテルで集合 (hoteru de shūgō, "meet at the hotel")

After: ホテルの正面玄関に14時45分集合 (hoteru no shōmen genkan ni jūyo-ji yonjūgo-fun shūgō, "meet at the hotel's main entrance at 14:45")

Why: a door and a time give a jet-lagged guest something to act on; "the hotel" gives them a building.

Some couples add a day trip into the mountains for guests who have travelled a long way. If yours does, the same checks apply with more at stake: departure point, departure time, return time and what happens if someone misses the bus back. Those details belong on paper, in both languages, before anybody boards.

Fourth pass: what went missing

The last pass is the one a second reader exists for: comparing the two versions to find what one says and the other doesn't. Translation errors of omission are rarely dramatic. A clause is dropped because it seemed obvious, or a negative disappears because the sentence read more smoothly without it.

Galley proof

Before (Japanese version): 帰りのバスがあります。 (kaeri no basu ga arimasu, "there is a return bus")

After: 23時以降の帰りのバスはありません。 (nijūsan-ji ikō no kaeri no basu wa arimasen, "there is no return bus after 23:00")

Why: the English said there was no late return bus; the translation dropped the time and the negative, and both versions still read naturally, which is why it survived.

Points to compare line by line:

• Every time and date in English has a match in Japanese, and the two agree
• Every negative ("no", "not after", "only") survives the translation
• Return journeys are listed as clearly as outward ones
• Luggage, dress, or accessibility notes appear in both versions
• A contact name and phone number for the day appear in both versions

For the arrangements themselves, rely on the company you book with. A good wedding transport provider will confirm times, pickup points and vehicles in writing; the job of the plan you hand to guests is to repeat that confirmation accurately, not to improve on it. If anything in the confirmation is unclear, ask the company before you translate it. A translator who resolves an ambiguity by guessing has only moved it into another language.

None of this needs a certified translation. A wedding schedule is a practical document, and a careful bilingual reader is enough. Contracts and anything official are a different matter, and there a professional translator is the right person to ask.

The final read

The check that matters most: put the English and Japanese versions side by side and read every time aloud, in both languages, against the company's written confirmation. If the three agree, your guests will be standing at the right door when the car arrives.

A beautiful ceremony deserves a timetable nobody has to reread twice.