1 · Staffing → 2 · Zones → 3 · Wrap-Up
Staffing
Events, their shifts and who works them. Then the crew email and the client confirmation.
Availability
Who can work which day, and everyone's usual week and days off.
Weekly Schedule
The regular week at a venue: generate it from the template, adjust it, save it and email everyone their shifts.
1 · Staffing → 2 · Zones → 3 · Wrap-Up
Zones
After Staffing: who stands in which parking zone at SoFi and Intuit Dome, per shift. Then email the layout to the managers and leads.
1 · Staffing → 2 · Zones → 3 · Wrap-Up
Wrap-Up
After the event: from Rippling hours to the client report: overtime, card expenses and the email draft.
1Event and hours
Or upload a Rippling export
Close reports
Rates and overtime come from the 💲 Rates tab of Lineup — Data. Reports are saved in Lineup — Event Reports. FluxOps is not changed.
2Hours
| Name | Position | Rate ($) | Break (min) | Clock in | Clock out |
|---|
3Card expenses (Ramp)
Approve the charges that belong to this event. Approved + billable ones go on the report at cost.
4Report
Messages
The monthly events email, who gets each kind of email, and a log of every email and Slack message Lineup sends.
Who gets what
Automatic recipients, plus your changesLoading…
Monthly events email
Sent by Lineup
Every email and Slack message, and whether it went outMy Hours
Start a timer when you begin, stop it when you finish. At the end of the week, send it for approval. Times are California time.
Team Hours
Approve each person's week or send it back with a note. Only approved hours count in the Budget.
Budget
Each project's approved hours and expenses against its budget, the quarter's retainer, and what needs attention.
Project Costs
Vendors, equipment, travel… per project, with markup: what it cost, what the client is billed, and the margin. Ramp charges can be placed on a project here.
QC Desk
Every project's QC in one place: re-QC queue, reviews, fixes from techs and the client email.
Field Guide
The page Flex techs open from their phone: the forms they file and the guide they follow. Edit it here; techs see changes right away.
Team link
Replaces the shared password"New link" makes the old one stop working at once (for example if it was shared outside the team). Then send the new one to the techs.
Forms
Top highlights
The 3 boxes at the topGuide sections
Route Automator
Upload a store list, get drivable survey routes on a map and adjust them. Then plan the teams (trips, flights, dates) and send the project to QC Desk.
Route Automator needs a Google Maps key: in Apps Script → Project Settings → Script Properties, add GOOGLE_MAPS_API_KEY (with the Geocoding API and Routes API enabled). The same key the current Route Automator uses works.
Hiring
New staff from the Join form until their first shift. Availability and first shift are checked automatically from FluxOps.
Crew
The Mobility crew from FluxOps: position and contact. New crew and people who leave: in FluxOps 👥 Availability for now (Lineup reads it); after go-live, in HR → Employees. Everyone in the company is in HR → Employees.
Inventory
Our inventory (what used to be TrackIt): where every item is, what goes out to each event or route, and what comes back.
Employees
Everyone at Flux and Flex, with their employee ID and where they appear: FluxOps, Rippling, QC, Project Hours, Lineup and Timeero.
Names to link
From other systems, not matched to anyone yet: link them to who they are, or add them as a new employeePayroll
Before paying: has everyone sent their hours, are they approved, and are the events closed? One pay week at a time.
Accounts
Everyone who can open Lineup: their company, their role and the screens it opens. Accounts are kept on the 👤 Users tab of Lineup — Data.