For some of our production systems we like to wait a few weeks to apply updates so that they've "baked" in the public a bit. We then wait a little longer after before patching backup systems lest we have issues in production with the patches. However, since Microsoft has moved to the cumulative update model, we run the risk of having those backup systems only show the next round of cumulative updates (since more than a month had passed) when what we really want is to install the prior month's. How is that possible? How do others manage this schedule without being forced to aggressively release patches?
I'm reasonably certain that the only way to mitigate this will be to use WSUS, Systems Center, or some other sort of patch management automation. You'll need to create at least one separate group for Servers, then use whatever system you choose to deploy on the patches that you want.
WSUS has no additional licensing, so at the very least you'll be able to test this without any purchase, just time.
Cumulative updates are cumulative, meaning "containing all previous updates." There's no danger of your missing out on updates.
Additionally, Update Rollups and Monthly Rollup updates are also cumulative.