Core features and capability map

Catalog

• I. Pet profiles: layered multi-pet information management to reduce mixed records and wrong writes.
• II. Health record types: weight, vaccines, deworming, visits, symptoms, medication, labs, and notes.
• III. Public content pages: announcements, FAQ, help, and topics, with search and internal linking.
• IV. Review workflow: daily records, weekly review, monthly summary, and long-term comparison.

I. Pet profiles: from "distinguishable" to "maintainable long-term"

The most common multi-pet issue is mixed information: same names, changing nicknames across periods, and temporary notes all blended together, making later review nearly impossible. Profile fields should be fixed: name, species, sex, birth/adoption date, neuter status, allergies, and history. Use a consistent naming format to avoid retrieval misses caused by ad-hoc naming.

The profile page should be your factual base, while record pages should be your event timeline. This allows quick cross-reference of baseline info when reviewing abnormal weight or visit records, instead of repeating fundamentals in every entry. The more standardized profiles are, the more complete context each later record carries.

II. Health record types: write frequent items as reviewable timelines

For weight, keep unit and context fixed (for example, same time slot weekly on the same device). For vaccines and deworming, record item, dose, execution date, reactions, and next plan. For visits, use a five-part structure: complaint-checks-conclusion-treatment-review. For symptoms and medications, add frequency, triggers, and feedback; avoid non-reviewable lines like "not feeling well today."

For lab and report content, add a "key indicator summary" on top of original results, including units, reference ranges, and comparison conclusions. This enables direct longitudinal comparison at the next recheck. Records are not for "logging once"; they are for helping your future self understand the period in one minute.

III. Public pages: full body text + natural text links

Announcements, FAQ, help, and topic pages use public-readable structures to carry high-frequency questions and operation guidance while reducing repeated explanations. Keep titles and body aligned, and avoid keyword-stuffed headings.

If you often face "I don't know how to write this" during recording, open the matching public page directly (for example weight format, visit summary, deworm reaction). Mapping each recording action to a matching instruction page is key to improving execution rate and data quality.

IV. Review workflow: daily records -> weekly review -> monthly summary

Split review into three levels: daily records capture facts and results; weekly reviews focus on trend changes and anomalies; monthly summaries extract action plans. Weekly review can focus on weight trends, whether vaccine/deworm tasks were executed on schedule, and whether symptoms keep recurring. Monthly summary can capture key events, handling outcomes, and next-month focus points.

The biggest long-term risk is "many records but no action." For each review, output at least one executable action, such as "fixed Tuesday weighing next month", "add 24-hour reaction record after deworming", or "run one outcome follow-up seven days after a visit." Records create value only when actions close the loop.

Suggested starter template (can be used directly)

• Fix one weekly weight record with unified unit and weighing context.
• After each vaccine/deworm event, add "item + reaction + next date" on the same day.
• Write one five-part visit summary each time and append comparison results at recheck.
• Write one monthly summary in the last week of each month and extract 1-3 actions for next month.

View long-form guide catalog · View FAQ templates · View pet topic columns