| Copy the form, personalize it, and send it. | Create a request with items, owner, statuses, and due date. |
| Usually lives in an email, shared document, or spreadsheet. | Keeps the request and item statuses in one current view. |
| Updated manually by the person following up. | Useful when each item needs a current status through review. |
| A person decides what to include in each follow-up. | Useful when repeated reminders should cover unresolved client-action items. |
| The team records whether a received file was accepted. | Useful when uploads need a separate pending-review and acceptance step. |
| Works when one person owns the request from start to finish. | Useful when multiple team members need the same request context. |
| Low client volume, a simple request, and one follow-up owner. | Recurring requests, several missing items, handoff, review status, or repeated reminders. |