How to Find an SOE Agent’s Codename

Understanding SOE Identification Systems

For researchers and family historians, identifying a Special Operations Executive (SOE) agent can be challenging because the organization utilized multiple layers of anonymity to protect its personnel. A single individual often operated under several different identifiers depending on the context of the communication or the stage of their mission.

Codenames vs. Aliases vs. Circuit Names

It is critical to distinguish between the different types of names associated with an agent. Confusing these terms often leads to dead ends in archival research:

• Codenames: These were official identifiers used by SOE headquarters in London to refer to agents in reports and wireless transmissions. For example, in F Section, agents were assigned specific codenames such as ACROBAT (John Starr) or ALMONER (Vera Leigh) [1].
• Aliases (Cover Identities): These were the false identities agents used while operating in the field to blend into the local population. An alias was a “legend”—a complete fake persona with a believable backstory, used to deceive enemy counter-intelligence [1].
• Circuit (Network) Names: A circuit (or réseau) was the clandestine organization established in the field. Agents were assigned to these networks, which also had their own codenames. For example, an agent might be a member of the Prosper circuit [2, 4].

Methods for Locating Codenames

Because SOE records were often destroyed or remained classified for decades, finding a specific codename requires cross-referencing multiple sources.

1. Utilizing Specialized Lists

For agents of the F Section (the section responsible for France), dedicated lists of codenames and aliases exist. These lists link the agent’s real name to their official SOE codename. For instance, records show that the agent Roland Dowlen operated under the codename Achille, while Lisé de Baissac used both the codename ARTIST and the alias Adele [1].

2. Searching by Network or Circuit

If the agent’s specific codename is unknown, searching by the network they served in is often the most effective route. A typical SOE network consisted of a circuit organizer, a wireless operator, and a courier [4]. By identifying the network (such as the Farrier circuit), researchers can find lists of all agents assigned to that specific group, which may then lead to the individual’s codename [2].

3. Archival Record Navigation

Official records are the most authoritative source but require knowledge of SOE’s internal abbreviations. Archival series often use shorthand for different sections and roles. For example, AD/E refers to the SOE head of operations for north-west Europe (London section) [3]. Researchers should look for:

• Personnel Files: These may contain the transition from the agent’s legal name to their assigned codename.
• Wireless Logs: Communications between the field and London almost exclusively used codenames to maintain security.
• Mission Reports: Post-operation summaries often list agents by their codenames, though they may be linked to real names in annexed lists.

Challenges in Identification

Several factors can complicate the search for a codename:

• Multiple Codenames: Some agents were assigned different codenames for different phases of their service or when moving between sections [1].
• Overlapping Names: In some instances, similar aliases or codenames may have been used by different individuals across different country sections.
• Incomplete Records: Many lists of SOE agents are noted as being incomplete, meaning not every operative has a documented codename in public databases [1, 2].

Why Accurate Identification Matters

Correctly identifying a codename is more than a genealogical exercise; it is the key to unlocking the agent’s operational history. Once a codename is established, a researcher can track the agent’s specific contributions—such as sabotage missions, intelligence gathering, or the organization of indigenous resistance groups—within the broader context of the Allied effort in occupied Europe [4].