Knowing where your child is is only part of safety.

MTFDX Safe focuses more on “who is authorized to pick up, who is currently responsible, whether the handover is complete, and who handles the next step when something goes wrong.”

An adult and a child reviewing a tablet in a classroom (MTFDX original candidate illustration / product mockup, project-owned)

Several families connected through trusted adults (MTFDX original candidate illustration / product mockup, project-owned)

Every pickup should answer four questions.

Who can pick up?

Who is responsible now?

Is the handover complete?

Who handles exceptions?

A Trusted Adult does not mean permanent permission.

Grandparents, teachers, coaches, temporary drivers and others can receive the minimum necessary permission based on the child, the scenario, and the time window.

Time-window permissions
Guardian approval
Valid only when needed

Product mockup of the institution handover queue (MTFDX original candidate illustration / product mockup, project-owned)

Responsibility changes only after both sides confirm.

If the receiver does not arrive, verification fails, or the child does not appear, the original responsible party is kept and the exception flow begins.

Plan
Authorize
Verify
Handover
Receive
Responsibility

Family view (confirmed together)

Haru TanakaConfirmed

15:30 scheduled pickup

CancelConfirm

Institution view (confirmed together)

Haru TanakaMatch

Verify receiver by QR / PIN

HoldVerify

Responsibility moves only after both sides confirm.

Different devices, unified into one safety language.

Sources such as GPS, access control, school buses, and manual confirmation are all converted into a unified Safety Event, and upstream flows do not depend on device brands.

GPS / access / bus
Human-confirmed input
Normalised to one event

Product mockup of QR / PIN / NFC receiver verification (MTFDX original candidate illustration / product mockup, project-owned)

Confirm first, then escalate.

The system does not label every delay as danger; emergency response starts only after high risk is confirmed.

Normal: quiet
Needs confirmation: verify first
Emergency: only after confirmation

Safety flows cannot assume the network is always available.

Organizations can cache the necessary roster and authorization summary for the day; after the network recovers, records are written back and marked offline_origin.

Offline, today's essentials stay available.