When several dozen home interventions occur each week, a paper schedule or a spreadsheet inevitably leads to oversights. Philia ADMR is the business information system of the ADMR network that combines scheduling, mobile time tracking, and beneficiary follow-up in a single interface. However, it is essential to know how to use it correctly so that the promise of fluidity translates into the daily lives of the teams.
PhiliaDom and route planning: the module that supervisors underutilize
Philia is not just a shared calendar. The software includes a dedicated module, PhiliaDom, designed to plan intervention routes while considering geographical constraints and the availability of each caregiver. In practice, many local associations continue to build their routes manually and then enter the results into Philia.
Further reading : Simple tips to easily identify the right or left sock
This approach negates a significant portion of the time savings. PhiliaDom offers a logical sequence of homes to visit, which reduces unnecessary back-and-forth trips and limits travel time between two beneficiaries. When a supervisor directly inputs the constraints into the module (time slot imposed by the beneficiary, duration of intervention, geographical area), the generated schedule also complies with the break rules stipulated by the collective agreement for the home care sector.
Adopting the right reflexes with Philia ADMR from the construction of the routes helps avoid correcting inconsistencies afterward that the software could have flagged in advance.
Related reading : How to Adopt an Ethical and Responsible Wardrobe Daily
Mobile time tracking and scheduling discrepancies: understanding where errors come from
Have you ever noticed a discrepancy between the schedule displayed on Philia and the hours actually recorded by a caregiver? This type of discrepancy is the most common issue reported by departmental federations.
Real-time tracking via the mobile browser
The telemanagement module allows home helpers to clock in and out directly from their phones. The time tracking is done through the mobile browser, not through a third-party application. A caregiver using an outdated browser or losing their connection at the time of clocking in creates a silent discrepancy in the system.
Checking the version of the mobile browser before each week begins is one of the simple actions that eliminate this type of incident. On both Android and iOS, a pending update is enough to cause a malfunction of the time tracking form.
Identifiers and first login
The other source of discrepancy concerns the identifiers. Upon first login, each caregiver receives a pair of temporary username/password. If this password is not changed quickly, it may be shared or forgotten, leading to clock-ins made under the wrong profile.
A useful reflex for supervisors: ensure that each caregiver has personalized their identifiers within 48 hours of account creation. Philia does not block access in case of an unchanged password, which allows the error to pass without alert.
Philia ADMR internal messaging: replacing SMS without losing responsiveness
Many ADMR associations have long coordinated last-minute replacements via SMS. The problem is twofold: SMS do not leave an exploitable trace in the beneficiary’s file, and they fall outside the GDPR framework that the ADMR network must comply with.
The messaging integrated into Philia centralizes exchanges between the coordinator’s space and the caregiver’s space. Each message is time-stamped and linked to the relevant schedule. In case of a dispute over an intervention not carried out or a change in schedule, the Philia messaging serves as a dated and consultable proof by the federation.
- Use Philia messaging for any schedule modification, even minor, to maintain complete traceability.
- Set up push notifications on each caregiver’s mobile browser so they receive alerts without manually opening the application.
- Reserve phone calls for emergency situations where the beneficiary is awaiting immediate assistance, and then confirm by message in Philia.
Reduction of administrative time: what associations notice after deployment
Associations that have deployed Philia ADMR report a significant reduction in time spent on administrative tasks related to managing interventions and schedules. This gain does not come from the software itself, but from the elimination of double entries: a schedule created in PhiliaDom automatically feeds into route sheets, time sheets, and billing documents.
On the ground, home helpers gain an average of fifteen minutes per intervention thanks to direct access to beneficiary information from their phones. Gone are the paper notebooks to consult before each home visit: the digital file displays specific instructions, the contact details of the attending physician, and the history of previous interventions.
This accumulated gain frees up time for human support, which remains the primary mission of the ADMR network.
Control points to ritualize each week on Philia
A planning tool does not correct input errors or oversights by itself. A few weekly checks are sufficient to maintain the reliability of the data in Philia.
- Compare the number of planned interventions with the number of recorded clock-ins to spot discrepancies before payroll closure.
- Check that travel times between two homes are correctly recorded, as they impact the caregiver’s remuneration and URSSAF declarations.
- Verify the absence of overlapping schedules on the planners of caregivers covering multiple beneficiaries on the same day.
- Ensure that any replacements notified via messaging have been properly recorded in the official schedule.
A weekly check of fifteen minutes prevents hours of corrections at the end of the month. Federations that have ritualized this verification notice a marked decrease in unbilled interventions or payroll errors related to missing clock-ins.
Philia ADMR, in its current version (10.13.0 accessible on philia-admr.org), offers all the necessary tools to ensure the reliability of the planning-tracking-billing chain. The difference between an association that suffers from bugs and another that runs smoothly rarely lies in the software: it lies in the regularity of entries and the rigor of controls implemented by supervisors from the outset of deployment.