How do you manage client requests during the QA phase?

I think it's essential to be clear about billing. If a change isn't in scope, it should definitely be a billable change. Even if it is in scope, I let clients know they are incurring costs and that it might delay delivery. If it's a significant change, I recommend scheduling it for post-release to properly manage expectations.

I usually tell clients, "I'm sorry, but during the QA phase, we can’t add any new features to avoid bugs being included in the final product." This has worked well for me because it frames the decision with a focus on quality.

In Germany, we tend to include clear terms in our offer, stating that any changes exceeding the project price by around 10-15% will incur additional charges. Clients who understand this will usually accept that their new requests come with a cost. If you have clients that don’t get this, it might be time to reevaluate who you work with!

If it's during the UAT period, I'm pretty limited, but afterward, I charge a flat fee for unlimited minor changes as long as they’re reasonable.

For smaller changes, like a text tweak, I might let it slide, but if a client frequently requests changes that seem outside the scope, I push for a proper quote to be issued.

You need to set clear boundaries right from the start. Create a detailed project scope that emphasizes that the QA phase is for bug fixes alone, not new features. If you clearly outline this in a contract, you can gently redirect clients back to the original scope when they make new requests. Also, it can help to implement a change control process where all new requests go through a formal approval stage to estimate time and costs.