Why a Decode is Not the Same as a Translation

People often describe what they're looking for as a "translation" of their ancestor's military service record. It's a natural word to reach for - the record is full of abbreviations and jargon that reads like a foreign language, so it makes sense to want it "translated" into something you can understand.

But a translation and a decode are fundamentally different things, and understanding the difference matters - because it determines what you actually get at the end of the process.

What a translation does

A translation converts text from one language to another. In the context of military records, a "translation" typically means taking each abbreviation or entry and providing its plain-language equivalent. TOS becomes "Taken On Strength." SOS becomes "Struck Off Strength." GSW becomes "gunshot wound." Emb. becomes "embarked."

That's useful, as far as it goes. If you're staring at a proceedings sheet covered in abbreviations you've never seen before, knowing that "TOS 3 Trg Bn" means "Taken On Strength to the 3rd Training Battalion" is a significant step forward. The abbreviations guide on this site covers more than 150 of the most common ones and will get you a long way.

But a translation stops at the boundary of the text. It tells you what the words mean. It doesn't tell you what happened.

The gap a translation leaves

Consider a real example. Your grandmother's WAAAF record shows the following entry: "TOS No. 3 WDTS, 14.8.43. Remustered A/c Plotr, 23.10.43. Proc. to 4 F.S., 11.1.44."

A translation gives you: Taken On Strength to No. 3 Women's Depot and Training Station, 14 August 1943. Remustered as Aircraft Plotter, 23 October 1943. Proceeded to No. 4 Fighter Sector, 11 January 1944.

That's accurate. Every abbreviation is correctly expanded. But does it tell you what an aircraft plotter actually did? That she was tracking incoming aircraft on a plotting table in an operations room, relaying real-time positions to fighter control so they could direct interceptions? That No. 4 Fighter Sector was part of the air defence network protecting northern Australia at a time when Japanese air raids were a genuine threat? That she was one of thousands of women performing roles that directly influenced tactical outcomes, in jobs that hadn't existed for women two years earlier?

A translation gives you words. A decode gives you the story.

What a decode does differently

A Decode My Digger decode is a five-layer reconstruction process. It doesn't just convert abbreviations into words. It takes the entire service record - every entry, every date, every unit reference, every medical notation - and rebuilds it into a coherent account of what your ancestor experienced.

The five layers are extraction (reading the handwritten entries accurately), deciphering (converting the abbreviations), research (mapping dates and units to real events), contextualisation (explaining what those events meant for the person living through them), and narrative (assembling everything into a story a family can read).

A translation covers layers one and two. A decode covers all five.

Why the extra layers matter

Take another example. Your great-uncle's AIF record shows he was admitted to the 1st Australian Field Ambulance on 4 August 1916 with "GSW lt. shoulder, shell frag." A translation tells you: gunshot wound to the left shoulder from shell fragments. That's the medical fact.

A decode tells you that on 4 August 1916, his battalion was at Pozières on the Western Front - the middle of a six-week battle that cost the Australian divisions 23,000 casualties. It tells you that the 1st Australian Field Ambulance was the nearest medical facility to his section of the line. It places the wound within the specific operational context of that day, that unit, that battle.

Or consider a different record entirely. Your grandfather's Navy record shows he was posted to HMAS Cerberus for three months in 1941. A translation tells you the name of the ship. A decode tells you that Cerberus wasn't a ship at all - it was the RAN's primary training depot at Flinders Naval Depot in Victoria, and a posting there meant he was undergoing specialist training before being assigned to a seagoing vessel.

These aren't obscure details. They're the difference between a list of events and an understanding of what someone went through. For a closer look at the specific information a service record contains, see five things you can learn from a war record.

What you receive

Every decode produces two documents. The first is a line-by-line Excel spreadsheet - this is closer to what people picture when they think of a "translation." Every original entry on the record is paired with its plain-language equivalent in modern terminology. It's the reference document that lets you see exactly what was written and exactly what it means.

The second is the contextualised Word narrative. This is where the decode goes beyond translation. It takes the translated entries and weaves them into a chronological story of your ancestor's service, mapping each date and unit reference to real events and explaining what they meant in context. For more detail on both documents, see what you get when you decode a war record.

When a translation is enough

If you're comfortable doing your own research and you just need the abbreviations cracked, the free resources on this site may be all you need. The abbreviations guide covers the most common entries. The handwriting guide helps with deciphering the penmanship. The research guides for WWI and WWII walk you through the full process of placing a service record in historical context.

But if what you want is the finished story - your grandmother's war service reconstructed into something the whole family can read, understand, and keep - that's what a decode delivers. It's $59 per record, and it covers all three services across all conflicts from the Boer War to the Vietnam War.

Frequently asked questions

Does the decode include the abbreviation translations as well?

Yes. The Excel spreadsheet provides the line-by-line translation of every entry on the record. The Word narrative provides the contextualised story. You receive both documents with every decode.

Can I just get the abbreviation translations without the full decode?

The abbreviations guide on this site is free and covers more than 150 of the most common entries found on Australian military service records. If you want to work through the record yourself, that's a good starting point.

How is a decode different from what a genealogist does?

A genealogist is a researcher who investigates family history across multiple archives and record types. A decode is specifically focused on interpreting a single military service record in depth. The two are complementary - a genealogist can help locate the record, and a decode interprets what's on it.

Does a decode work for all services - Army, Navy, and RAAF?

Yes. Decode My Digger covers Army, Navy, and RAAF records across all conflicts. The abbreviations, administrative processes, and record formats differ between services, which is one of the reasons a decode goes beyond simple translation - each service used its own conventions and terminology.

What if my ancestor's record is from WWII, not WWI?

WWII records are fully supported. They tend to be more standardised and often typed rather than handwritten, which makes the extraction layer faster. The contextualisation and narrative layers apply equally - the decode maps the service against the events of the war regardless of which conflict the record covers.