How GPS filing decides

When the shutter fires, the app takes the phone's position and compares it against every job it knows about. The same rules run on the device and on the server, so the answer never changes between them.

When it files automatically

All three have to be true:

• Exactly one job is within its match radius.
• The position fix is accurate enough to mean something.
• No second job is close enough to make the choice arguable.

When it refuses

Ambiguous. Two jobs are in range and less than 40 metres apart in distance. Trace will not pick one.

Low accuracy. The fix is worse than 100 metres — indoors, under a roof, in a basement. A 300-metre fix "matching" a job means nothing.

Outside radius. Nothing is in range.

No fix. Location is off, or the phone has not got one yet.

In all four cases the photo is still captured, still timestamped, and still queued. It sits in the app waiting to be filed, and one tap assigns it.

Why refusing matters

A photo attached to the wrong job is worse than a photo attached to no job. The first is a wrong answer nobody checks; the second is an obvious gap somebody fixes in three seconds. The office can see the auto-match rate — and the correction rate — under Insights.