
Client Portal Document Versions: Keep Reviews and Approvals Attached to the Right File
Manage client document revisions with stable identities, version-specific decisions, clear current-file labels, and controlled access.
Custom Portals
Build portal comparisons around authorized records, explicit versions, stable field meanings, comparable units, accessible layouts, and useful explanations of missing data.

LET’S BUILD SOMETHING USEFUL
Talk to Ataraxy Developers about your website, app, or custom software.
A customer selects two supplier submissions and clicks Compare. One column shows an annual service charge, the other a monthly charge. A blank cell might mean that no answer was supplied, that the field did not exist in the older form, or that the viewer lacks permission to see it. A visually aligned table can therefore imply a comparison that the underlying data does not support. The layout needs a clear comparison contract before it needs colored differences.
Define what the portal is comparing: two records, two versions of one record, or two proposals prepared under different rules. Each has a different meaning. A useful comparison identifies its inputs, preserves their context, and explains where a direct comparison is unavailable.
Show recognizable record names and version identifiers at the top of the comparison. Include the relevant confirmation or submission dates and identify drafts as drafts. If a record changes while the comparison is open, decide whether to keep the original version with a notice or ask the viewer to refresh. Do not silently replace one column while leaving the other and its difference highlights unchanged.
For a proposal review, save the selected revision identifiers with the comparison request. That makes the result reproducible and helps a colleague understand which versions were examined. A “latest” shortcut can be convenient, but resolve it to explicit versions when the comparison is generated. If the product promises a consistent point-in-time view across several records, implement and verify that stronger guarantee rather than inferring it from similar timestamps.
Authorize every selected record and each field included in the response. The OWASP authorization guidance emphasizes checking permissions on every request. A comparison endpoint is another data access route, not an exception because the user previously viewed one record in a list. Recheck access when the comparison is generated, shared, exported, or refreshed.
Exclude unauthorized values before creating differences, summaries, or search indexes for the comparison. Hiding a cell with CSS is insufficient if the full value remains in the response. Also review indirect signals: a “three confidential fields changed” message may reveal information the viewer should not receive. Choose a consistent product policy for unavailable information, and avoid implying that a protected value is simply an unanswered question.
Use stable field identifiers to align columns. Display order can change between form versions, and translated labels can differ while referring to the same field. Conversely, two fields with the same short label can have different meanings. Keep a maintained mapping for schema changes and mark fields that cannot be compared directly. Do not match them solely through similar wording or their row number in an exported file.
For repeated items, define whether order matters and how items correspond. A list of approved locations may be a set, while a sequence of delivery milestones has meaningful order. Compare items using appropriate stable identifiers rather than treating every moved row as a deleted and newly added item. Show an explicit mapping problem when identity cannot be established confidently; a misleadingly precise difference is worse than a clearly explained limitation.
Define comparison rules for each data type. Dates need an agreed interpretation, amounts need a currency and period, and measurements need units. A display formatter alone cannot establish equivalence. If the portal converts values for comparison, identify the conversion basis and retain the original values so the reviewer can see what was actually submitted. Do not silently convert an estimate into a contractual amount.
Separate missing, blank, zero, false, not applicable, and unavailable states. In a service proposal, zero setup cost differs from an omitted setup-cost answer. “Not applicable” may be an explicit response with a reason. If a field was introduced after the older revision, say that the field was not collected in that version rather than suggesting the supplier forgot it. These distinctions often matter more than the visual highlight itself.
The W3C tables tutorial explains the importance of marking header and data relationships so assistive technologies can provide context. Apply that principle to side-by-side comparisons. A reviewer should know both the field and the record associated with a value. Keep column names available while navigating a long comparison, and ensure any sticky presentation does not create duplicate confusing reading content.
On small screens, consider a field-by-field presentation with clearly named values rather than squeezing several narrow columns into unreadable text. Do not rely on red and green alone to convey change. Add text such as “Added,” “Removed,” or “Changed,” and provide a clear explanation for incomparable fields. A differences-only filter should state what it omits and let the viewer return to the complete authorized context.
An AI summary can help a reviewer navigate a long proposal comparison, but it must be derived from the same permitted snapshots shown on screen. Identify the compared revisions and provide links to the relevant fields. A summary should not invent reasons for a change, infer that a missing response means refusal, or decide which proposal is best without an explicit decision framework.
Treat the summary as a reading aid. Preserve the underlying deterministic differences and allow the user to inspect them. If one source changes, mark or regenerate the summary with the same version discipline as the comparison. For consequential reviews, require the human reviewer to examine the relevant source values and record the actual decision separately from the generated explanation.
Test a comparison link opened by a colleague with different permissions. Decide whether it stores only the selected identifiers or a retained authorized snapshot, and apply the corresponding access policy. Exported comparisons need the same field restrictions and version labels. A downloadable spreadsheet should not quietly include hidden columns that the web comparison excluded.
Exercise renamed fields, new schema versions, reordered lists, different currencies, explicit zero values, and records removed after selection. If the comparison offers “Use this version” or “Approve,” treat that as a separate current-state action with fresh validation. The fact that a historical snapshot was safe to read does not prove that restoring or approving it is still allowed. Keep the review evidence connected to, but distinct from, the operation that follows.
A dependable comparison aligns meaning as well as columns. Identify the selected versions, apply access rules before deriving differences, preserve units and missing-value distinctions, and provide readable context on every screen size. Keep summaries traceable and follow-up actions separately validated. Customers can then use the comparison to understand a real choice without mistaking visual alignment for equivalent information.
LET’S BUILD SOMETHING USEFUL
Talk to Ataraxy Developers about your website, app, or custom software.