Revision
It's important to have a clear understanding of how revisions work when working with a freelancer. Simply assuming and not comprehending the revision process can lead to a frustrating journey.
When clients ask about how many revisions come with a package, it suggests that they anticipate a certain number of mistakes might happen in their projects. Why would I want to provide my services if they come with mistakes? I encountered clients who kept changing their minds, and every time they did, they hadn't been properly screened. They thought it was just a small tweak and didn't see it as a revision round. Due to this, both of our time management suffers as a result.
Why revisions are not included in our package
- Revisions are different in duration and complexity.
- To avoid project delays by having changes that were not well-considered.
- To maintain efficiency. Here is something that you might not consider ahead of time, but your designer surely will: a landing page for RM2,000 (for example) may seem like a fair price for both parties, but if that page takes 1,000 drafts, then it might not be such a profitable use of your designer’s time, after all. To avoid this circumstance, it's important to make sure you have the right type of information collected for the designer prior to starting the project.
Debunking common misconceptions about revisions
Myth #1: I can use revision phase to change however I want to.
Fact: If you can make any changes you want, your goal and purpose for the project will be completely meaningless, unless the changes are in line with the project's goals. All request will be evaluated to be approve or decline before moving forward.
Myth #2: I can request for unlimited revisions.
Fact: We are not running a charity so any changes / additions not due to the fault of designer will be billed to the Client as an additional and separate charge.
Myth #3: Revisions don't change deadline.
Fact: The deadline changes with every revision.
How revision works
The following is a guide for clients on how to provide designers with constructive feedback that will help them understand their demands better, decrease the number of errors caused by miscommunication, and save you both time and money. Any change request must be done with the feedback tool. Please provide a constructive feedback with a reason to support your change request.
For example, if you provide feedback on a specific component of a project that you believe doesn't work correctly you should be prepared to explain why, just as you should identify design issues rather than advising the designer on how to accomplish the work. The designer can then propose an improvement to the problem.
Broad feedback such as, "I don't like the color you chose," is not helpful. On the other hand, if you share, "I don't like the color you chose, because it's not accessible," then you're explaining your reasoning and providing the designer an actionable improvement.