Безопасная сделка - Гарант

Design revision disputes how to distinguish defects from new scope

When a designer requests extra payment for revisions, compare each disputed request with the agreed brief and approved version. Distinguish a missed requirement, a clarification within existing scope and genuinely additional work. Record the evidence and proposed action for every item. This lets the parties accept an undisputed milestone without treating every disagreement as a rejection of the whole project. There is no universal number of free revisions: the answer depends on the transaction documents, agreed process and applicable law.

Establish the brief that both sides will use

Collect the original specification, approved changes and the last accepted concept. Do not create a replacement brief after delivery and treat it as the original instruction. If a decision was made verbally, write a summary and ask the other party to confirm it. Where memories differ, preserve both positions instead of reporting one as an established fact.

Consider an illustrative purchase of five mobile application screens. Adding a sixth screen and restoring a previously specified button on one of the five are different requests. The first may expand scope, while the second may address a missed requirement. The example demonstrates a comparison method rather than deciding a real dispute without its documents.

Identify the output purchased at the current stage. A concept, visual screen set, component library and development handover are distinct deliverables. The phrase application design does not by itself establish whether responsive states, editable source files or every error message was included. Acceptance should follow the actual stage rather than an idealised complete package introduced later.

Replace general dissatisfaction with an issue matrix

For each issue, record an identifier, object and version, relevant requirement, observed result, category, evidence and proposed action. Feedback such as make it better does not identify a reproducible task. A useful entry might state that named components do not use the approved palette or that an agreed error state is absent from a specified screen.

Use a deviation category when the delivered item conflicts with an existing measurable requirement. Use clarification where an incomplete instruction supports different interpretations. Use scope change for a new screen, a new user journey or replacement of an already approved concept. These are negotiation tools, not legal classifications that automatically resolve every contract.

Keep a needs-evidence category. A claim that type is too small needs a viewing context and the requirement being applied. If accessibility is part of the purchase, specify the actual agreed standard and criteria. Do not invent a compliance promise after delivery or claim a particular standard was met without checking its requirements.

Work through six review actions

  1. The client freezes the received design version and lists comments without modifying the delivered original. The designer receives the same evidence pack. Both sides identify the person authorised to consolidate feedback so conflicting instructions from several stakeholders do not masquerade as one brief.
  2. The designer responds to every issue, accepting a deviation, requesting clarification or proposing additional scope. Each disagreement refers to a particular instruction or approval. A blanket statement that all changes cost extra is no more useful than a blanket statement that nothing is acceptable.
  3. The parties agree uncontested corrections and a delivery sequence. For disputed items, they record both positions and the missing evidence. A disagreement should not erase previously agreed requirements or transform an unpurchased feature into a free obligation.
  4. For additional work, the designer proposes price, timing and effects on subsequent milestones. The client decides whether to commission it now. If the change revisits accepted screens, state that explicitly so the additional charge is attached to a new instruction rather than a second bill for the same deliverable.
  5. The designer supplies a revised version with a change log. The client checks the relevant issues and connected elements. Acceptance names that version, rather than a live link whose contents may continue to change after the decision.
  6. The authorised client representative records what is accepted, what remains disputed and what additional work has been ordered. Payment follows the agreed arrangement. If partial release may be needed, establish its permitted basis before funding a payment intermediary.

Allocate milestone value without arbitrary arithmetic

Imagine an entirely hypothetical project priced at 1,200 accounting units: research at 200, concept at 300, screen set at 500 and file preparation at 200. These figures are teaching assumptions, not a market quotation. A dispute about the screen set does not automatically erase the value of research and concept work that was separately accepted.

Equally, dividing the screen-set price by the number of screens may misrepresent the work if one screen contains most of the interaction design. For partial acceptance, define commercially independent outputs and their value in advance. Where that structure was missing, negotiate a settlement allocation rather than presenting a convenient division as the other party's pre-existing obligation.

Associate accepted outputs with file identifiers and permitted use. Commercial acceptance, delivery and licensing may have different contractual triggers. Do not assume a partial payment automatically authorises a disputed advertising campaign or every future reuse. Determine what the actual agreement permits and obtain specialist advice where rights materially affect the proposed use.

Know when to pause full acceptance

Pause when the final file set is missing, the candidate version cannot be identified or the supplied document is being changed without a traceable record. Also verify that the person approving the work can act for the customer. A designer should not be expected to reconcile incompatible final instructions from people whose authority has not been settled.

A difference in artistic preference is not itself evidence of bad faith. A shade may be disliked even though no objective colour requirement was agreed. Examine the decision process and previously approved concept. An independent reviewer is most useful when asked a specific question tied to the brief, rather than asked to declare one side generally right.

Repeated demands to replace an accepted concept without a change order can expand the project indefinitely. The reverse problem occurs when a supplier charges extra to restore an explicitly specified element. Apply the same matrix to both situations: original requirement, delivered version and identifiable difference. Consistency makes the eventual payment decision easier to explain.

Handle the common breakdowns

If instructions conflict, the designated client representative chooses a consolidated instruction and confirms the timing consequences. If approval is buried in chat, build a chronology with references to the original messages. Keep enough context to show what was accepted and any condition attached to that acceptance.

If the designer disappears after partial delivery, preserve files, payment records and a list of outstanding objects. Use the notice route in the contract when pursuing the matter. If the client stops responding, the designer records delivery and follows the agreed reminder procedure. Silence cannot be treated universally as acceptance or rejection without examining the governing terms.

Set the next payment trigger before work resumes

Define the next stage's deliverable, delivery format, review window and accepting person. Add a process for reasoned objections and a separate route for new instructions. A conditional payment arrangement can connect release to an agreed event, but it does not automatically turn an operator into an artistic expert or determine every legal disagreement.

Review the published service questions when selecting an operator, and ask separately how a disagreement about a design brief would be handled.