Skip to main content

New: Cross-Block Request Banning

We’ve added a new setting designed specifically for PGME organizations: Cross-Block Request Banning.

Marianela Davalos avatar
Written by Marianela Davalos
Updated this week

This new setting allows you to prevent residents from submitting requests that span across different academic blocks, even if those blocks haven’t been published yet. It helps:

  • Maintain consistency in request periods

  • Avoid scheduling conflicts across block boundaries

  • Ensure requests align with strict academic periods

How It Works

When Cross-Block Request Banning is enabled:

  • The system automatically blocks any request that crosses into another academic block

  • This applies regardless of whether the blocks are published

  • Residents attempting to submit a cross-block request will see a red warning message explaining the issue and prompting them to split the request across two blocks

Who Is This For?

This setting is available only for Postgraduate Medical Education Organizations. It gives administrators an added layer of control over how and when availability requests can be submitted, especially useful in structured academic scheduling environments.

Did this answer your question?