Last updated June 17, 2026

Section 3.3: Work Orders & Agreements

A Work Order is the contract container in ABRAM used to schedule and book personnel (freelancers or internal staff) and physical resources (camera packages, equipment kits, vehicles) for specific dates, times, and locations.


1. Structure of a Work Order

Work orders are housed inside individual Work Packages. They lock down the operational details of a shoot day, campaign sprint, or review workshop:

  • Title & Notes: Detailed scope of work, directions, and production guidelines.
  • Timeline: Exact start and end dates/times (supporting hourly scheduling or all-day events).
  • Location: Specific physical address or remote workspace link.
  • Status: Tracks the agreement state: Pending or Confirmed.

2. Personnel, Rates, and Compensation

When adding crew members to a Work Order, you can invite:

  • Internal Org Members: Staff already active in your company workspace.
  • Roster Freelancers: Approved external talent on your private roster.
  • External Emails: Invite new freelancers by entering their email address.

Rate Integration

Compensation is automatically calculated to keep projects within budget:

  1. Hierarchical Rate Selection: When you add crew members to a Work Order, the system automatically resolves their billing rates using a strict priority order:
    • Crew Roster custom rate (highest priority, set when inviting the crew member to the project roster).
    • Organization membership custom rate (set in the team member edit panel).
    • Platform profile rate (defined on the freelancer's public profile page).
    • Platform default day rate (the standard platform baseline).
    • Zero ($0.00) default (if no rate is configured anywhere).
  2. Resource Unit Rates: Physical gear, camera kits, or vehicles include a standard daily rate or cost-per-day defined in the organization’s inventory manager.
  3. Budget Impact: As you add personnel and kits, the system displays the total projected cost of the Work Order based on hours or days booked, warning you if it exceeds the parent package's budget allocation.

3. Availability Conflict Checking & Validation

To prevent double-booking crew or equipment, ABRAM performs real-time checks. These are handled differently depending on whether they involve personnel or physical resources:

Personnel Conflicts (Soft Warnings)

  • Soft Warning System: When you assign a freelancer, the platform checks their calendar across all projects in your network.
  • Informational Alerts: If a scheduling overlap occurs, the system flags it with a yellow Conflict Warning icon in the UI and logs a conflict (such as an overcommitment or unavailability) in the Team Management dashboard.
  • No Save Block: Personnel conflicts do not block you from saving the work order; they serve as informational warnings so you can coordinate schedule adjustments.

Resource & Kit Conflicts (Hard Blocks)

  • Strict Booking Lockout: Physical resource bookings (gear, rooms, vehicles, or kits) are strictly enforced by the system.
  • Double-Booking Prevention: If you attempt to save or confirm a work order that allocates a resource whose quantity is fully booked elsewhere during that timeframe, the system actively throws a hard validation error: Insufficient resource availability for "[Resource Name]" during requested dates.
  • Validation Enforcement: You will be blocked from saving the work order until you resolve the resource double-booking, either by selecting a different piece of gear or shifting the booking timeline.

4. Resource Allocation & Lifecycle Cascades

ABRAM synchronizes your physical inventory, kit assignments, and project locations with your active work orders.

Kit Expansion & Group Syncing

  • Kit Expansion: When you assign a pre-assembled kit (e.g., a "DSMC2 Camera Kit") to a work order, the system automatically expands the kit into its individual constituent items.
  • Unified Group Rescheduling: All allocations within a kit are linked. If you reschedule the work order or change booking dates, the system automatically shifts or deletes all constituent items as a unified group, preventing kits from being fragmented.
  • Location Auto-Sync: If you allocate a physical room or studio resource (e.g., "Stage A") to a work order, the platform automatically syncs that resource's location address to the work order's main Location field.

Work Order Status Cascade

The system automatically syncs the statuses of linked personnel and resource bookings to the parent Work Order's status:

| Work Order Status | Linked Resource Booking Status | Crew Booking Status | Operational Behavior | | :--- | :--- | :--- | :--- | | Draft / On Hold | Reserved | Hold | Resources are blocked out; crew calendars show tentative holds. | | Confirmed / Pending | Reserved | Pending Invite / Hold | Roster invitations are sent; gear remains blocked out. | | In Progress | In Use | Active | Crew is actively checked in; resources are marked in-use. | | Wrapped / Completed | Returned | Completed | Crew completed assignment; gear is released back to inventory. | | Cancelled | Cancelled | Cancelled | Gear and calendar hours are freed up immediately. |


5. Timesheet Auto-Population

To streamline payments, the platform automatically generates timesheet entries from your Work Orders:

  • Automatic Entry Generation: When a Work Order is active or wrapped, the system distributes the total hours evenly across the booking's calendar days and creates draft timecard entries.
  • Manual Protection: The system protects manual edits. If you manually enter or adjust hours on your time card, the auto-population will not overwrite your custom entries.
  • Roster Sync: If a crew member is removed from a Work Order, their auto-populated draft timecard entries for those dates are automatically cleaned up to prevent invoicing errors.

6. Agreement Workflow

Managing work orders follows a structured invitation and confirmation cycle:

Draft Work Order

Define tasks, dates, and pre-auth budget details.

Send Invitations

Dispatch notifications to matched crew candidates.

Freelancer Decision

GATEWAY

Freelancer reviews terms and holds the booking decision.

ACCEPT

Confirmed Booking

TERMINAL

Booking locked, calendar capacity synced, and PO generated.

REJECT

Re-Staffing Required

TERMINAL

Releases previous locks; alerts project manager to match new crew.

  1. Drafting: The Project Manager creates the Work Order, selects the date/time range, books the crew, and configures the physical resources. The initial status is set to Pending.
  2. Dispatching: The manager clicks Send Invitations. This triggers:
    • Real-time platform notifications for registered freelancers.
    • Email invitations for external users, providing a secure checkout link.
  3. Review & Sign-Off: The freelancer reviews the work order details, dates, rates, and guidelines. They can click to Accept or Decline.
  4. Confirmation & Sync:
    • Accepting shifts the booking status to Confirmed.
    • The confirmed hours are written to the project timeline.
    • The event is synced to the freelancer’s calendar and the organization's resource allocator.