How to write technical project acceptance criteria to avoid rework?

Rework in technical projects often isn't because development is slow, but because the acceptance criteria were too vague from the start. Requirements like "synchronize customer data," "generate reports," or "support permission control" sound clear, but upon delivery, you realize the client expected historical data cleaning while development only did incremental sync, and QA tested against a…