What should you check in the proposal?
The package name alone is not enough. Review the pages, languages, additional services, files to be provided by the client, and work that is out of scope. The currency, tax treatment, payment terms, and proposal validity must be clearly stated. If any information is missing, ask about it before accepting. Distinguish between the initial estimate in the form and the final, approved scope.
Describe revisions in an actionable way
When evaluating a draft, specify the location, the issue, and the expected outcome together. Instead of saying "it doesn't work," it is more actionable to say, "the mobile header is covering two buttons; please place the buttons on separate lines." A revision improves an existing decision; a request for a completely new page or function may constitute a change in scope. The agreement should specify the number of revisions allowed and how scope changes will be handled.
What is expected of me now?
Track the project's current stage, required materials, and approval requests via the client portal. Check the status of any files you have submitted—such as whether they are pending or undergoing security scanning. If a stage is not within your control, clarify who is responsible and identify the next checkpoint instead of sending unnecessary follow-up messages. Documenting important decisions in supporting correspondence or project records helps minimize verbal disagreements.
Your quick checklist
- Review the scope and conditions together.
- Consolidate feedback into a single list.
- Track pending approvals and files.