{"id":3042,"date":"2026-11-19T11:03:49","date_gmt":"2026-11-19T09:03:49","guid":{"rendered":"https:\/\/www.kaarne.fi\/superstore\/?p=3042"},"modified":"2026-11-19T11:04:04","modified_gmt":"2026-11-19T09:04:04","slug":"did-the-client-ask-again-or-did-the-website-change-again","status":"publish","type":"post","link":"https:\/\/www.kaarne.fi\/superstore\/articles\/did-the-client-ask-again-or-did-the-website-change-again\/","title":{"rendered":"Did the Client Ask Again, or Did the Website Change Again?"},"content":{"rendered":"<p>A maintenance client writes, \u201cThe opening hours are wrong again.\u201d You remember fixing them last week. Before replying that the work is already done, find out whether \u201cagain\u201d describes the message, the observed page or a change since your last check.<\/p>\n<h2>Keep three records side by side<\/h2>\n<p>Use the original request, the completion record and the new observation. The first explains what was asked for. The second should show what was changed and what was checked at the time. The third says what someone is seeing now. When these records blur together, a new symptom can look like a repeated instruction and an unverified completion can look like a new failure.<\/p>\n<p>Consider a fictional freelancer maintaining a community studio\u2019s website. The original request was to replace winter opening hours on the contact page. The completion note names that page and the revised hours. The new message includes a screenshot from a different page. The words sound familiar, but the comparison has already revealed a location difference.<\/p>\n<h2>Case one: the request is unchanged and the result matches<\/h2>\n<p>First ask whether the client is looking at the same location and asking for the same result. Open the exact place they identify and compare the actual content with the agreed change. If your observed result matches the request, show the client where you checked and ask whether that is the location they mean.<\/p>\n<p>A useful response is: \u201cI checked the contact page at the address below today, and it shows the hours agreed last week. Is that the page you are looking at? If not, please send the page address or a screenshot with its location.\u201d This is a request for a discriminating detail, not a declaration that the client is mistaken. Avoid diagnosing a browser or system cause without evidence.<\/p>\n<h2>Case two: the completion was narrower than expected<\/h2>\n<p>The studio\u2019s screenshot may show a service page that still contains the old hours. Perhaps only the contact page was named in the original request, while the client reasonably expected all public occurrences to be updated. Compare the scope of the request and completion note before calling this a fresh regression.<\/p>\n<p>Reply with the distinction: \u201cThe recorded change covered the contact page. Your screenshot shows the service page, which still has the earlier text. Let\u2019s confirm where the opening hours need to appear and which source should be maintained.\u201d Follow your actual service agreement for any scope or cost decision. Do not imply a contractual conclusion from a single note.<\/p>\n<h2>Case three: a checked result changed afterwards<\/h2>\n<p>If the completion record shows the same location displaying the correct text, and the new observation now differs, treat that as a new investigation linked to the old work. Record when each observation was made and what page or version it concerns. Identify relevant changes since the earlier check using the records available to you.<\/p>\n<p>You can say: \u201cThe earlier check recorded the agreed hours on this page. The page now shows a different value, so I\u2019ll compare the intervening changes before choosing a correction.\u201d Do not claim to know the cause yet. A later edit, a different location or another dependency may be relevant, but a plausible explanation is still only a possibility until checked.<\/p>\n<h2>Use a compact decision note<\/h2>\n<p>Write: original request; affected location; expected result; earlier observed result and date; new observed result and date; same scope or different scope; next check and owner. Add the supporting page address or agreed reference in your normal working record. Keep the note focused enough that a colleague can continue without asking you to retell the conversation.<\/p>\n<p>If the earlier completion has no useful evidence, say that. \u201cMarked complete; verification not recorded\u201d is more informative than reconstructing a successful test from memory. It may mean you need to check the result now before deciding which of the three cases fits.<\/p>\n<h2>Close the loop in the client\u2019s language<\/h2>\n<p>After the investigation, explain what you found, what you changed if anything, and where the client can inspect the result. If a wider maintenance decision remains, name it separately. Your aim is to make the next action clear while keeping a respectful distinction between the client\u2019s report and your confirmed findings. The phrase \u201cwe already fixed that\u201d rarely does either job by itself.<\/p>\n<p>Keep the original request, the completed change and the new observation distinguishable. That is a useful test for any system you use to collect recurring website feedback.<\/p>\n<p>For the underlying completion record, use <a href=\"https:\/\/www.kaarne.fi\/superstore\/articles\/resolved-is-not-the-same-as-ready-to-launch\/\">a four-stage implementation and verification record<\/a>. If the observation is still vague, adapt <a href=\"https:\/\/www.kaarne.fi\/superstore\/articles\/the-client-says-make-it-pop-what-do-you-ask-next\/\">the questions for making feedback specific<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>An apparently repeated request can describe three different situations. A short comparison helps you choose the next check and reply without blaming the client.<\/p>\n","protected":false},"author":1,"featured_media":3078,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_hide_featured_image":false,"_jetpack_featured_image_duplicate_dismissed":0,"_jetpack_feature_clip_id":0,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_post_was_ever_published":false},"categories":[24],"tags":[],"class_list":["post-3042","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-customer-understanding"],"jetpack_sharing_enabled":true,"jetpack_featured_media_url":"https:\/\/www.kaarne.fi\/superstore\/wp-content\/uploads\/sites\/7\/2026\/11\/np-02-01.webp","_links":{"self":[{"href":"https:\/\/www.kaarne.fi\/superstore\/wp-json\/wp\/v2\/posts\/3042","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.kaarne.fi\/superstore\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.kaarne.fi\/superstore\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.kaarne.fi\/superstore\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.kaarne.fi\/superstore\/wp-json\/wp\/v2\/comments?post=3042"}],"version-history":[{"count":7,"href":"https:\/\/www.kaarne.fi\/superstore\/wp-json\/wp\/v2\/posts\/3042\/revisions"}],"predecessor-version":[{"id":3160,"href":"https:\/\/www.kaarne.fi\/superstore\/wp-json\/wp\/v2\/posts\/3042\/revisions\/3160"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.kaarne.fi\/superstore\/wp-json\/wp\/v2\/media\/3078"}],"wp:attachment":[{"href":"https:\/\/www.kaarne.fi\/superstore\/wp-json\/wp\/v2\/media?parent=3042"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.kaarne.fi\/superstore\/wp-json\/wp\/v2\/categories?post=3042"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.kaarne.fi\/superstore\/wp-json\/wp\/v2\/tags?post=3042"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}