NINE: A Veterinary Report Must Be More Than a Beautiful PDF

While developing NINE in PARDPro Lab, we initially treated generating a veterinary report as a relatively clear product feature. A cat owner would keep recording weight, symptoms, Body Condition Score, and vaccination information. The system would organize those records into a PDF with clear typography and complete charts that could be saved, printed, or shared with a veterinarian.

From the interface, the workflow appeared complete: record the data, generate the report, and bring it to the appointment. But when we followed the workflow into a real consultation, a more important question emerged: does a veterinarian actually need a beautiful PDF? Probably not.

Pet owners rarely arrive at a clinic with a fully understood and well-structured problem. More often, the information is fragmented: the cat seems to have lost weight; it vomited recently, but the exact day is unclear; its appetite changed, although it sometimes eats normally; the home scale may not be accurate; useful photos exist somewhere in the camera roll but cannot be found during the appointment.

None of this information is worthless. It may contain important clues about how a condition developed. The problem is that those clues are scattered across memory, photos, messages, measurements, and subjective observations made at different times.

At first, we thought the product should make this information look better. We gradually realized that the real task was to make it more trustworthy and easier to evaluate.

Professional layout cannot answer the most basic questions by itself. When was each item recorded? Does it represent a sustained change or an isolated fluctuation? Did it come from a measurement, a photo, or the owner's description? Are there long gaps in the record? Are units consistent? Can the original photo still be opened? Is the report showing a source record or a system-generated inference? Without those answers, a refined PDF may simply arrange uncertain information more neatly.

Health tracking products can easily assume that more records automatically create a more valuable report. In a consultation, however, information volume and information value are not the same thing.

A report containing dozens of entries can still force the veterinarian to search from the beginning if it does not reveal timing, direction of change, or important exceptions. The user has done substantial recording, but the work of finding the signal has merely been transferred to the clinician.

This led us to redefine the role of a veterinary report. It should not attempt to diagnose on behalf of a veterinarian. It should not create the illusion that the product understands a medical condition by presenting a precise-looking health score.

It should behave more like an organized factual summary. It should help the veterinarian see what changed, when the change began, which symptoms recurred, whether weight loss appears to be a single measurement error or a continuing pattern, whether symptoms and body changes occurred around the same time, whether vaccination and previous-care records are complete, and which details are measured facts versus owner observations.

The goal is not to reach the conclusion for the veterinarian. The goal is to reduce the time required to find relevant clues.

This is a boundary we believe consumer health products must protect: the product can preserve facts, present change, and identify uncertainty; medical judgment remains with a qualified veterinarian.

Consider a report that says, “Current weight: 4.2 kg.” On its own, that number provides very little context.

If the report instead shows that weight declined steadily from 4.8 kg to 4.2 kg over six weeks, it begins to offer useful evidence. If it also shows three records of reduced appetite and two vomiting episodes during the same period, with two symptoms recorded after the more substantial weight decline, a temporal relationship becomes visible.

Even then, the product must remain restrained. It cannot turn that relationship into a causal conclusion or tell the owner that the cat has a particular disease.

A more responsible presentation would state that weight showed a sustained six-week decline, that reduced appetite and vomiting were recorded during the same period, and that these records should be reviewed by a veterinarian.

This may appear to be a small difference in wording, but it represents a fundamentally different product position. One approach tries to perform intelligence. The other tries to preserve trust.

In health-related products, trust is rarely damaged because a product admits what it does not know. It is damaged when uncertain information is packaged as a certain answer.

A useful veterinary report must make the source of each item understandable. A measurement from a connected device is not the same as a manually entered estimate. A dated photo is not the same as a remembered observation. A system calculation is not the same as a clinician's assessment.

These forms of information can all be useful, but only when the report does not flatten them into the same apparent level of certainty. Traceability allows the reader to judge the evidence instead of trusting the visual authority of the document.

When designing a report, it is natural to want every page to feel complete. If there is no vaccination record, the interface can display a default state. If there are not enough weight measurements, it can still draw a simple line. If a photo is missing, a placeholder can preserve the layout.

But missing data is itself information. If an entire month contains no records, the report should show that interruption instead of allowing the visual design to hide it. If a photo existed only on the original device and is no longer available, the report should say, “The original photo is currently unavailable.” It should not imply that complete evidence remains safely stored in the cloud.

If a change is based on a single measurement, the report should not call it a trend.

This changed how we think about completeness. We once focused on page completeness: every module had content and every card was filled. We now care more about evidence completeness: show the data that exists, state what is missing, confirm only what can be confirmed, and preserve uncertainty where confirmation is impossible.

For a health product, an honest blank is more valuable than false completeness.

PDF can easily become the finish line for a product team. It is concrete, visible, and easy to demonstrate. It can carry the brand, charts, careful typography, and the appearance of a finished result.

But the user is not really buying a file format. The user needs long-term records that are not easily lost, less dependence on vague memory during an appointment, fast access to important changes, a shared timeline across different kinds of data, traceability from every report item back to its source, and a product that does not disguise algorithmic inference as a medical conclusion.

Without those capabilities, exporting a PDF is only a layer of packaging.

We now see NINE's veterinary report as a concentrated test of the credibility of the entire product. It forces us to inspect whether records are clear at the point of entry, whether data is actually preserved, whether dates and units are consistent, whether Free and Pro boundaries are transparent, whether photo-backup claims match the real capability, whether the report distinguishes facts from owner descriptions and system prompts, and whether the product remains restrained about what it can do.

The report is not simply the last step of the data workflow. It is a mirror that reveals whether every earlier step can be trusted.

Software often communicates professionalism visually. Ordered grids, restrained color, refined charts, and a branded export can all make a product feel mature. These qualities matter, and PARDPro Lab values clear, disciplined, high-quality design.

But in a health product, deeper professionalism comes from a different set of choices: do not exaggerate capability; do not hide missing data; do not present correlation as causation; do not make health claims that cannot be supported; do not blur a user's data boundaries because a feature belongs to a paid tier; and do not allow visual certainty to exceed the evidence itself.

This restraint may not make the product more spectacular at first glance. It does determine whether users will trust it with important information over time.

Before improving the next version of the report, we want every module to answer this question. If a module only makes the page appear complete but does not support understanding, it should not occupy a central position in the report.

Was it measured by a device, entered manually by the owner, preserved in a photo, or calculated by the system? The origin must remain identifiable.

When evidence is limited, records are interrupted, or a source file has been lost, the report must say so honestly instead of using design to conceal the gap.

These three questions seem simple, but they changed how we evaluate the entire feature. Our goal is no longer to generate a more beautiful veterinary PDF.

The real question is this: when an owner is sitting in a consultation room, unable to describe a health concern accurately, can NINE help communicate what happened more clearly and credibly to the veterinarian?

If it can, PDF is simply one delivery format. If it cannot, then no matter how polished the report looks, the product is not finished.