1. Agencies PM
  2. Features
  3. Revision Requests
Feature · Revision Requests

Revision Requests

Track client and studio feedback from first report through verification.

OverviewRevision Verification
Agencies PM · Revision Requests

Revision Verification

Revision requests

New
Request numberTitleProjectOwnerStatus
RR-39359Fixed rr-759PRJ-7989Fixed
RR-83655Fixed rr-410PRJ-2059Fixed
RR-31063Fixed rr-996PRJ-8008Fixed
RR-35821Fixed rr-179PRJ-4587Fixed
RR-73958Fixed rr-354PRJ-4555Fixed
6 of 6 records
Fixed rr-759Revision requests · RR-39359
Fixed
ProjectPRJ-7989
Example screen with sample data

What you can do

Revision Requests in daily delivery

Track client and studio feedback from first report through verification. A contributor records the request title, client project, severity, note and owner. Open requests enter the triage workflow. When an open request has severity, the workflow changes it to Triaged and writes an operation receipt. An attempt against a request in another state, or without severity, is blocked and also recorded.

How the work is organized

  • Capture the request. Record feedback, severity, owner and project while the client change is still clear.
  • Triage from Open. A request with severity moves to Triaged and leaves an operation receipt.
  • Verify the result. Follow the owner through in progress and Fixed before a person marks the work Verified.

A client asks for a revised headline on a campaign asset. The studio records the feedback on the related project, marks severity and assigns an owner. After triage, the contributor works it through in progress and Fixed. The project manager checks the result before marking it Verified and eventually Closed.

What to agree during setup

Agree who may raise a request, who decides severity, and who verifies the work. Use the project reference to keep feedback with the right engagement. Decide what evidence belongs in the feedback note or attached file, and when a request becomes a task in the package plan. Agree who raises requests, who chooses severity and who verifies completed work. Decide when a request also needs a task in the package plan. Keep feedback and attachment references with the same project so the reviewer can inspect the original request.

Check the handoff on an actual case

Rehearse an Open request with severity and confirm it becomes Triaged with a successful receipt. Try one without severity and one already Triaged; both should remain unchanged and leave a failed receipt. Then move a fixed request to verification and make sure the owner and client project stay visible. Submit an Open request with severity and inspect its successful triage receipt. Repeat without severity, then retry after the request is Triaged; each attempt should leave the request unchanged and record failure. Once work is Fixed, the project manager checks the result before marking it Verified.

What your team sees

  • Open Revision Requests — Lists active feedback with severity, project and owner.
  • Delivery Exception Queue — Points to Fixed requests still waiting for verification.

Follow the work through

Follow revision triage for the guarded move from Open to Triaged. Use studio delivery when the revision creates task work.

What it keeps track of

Data model
Revision requests
Client and studio revision requests raised against project work, with severity, status, reporter note and owner.
Projects
Engagements delivered for an organization, with budget and schedule.
Team members
Delivery staff with role, practice and weekly capacity.
Operation receipts
Evidence that a delivery operation was executed.

Who uses it

Permissions
Project Manager
, Studio Contributor, Client Reviewer keep feedback attached to the client engagement.
The Studio Contributor records and resolves it; the Project Manager checks severity and verifies the result.

Set up Agencies PM your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started