Setup checklist: separate assignment from accountability
ManyRequests supports request assignment and followers. Our operating distinction is that followers need visibility, while an accountable owner ensures the next action happens. Several people can contribute without all being responsible for deciding what is next. Record who handles the brief, who produces the work and who can approve a client commitment. Do not assume an assignment alone communicates every one of those responsibilities to the people involved.
Give the backup enough context
A backup needs the current approved brief, the latest version, the outstanding question and the next promised update. A folder full of assets without this context is not a usable handoff. Use one short note attached to the existing work record rather than scattering instructions through private messages. Include a link to the accepted scope so the backup does not have to infer it from the most recent client comment.
Avoid broad access as a shortcut
Someone covering one request may not need billing access or visibility into every client. Review the current role and permission documentation before granting access. Do not share another employee’s login to make coverage easier. If the system cannot express the narrow role you need, document the limitation and choose an approved alternative rather than quietly exposing more information. This is a process recommendation, not a security certification of any product.
Test the handoff with one question
Ask the backup: “What would you do next, and what are you not authorized to change?” If the answer is unclear, improve the note before the original owner becomes unavailable. When responsibility transfers, preserve the old comments and decisions. A clean-looking new request can be less useful than a complete existing record. The goal is continuity for the client, not simply reducing the number of names on the screen.
Sources used for this page
These records support the facts and comparisons above. Merchant-controlled records are labelled so you can separate product claims from independent evidence.
- ManyRequests managing requests and exporting data — Merchant documentation · help.manyrequests.com · Merchant-controlled · checked 2026-09-19
- ManyRequests admin, client and team permissions — Merchant documentation · help.manyrequests.com · Merchant-controlled · checked 2026-09-19