Situations that call for different kinds of digital work

These examples illustrate project decisions; they are not accounts of completed client work. Each starts with a specific discrepancy and a result that someone can inspect.

Two reviewers believe they own one request

A shared queue displays an unassigned technical inquiry. Two colleagues open it and both press the action to take responsibility. If the application merely saves whichever owner was entered last, one colleague may continue work without realising that the record now names the other.

The outcome needs an agreed ownership rule, a single successful claim and useful feedback for the colleague whose view became stale. Handing the work back must be deliberate too. This is a software and operational-handoff problem, not simply a need for more reminders.

One payment appears to settle too much

A customer pays an amount intended to cover parts of two invoices. The actual receipt is correct, but the application treats the whole payment as available against each invoice. A green payment badge can conceal an allocation problem.

The review distinguishes the receipt from its allocations and checks that the allocated amounts are conserved. The payments and formats guide develops that question without making accounting or legal decisions for a business.

A marker points to the wrong part of a correct photograph

A field colleague marks a detail on a small phone preview. The original image, caption and task reference reach the office correctly, but the marker is drawn at the same pixel coordinates on a much larger image. It now points somewhere else.

The annotation needs a defined relationship to the source image's dimensions. The field-photo note follows that correction and checks a second marker without changing the original evidence.

A page looks purchasable while the business offers review

A quotation-only item has no approved immediate price, but inherited structured data describes it as a zero-price offer. The visible inquiry explanation and machine-readable description disagree.

The structured-data note explains how to compare the actual route and claims. Search syntax cannot supply commercial facts that the business has not approved.

The catalogue supports a task, but the first release includes too much

Some items have complete reviewed facts and documents; others depend on unanswered product questions. Publishing all of them together may delay a useful route or create unsupported claims.

The first-release guide compares a bounded complete set with a larger incomplete one. The decision should leave a clear current task and a visible next phase.

Discuss the discrepancy you have found, or use the solutions guide to identify the likely starting scope.