Need Clarification on Using Location Push Service Extension for Firefighter Check-In/Check-Out

I’m building a firefighter app that needs to automatically check in a firefighter when they arrive at the station and check them out when they leave — even if the app is killed. We need reliable enter/exit detection, low latency, and only one fixed location per user.

We’re evaluating Region Monitoring, which works in the killed state but may introduce delays and inconsistent accuracy. To ensure mission-critical reliability, we are considering the Location Push Service Extension, since it can fetch precise location on demand and wake the extension even when the app is terminated.

Before requesting the restricted entitlement, we need clarification on Apple’s expectations:

Is Region Monitoring recommended for this fixed-location use case?

Would Apple consider approving the Location Push Service Extension for a public-safety workflow?

What prerequisites do we need before submitting the entitlement request (Always permission, prototype, privacy disclosures, etc.)?

What details should be included in the justification form?

Our goal is to follow the most reliable and Apple-approved approach for firefighter check-in/out. Any guidance would be greatly appreciated.

Need Clarification on Using Location Push Service Extension for Firefighter Check-In/Check-Out
 
 
Q