Student-to-site assignment

Assignments built on a stale roster get rebuilt. Start from the true list.

• The student roster for the term is final (adds, leaves, repeats resolved).
• Special requests and accommodations are logged privately.
• Students on away rotations are marked so they are not double-assigned.

Rules decided up front make the results defensible. Rules decided after look like favoritism.

• The assignment method is chosen (preference ranking, lottery, hybrid) and written down.
• Equity guardrails are set (e.g., caps per site, distribution across high-demand sites).
• Per-site caps from the capacity ledger are loaded — no site can be overfilled.

Fill the grid, then interrogate it.

• Every student has a site for every block.
• Conflicts and unplaced students are flagged, not silently dropped.
• Exceptions to the rules are documented with a reason.

A second pass catches what the algorithm missed — especially comparability.

• Required-experience coverage is verified for every student's assignment set (Element 8.7).
• Swap requests are triaged against the rules, not ad hoc.
• The final grid is reviewed by the clerkship director before notification.

Students, site directors, and preceptors all need the same information at the same time.

• Students are notified with their full assignment set and key dates.
• Site directors receive their student lists with rotation dates.
• Preceptors are told who is coming and when — before the student arrives.