A risk desk watches every fill from six trading desks on one screen, in real time, and cannot place a single order from it. That screen is fed by a drop copy. Retail traders use the phrase for something adjacent but different — and the overlap with trade copying is more useful than it first looks.
A risk desk sits behind glass watching one screen. On it, in near real time, is every order and every fill from six separate trading desks across three venues. The person watching cannot place an order from that screen, cannot amend one, and cannot cancel one. That is not a limitation of the software. It is the entire design.
The feed behind that screen is a drop copy, and it is one of the oldest ideas in market infrastructure: the desk that trades should never be the only source of truth about what it traded.
A drop copy is a secondary, read-only stream of order and execution activity, delivered in parallel with the primary trading connection, to a party who is not the one trading.
The name is literal. Copies of the activity are dropped off to a third party as it happens. The primary session keeps doing its job; the drop copy session simply receives a duplicate.
In practice these feeds ride on FIX, the messaging protocol most institutional order flow uses. On a primary session, a participant sends order messages — a new order, an amendment, a cancel — and receives execution reports back describing what happened to each one: accepted, partially filled, filled, cancelled, rejected. A drop copy session receives those execution reports for a designated set of accounts or trading identifiers, and typically cannot send order-entry messages at all. Exchanges operate their own versions of this — CME's drop copy service being among the best known — and brokers, prime brokers and clearing firms offer equivalents for their clients.
Four properties define the category:
Read-only by construction, not by configuration. The session is not permitted to enter orders. This is enforced at the protocol and entitlement level rather than by a checkbox someone could flip.
Out of band. It is a separate connection. If the trading session degrades or drops, the risk view does not go blind with it — and, just as importantly, a fault in the monitoring path cannot interfere with trading.
Scoped. A drop copy is configured for particular accounts, desks or trader identifiers. A clearing firm sees its clients; a risk desk sees its own firm.
Complete, not just fills. A good drop copy carries the whole order lifecycle, including rejects and cancels, not only the trades that happened. What a desk tried to do is often more interesting to a risk function than what it succeeded in doing.
The common thread is separation of duties. Every one of those functions needs to know what a trading desk did, and none of them should have to ask the desk.
TIP
The design principle transfers directly to a one-person trading operation. Any system that both executes your trades and reports on them has a single point of failure in the reporting. A read-only view fed independently of the thing doing the trading is worth having, even at a very small scale.
Search the phrase and you will find people using it for two different things, neither of which is the institutional one.
"A copy of my trades on another account." This is trade copying. Somebody wants their positions reproduced somewhere else — a second broker, a funded account, a family member's account. It is a write operation onto an account, which is exactly what a drop copy is not.
"A read-only view of my account for someone else." This is much closer to the real meaning. A mentor, an accountability partner, a risk partner in a small fund, or a firm watching an allocated account. Read-only, out of band, someone other than the trader looking at it. This is a drop copy in everything but the protocol.
The confusion is understandable: both involve a copy of trade activity going somewhere else. The distinction is whether the destination acts on it or only observes it.
Here is the framing that makes both concepts clearer, and it is not a stretch.
A trade copier is a drop copy with an execution stage bolted on the end.
Look at the provider side of any well-built copier. It connects to an account, observes positions and fills, and never places an order there. On MetaTrader that connection can use a read-only investor password — a credential that is physically incapable of trading. That is a drop copy in miniature: read-only by construction, out of band, scoped to one account.
What a copier adds is the second half: a replication policy that decides what the observations should cause, and a write path to accounts that will act on it.
Splitting the two halves in your head pays off immediately.
WARNING
If a tool asks for full trade credentials on an account you only want to observe, it has merged the two halves for its own convenience. Ask why. A monitoring function that can place orders is not a monitoring function.
You cannot get a FIX drop copy from a retail broker. You can get several things that do the same job.
Be honest about the limits of the retail version.
It is not audit-grade unless it is immutable and timestamped. An institutional drop copy is a separate record from a separate system. A read-only view of the same terminal is not independent in the same way. If the record matters — for a prop firm dispute, for tax, for a partner — it needs its own timestamped store.
It may lag. Retail read-only views refresh on the terminal's schedule, not on a wire.
It usually shows fills, not attempts. The institutional version's most valuable property — seeing rejected and cancelled orders — is largely absent from retail read-only views. If you want to know about the trades your automation tried to place and could not, that has to come from the tool's own log, which is why a skip log with a reason per trade is not an optional feature.
It cannot save you. A drop copy is a view. It has no ability to flatten a position, cancel an order or stop an algorithm. A circuit breaker is a different mechanism and every automated setup needs one regardless of how good the monitoring is.
If you are evaluating anything that claims to give you a monitoring view:
If you arrived here because the terminology of copy trading is a thicket, /blog/master-copy-meaning sorts master, provider, follower, mirror, PAMM and the rest into one glossary. And for what a live read-only control surface should actually put in front of you — instances, open copies, and every held or skipped trade with its reason — see /blog/cockpit-copy-trading.
