- Date
- 1 BBY
- Continuity
- Canon
- Place
- Scarif
Chronology note. Following Star Wars: Timelines, this pre-Yavin event is placed in 1 BBY. Older publications sometimes label it 0 BBY. About the dating convention →
An Imperial shuttle slips past security
The Rogue One team used a stolen Imperial transport and its access codes to approach Scarif, the tropical world housing a major Citadel archive and heavily defended Imperial installations. The planet was protected by a shield gate and security forces, making an unauthorized landing only the first obstacle.
Creating space for an archive search
The group divided its efforts. Jyn, Cassian and K-2SO entered the Citadel complex searching for the original Death Star schematics, while the other volunteers created diversions among the garrisons, landing pads and beaches. Rebel ground action relied on precise cooperation with a very small force.
A large fleet moves to the battle
The Alliance learned of the unauthorized assault and elements of its fleet joined the fighting above Scarif. The arrival complicated the Empire's response but also placed irreplaceable ships and pilots within range of Star Destroyers and the planetary shield.
Anthropological assessment
Scarif shows an intelligence raid turning into a fleet engagement because control of information was inseparable from control of infrastructure. The shield gate, archive and orbital communications network together decided who could move and transmit crucial knowledge.
Interactive evidence lab
Open a chronology check or switch perspectives. The result appears immediately below your selection.
Was Rogue One a conventional planetary invasion ordered by the full Rebel council?
No. It began as an unauthorized infiltration by a small volunteer team.
Source-critical investigation · Scarif to Yavin
Imperial infrastructure determines the shape of the raid
Rogue One enters Scarif using an Imperial shuttle and a cover story before separating into ground and archive operations.
Scarif is not an undefended island where the presence of a data vault automatically makes information accessible. The official Databank identifies a heavily protected Imperial military installation enclosed by a deflector shield. The shuttle's approach depends upon an accepted clearance and a believable place within Imperial traffic. Once inside, the team must navigate separate barriers: local patrols, archive permissions, physical data retrieval and the communications connection beyond the shield.
The ground team's actions have different purposes. Some members draw Imperial forces away from the Citadel, while Jyn, Cassian and K-2SO move toward the records. Bodhi's expertise as a former Imperial cargo pilot matters because knowing how a system works can be as valuable as a weapon. The subsequent arrival of Rebel warships does not make that local knowledge irrelevant. Instead, movement of information from a secure storage unit toward an external fleet becomes a multi-level operation requiring cooperation among people who do not all occupy the same place.
That division of labor also explains why the battle cannot be treated as only a confrontation between Jyn and Director Krennic. Imperial guards and military personnel preserve the archive's access restrictions, while Rebel specialists work around them. The archive records a system in which scientific knowledge has become state property. Copying the data is not the same as protecting the people who recover it, and the story does not provide survivors' testimony from every team member. A stage-by-stage account should retain both the victory in transmission and the losses of the raid.
Test the historical record: Did reaching Scarif's surface give Rogue One an unrestricted channel to send the plans immediately?
Correction and insight: No. The archive, communications links and shield gate still had to be overcome before the plans could be transmitted.
Primary source: Rogue One: A Star Wars Story and Lucasfilm: Scarif Databank. The Databank establishes narrated events; institutional interpretation is IDS analysis, not attributed dialogue.
Related records: scarif transmits death star plans 1 → · rogue one unsanctioned scarif 0 →
Sources and methods
Rogue One: A Star Wars Story; StarWars.com Scarif databank. Explore the original background →. Interpretive analysis is distinguished from information shown in the story. Captions disclose when artwork is a character portrait rather than a depiction of the specific historical scene.
Canon · 1 BBY · Pre-Yavin history
Rogue One infiltrates Scarif
Documented historical sequence
Jyn, Cassian, K-2SO and volunteers used a captured Imperial craft and access credentials to reach Scarif. The planet's Citadel contained classified technical records and was protected by a planetary shield. The ground team faced an escalating fight as Alliance ships attempted to intervene.
Institutions, identity and material life
An archive's catalogues and security systems decide which knowledge can be accessed. Scarif's data was not freely available even to citizens harmed by the weapon being built. The operation relied on trained specialists, pilots and droids as well as the central protagonists.
Why 1 BBY, rather than 0 BBY?
Recent Star Wars chronologies use the Battle of Yavin as the zero point. Rogue One and events immediately before that battle belong to 1 BBY rather than a separate 0 BBY year. The character or story illustration at the top provides context, not a photograph of the entire event.
Test the historical evidence
Two graded questions with corrections and explanations.