Concept paper Puteaux, September 1, 2026
Home-care systems have traditionally been built around the employer's schedule. A provider schedules its caregivers, assigns working hours, and asks them to clock in and out. The provider's platform therefore becomes the operational record of the service. This model is logical from an employment perspective.
But it leaves an important question unanswered: What happens when the question is not how many hours the employee was scheduled to work, but whether the beneficiary actually received the care that was supposed to be provided?
A monthly employer schedule says: You are scheduled to work at this time. It does not necessarily say: You have accepted to provide this visit to this beneficiary.
This distinction becomes important when a visit fails. A caregiver may argue that the assignment was too far away, that travel was not adequately compensated, or simply that the schedule changed without their agreement. The employer may take the opposite view and consider the caregiver responsible. The result can be an internal employment dispute. But from the beneficiary's perspective, there is a much simpler fact: The expected visit did not take place.
To be clear from the outset: this is not a proposal to replace the employer's scheduling system. Providers still need to manage employment, payroll, and HR, and they remain best placed to do so. What is missing is the layer that records the service relationship itself, independently of who is managing the workforce.
YouTime proposes a complementary model. The caregiver does not re-enter their employer's monthly schedule. Instead, seven days before a requested visit, YouTime informs the caregiver of the beneficiary's request. The caregiver can accept or decline.
If the caregiver accepts, the event becomes something different from an internal employer assignment: a recorded commitment to the beneficiary.
The caregiver then records the actual start and end of the visit through YouTime.
The resulting sequence is: Requested → Offered → Accepted → Expected → Delivered
or, when something goes wrong: Requested → Offered → Accepted → Expected → Not delivered
That distinction makes the failure measurable — not as a workforce-management incident, but as a service outcome.
In the United States, Electronic Visit Verification (EVV) is already used to record when and where a visit took place and which caregiver provided it.
This raises an obvious question: Why should a caregiver clock in and out twice?
They should not. If YouTime is to become a practical infrastructure for home care, it cannot simply add another layer of data entry on top of EVV. The objective is to replace a provider-centred timekeeping process with a shared service-delivery record centred on the beneficiary.
The difference is what happens before the clock-in.
EVV primarily establishes that: a worker → was at a location → at a given time.
YouTime starts earlier: a beneficiary → requested a specific service → for a specific duration → a caregiver accepted it → the service was expected → the service was delivered or missed.
This matters because a visit can be physically verified without establishing that it was the service the beneficiary actually requested.
Consider a simple example. At the end of a funding period, three remaining hours may be scheduled for a beneficiary although the beneficiary only requested one. The caregiver can legitimately clock in and remain for three hours. EVV can verify those three hours. But it cannot, by itself, answer the prior question: who requested three hours?
YouTime makes that question part of the service record. The beneficiary requests the service. The caregiver accepts or declines the request seven days in advance. If accepted, the visit becomes a recorded commitment. The caregiver then clocks in and out once — in YouTime — and the resulting event records both the commitment and its outcome.
The complete chain becomes: care needed → requested → accepted → delivered → confirmedor: care needed → requested → accepted → missed → replaced
This creates a fundamentally different form of visit verification. It does not merely verify that a caregiver was physically present. It verifies the relationship between the care requested by the beneficiary, the commitment made by the caregiver, and the care actually delivered.
One clock-in, not two. The principle is simple: YouTime should not add a second clock-in system. It should become the system through which the visit is both committed to and verified.
The provider still manages the employment relationship. The caregiver still records the time worked. But the same event also becomes evidence, for the beneficiary and the public funder, of what care was actually delivered.
One schedule. One acceptance. One clock-in. One clock-out. One shared record.
The YouTime control mechanism protects caregivers. A caregiver receives a precise record of the visits they accepted, the visits they completed, and the visits that were accepted but ultimately not delivered.
The system can therefore distinguish between:This gives the caregiver an independent record of their own service commitments — one they do not have to reconstruct after the fact in a dispute with their employer.
For a beneficiary, certification and reliability are both important, but they answer different questions.
Certification answers: Is this caregiver qualified to provide care? Reliability answers: When this caregiver accepts a visit, how consistently is that visit actually delivered?
A caregiver YouTime profile could show both — for illustration only, not real figures:
This adds a second dimension: observed reliability in delivering accepted visits, alongside the credential itself.
Public authorities finance care because a person needs care. The relevant chain is therefore not simply: authorized hours → provider schedule → timesheet
It is: funded → requested → accepted → expected → delivered → missed → replaced
The difference matters. A provider's platform remains essential for managing employment, scheduling, payroll and operations, and YouTime is not built to duplicate it. But the beneficiary and the public funder also need to know whether the service was actually delivered — and that requires a record of the commitment itself, not only of the employment relationship behind it.
The question is not whether beneficiaries should have a role in the organization and validation of their care. The question is whether existing technology can turn that role into a reliable, visit-level record of care commitments and outcomes — one that complements, rather than duplicates, the verification systems already in place.
Could the next generation of IHSS technology make visible, for each requested visit:
requested care → accepted care → delivered care → missed care → recovered care.
Because ultimately, the most important unit of measurement is not the employee's schedule. It is the care that the person actually requested and received.
If you work with SFHSA, DAAS, Homebridge, or a beneficiary advocacy organization in San Francisco and are interested in exploring what a beneficiary-centred continuity-of-care pilot could look like, I would welcome your feedback.
Chi Minh PHAM
Founder, YouTime — home care infrastructure
https://www.linkedin.com/in/chiminhpham/