Back to journal

The detail page should agree with the result card

On October 31, I prepared a correction for conflicting housing information on Seasonal.Work. Job cards and the housing filter could use a listing's stored accommodation value, while the detail page did not receive that same field. Its fallback could therefore describe housing as not included for a job whose card indicated otherwise. Following the result into the detail page changed the apparent meaning of the listing.

The problem was in the information passed to the detail page, not evidence that the employer's stored value needed to be changed. The correction added the existing accommodation value to the public detail result. That kept the source of the answer the same across the card, filter and detail view. It also avoided a broader interface rewrite: the display already knew how to use the field once the result actually supplied it.

The change preserved the existing job lookup and visibility rules. It did not alter listing records, default values or the meaning of accommodation. That last distinction matters to candidates: a listing that offers housing does not necessarily offer it without charge. Making two screens agree about availability should not silently upgrade the claim into a promise about cost, quality or terms that the stored information does not establish.

The dated review record describes a reproduced missing-field case, focused database and application checks, and independent review of the small correction. The database fixtures were synthetic, and the interface checks used a simulated document environment rather than a real signed-in browser journey. The change was prepared on October 31 and merged the following day. Those records support the implementation, but they do not establish that the database change was applied live or that a candidate observed the corrected detail page in production.

Reflection

A detail page should deepen the information in a result card, not contradict it because one field disappeared along the way. For Seasonal.Work, tracing that discrepancy back to the shared data was the useful step. Consistency improves trust only when the corrected wording stays within what the source actually says.