Request territory
Start the workflow from a simple field-user request rather than exposing administration complexity.
Field assignments
Receive it. Work it. Return it.
A lightweight iPhone and iPad companion built around one field workflow: request a territory, receive it, understand it immediately, work it offline, record progress, and return it.
Field session
Territory Field is intentionally narrower than TerritoryHub. The experience follows the assignment from receipt through return without exposing congregation-side administration.
Open the assigned territory with its identity, essential boundaries, and the context needed to begin without hunting through admin screens.
Keep the active assignment centered while map context and local-first state remain available even when the network is not.
Capture practical progress updates inside the field flow instead of breaking attention with a second management workflow.
Close the loop explicitly, preserving the local result and allowing synchronization back to TerritoryHub when connectivity permits.
Features
Territory Field deliberately does not become a second administration app. TerritoryHub owns map authority and congregation-side management; Territory Field stays centered on the assignment in the user’s hands.
Start the workflow from a simple field-user request rather than exposing administration complexity.
Present the assignment, territory identity, boundaries, and essential context in a form that can be understood quickly.
Keep the core field workflow usable without depending on a live network connection.
Capture field-service progress locally with a workflow designed for fast, practical updates.
Close the loop by returning the territory and synchronizing the state back to the management side when connectivity allows.
Keep navigation, data entry, and assignment context focused on the field user instead of duplicating TerritoryHub.
Interface
The production app is designed to adapt across compact iPhone layouts and larger iPad layouts. This website panel illustrates the information hierarchy without pretending to be a shipping screenshot.
The field experience prioritizes the active assignment, map context, progress, and return path. Larger layouts may expose more persistent context, while compact layouts stay thumb-friendly.
Requirements
Territory Field is currently opened from its Swift package in Swift Playgrounds on iPad or in Xcode with a current Swift toolchain.
Roadmap
The product keeps offline usability as a non-negotiable boundary while cloud synchronization is layered in around it.
Finish the request, receive, understand, work, progress, and return experience with strong local behavior.
Keep compact devices focused while allowing larger iPad layouts to expose useful persistent context.
Synchronize assignment snapshots and queued field mutations without making connectivity a prerequisite for field work.
Publish a signed beta only after device, data-integrity, offline, and synchronization gates pass.
Downloads
No public installer or App Store acquisition path is published by the website until an approved, signed release artifact exists.
The source package is under active engineering. The public website does not expose repository development packages as end-user releases.
Controlled and public channels remain closed until the product’s distribution criteria are satisfied.
Administration side
TerritoryHub owns the congregation-side territory records, maps, assignments, campaigns, and history that Territory Field consumes.