Start with the outcome
Write one sentence explaining who the website serves and what visitors should do, such as Australian customers learning about a service and sending an enquiry. A clear outcome helps providers prioritise pages, content and features.
1. List the pages
List the home, services, work examples, about and contact pages you need. Mark which require Chinese and English, and estimate the number of articles, services or products.
2. Assign responsibility for content
Clarify who supplies copy, translation, images and video. Mark missing materials and allow time for your review rather than assuming everything will be available when development begins.
3. Define the required features
Separate launch requirements from later ideas. For forms, search, booking or accounts, describe the behaviour you need. If sharing a reference website, point to specific features rather than asking for a complete copy.
4. Describe the existing setup
Explain whether a domain, hosting account or current website already exists, and what needs to be migrated. Share system names and scope at enquiry stage; keep passwords and customer data out of public briefs.
5. Include mobile and bilingual checks
Agree the screen sizes and browsers to check, and whether language switching should keep visitors on the equivalent page. Include navigation, forms, error messages and email templates in the language review.
6. Set acceptance criteria
Turn broad expectations into checks: working pages and links, useful form validation, no horizontal overflow on phones, and agreed features completing their intended flow. Actual email delivery, account and payment tests need suitable environments.
7. State budget and timing
Specify currency, a budget range, target launch and any fixed deadline. Ask providers to identify inclusions, additional costs, tax treatment and payment terms, as well as the effect of delays in supplied materials.
8. Agree the handover
List editable files, account ownership, backups, operating notes, third-party subscriptions and support after launch. Distinguish later feature changes from correction of agreed defects.
Turn the checklist into a brief
Use the 51JOB project tools to prepare a draft, then review and post it. Project payments are arranged directly between the parties. Ask about scope and fees before requesting optional platform support.