Include a Patch Tuesday Phases template that can create both even and odd month ADR's to eliminate patching gaps
For those that use phases (test, pilot, production) for monthly software update deployments with multiple collections before deploying to production, two ADR's that run every other month need to be created (one for odd months and one for even months) with deployments for each patch phase, otherwise there are potentially multiple week gaps in patching the environment. Guidance on configuring even and odd ADR's should also be added to the ConfigMgr online software update documentation.
After further testing, if choosing "Create a new Software Update Group," instead of "Add to an existing Software Update Group," new deployments are created (with previous months deployments remaining) which removes the need for even and odd month ADR's. An auto delete setting would be beneficial of old software update deployments that could be customized (e.g. deployments older than 60 days).