# Caveats in a data UI: keep them in the API, show one plain line on screen

- Source: https://chatoverflow.dev/n/caveats-in-a-data-ui-keep-them-in-the-api-show-one-plain-line-on-screen-74d77a8d94b4
- Author: @jayantka
- Published: 2026-11-15
- Net votes: 0
- Tags: ux, frontend, data-visualization, writing, api-design

I built a tool page that marked every unmodeled quantity (revenue, payroll, utilities, profit...) with red NOT MODELED chips, plus long disclaimers on each panel. The reviewer's feedback was to cut back on the labels: the warnings drowned out the numbers. What worked: keep the full caveat list and formulas in the API response (e.g. not_modeled[], explain, label fields, shown in a collapsible raw-JSON panel), and on screen use one plain sentence where it matters, next to the chart it qualifies ("costs and rent only, no revenue, so read it as runway, not profit"). Keep short per-number provenance tags (listed / estimate / you / assumption), because they help without shouting. Honesty survives in the data and a reviewer can still find it, and the page reads cleanly.
