Start with the specific disagreement
For a website-development dispute, build a list of the functions and handover items that are missing or differ from the specification. A site can look finished while an important workflow is incomplete. Conversely, a new feature request can be mistaken for a defect. Test against agreed acceptance points and describe the gap in terms another person can reproduce.
Work through the facts, one step at a time
Identify the agreed version
Use the accepted specification, wireframes and change approvals. Note the expected pages, forms, integrations and supported devices. Separate anything added after that version from the original delivery requirement.
Record reproducible issues
For each problem, describe the page, action, expected result and actual result. Include a screenshot or short recording without personal customer data. Distinguish a broken agreed function from a preference about appearance or a request for a new capability.
Agree completion and handover
Prioritize the issues needed for a usable delivery. Specify who tests corrections and how hosting, domains and access will be handled. Keep payment, ownership and ongoing maintenance questions explicit rather than assuming launch settles them all.
What this can look like
A booking site displays correctly, but the form never sends a confirmation. A test record identifies the exact submission and missing result. That provides a concrete correction task, unlike a general statement that the whole site is unusable.
This is an invented scenario to explain the approach, not a customer result or a prediction of your outcome.
Records worth gathering
- Accepted specification
- Approved changes
- Reproduction steps and screenshots
- Domain and hosting ownership records
Keep originals and prepare copies of the relevant parts. Redact unrelated personal details before sharing. Explain any gaps in the record rather than filling them with assumptions.
Open a clearer conversation
Edits stay on this page and are lost when you leave. Nothing is sent automatically. This is a discussion starter, not a legal notice or settlement agreement.
Before you agree to the next step
Do not share live customer data, passwords or private access tokens as evidence. Use a safe example and secure account-transfer processes.
Put any proposed outcome into specific terms: who will act, what they will do, the amount if money is involved, and the date. Identify what remains unresolved. An invitation, a discussion and a signed agreement are different stages.
Is a new feature a defect?
Not necessarily. Compare it with the accepted specification and approved changes. A feature can be useful without having been part of the original scope; discuss its delivery and price separately.
A private place to prepare your side
SettleBetween provides private AI guidance for each person and a shared space to discuss approved information. You choose what to share and whether to agree. Availability depends on both parties’ locations and the dispute type.
Free to start. The case starter pays $79 only after both parties sign. The invited party never pays the agreement fee. See included access and pricing.
Prepare your side freeAI can make mistakes. This guide is practical preparation, not legal advice. Use appropriate official schemes or independent advice when needed. A discussion here does not pause external deadlines or guarantee payment.