Get Upcoming Reviews

The company's review schedule: one row per active vendor, carrying its last completed review, its inherent risk and assignees, the next assessment date derived from its review key dates, and whether the last one went by unassessed.

Every active vendor is a row, not just the ones with a date scheduled — "which vendors have fallen off the calendar" is as much of the question as "what is coming up", and a vendor with no review key date has no other way to surface. Rows are ordered overdue-first, then soonest, then undated.

entity_type scopes the schedule to the active view mode's relationships, as on GET /vendors/options — the sibling views scope by review type, but a row here is a vendor, so the mode's entity scope is what separates Vendor Management from Fintech Partners.

Unpaginated, like GET /vendors/options and GET /thirdparties/key-dates/all: the scope is one row per active vendor, and the column the view is read by — the next assessment date — is a per-key-date recurrence computed in Python, so it can't be ordered or paged in SQL.