Revisions

The revision system allows buyers to request changes or improvements to delivered results.

Understanding how revisions work helps you provide excellent customer service and maintain high satisfaction rates.

Overview

When a buyer receives results from your AI Tool, they may request revisions if the output doesn't fully meet their needs.

This creates a collaborative process to ensure buyer satisfaction.

Revision states

Orders with revision requests progress through these states:

Revision Requested

• Status – "Revision Requested" (displayed in blue/yellow)
• What it means – Buyer has asked for changes to the delivered results
• What you see – Order appears in "Order Attention" with revision details
• Your action – Review the request and decide whether to accept or decline
• Timeline – Consider responding within 24-48 hours

Revision In Progress

• Status – "Revision In Progress" (displayed in blue)
• What it means – You've accepted the revision request and are working on changes
• What you see – Order shows you're actively working on the revision
• Your action – Complete and upload the revised results
• Timeline – Deliver within 24 hours when possible

Revision Ready

• Status – "Revision Ready" (displayed in green)
• What it means – Your single revision has been provided to the buyer
• What you see – Revision timeline shows completion
• Buyer action – Buyer reviews revised results
• Next steps – Order completes after 7-day review period (no further revisions allowed)

Revision timeline

The order detail page shows a simple timeline of revision activity (limited to 1 revision):

1. Original delivery – Initial results sent to buyer
2. Revision request – Buyer explains what needs improvement
3. Revised results – Your single updated output delivered to buyer
4. Order completion – Order automatically completes after 7-day review period

Providing revisions

Review the request

Before starting work, carefully read the buyer's revision request:

• Specific issues – What exactly needs to be changed
• Expected outcomes – What the buyer wants to achieve
• Scope of changes – How extensive the revisions need to be
• Deadline expectations – Any time constraints mentioned

Revision workflow

1. Click "Provide Revision" – Access the revision interface
2. Upload improved results – Same format as original delivery
3. Add revision notes – Explain what you changed and why
4. Submit revision – Deliver updated results to buyer

Revision best practices

• Address specific feedback – Focus on the exact issues raised
• Maintain quality standards – Don't compromise overall quality
• Document changes – Clear revision notes help buyer understand improvements
• Test thoroughly – Verify revisions actually fix the issues

Types of revision requests

Quality improvements

• Common requests – More detailed analysis, better formatting, additional insights
• Response approach – Enhance the depth and quality of your output
• Example – "Can you provide more specific SEO recommendations?"

Formatting changes

• Common requests – Different file format, layout adjustments, styling improvements
• Response approach – Reformat results while maintaining content quality
• Example – "Can you deliver this as an Excel file instead of CSV?"

Scope adjustments

• Common requests – Focus on specific aspects, include additional data points
• Response approach – Adjust analysis scope within reasonable bounds
• Example – "Can you focus more on mobile SEO issues?"

Error corrections

• Common requests – Fix incorrect data, resolve processing errors
• Response approach – Identify and correct the underlying issue
• Example – "The competitor analysis shows wrong pricing data"

Revision policies

What you should revise

• Quality issues – Results that don't meet your stated standards
• Processing errors – Technical problems that affected output
• Scope misunderstandings – Legitimate interpretation differences
• Format preferences – Reasonable output format changes

What you might decline

• Scope expansion – Requests that significantly exceed your AI Tool's description
• Unreasonable demands – Changes that aren't technically feasible
• Input-related issues – Problems caused by inadequate buyer inputs

Managing your single revision

Making the most of your revision

• Address all feedback – Since you only get one revision, address all points thoroughly
• Quality over speed – Take time to deliver a comprehensive revision
• Communicate progress – Update buyer on complex revision work
• Learn for next time – Use insights to improve future AI Tool descriptions

Revision policy

• Platform limit – Only 1 revision allowed per order
• Set expectations – Clearly communicate revision limitations in AI Tool descriptions
• Quality focus – Prioritize getting results right the first time
• Support available – Contact support for complex revision situations

Common revision scenarios

SEO audit revisions

• Request – "Can you provide more specific mobile optimization recommendations?"
• Response – Add detailed mobile SEO section with specific fixes
• Notes – "Added comprehensive mobile optimization section with 12 specific recommendations"

Product research revisions

• Request – "The competitor data seems outdated, can you refresh it?"
• Response – Re-run analysis with current data sources
• Notes – "Updated all competitor pricing with data from [current date]"

Content creation revisions

• Request – "Can you make the tone more professional and less casual?"
• Response – Rewrite content with adjusted tone and style
• Notes – "Revised all copy to use professional business tone while maintaining readability"

Tips for revision success

• Respond quickly – Acknowledge revision requests within 24 hours
• Ask clarifying questions – If requests are unclear, ask for specifics
• Set expectations – Communicate timeline for revision delivery
• Document everything – Keep detailed notes on changes made
• Learn and improve – Use revision feedback to enhance future outputs
• Stay professional – Maintain positive communication throughout

Preventing revisions

• Clear descriptions – Detailed AI Tool descriptions reduce misunderstandings
• Good examples – Portfolio images set proper expectations
• Quality inputs – Validate buyer inputs to ensure good results
• Thorough testing – Test your automation with various input types
• Realistic ETAs – Accurate timing reduces rushed, lower-quality outputs