Small correction
Typo fixes, minor wording swaps, broken links, tracker field renames, or small layout clarifications.
Client revision control
This form keeps every post-delivery change clear. The client points to the exact file, section, or line, explains the requested change, and the request is classified as included, needs clarification, add-on, or declined before any work starts.
Classification
Typo fixes, minor wording swaps, broken links, tracker field renames, or small layout clarifications.
Conflicting comments, missing replacement assets, unclear examples, or a request that points to no exact section.
New pages, new funnels, new content batches, new platform setup, new design direction, or extra automation.
Guaranteed sales, fake engagement, account-risk behavior, unlimited revisions, or off-platform risky actions.
Request fields
The exact delivery room or file package where the request belongs.
Page name, tracker tab, content row, screenshot, or paragraph that needs attention.
What is there now, what should replace it, and whether a new asset is attached.
Why the change matters, the ideal deadline, and whether it changes the agreed scope.
24-hour flow
Log the request, check if it points to an exact deliverable, and ask one clarification if needed.
Mark it as included, clarify, add-on quote, or declined before touching the files.
Apply included edits, update the delivery room, and record what changed.
Client copy
Please send revisions through the revision request format: delivery room URL, exact file or section, current text/screenshot, requested change, reason, priority, and whether it changes the original scope. I will classify it as included, needs clarification, add-on quote, or declined before making changes.