The Production Pipeline

Every job in Vremly follows the same lifecycle, tracked by six statuses that appear consistently across every list, card, and notification in the product: PENDING (order placed, not yet scheduled or assigned), BOOKED (technician assigned and a shoot time confirmed), SHOOTING (technician is on site or in progress), EDITING (raw files are with the editor), DELIVERED (media has been released to the client), and CANCELLED. You'll see these statuses rendered as color-coded badges throughout the dashboard, the jobs list, and the job detail sheet. The product also surfaces an intermediate 'Awaiting Editor' state between shooting and editing, reflecting the real-world handoff from capture crew to post-production.

Stage 1 is Booking. An agent navigates to /booking (or taps 'Book' in the iOS tab bar) and steps through a five-stage flow: Address (Mapbox autocomplete to resolve lat/lng and address components), Provider (select the media company), Package (choose a pre-built bundle or build a custom order from individual add-ons), Schedule (pick an available date and time slot, or request scheduling by the provider), and Review (confirm everything before submitting). After submission, agents see an Order Submitted screen that summarizes the service provider, package, address, and scheduled time. If the company requires a card on file, a Stripe SetupIntent card-entry screen appears before the success screen. On iOS, the booking flow is a bottom sheet that slides up over a live Mapbox map — a property annotation grows alongside each step so the agent always has spatial context.

Stage 2 is Dispatch. For COMPANY users, the job appears immediately in the Projects list (/projects) and on the live technician map (/map). A company dispatcher or project manager opens the job detail, assigns a technician from the ranked provider list (the system ranks by proximity, rating, and availability), and the status moves from PENDING to BOOKED. On iOS, the CompanyDashboardView and DispatchView mirror this: technicians appear as pins on the map, and the job assignment sheet is accessible directly from a job card.

Stage 3 is Capture. The assigned technician sees the job appear in their personal dashboard and on their calendar. On iOS, the ProviderPersonalDashboardView shows the day's docket with a prominent 'Start Trip' card when a confirmed job is scheduled near or during the current time window. Tapping it launches TechnicianTripView, which provides geo-navigation to the property and tracks the trip state (en route, arrived, in progress, complete). The customer can see this activity timeline in real time on the order detail screen.

Stage 4 is Editing and Delivery. Once shooting completes, the status moves to EDITING. An editor assigned to the job — accessible via the /job-management route for PROVIDER accounts, or the Projects list for COMPANY accounts — processes the raw assets. When editing is done, the status moves to DELIVERED and the client receives a notification. The agent can access the delivered media from the order detail in the web app at /orders/[id] or in the iOS OrderDetailView, which shows a media section alongside the activity timeline, chat preview, technician info, and the original booking summary. Invoicing is handled through the /invoices route for company users, where invoices can be sent in Draft, Sent, Paid, Overdue, or Void states.

Throughout the pipeline, two real-time communication channels run alongside the status machine: a TEAM channel (visible to the provider company, technicians, and editors but not the agent) and a CUSTOMER channel (the agent sees only this). Both are accessible from the job task view — a slide-in sheet on the right side of the screen in the web app. This means the production crew can discuss internal logistics without the client seeing that conversation, while the client channel stays clean and professional. On iOS, the same chat preview appears in OrderDetailView with a 'View full conversation' control that opens the full chat sheet.