External website; opens in a new tab.

Working with YBT

Is that a defect, a revision or a new project requirement?

Compare the requested behaviour with the accepted version and criteria; protect both defect remedies and a fair change process.

Working with YBT

Source review 21 November 2026

Disagreements often begin when “finished” or “one revision” meant different things to each person. The accepted brief, deliverables and criteria provide the reference point. A reproducible failure against them is different from a new idea or a changed environment, even if both arrive as a short message saying something needs fixing.

Compare evidence with the baseline

Identify the exact accepted scope and presented build/design. Describe the expected behaviour, actual result and conditions. A broken enquiry button within the agreed scope is not an optional paid enhancement merely because it was discovered late. A request to add a booking system where only an email form was agreed may be a new requirement.

A revision round should mean a reasonable coordinated feedback process, not loss of statutory rights or permission to deliver defects. Conversely, an unlimited sequence of new design directions can exceed the original commercial scope. The parties need a shared description of what the round includes and how further work is agreed.

Separate cause, impact and permission

Legacy faults, customer changes and third-party API changes can affect the diagnosis. Establish the evidence before automatically blaming a supplier or classifying every failure as included. Where investigation is genuinely uncertain, agree a bounded diagnostic assignment and a useful output. Do not turn a question into an invisible authorisation for extra hours.

For a change, show what is added or removed, price/tax, timing, dependencies, acceptance, security/data and continuing support effects. Offer accept, decline, defer or investigate-only choices through the named authorised person. Unaffected work can continue where safe; a material dependency may require a clearly explained pause.

Preserve the history

Keep the original agreement, acceptance and evidence, then link the new accepted revision. Do not overwrite the past and pretend a changed feature was always included. A fixed-price contract remains fixed unless a separately accepted change alters it. Internal effort, negotiated write-offs and progress forecasts are useful management information but not automatic customer charges or accepted completion.

Issued invoices and accepted scope use governed amendment/correction workflows. A project note or manually changed status cannot establish a new financial truth. Keep the accounting provider authoritative and identify which customer approver accepted which document.

At closure, record the delivered version, test results, customer decision and residual items. The aim is not an obstructive approval loop for every routine correction. It is a practical distinction between YBT putting its agreed work right, a customer choosing something different, and a consequential action needing its own authority.

Sources and review

Prepared by Yellow Brick Tech. General guidance; the source and test conditions for your own situation still matter.

Next review: 4 May 2027

Related services

How Yellow Brick Tech can help.

Next step

Need to apply this to a real situation?

Ask a question or choose the closest project route. A short conversation can often clarify the next step.