The short answer
A change is ready when it works in the real website, not just when the code runs or AI reports success. Confirm the intended page or module changed, approved content and settings remain intact, and the result works at relevant screen sizes. Check links, forms, accessibility, and other behavior affected by the change. If you cannot verify a required outcome, keep the work in review rather than calling it done.
A closer look
Start with the purpose of the change and the parts of the site that must remain stable. Review the implementation in the correct HubSpot environment or other live destination, not only in a local editor. Compare the visible result with the approved design and content, including mobile and desktop layouts where relevant.
Then test the behavior the change could affect: navigation, links, forms, responsiveness, accessibility, and any connected module or template. A successful upload or tool response is evidence that a step ran, not proof that the visitor experience is right. Record unresolved issues and get the appropriate human approval before treating the work as finished.
