Back to wiki menu

Dispatch & Field Operations

Institutional campaigns

Last updated: July 8, 2026 at 20:16

INSTITUTIONAL CAMPAIGNS GUIDE

Institutional campaigns are large-scale, multi-site engagements specifically designated as advanced network opportunities. These B2B engagements consist of a primary umbrella contract covering multiple child site contracts. The critical distinction between non-discretionary and discretionary campaigns concerns when the field location is determined.

  • Non-Discretionary Campaigns: A fixed, concrete address is assigned to every site slot at the moment of contract purchase.

  • Discretionary Campaigns: Often referred to as a campaign with locations "in the bank," the client purchases a specific capacity of missions, but the exact field locations for those slots are defined later when the designated Lead Campaigner dynamically dispatches them.

Independent contractors should understand how these types influence mission availability on the Radar and their associated economics. Campaigns operate entirely outside of standard consumer payout mathematics and individual investigation cap-table structures. Verification in the field utilizes a Trusted Agent Handshake, involving a secure PIN provided by the field contractor rather than standard client-side verification gates.

THE MISSION LIFECYCLE FROM THE FIELD

Campaign assignments move through distinct phases that impact their visibility to terminals in the field. Preliminary phases involve intake, funding, and staging by HQ to prepare site drafts for validation and handoff to a Lead Campaigner; these phases do not appear on the verifier Radar.

The active field lifecycle unfolds across the following phases:

Phase C: Lead Campaigner Management

Campaign umbrellas contain a primary Lead Auditor position. The appointed Lead Campaigner must accept this commercial offer within the dossier UI before they can deploy sub-missions or self-dispatch their terminal to specific site assignments.

Phase D: Releasing Missions to Radar

Depending on the campaign classification, a Lead Campaigner utilizes different deployment paths to move child site briefs onto the active Radar:

  • Non-Discretionary Briefs: Fixed-address assignments are bulk-deployed by the Lead Campaigner directly to the open pool, moving the child contract status immediately to an open state where any eligible terminal can claim it.

  • Discretionary Briefs: Banked-location assignments must first be released from the platform bank by the Lead Campaigner. The Lead updates the title, region, and location parameters via an explicit dispatch containing a real physical address. This dynamic dispatch automatically applies a substantial Radar Head Start Hold for that Lead Campaigner's terminal.

  • Speed-Path Exceptions: If a Lead Campaigner releases a discretionary site brief without a pre-defined location, this occurs strictly within specialized "speed-path" campaign configurations, where GPS data is captured dynamically at the exact millisecond of execution without fixed location constraints.

  • Self-Dispatch Reservations: The Lead Campaigner retains the option to reserve any child site brief for themselves via self-dispatch. This moves the assignment into a dispatched status and applies a 12-hour exclusive Radar window for that Lead. During this window, only the originating Lead can claim the brief, and they must still physically accept it via the Radar interface to establish proper device credentials for field execution.

Terminals not designated as the Lead Campaigner will only see campaign assignments on their Radar after these exclusive head-start windows have expired or after a standard open bulk deployment has occurred.

Phase E: Field Execution and Settlement

Campaign assignments utilize isolated unit-gross payout rules defined entirely outside of standard uncoordinated bounty economics:

  • Field Stipends: The unit-gross structure includes a fixed field contractor milestone settlement of $115 standard or $185 enterprise per verified location. Standard tier referral multipliers apply directly to this base.

  • Management Fees: These field stipend values are completely separate from the fixed coordination fees paid to the Lead Campaigner for managed locations, which are settled via flat transfers of $35 per site.

  • Fulfillment Protocol: The transition to a terminal umbrella status triggers automated archival retention sweeps, securing standard-storage Truth Packets immediately following final composite deliverable fulfillment.

VERIFIER STATUS INDICATORS

As an independent contractor tracking a campaign assignment, you should monitor the primary status vocabulary that dictates terminal visibility:

  • Draft: The assignment parameters are HQ-generated and have not yet been transmitted to the Lead Campaigner, meaning they remain completely invisible to the field pool.

  • Pending Review: The brief resides within the Lead Campaigner’s queue but is not yet released to the open Radar, typically awaiting finalized location input or active deployment authorization.

  • Dispatched: The Lead Campaigner has formally released the assignment, initializing active Radar holds and exclusive terminal windows.

  • Terminal Umbrella Status: Achieving final complete fulfillment triggers automated settlement processing and initializes data retention architecture sweeps.

SUMMARY DECISION GUIDE FOR VERIFIERS

When you are monitoring the Radar for campaign assignments, you are observing the culmination of specific client deployment paths:

  • Fixed Upfront Routing: If the B2B client mapped every site address at genesis, a non-discretionary campaign was purchased. HQ staged concrete drafts, and the Lead bulk-deployed them to the Radar, generating assignments with clear addresses available immediately in the general field pool. Mid-campaign expansion for this type requires an entirely new custom quote.

  • Dynamic Banked Routing: If the client purchased data capacity but left dynamic location choice to the Lead Campaigner, discretionary slots are involved. These banked missions only populate on the Radar after the Lead adds a verified address and executes a dynamic dispatch, usually triggering initial Radar holds for that Lead before opening to the wider network. Dynamic site expansion is allowed only within these discretionary or speed-path campaigns, appending new banked child sites directly to the existing master umbrella contract.