The Requests dashboard — Help

When you've asked a dozen suppliers for their insurance and a room full of casual crew for their shirt sizes, the question stops being "what did I ask?" and becomes "what's still missing?". The Requests dashboard answers that. It sits on the event's planner page, alongside the RSVP dashboard, and turns every request on the event into a single scoreboard: how many submissions you expected, how many are in, how many you've signed off, and how many people still owe you something.

This article covers where the dashboard lives, how to read the tiles and the chart, how to drill into a status, and how to print a chase list to carry around.

Where to find it, and showing it

Open an event and go to its planner page. Below the timeline, the request area has a Requests heading with a Show Requests button. Unlike the RSVP dashboard, which is open by default, the Requests dashboard starts hidden, because most of the time the per-request count badges tell you enough at a glance. Click Show Requests when you're actively chasing.

The dashboard remembers its state per event, so an event you chase often stays open while others stay tidy. Even when it's collapsed, an Outstanding count badge sits next to the Requests heading and turns orange when anything is still outstanding, so you can see there's work to do without expanding the panel.

What a "line" is

The dashboard counts submissions, not requests. One request asked of ten crew members is ten expected submissions, or ten "lines", one per person. This is what lets the numbers add up to something useful: a single event-wide "upload your PLI certificate" request becomes one line per supplier, and the dashboard tracks each of those lines separately. The headline tile reads "All requests" and counts every expected line across the event.

The tiles

Five tiles sit across the top, each a clickable filter into the table below:

All requests. Every expected submission line on the event.
Received. Lines where something has come in, whatever state it's in.
Approved. Document uploads you've signed off.
Rejected. Document uploads you've sent back for re-submission.
Outstanding. Lines with nothing submitted yet, the people you still need to chase.

Click any tile to load just those lines into the table beneath.

The chart

A donut breaks the same lines down by status, with a slice for each state that has anything in it:

Approved, a document upload signed off.
Answered, a text or choice question that's been answered.
Needs review, a document uploaded and waiting for you to approve or reject it.
Rejected, an upload sent back.
Outstanding, nothing submitted yet.

Click a slice to drill the table into that status, or click the middle of the donut to load everything. The centre also shows the total line count, so the chart and the "All requests" tile always agree.

The table and chasing

The table lists the lines for whatever tile or slice you've picked, sorted in the same order your requests are arranged in, so they read in the order you asked. It's a preview rather than the full set: for a busy event it shows a capped number of rows so the page stays quick.

The dashboard updates live. If a co-planner approves an upload or a crew member submits a file while you're looking at it, the tiles, chart, and table refresh on their own without a reload.

Printing a chase list

For the full set (and for something to carry around back-of-house), use the printable report. The table's Print button opens a report in a new tab that honours whichever filter you've drilled into, so printing the Outstanding view gives you exactly the chase list of who still owes what.

The report is grouped by crew member, listing each person's requests as rows, and prints in clean black and white in landscape, the same paper-first treatment as the printed run of show and the RSVP roll. It's the full filtered set, not the capped preview, so nothing is left off the page.

How it differs from the other request views

Three surfaces touch requests, and they answer different questions:

The Requests dashboard (this one) is the per-event scoreboard: for this one event, what's in and what's outstanding across everyone you asked.
The Requests overview at 1pm.app/Requests is the cross-event chase view: what's still pending or rejected across your whole account, so you can work through outstanding items in a batch regardless of which event they belong to.
The Requests tab on a contact is the per-person record: everything one supplier has ever been asked, and everything they sent back, across all their events.

Asking crew for documents and info and Asking everyone for the same thing cover creating the requests this dashboard tracks.
Reviewing crew uploads covers approving and rejecting the files that move lines from Needs review to Approved or Rejected.
A contact's request history covers the per-person view of the same submissions.