What if service work does not go to plan?

Check the scope, milestones, included revisions, and the completion path recorded for the affected work. A preview approval, final handover, and Buyer-reviewed completion have different consequences. Keep the concern in the Deal and act within the applicable review period while the affected amount is still protected.

Compare the request with the recorded deliverables and exclusions. Distinguish correcting a promised requirement from using an included revision and from adding new work. Discuss the difference before the Seller starts the extra work.

For example, a Deal for a logo does not automatically include a full website because the Buyer asks for it later. Use the available process for any proposed change. A separate message does not rewrite the accepted Shyld Agreement, and refusing extra work is not the same as failing to deliver what was promised.

Check the agreed due date and the next action available for that stage. Record what is missing and discuss any proposed next step through the Deal. Do not approve an incomplete stage merely to keep the project moving.

If the work is not being fulfilled, use the applicable concern or Dispute path before releasing the affected amount. A missed deadline does not let support invent a financial outcome. Follow any predefined completion or resolution conditions, and request assistance if you cannot tell which action applies.

Review it against the scope and describe the requested change precisely. Use the available revision or correction path and check the included allowance. A missing promised requirement is different from a new preference.

Ask for the change before authorizing a preview that carries a release consequence. For example, if the agreed design includes a specific colour version and it is missing, identify that requirement. Do not approve first on the assumption that the final handover will always offer another financial review.

An unanswered preview is not approval. Its review period can become overdue, but silence does not replace the Buyer's required authorization. Check the Deal for the available follow-up or support step.

This differs from a preview the Buyer already approved with their release passcode under an agreement that releases funds at final handover. That authorization can allow release when the final agreed work is handed over on time. Check the actual approval and completion conditions rather than treating all unanswered messages the same way.

Keep the promised file list and the missing or late deliverables clear in the Deal. When preview approval authorizes release at final handover, the final work must meet the agreed handover conditions within the accepted deadline. Late handover needs renewed Buyer authorization.

Use the action shown for the affected stage. If the amount is still protected and a Dispute is available, raise the concern within the applicable window. Do not authorize final release to fix a file-access problem without first reading the consequence of that action.

The release sequence still applies. A later stage cannot skip an earlier unresolved milestone. Check which stage is currently waiting for review, handover, or a resolution step.

Approving a preview for one milestone does not approve the whole project. A timely, valid handover that was already authorized may wait for the earlier stages without needing another approval when its turn arrives. Keep the discussion tied to the specific stage so neither participant mistakes readiness for completed release.

After a handover that releases funds under your earlier preview approval, use the access-care request available during the period shown in your Deal. Open and save the files promptly, identify the inaccessible or damaged file, and respond when a repair is provided.

Access care is assistance with obtaining working files; it does not reverse released funds. If final work differs from the approved preview, or a new problem arises after access care ends, use the available reporting or Support Request path. Other completion paths keep their own agreed access-check and Dispute conditions.

Use Forgot passcode? where available and follow the recovery steps for that Deal. Recovery can require the stated waiting period and a fresh sign-in before the Buyer can set a replacement. Check the recovery status before trying the next action.

A replacement passcode does not release funds on its own, approve a preview, or complete a milestone. The Buyer must still review the action they intend to authorize. Keep the passcode private; the Seller and support cannot use recovery to authorize release for the Buyer.