When a detachment is attached to a host command, or two units work alongside each other, a single coin often has to represent both. The usual solution is one unit’s insignia on each face, inside a shared outline that belongs to neither of them.
When Does One Coin Represent Two Units?
This comes up far more often than the coin market acknowledges, and the people it happens to are usually working it out from scratch.
A detachment attached to a host command. The detachment has its own identity and its own chain, but it lives and works inside somebody else’s organization. Both matter, and leaving either off produces a coin that is not quite true.
A supporting unit and the unit it supports. Logistics, medical, communications, engineering. The supporting unit’s people spend their whole tour with an organization they do not belong to, and they tend to identify with both by the end of it.
Augmentees serving with a command that is not their own. Individuals or small groups filling out another unit’s strength, often from a different component or a different service entirely.
Two units on a joint exercise or a shared deployment. A defined period of working together, which is exactly the kind of thing a coin exists to mark.
A tenant unit and the installation that hosts it. Small units sitting on large bases develop a relationship with the installation as well as with their parent command.
In every one of these, the person organizing the coin faces the same question, and it is not really a design question. It is a question about whose name goes first.
How Do You Give Both Units Equal Weight?
One insignia per face. The cleanest answer and the one most shared coins arrive at. Each unit gets a whole side, undivided and uncompromised, and neither emblem has to be shrunk to make room for the other. Trying to fit two insignia onto one face almost always produces a worse coin: both end up smaller, the composition splits down the middle, and the result looks like a merger announcement.
Use a shared outline that belongs to neither. This is the part people miss. If the coin is cut to the shape of one unit’s patch, that unit has won before the artwork starts. A neutral shape, such as a generic shield with a ribbon, is common property. Both units recognize the form, neither owns it, and the object reads as shared rather than as one unit’s coin with a guest on the back.
Match the treatment, not the style. The two faces do not have to look alike, and forcing them to usually flattens both. What they do have to share is effort: the same relief depth, the same quality of finish, the same amount of the face used. A detailed sculpted front against a thin engraved back tells everyone which unit mattered more, whatever the intention was.
Then decide which face is the front, and decide it openly. This is a diplomatic question dressed as a design one, and pretending otherwise wastes everyone’s time. The conventions that help: the host command usually takes the front when a detachment is attached to it, the supported unit usually takes the front when a supporting element is involved, and the unit paying for the majority of the order has a reasonable claim either way. Agree it early, at the same time as the budget, because it is far harder to raise once artwork exists.
Why a Patch Shape Works for a Shared Coin
A shield with a ribbon beneath it is the shape of a thousand unit patches and the property of none of them. That neutrality is exactly what a two-unit coin needs.
It also brings a genuinely useful feature. The ribbon is a place to put something that belongs to both. A shared deployment name, a date range, an exercise title, the word “attached.” It gives the coin a third piece of information that sits outside the ownership question entirely, which takes some of the pressure off the two faces.
There are practical consequences to the outline. A shield is wider at the top than the bottom and usually tapers to a point, so the usable area shrinks as you go down and a centered element has to be positioned by eye. Lettering has to follow a curve that is not circular, which is set by hand rather than generated. And the point at the base takes the wear first.
Coins made to look like patches more generally, including their edge and stitch treatments, are covered on our page about coins made to look like patches.
About This Detachment Coin
This coin was made for a lettered detachment working with Madigan Army Medical Center. Madigan is at Joint Base Lewis-McChord in Washington, and we are a Washington company, so this one was made close to home.
The coin is patch-shaped, a shield with a ribbon beneath it, carrying one unit’s device on each face. The front is a black field with a skull and crossbones device picked out in silver, white and yellow paint. The reverse is an etched and painted mountain scene with a United States flag.
What makes it work is that the two faces are not trying to match. One is graphic and stark, a hard device on a flat black ground with three colors and no scenery. The other is pictorial, an etched landscape with depth and atmosphere. On most coins that mismatch would be a fault.
Here it is not, and the reason is worth understanding: each face is given the whole coin. Neither is a panel, neither is squeezed around the other, and both use the full area and the full range of technique available to them. Equality on a shared coin is not about similarity. It is about neither side being asked to make room.
See another Joint Base Lewis-McChord project on our page about the 7th Infantry Division coin, medical unit conventions on our page about military medical unit coins, and the same shared-coin problem across sectors on our page about a coin shared by a company and a government body.
Can We Use Both Units’ Insignia on a Coin?
Two sets of insignia means two permissions, and that is the part most people underestimate.
Unit insignia, command emblems and installation devices are controlled by the organizations that own them, and the rules differ between branches and between commands. A detachment being attached to a host command does not give either one authority over the other’s marks.
The practical version is straightforward. Clear the artwork through both chains of command before you order, and send us artwork each organization is authorized to supply. We produce from what the customer provides and we do not grant permission on anyone’s behalf. Start this early, because two approvals take longer than one and they rarely run in parallel.
Design a Coin for Your Detachment
A shared coin usually means a shared order, so agree the split before you order rather than after. Who is paying for what, how many each unit takes, and which face is the front are all easier conversations to have at the start.
Professional artwork is free with unlimited revisions, and nothing goes into production until you approve a digital proof, which on a two-unit coin means both parties should see it. The minimum order is 50 coins, standard production runs about 45 to 50 days after final artwork approval, rush production is available on many projects, and shipping within the continental United States is included. Embleholics is veteran-owned, SDVOSB and registered in SAM.gov. See more custom Army challenge coins or request a quote to get started.
Frequently Asked Questions
Can one challenge coin represent two units?
Yes, and it is a common requirement for attached detachments, supporting units, augmentees and joint exercises. The usual solution is one unit’s insignia on each face inside a shared outline, rather than trying to fit both emblems onto a single side.
Whose insignia goes on the front?
There is no fixed rule, so agree it early. Conventionally the host command takes the front when a detachment is attached to it, the supported unit takes the front when a supporting element is involved, and the unit funding most of the order has a reasonable claim either way.
Can an attached detachment have its own coin?
Yes. Attached detachments frequently produce coins carrying both their own insignia and the host command’s, which records where they served as well as who they belong to. A detachment can also order a coin of its own with no host insignia at all.
Do you need permission from both units?
Yes. Each organization controls its own insignia, and being attached to a host command grants no authority over that command’s marks or the reverse. Clear the artwork through both chains of command before ordering, and allow extra time, since two approvals rarely run in parallel.
Can a coin be shaped like a patch or a shield?
Yes. A shield with a ribbon beneath it is a common custom shape and a good choice for a shared coin, because both units recognize the form and neither owns it. The ribbon also provides a natural place for a shared date, deployment or exercise name.
Can the two faces be designed differently?
Yes, and they often should be. What matters is that each face gets the full coin, the same relief depth and the same quality of finish. A detailed front against a thin reverse signals which unit mattered more, regardless of intent.
Who pays for a shared coin?
That is agreed between the units, and it is worth settling before the order is placed. Common arrangements are an even split, a split by headcount, or one unit funding the order and the other buying its allocation back. The funding split often influences which face leads.
What is the minimum order for detachment coins?
The minimum order for custom challenge coins is 50 coins. On a shared order that total is usually split between the two units, and larger quantities reduce the cost per coin for both.
More Special Operations Projects
