Schema

Write down the exact fields that go in and the exact fields that must come back, so neither side has to guess what a good update looks like.

Your dad is 82 and you and your sister split his care by week. She texts you Sunday nights: "Good week, he seemed tired but okay, doctor was fine." Three weeks later his cardiologist asks when the ankle swelling started, and neither of you can say. You do not know his weight on any given day, which pills he skipped, or what the nurse actually said about the diuretic. Every update was warm. None of it was usable.

Schema means writing down the exact fields that go in and the exact fields that must come back, so neither side guesses what a good update looks like. The cue is a repeating handoff where both people are cooperating and the reports still cannot be compared week to week. Name the fields: morning weight, pills taken and skipped, ankle swelling yes or no, appetite, any clinic call and what was said. Name the format and deadline: five lines in the shared note by Sunday night, no paragraphs. Name what counts as done, so a blank field reads as a missing answer, not a quiet week. What changes is that you see a trend instead of a mood, and the cardiologist gets dates. When the work is genuinely one-off, or when the signal that matters is the thing you never thought to ask for, a fixed schema hides more than it captures.