Achaemenid Roads and Communications: Routes for Imperial Commands and Reports

From about 550 to 330 BCE, Achaemenid kings governed territories joined by regional paths, major roads and administrative correspondence. A command could move through relays of riders and horses, while an authorised traveller might carry a sealed tablet allowing local officials to issue provisions. These systems served royal and provincial business.

On this page5 sections

Routes connected older centres and new imperial works

The empire incorporated older regional roads and caravan paths into its communications. Royal projects also improved long-distance connections between major centres. Sardis, in western Anatolia, and Susa, in southwestern Iran, were linked by the route Herodotus described as the Royal Road. It crossed several rivers, including the Halys, Euphrates and Tigris, and passed through 111 stations. Roads also connected Susa and Babylon with provincial centres, while routes through Persis, the southwestern Iranian heartland around Persepolis, served the royal establishment there.

Herodotus estimated that an ordinary traveller took about ninety days to cover the Sardis–Susa route. That estimate describes travel at a normal pace, not the time for a royal dispatch carried through relays. The long route still depended on local geography: rivers required crossings, and roads had to connect places where people could change animals or obtain official support. A route was therefore a chain of usable stages, not simply a line drawn between two capitals.

Relay stations kept dispatches moving

Herodotus describes a message passing from one rider to the next. Men and horses waited at successive stages, so the next courier could take the dispatch onward instead of requiring one rider and mount to complete the full distance. In his description of the relay, the handoff continued through the night as well as the day. Fresh horses and prepared personnel made speed possible; the dispatch itself remained the same as it passed between couriers.

This system connected the royal court with provincial governors and other officials. Orders could travel outward, and reports could bring information back. The mechanism depended on coordination: a station needed riders ready to receive the dispatch and horses fit for the next leg. Royal communications thus used people and animals arranged along a route, while ordinary travellers moved at the pace of their own party.

Authorisations joined travel to local stores

Travel documents in the Persepolis Fortification archive show another part of the system. Officials issued sealed authorisations that entitled named travellers to receive specified provisions. At an authorised store, a supplier could issue grain or other goods against the document, record what had been handed over, and retain a transaction trail. The authorisation made the traveller’s claim legible to local staff; the matching record allowed the central administration to account for stock issued along the route.

The Persepolis records include travel rations for people and animals. A party with several travellers and horses required more supplies than a single official, so an issue connected an authorised group with quantities drawn from a store. The system made official movement practical across distances while assigning responsibility for the food and other resources consumed on the way.

Letters carried instructions between named officials

A surviving Aramaic letter from Aršāma, Egypt’s satrap (provincial governor), illustrates how a written order could combine people, provisions and work. Addressed to Nakhtḥor, Kenzasirma and their colleagues, including officials and accountants in Egypt, letter A6.12 orders rations for Ḥinzani, a sculptor whom Bagasrava had brought to Susa, and for the sculptor’s household. It also commissions statues, notes that Artavahya knows the order, and names Rašta as the scribe. The letter gives recipients a specific instruction they could act on and account for.

Written dispatches operated within a multilingual administration. Aramaic served as a widely used language for communication across regions; at Persepolis, many routine administrative records were written in Elamite on clay tablets. Seals marked documents and transactions with an identifying impression. In the Fortification records, some tablets were sealed by both supplier and recipient and returned to Persepolis, linking a local issue to the central account.

Archives preserved the work of communication

The Persepolis Fortification archive was recovered from the site’s northeastern fortification area. Its more than 30,000 tablets and fragments mainly date from 509 to 494 BCE. They record supplies received, stored, moved and issued across Persis and eastern Elam, with entries and summaries reaching an administrative centre at Persepolis. The archive preserves routine work behind journeys and distribution: officials identified recipients, recorded quantities and retained evidence of transactions.

A separate group, the Treasury archive, mainly dates from 492 to 458 BCE and includes records of work and payments. Letters, travel authorisations and accounts therefore served related but distinct tasks: a letter directed an official, an authorisation supported a traveller’s claim to provisions, and an account let administrators track what had been issued. The article on Achaemenid writing and archives explains the surviving records, scripts and scribal practices in greater detail.