Keep each pet’s records separate and ready for handover

PETICO.app is free to download and use. Website resources do not create or import app records.

Keep each pet's observations attached to the intended animal, source and time. A household total is not automatically an individual record. A note about one pet should not become another pet's history because the names, bowls or dates look similar.

This guide is a practical organization method. It does not require PETICO and does not establish access to another owner's records.

Start with a clear local pet label

Use a stable label that you understand. In a local template, a simple pet code can be enough; there is no need to include an owner's email or other contact details.

Keep the label beside every row, not only in a filename that may later be separated from the table. Use another distinguishing note if labels could be confused, without adding irrelevant private information.

Fictional example: a shared bowl becomes two false records

Fictional household: Cat A and Cat B share a bowl. A caregiver records “120 mL change in bowl amount” over a stated period, with individual attribution unknown.

If that full amount is copied as “Cat A drank 120 mL” and “Cat B drank 120 mL,” the record now contains two unsupported claims. Adding them creates a 240 mL total from a single 120 mL source.

The correction is to preserve one shared/unattributed observation with its original source and window. Neither individual cat's measured intake is established by it.

RecordSupported?Reason
Shared-bowl amount changed by 120 mLOnly within the stated collection limitationsIt describes the source observation
Cat A consumed 120 mLNo individual attribution establishedShared access
Cat B consumed 120 mLNo individual attribution establishedShared access
Combined individual intake was 240 mLNoDuplicate attribution of one source

These are fictional arithmetic and record-quality examples, not actual PETICO histories.

Preserve the source when more than one person records

An owner and caregiver may describe the same event. Keep both source notes if useful, but do not count the event twice simply because it appears twice.

Record the observation date and window separately from the date someone typed the note. If entries disagree, retain the disagreement and resolve it with the source where possible. Do not silently choose the more convenient value.

A household handover checklist

The observation template includes a pet label and source-note field. Separate files per pet can help, but do not remove labels from rows.

A dog-and-cat handover that keeps the sources clear

Fictional sample: prepare one short note for each pet, with links or references to the originals you can actually find.

PetDated recordSource and handover note
Dog A25 October, morning meal: descriptive appetite noteOwner’s original diary; amount was not measured. Keep it separate from the vaccination document dated 12 March.
Cat B24 October veterinary-visit documentOriginal visit document. Medication details should be taken from the existing prescription record, if applicable; do not copy Dog A’s information.

Before sending, check the pet label and intended recipient. A prepared summary is not confirmation that it was sent, received or reviewed. Use the actual supported sharing route and share only relevant information.

Check which records you can locate, then see the English PETICO.app Health history and connected-records workflow. The website checklist is separate from app access; no subscription is required to use the app.

When comparing periods

First select one pet's comparable observations. Then check signal, unit, method and window. Do not combine two animals' series because each has too few entries.

If the individual basis is insufficient, say so. A household series may be useful for a different question, but label it as household-level and do not imply an individual result.

In a connected product

PETICO's structured story is pet-specific. An integration, where supported, must use the intended permitted pet and appropriate context. A public guide does not choose that pet or grant access.

Read about structured context, or prepare a clear history for a visit. The basic rule remains the same: identify the pet before interpreting the record.

One cat’s daily patterns, one distinct history

A household timeline should preserve which pet each observation concerns. PETICO.app connects daily signals and longer health history around the individual pet. The Android example shows Fındık’s named signal workflow, including water, sleep and comfort. Keep shared-bowl amounts unattributed when the record does not identify which cat drank them.

PETICO.app Android Signals screen for Fındık with eating, water, activity, sleep, comfort and engagement.
Android screenshot from the public Google Play listing, checked 21 October 2026. Fındık is the named cat profile; this screen is not a multi-pet overview or a displayed Learning Map. Its capture build/date is not supplied.

No subscription is required to use the app.