In 58 BC, Julius Caesar learned that the Helvetii, a migrating people moving across eastern Gaul, had almost finished crossing the River Saône. His scouts reported that roughly three quarters of them were already on the opposite bank. Caesar took three legions out during the night and attacked the group still waiting to cross. With the Helvetii divided by the river, he could fight one portion of their force before the others could join it.

Scouting gave commanders information they could act on. Soldiers and other trusted observers went ahead of Greek and Roman armies to find enemy positions, trace movements and examine roads and crossings. Commanders depended on what came back to decide when to march, where to camp and whether to attack. They also questioned prisoners, drew information from merchants and consulted local allies. A report had to arrive while there was still time to use it.

A scout could observe only part of the situation. A rider approaching an enemy camp might see its tents but miss soldiers concealed beyond a ridge. A defector could offer reliable information or a carefully prepared lie. Ancient historians describe battles shaped by sound intelligence and by costly errors of judgment. Inscriptions and writing tablets from military sites record the routine arrangements behind reconnaissance.

Roman scouts and the intelligence they carried

Wooden writing tablet recording ancient military intelligence from Roman frontier
Roman wooden writing tablet carrying a military intelligence report from Vindolanda; Source: British Museum

The observers are called exploratores in Caesar’s account of the Helvetian crossing. They were sent to investigate and bring back news of the enemy. Some reconnaissance was undertaken on horseback, but the Latin term does not tell us the patrol’s size, equipment or distance from the army. Its work depended on the country. In the woods of Gaul it needed to locate usable tracks and river crossings. On open ground it could watch a marching column and judge how quickly it advanced.

The Saône was called the Arar by the Romans. Caesar says his scouts found that some Helvetii had yet to cross it, allowing him to attack the Tigurini, one of their constituent groups, by surprise. The Tigurini had previously defeated a Roman army, a grievance Caesar emphasised when recounting his victory. His three legions moved against people temporarily cut off from the rest of the migration. The scout report gave Caesar his opportunity. His own account, however, presents the decision and victory from the commander’s perspective.

Scouts performed similar work around Roman camps. River crossings were particularly dangerous: troops, pack animals and baggage could become crowded into a narrow approach while the army was only partly across. Patrols checked whether an enemy occupied high ground, had closed a road or was genuinely retreating. A patrol could report accurately and still leave its commander to draw the wrong conclusion. Roman campaigns show how much depended on interpreting what the patrols had seen.

Exploratores, speculatores and frontier units

Roman cavalry charges in an arena, scouts Roman army on display
Seventeenth‑century painting of mounted Roman soldiers in a crowded circus setting; Source: Museo del Prado

Roman terminology distinguishes several kinds of forward duty although the roles did not form fixed branches like those in a modern army. Exploratores generally reconnoitred roads and opposing forces. Speculatores were watchers who might also perform covert tasks; the word appears in military and administrative settings beyond battlefield scouting. Procursatores were troops moving in advance of a larger force. Duties overlapped, and the way they were organised changed over the centuries.

The inscriptions found on the Roman frontiers identify scouting units stationed at frontier forts. An inscription from Risingham in northern Britain, at the fort of Habitancum, dates to AD 213 and the reign of Caracalla. It names the Exploratores Habitancenses alongside the First Cohort of Vangiones and Raetian spearmen. The dated inscription places a named scouting formation at a specific frontier fort, rather than merely mentioning scouts during a campaign.

A second inscription, RIB 1262 from Bremenium at High Rochester, mentions scouts and the standards of the First Cohort of Vardulli. It dates to the reign of Gordian III in the third century. The much later Notitia Dignitatum, a list of military and civilian offices, records a commander of scouts at Lavatris, usually identified with Bowes. Together, the records locate named scouting units at particular posts. They leave the units’ numbers, daily patrol routes and individual assignments unknown.

Men stationed along a frontier needed to know its paths, valleys, grazing grounds and regular crossing points. Such knowledge helped them tell routine movement from the approach of hostile riders. Roads and forts also gave patrols routes by which to return with their reports. The evidence does not support a single continuous network of watchtowers and patrols warning every Roman frontier garrison in the same way.

Advertisements

The coded warning that reached Ammianus Marcellinus

Ammianus Marcellinus, a historian who had served in the fourth-century Roman army, describes intelligence work from personal experience. During the Persian campaign of AD 359, the Roman frontier in Mesopotamia, between the Tigris and Euphrates, faced an invasion by the Sasanian ruler Shapur II. Officers needed to learn which route his army would take and where it might cross into Roman territory. Finding out the army’s route could give threatened fortified cities time to prepare.

Scouts and deserters had already brought warnings of Persian preparations, Ammianus writes. At Amida, returning scouts delivered a parchment concealed inside a sword scabbard. Its sender was Procopius, the Roman envoy at the Persian court. He hid the enemy’s movements behind references to Greek places and historical events. Ammianus, Res Gestae 18.6.17–19 records the difficulty of making sense of the message. The disguise was meant to protect the information if the courier was captured.

The Romans then sent observers to confirm the Persian movements. Ammianus and a centurion travelled through mountain country into Persian-held Corduene, where an official named Jovinianus favoured Rome. Guided to a vantage point above the route, they waited two days before Shapur’s army and allied contingents appeared below. Ammianus describes a vast force visible across an extraordinary distance. He had taken part in the mission, making his account unusually immediate, although his stated distances and the extent of the view deserve caution.

Once the warning reached Roman commanders, mounted messengers carried orders to evacuate civilians and livestock from the threatened area. Crops were to be burned so the invaders could not feed themselves from the land. Shapur’s movements nevertheless changed. Flooding ruled out an intended crossing of the Euphrates, while Antoninus, a Roman defector advising the Persians, helped redirect their advance. Shapur eventually laid siege to Amida. Ammianus records both the warning and the Roman response, as well as the unexpected developments that frustrated their preparations.

Merchants, prisoners and defectors

An overseas expedition demanded information that mounted patrols on familiar ground could not supply. Before his invasion of Britain in 55 BC, Caesar asked traders in Gaul about the island. They knew little beyond its nearer coastline. He therefore ordered Gaius Volusenus to examine the approaches from a warship. Caesar, Gallic War 4.20–21 says Volusenus came back after five days, reporting what he could observe without landing in hostile territory.

The decision not to land restricted what Volusenus learned. Volusenus could inspect cliffs, beaches and coastal defences from the water, but not reliably establish the roads inland or the strength of the communities beyond the shore. Nor could he be certain how the landing places would work for soldiers and horses disembarking under pressure. Caesar also sent Commius, a ruler allied to Rome, to approach British communities diplomatically. Caesar therefore gathered coastal observations and diplomatic intelligence ahead of the same crossing.

Armies questioned prisoners, listened to refugees and sometimes received news from deserters who knew an opponent’s camps, provisions or orders. Each source had reasons to withhold or distort the truth. Captives might conceal information to protect themselves; deserters might hope to mislead a former enemy or ingratiate themselves with a new one. Ammianus even recounts a Roman who entered Persian service and returned with information. Research on late Roman military informants also identifies captives, deserters and secret messengers as channels of late Roman military intelligence. Commanders had to compare these accounts with observations from other sources.

Greek armies used scouts too

Greek hoplite attacks Persian archer, illustrating ancient battlefield tactics in art
Classical Greek red‑figure pitcher showing a hoplite spearing a Persian archer; Source: Museum of Fine Arts, Boston

Greek commanders had long employed scouts. In Herodotus’s account of the invasion of Greece in 480 BC, the Persian king Xerxes sends a mounted observer towards the defenders at Thermopylae. The rider cannot see every Greek behind the defensive wall, but he notices Spartans exercising and combing their hair. Xerxes cannot understand why the Spartans are behaving this way. Demaratus, an exiled Spartan at his court, explains that the men are preparing for a fight they expect to be desperate. In Herodotus 7.208–209, the observer reports accurately, but Demaratus supplies the knowledge needed to interpret the scene.

Herodotus composed the episode decades after Thermopylae, giving it speeches and a dramatic arrangement. It cannot be read as a word-for-word record of Xerxes’s conversations. Even in this crafted narrative, mounted reconnaissance appears as ordinary military preparation. Herodotus distinguishes the scout’s observations from Xerxes’s interpretation of them.

During the following year’s campaign, at Plataea in 479 BC, Persian horsemen disrupted the allied Greeks’ access to water and supplies. Herodotus 9.49–50 describes their fouling of the Gargaphia spring and their efforts to stop Greek parties collecting water from the Asopus. Greek leaders consequently considered a nighttime move to another position. Cavalry interfering with water supplies could compel an army of heavy infantry to change position before battle.

The Greek hoplite was a citizen infantryman equipped with spear and shield, usually fighting in the closely ordered phalanx. That formation depended on suitable ground, dependable supplies and advance warning of threats to its flanks. Cavalry and lighter troops could scout and screen for it, even though surviving narratives tell us little about their ordinary patrol assignments. The formation and equipment of the infantry are discussed in how Greek hoplites fought.

Advertisements

Alexander and the problem of finding Darius

Alexander’s army clashes with Persians at Issus, echoing reconnaissance in antiquity
lbrecht Altdorfer’s panoramic painting of Alexander’s victory over Darius at Issus; Source: Alte Pinakothek, Munich

Alexander III of Macedon commanded a more varied army of long-pike infantry, cavalry and lighter troops. On long campaigns his troops needed advance reports on roads, water and the enemy’s position. At Issus in 333 BC, he encountered Darius III on a narrow coastal plain in southern Anatolia. The terrain constrained their armies, but the battle’s location alone does not establish that Alexander conducted any particular scouting operation. The sources say little about the preparations before the two armies met.

Two years later at Gaugamela in northern Mesopotamia, the sources describe the reconnaissance more clearly. Arrian, Anabasis 3.9 reports that Alexander interrogated Persian scouts who had been captured and learned about Darius’s preparations. He then rested his men and fortified a camp before approaching the field. Arrian links questioning captured scouts to Alexander’s decision about when to advance. A prisoner could provide details that an observer approaching the Persian position from outside might miss.

The Macedonian cavalry needed room to manoeuvre, while its infantry had to arrive in formation and its baggage train required protection. Road conditions, scouting and timing mattered alongside the cavalry charges described in later histories. Alexander’s battlefield achievements depended in part on troops performing such work before the fighting. The wider campaigns are covered in Alexander the Great’s military career.

Signals, watch posts and military records

Scouts also needed a way to get their reports back. The information had to reach a commander before it became obsolete. Runners, mounted couriers and visual signals connected ancient forces, but a distant warning fire could usually say little beyond something agreed in advance, such as the sighting of an enemy. Detailed or unexpected news required words, a messenger or a more elaborate code.

Polybius, the Greek historian writing in the second century BC, described why ordinary fire beacons were so limited. In Histories 10.43–45, he explains an alternative in which arrangements of torches refer to letters on prepared tablets. Operators who knew the system could in principle send an unfamiliar message rather than merely sound an agreed alarm. They needed clear visibility, training and enough time to signal it. Polybius explains the system, but his description does not establish that every Roman watchtower used it.

The archaeological remains of forts and watch posts help locate places from which roads, passes and river valleys might have been observed. Frontier inscriptions show that units of scouts served at specific garrisons. The Notitia Dignitatum, meanwhile, lists military offices and units from late antiquity. Its official titles do not reveal how quickly a warning moved, which route it took or how many stations relayed it.

A wooden tablet from Vindolanda, a Roman fort near Hadrian’s Wall, shows military information preserved in writing. Listed by the British Museum as 1986,1001.34 and published as Tabulae Vindolandenses II 164, it describes Britons’ fighting methods, including their use of cavalry and armour. The writer uses a disparaging diminutive for the Britons. It is unclear whether the report concerned enemies or prospective recruits, or exactly what purpose it served. Another document, Vindolanda tablet, number 154, records a cohort’s strength and movements. Both show soldiers recording useful information. Neither is evidence for an empire-wide intelligence bureau organised on a single model.

When scouts got it wrong: Adrianople in AD 378

Reconnaissance failed to prevent disaster at Adrianople. In AD 378, the emperor Valens led an army against the Goths in Thrace, part of the eastern Balkans. Gothic groups had crossed the Danube two years before, and Roman mistreatment and subsequent warfare had produced a dangerous crisis. Valens had to choose between attacking with his available troops and waiting for reinforcements from Gratian, the western co-emperor.

Roman skirmishers reported an enemy force of approximately 10,000, according to Ammianus 31.12.3. The estimate covered the Goths visible to the scouts and could exclude other forces nearby. Ammianus portrays Valens as determined to secure a victory without sharing the honour with Gratian. His men marched through oppressive summer heat and came upon the Gothic wagon camp before the Roman army had fully deployed.

The Romans had not encountered all the Gothic cavalry. A contingent led by Alatheus and Saphrax was away when they arrived, but returned during negotiations and attacked as Roman troops were becoming engaged. Valens died in the crushing defeat. The estimate missed a substantial part of the Gothic force. Ammianus also describes rivalry, haste, exhausted soldiers and poor discipline. The deficient reconnaissance compounded those problems rather than explaining the defeat by itself.

Gathering such information could put the scouts themselves in danger. Ammianus describes riding in danger of capture, signalling to warn other Romans and making a difficult journey through enemy-controlled mountains. Scouts could encounter opposing cavalry without warning, or depend on local informants whose loyalty was uncertain. After evading capture, they might still have seen only a fraction of the enemy army.

At the Saône, in Mesopotamia and at Adrianople, scouting shaped decisions in very different ways. Caesar exploited news of a divided enemy; Ammianus helped report a Persian advance and Roman authorities acted on it; Valens marched after receiving an estimate that omitted Gothic cavalry. The reports gave commanders a view beyond their own marching columns. Whether they acted wisely depended on how they judged incomplete and sometimes misunderstood evidence.