How to avoid common service-provider problems

Resolve unclear promises before starting

Ask what the professional will deliver, what they need from you and what is excluded. If an estimate relies on information you have not supplied, record that assumption. Pressure to proceed while scope or identity remains unclear is a reason to pause and ask for clarification, rather than filling the gaps yourself.

Use milestones with observable outputs

Break substantial work into stages you can review: a discovery memo, an approved design, a working preview or a final handover. Agree the review period, who approves and what happens when feedback is late. Tie discussions about progress to these outputs rather than relying only on informal updates.

Keep access and changes under control

Use your own organisation’s accounts where possible, grant only the access needed and avoid sharing passwords in project notes. Record changes with their impact on scope, timing and cost before approval. Keep one current version of the brief and proposal so neither side works from a superseded instruction.

Make a concern specific and actionable

If work differs from the agreement, identify the deliverable, the expected check and the observed gap. Share supporting examples and ask for a proposed next step and date. Preserve the relevant messages and versions. Use the reporting or support route that applies to your engagement when direct discussion does not resolve the issue; do not assume a particular refund or outcome.

Close the project deliberately

Review the handover before treating the project as complete. Confirm any unresolved items and the next contact point.

• Final deliverables, editable files or source code where agreed.
• Account ownership, access removal and a list of recurring services.
• Licences, documentation and instructions for routine use.
• Recorded approvals, remaining issues and the agreed support period.