Three complaints that require different investigations
The following examples are fictional. They illustrate how a project can move from a plausible complaint to a bounded decision. They do not describe client work or promise that another organisation will have the same cause.
“Customers request the wrong thing”
A supplier offers a wood material sample and a separate steel product. The source records distinguish them correctly. Yet the Dutch action label uses a word that can be read as either a sample or a material. Looking only at the database would miss the customer's difficulty.
The investigation follows the independent labels and the associated product identities. A Dutch reviewer approves wording that explicitly asks for a material sample. The complete rehearsal then follows the buyer's choice through the stored request to the staff view. The actual steel product remains correctly described; an unknown item remains unresolved.
This is a publishing and task-interpretation problem. It is not evidence that all instances of a word should be replaced, or that every material description requires a new translation system. The full language guide shows the evidence and controls.
“The balance increases when a credit is applied”
A fictional account summary starts at 240 and receives two approved lines whose amounts are already negative: −30 and −20. The displayed result is 290. The source records have not changed, and no new financial operation is needed to investigate the summary.
The faulty calculation subtracts the negative values a second time. Under the inspected signed-line contract, adding them once produces 190. Acceptance also checks a positive adjustment, a zero line and a credit that exceeds the opening amount according to the fixture's approved handling rule.
The useful correction is a derived-view change with source preservation and eligibility checks. It does not determine the organisation's accounting policy, issue a credit or move money. The signed-credit guide explains that boundary.
“The monthly task appears on extra dates”
A team intends a review on the first Friday of each month. Its inspected scheduler treats two restricted calendar fields as alternatives. A rule that appears to combine “days one through seven” and “Friday” therefore selects a wider set than the owner intended.
The revised design uses an explicit Friday schedule and an additional day-of-month gate in the named local zone. The dated model selects 6 November and 4 December 2026 and rejects 1 and 13 November. An unrelated weekly Friday task remains unchanged.
That calculation demonstrates date membership. It does not prove that a production scheduler ran, that a staff member attended or that the review finished. The schedule guide keeps those different forms of evidence separate.
Turn your own complaint into a useful example
Record what the person saw, the underlying information you can inspect and the outcome the authorised owner expected. Include a nearby case that should remain unchanged. If evidence is missing, record the gap instead of completing the story with an assumption.
The next step may be a content decision, a short technical investigation or a controlled rehearsal. The project workbook helps organise those questions across a complete request. Contact us when you can describe the task and the point where its meaning or result becomes uncertain.