Handling Revisions

Overview

Revisions are a normal part of the creative process. This guide helps you handle them efficiently while maintaining good client relationships.

Receiving Revision Requests

Notification

When a client requests revisions:

1. You receive an email notification
2. In-app notification appears
3. Delivery status changes to "Revision Requested"

Reviewing Feedback

1. Go to the delivery
2. Click View Feedback
3. Read all comments
4. Note specific file requests

Figure 1: Viewing client feedback

Responding to Revisions

Step 1: Acknowledge

Let the client know you received their feedback:

1. Go to the delivery
2. Click Reply
3. Send a brief acknowledgment
4. Set expectations for timeline

Example response:

"Hi! I've received your feedback. I'll have the revisions ready by [date]. Let me know if you have any questions."

Step 2: Make Changes

1. Review each feedback item
2. Make the requested changes
3. Save your work

Step 3: Upload New Files

1. Go to the delivery
2. Click Upload Revision
3. Add new files
4. Add notes explaining changes
5. Send for re-approval

Step 4: Follow Up

After sending revisions:

1. Confirm with client
2. Offer to clarify anything
3. Wait for approval

Common Revision Types

Revision Limits

Your Plan Limits

Setting Client Expectations

Include revision terms in your contracts:

• Number of revision rounds included
• Time limit for requesting revisions
• Additional costs for extra revisions
• What constitutes a revision vs. new work

Revision Communication

Best Practices

1. Be specific - Ask clarifying questions if needed
2. Stay professional - Keep tone positive
3. Document everything - Save all correspondence
4. Set timelines - Agree on revision deadlines
5. Limit rounds - Define how many rounds are included

Handling Difficult Situations

Client wants changes outside scope:

1. Acknowledge the request
2. Explain what's included in the project
3. Offer to add scope for additional fee
4. Document the agreement

Client is unclear about what they want:

1. Ask specific questions
2. Provide examples
3. Schedule a call if needed
4. Get written confirmation

Revision Tracking

Activity Log

Track all revisions:

• When feedback was received
• What changes were made
• When revisions were sent
• Client's response

Version History

Keep all versions:

1. Name files clearly (v1, v2, v3)
2. Store all versions in project folders
3. Archive old versions when complete

Best Practices

1. Respond promptly - Acknowledge within 24 hours
2. Be proactive - Suggest improvements if appropriate
3. Communicate clearly - Avoid jargon
4. Set boundaries - Define what's included
5. Stay organized - Keep track of all changes

Next Steps

• Track approval status
• Manage project folders
• Set up notifications