Hunt log

Review completed live hunts: tracks, participants, sightings, downed and wounded game.

Where to find it

• Web: sidebar entry Hunt log (icon: history clock).
• Mobile: home screen tile Hunt log (icon: history clock).

The list shows every completed hunt for the currently selected team, most recent first.

List view

Completed hunts are grouped by month under a heading that shows the month name and the number of hunts that month. The current month is open by default. Tap a month heading to expand or collapse it.

At the top of the page there is a Start hunt button when no hunt is in progress. When a hunt is active, a card showing the live session appears at the top instead so you can jump back into it.

Each row shows:

• Hunt name (or the linked calendar event title, or "Unnamed hunt" if neither is set)
• Date and time the hunt ended
• Linked calendar event (if any)
• Participant count and total duration
• The names of the dogs tracked during the hunt, with a paw icon
• Counters for sightings, downed, and wounded game shown as icons
• A speech bubble with the message count, if you have access to the hunt chat. Tap it to open the chat directly without going via the summary

Mobile loads twenty hunts at a time and fetches more as you scroll down. The web app has Previous and Next buttons at the bottom so you can page back through older hunts.

Archiving hunts

When the list gets long, old hunts can be moved out of the way into the archive. The hunt then leaves the hunt log, but it is not gone. It is still counted in statistics and in the harvest log, and you can bring it back at any time.

Requires administrator role

Only secretaries and hunt leaders can archive and restore hunts. Everyone on the team can open the archive and read the hunts in it.

To archive a hunt:

1. Open the hunt from the hunt log.
2. Tap the archive button (a box) next to the hunt name.
3. Confirm. The hunt moves to the archive.

A hunt that is still running cannot be archived. End it first.

Open the archive: tap the archive button at the top of the hunt log. Archived hunts are listed the same way as in the hunt log, most recently ended first.

Restore a hunt: open it from the archive and tap the button next to the name again. The hunt returns to the hunt log.

Deleting hunts

A hunt that was a mistake, for example a test start, can be deleted entirely. Unlike the archive, a deleted hunt is not counted anywhere: it disappears from statistics, from the harvest log and from the team data export. Tracks and observations are still kept in the background, so the hunt can always be brought back if it was deleted by mistake.

Requires administrator role

Only secretaries and hunt leaders can delete and restore hunts. Everyone on the team can open the list of deleted hunts.

To delete a hunt:

1. Open the hunt from the hunt log or the archive.
2. Tap the trash button next to the hunt name.
3. Confirm. The hunt moves to the list of deleted hunts.

A hunt that is still running cannot be deleted. End it first.

Open the list of deleted hunts: open the archive from the hunt log and tap the trash button at the top.

Restore a hunt: open it from the list and tap the restore button next to the name. The hunt is counted again. If it was archived before it was deleted it returns to the archive, otherwise to the hunt log.

Summary view

Tap a row to open the summary. The page shows:

1. Header stats: date, duration, total distance covered, participant count, linked event.
2. Summary: a card with the number of participants who joined, the total hunting hours (the sum of each participant's time in the hunt), and observations broken down per species (sightings, downed, and wounded counts side by side for each animal).
3. Playback timeline: a row with play/pause, a speed (1x, 2x, 4x, 8x), and a draggable timeline. As the hunt plays back, the tracks are drawn out over time and the sighting / downed / wounded / tracks & signs pins appear in the moment they were reported. Useful for seeing how the hunt unfolded minute by minute.
4. Map: one coloured line per participant track and pins for every sighting / downed / wounded / tracks & signs event marker. Tracked dogs are drawn too, with their own colours and a paw symbol at the dog's latest position. You can zoom in and out with the plus and minus buttons in the corner. Tap a participant, a dog, or a pin to see a card with details.
5. Participants: one row per participant with a coloured swatch matching the track on the map, distance covered, and an eye toggle to hide their track.
6. Dogs: one row per dog tracked during the hunt, with the dog's name, handler, distance covered, and an eye toggle to hide the dog's trail. Tap the row to zoom the map to the dog's trail.
7. Sightings / Downed / Wounded: three sections grouping the event markers by type. Each entry shows species, notes, photo (if uploaded), and a Show on map button that re-centres the map on the marker.

If you started the hunt, or are a secretary/team lead, you can rename the hunt with the pencil next to the title.

Hunt report

Below the summary you find the Hunt report section, a few lines of free text about how the day went. The report can be written right when the hunt ends, or added here afterwards. Everyone in the team can read it. The person who started the hunt, or a secretary/team lead, can write and change the report with the pencil next to the heading.

Distance accuracy

Per-participant distance is computed server-side from the recorded positions using the haversine formula. Two filters reduce GPS jitter:

• Points with reported accuracy worse than 100 m are skipped.
• Pairs of points more than 10 minutes apart are treated as a disconnect (not movement) and excluded from the running total.

Treat the distance as approximate. Real-world accuracy depends on hardware, sky visibility and how often the phone reported.

Active hunts

The history list only contains hunts that have ended. The active hunt (if any) still appears in the regular live-hunt entry above the main navigation. Opening a history link for a hunt that has not yet ended redirects to the live view.

Downsampling

To keep the page snappy, the API down-samples positions to one point every 30 seconds for the summary view by default. The full-resolution data remains available via the API for analytics use cases.