Requests

Requests (/requests) is where you ask Lunar Launch Labs for anything — new bookings, swaps, schedule changes, pauses, and offboards — and where you respond to the proposals that come back. The title is “Requests”, subtitled “Everything you’ve asked Lunar Launch Labs to action — new bookings, swaps, schedule changes, pauses and offboards, all in one place.”

The header has a search box (“Search requests…”) and “+ New request” (also reachable as /requests?new=1 — the target of every “+ Book a crew” button in the app). The sidebar’s Requests item shows a badge counting requests that need your action.

Tracking your pipeline

Four summary tiles: OPEN, ACTION NEEDED (highlighted), IN PROGRESS, RESOLVED · 30D. Tabs filter the list: All, Action needed, In progress, Resolved; in the All view, requests group under ACTION NEEDED, OPEN, IN PROGRESS, and RESOLVED · LAST 30 DAYS headers. (Today the resolved tile and group actually include your full resolved history, not just 30 days.)

Each request card shows its type badge (BOOKING, SWAP, SCHEDULE, PAUSE, OFFBOARD), title, a subject line (“Needed by {date}” when you set one), a chip per requested line (“{Specialty} ×{qty} · {n}wk”), the submitted date, and a status pill:

Pill	Meaning
MATCHING	The crew desk is working on it (newly filed, routed, or proposals coming in)
NEEDS ACTION	A proposal is waiting for your per-line response
BOOKED	At least one line was accepted and booked
RESOLVED	Completed
CANCELLED	Cancelled before booking

Empty states: “No requests yet” — “Ask for crew, swaps or schedule changes — we’ll take it from there.”; or, for an empty tab, “Nothing here”. Load failure: “Could not load your requests. Please try again.” with Retry.

Filing a new request

Click “+ New request”. The sheet is titled “Request crew” and opens with: “Tell us what you need and we’ll match the crew. These are requests — nothing is booked until Lunar Launch Labs confirms.”

1. Optionally set “Needed by” — “When you’d like the crew to start. We’ll confirm exact availability.” (Placements start on Mondays; if the date passes before booking, the start rolls to the next Monday.)
2. Under “Roles requested”, build one line per role: pick the role, set the quantity (1–10), choose a booking period (1 week – 4 weeks), and optionally add “Note for this role (optional)…”. Use “+ Add another role” for more lines; extra lines can be removed.
3. Click “Submit request” (“Submitting…”; enabled once every line has a role and period).

The success screen — “Request submitted”, stamped “PENDING CONFIRMATION · NOT YET BOOKED” — lists what you asked for and explains: “Lunar Launch Labs is matching your crew now — nothing is booked until we send you candidates to approve. You’ll see this request under “Open” until then.“ The crew desk is notified by email the moment you file.

Booking periods are defaults, not lock-ins

The booking period sets the initial schedule. After booking you can add or drop future, uninvoiced days freely on Schedule — you pay for scheduled days that get invoiced, not for the period label.

If submitting fails

Validation problems show inline under each field. If your workspace has a long-overdue invoice, the platform pauses new requests until the balance is settled (existing placements keep running) — if submission keeps failing with “Could not submit your request. Please try again.”, check Billing for a past-due banner first.

Responding to a proposal (the booking moment)

When the crew desk sends candidates, the request turns NEEDS ACTION (you’ll also get the email “Your crew proposal is ready”). The card grows a panel labeled “PROPOSED CANDIDATES · RESPOND PER LINE”. Each line shows the candidate’s name (this is the reveal moment), a VERIFIED tag, their title, and their all-in day rate (e.g. $840/day).

Respond to each line independently:

• Decline — the line is marked DECLINED. If you decline every line, the request goes back to the crew desk for another match.

• Accept — opens the booking confirmation, with up to two checkboxes:

  1. “I have authority to bind my company and accept the Master Client Services Agreement.” (links to /mcsa) — shown only the first time your account books; once your MCSA acceptance is on file it isn’t asked again.
  2. “I accept the Placement Order terms for this booking at the day rate shown.” (links to /placement-order) — required for every booking.

  Then click “Confirm booking” (“Booking…”).

Accepting a line is binding and immediate:

• A placement is created at the shown day rate (snapshotted — it never reprices), starting the Monday implied by your needed-by date (or the next Monday).
• The initial weekly schedule is generated from the line’s booking period and cadence.
• The candidate appears on Crew and Schedule; the line shows “✓ ADDED TO YOUR CREW”.
• Your acceptance (with document versions) is recorded in the platform’s audit trail.

If a line was already resolved elsewhere you’ll see “This line was already resolved.”; skipping a required checkbox returns “You must accept the Master Client Services Agreement” / “You must accept the Placement Order terms for this booking”.

Lifecycle requests (pause, offboard, swap, schedule)

Pause, offboard, and swap requests are filed from the crew member detail sheet; they appear here as PAUSE / OFFBOARD / SWAP cards and follow the same pipeline. Swap proposals come back for per-line acceptance exactly like bookings.