Management would like you to front-load the requirements with the most risk requirements. Why would management prefer the risky requirements first in the prioritization?

Prioritizing high-risk requirements early exposes potential project-ending failures at the point of least financial and resource commitment. If a risk event proves a requirement infeasible or causes the project to fail, the organization avoids sinking the full project budget into a doomed effort. This is a deliberate 'fail fast and cheap' strategy that protects the organization from large sunk costs on undeliverable work.

The project manager's ability to mitigate a risk event is independent of when risky requirements are scheduled - front-loading changes the timing of exposure, not the PM's risk response capacity.

Risky requirements represent threats, not opportunities - there is no reward to receive sooner, and front-loading is not motivated by benefit realization.

Having ample time to correct a problem is a rationale for early risk detection generally, but the specific driver here is minimizing sunk cost when the risk is fatal, not enabling correction.