We do this as well (we use the Reviewer role rather than Requestor as it
is broader). We've also created dashboards on layout templates so when a
Reviewer logs in they start with tasks due near term, issues assigned to
them with last updates, longer term activities, documents for them to
approve, etc. We use issues heavily as the reviewer can change statuses
there so most of their interaction is on issues rather than tasks. It is
very effective for those project team members who are only on one ...