What will the site be like to run?

Ask to see the important tasks

Choose representative examples: adding a service page, updating an opening time, changing a product option or handling an order. Ask how those tasks will work and which require a developer.

A polished mockup is useful for reviewing appearance, but a working review version is needed to check behavior.

Understand the software choices

Ask which theme and plugins are proposed, what each does and where custom code is needed. Identify licences, recurring costs and provider-controlled features. The explanation should be specific enough for the owner to understand what must be maintained.

Keep ownership explicit

Record who controls the domain, hosting, software accounts, source files and business data. Agree who approves changes and which materials will be supplied at handoff. Do not treat a shared password in a public message as an access plan.

Agree the checks before launch

• Visitors can find the important information.
• Relevant layouts work at mobile widths and with keyboard navigation.
• Editors can perform the agreed publishing tasks.
• Forms store or deliver the intended record.
• Store tests use controlled data and agreed payment-provider test methods.
• The plan covers content moves and release recovery where needed.

Discuss maintenance before the project ends

Clarify which updates, backups, monitoring and support are included and who takes over the rest. Read the development process or describe your planned site.