How Jobs Are Posted
Jobs on the Pandora marketplace start as regular operational jobs within an organization. When an organization has a job they need filled, an admin can post it to Pandora to find qualified workers. This page explains the posting process from end to end.
Who Can Post Jobs
Only organization administrators with job creation permissions on a Pro or Enterprise plan can post jobs to Pandora. Organizations on Free or Starter plans see an upgrade prompt when attempting to access Pandora features.
The Posting Process
Step 1: Start from an Existing Job
Pandora jobs are not created from scratch. An organization first creates a regular job in their Operations dashboard — setting the client, location, date, time, and service details. Once the job exists and is in a "scheduled" or "approved" status, the admin sees a "Post to Pandora" button on the job detail page.
Step 2: Configure the Posting
Clicking "Post to Pandora" opens a modal where the admin configures:
Worker Payout Value (required)
The maximum amount the organization is willing to pay a worker for this job. This must be greater than $0 and cannot exceed the job's client value. The organization's margin is the difference between what the client pays and this payout value.
For multi-person jobs, this value is the total payout pool — it is split among all workers who show up, not a per-person amount.
Visibility Scope (required)
Controls who can see the job:
| Scope | Description |
|---|---|
| Internal Only | Only workers linked to this organization can see the job |
| External (Platform-wide) | All eligible workers on the platform can see the job |
| Internal First (with escalation) | Internal workers get first dibs; if no one claims it within a configurable window, it opens to the full platform |
Minimum Tier (optional)
The minimum worker tier required to see and claim the job. Defaults to Tier 1 (any worker). Setting a higher minimum restricts the job to more experienced workers.
Supply Requirement (optional)
Whether the worker needs their own supplies:
- Worker must have supplies
- Supplies provided on site
- No requirement
Total Slots (required for multi-person)
How many workers are needed for the job. Defaults to 1. For team jobs, set this to the total number of workers required.
Minimum Required (optional, multi-person only)
The minimum number of workers who must show up for the job to be completable. Defaults to the total slots value. For example, a 3-person job might have a minimum of 2 — meaning the job can still proceed if one worker does not show up.
Step 3: Review Payout Preview
Before submitting, the admin sees an Estimated Payout by Worker Tier preview table. This shows what workers at each tier would earn for this job, helping the admin set a competitive payout value.
For multi-person jobs, an additional Multi-Person Payout Preview shows how the pool splits based on different attendance scenarios.
Step 4: Submit
The admin clicks "Post to Pandora" to finalize. The job immediately enters the visibility pipeline and begins appearing in eligible workers' Available Jobs lists based on their tier, lead time, and other filters.
Payout Math
The organization sets two values:
- Job Value — What the client pays the organization for the job
- Pandora Value — What the organization is willing to pay out to workers (always less than or equal to job value)
The difference is the organization's guaranteed margin (the "spread"). On top of that, the organization benefits from the tier system — lower-tier workers receive a smaller percentage of the Pandora value, generating additional savings.
Worker payout = Pandora value x tier payout percentage
Org margin = Job value - Worker payoutVisibility Scopes in Detail
Internal Only
The job is visible only to workers who are active members of the posting organization. This is useful when an organization has a bench of regular workers and wants to keep the work in-house.
External (Platform-wide)
The job is immediately visible to all eligible workers across the entire platform (subject to tier, lead time, value cap, and other filters). This maximizes the pool of potential workers.
Internal First (with Escalation)
The job starts as internal. If no internal worker claims it within the organization's configured escalation window (default: 4-24 hours depending on urgency), it automatically escalates to external visibility. The organization is notified when escalation occurs.
| Job Urgency | Default Escalation Window |
|---|---|
| Standard (3+ days out) | 24 hours |
| Soon (1-3 days out) | 8 hours |
| Urgent (less than 24 hours) | 4 hours |
| Emergency (less than 4 hours) | 1 hour |
After Posting
Once posted, the job shows a "Posted to Pandora" badge on the job detail page. The admin can:
- View the posting details including current claim status
- Cancel the posting if no workers have claimed it yet
- Monitor claims as workers accept slots
If a worker has already claimed a slot, the posting cannot be cancelled until the claim is resolved (completed, put back, or no-show).
On this page