counter-screen
After a primary screen flags some hits, a counter-screen is the second test you run specifically to catch cheaters — compounds that scored not because they hit the intended target, but because they fooled the assay or hit something they shouldn't. It is the control question asked in reverse: instead of 'does it work?', it asks 'is it working for the wrong reason?'
Counter-screens come in a few flavors. An artifact counter-screen looks for interference with the detection system itself — for example, running the readout chemistry without the target to catch compounds that quench fluorescence or interfere with the signal. A selectivity counter-screen tests the hit against a closely related off-target (such as a sibling enzyme) to flag promiscuous binders. A counter-target screen checks activity against a protein whose inhibition would be undesirable or would explain a phenotype trivially.
By design, a hit should be active in the primary screen and inactive in the appropriate counter-screen; a compound that lights up in both is almost always an artifact or a non-selective binder and gets deprioritized. Counter-screens are a core part of hit confirmation and triage, turning a raw, noisy hit list into a smaller set of compounds that are real and on-target.
Hits from a fluorescence-based enzyme screen are run through a counter-screen lacking the enzyme; compounds that still produce a signal are exposed as optical interferents and dropped.
A counter-screen exposes compounds that scored by interference rather than real target engagement.
The logic is inverted from a primary screen: here, activity is the bad result. A clean hit is potent in the primary assay yet silent in the counter-screen — the opposite pattern usually means artifact or lack of selectivity.