Event manpower
View authorised staff, suppliers and shifts for the selected event and date.
Good to see you. What needs attention?
Choose an event once, then continue the next required step. Technical and low-frequency controls remain under Reports & settings.
Event progress
- Event details
- Manpower
- Staff compliance
- Accreditation
- Attendance
- Timesheets
Event lifecycle and season
Review this complete event before changing its state. Planning and Live permit operations. Completed and Archived refuse new bookings,sign-ins and publication;history remains available. No lifecycle is inferred for unconfigured events.
Entering Live requires a current ready accreditation publication. Sign all staff out before choosing any non-Live state. This change does not enable email,PIN delivery or an external sync worker.
Accreditation publication
Review the selected event’s complete roster across all booked dates. Named shifts need a current verified identity, PIN, valid booking times and compliance readiness. Unfilled slots remain separate.
Publication preserves immutable evidence of the roster and readiness you reviewed. Current bookings, attendance and operational access continue as recorded. Event lifecycle controls and PIN delivery are separate.
Current event details and saved snapshots
Event KPIs
Covers all booked dates for the selected event. Counts are per shift. Current compliance readiness requires approved PNC and the required clearances valid now and through the booked finish.
Deadline adherence, manpower stability and supervisor feedback are unassessed until their source evidence is available. Female representation is informational. Immutable historical periods are shown separately and never overwrite current KPI data.
Supplier breakdown
KPI history
Read immutable recalculation snapshots for the exact event, month, year or a bounded custom period. Event history includes every revision; broader periods use only each event’s latest revision.
Owner recalculation
Records a new immutable snapshot of the selected event’s complete current KPI source and benchmark fingerprints. It does not alter allocations, compliance, attendance or earlier snapshots.
Upload manpower requirements
Manpower
Manpower
Change staff or booked times, then submit manpower. Submit again whenever plans change. Signed-in shifts and their history stay protected.
Manpower
Synthetic development only. Showing rows authorised for your account. Overnight finish times remain on the following day when earlier than the start.
Manpower changes
Revise an existing booking
The original booking is retained. This form changes date, times, zone, position or rank, keeping the same staff identity and supplier. Protected history prevents a revision. Online access is required.
The last save is unconfirmed. Check its saved result before another change. A missing receipt does not prove that nothing saved.
Manpower changes
Saved changes appear immediately in the event roster. New supplier manpower submissions apply automatically.
Daily view
Summary and supplier totals cover all authorised active shifts for the event and date. Filters apply to the rows below. Attendance refreshes every 30 seconds while this screen is visible.
Supplier breakdown
Arrivals
Attendance for the selected event and date, within your access.
Delete or restore planned manpower
This operation covers every date in the selected development event. Deleting makes planned bookings inactive; original records and history remain. Restoration is limited to the latest eligible deletion and creates linked bookings after fresh checks.
Downstream position requirements and publication remain separate. A successful operation here does not publish or email changes.
A deletion or restoration is unconfirmed. Check its original saved result before another operation. A missing receipt does not prove failure.
Bulk booking revisions
Select existing bookings for the event and date above. Edit their proposed values, review the server preview and confirm the whole batch. Staff identities and suppliers stay the same; original records remain in history. Online access is required.
Proposed changes
Edit each booking below. Start and finish timestamps must include Z or a UTC offset. Use Apply to set a common zone, position or rank for every loaded booking; otherwise clear that common value before preview.
A bulk save is unconfirmed. Check its original saved result before another change. A missing receipt does not prove that nothing saved.
Manpower history
Read immutable snapshots of committed bookings across all dates, including inactive original bookings. Capturing a snapshot preserves current manpower for reference. Bulk amendment and latest-deletion restore remain separate workflows.
A snapshot save is unconfirmed. Check the saved result before another change. A missing receipt does not prove failure.
Event settings
Create an event or change its name and timezone before manpower exists. Any manpower history, including cancelled shifts, locks these settings. Event codes stay fixed. Venue, operational date, manager contact and saved email templates have separate versioned settings below.
Development project only. Creating an event does not allocate staff, create sheets, grant memberships or send messages.
2 · Select an event and basic settings
3 · Venue, contact and email templates
Event details and email templates
Save venue, operational date and manager contact information for the selected event. Email text is stored as a template for the later email workflow. Account access is managed separately.
4 · Event image and browse dates
5 · Add staffing requirements
Select a saved event above, then upload its staffing requirements.
An event change is unconfirmed. Check its saved result before creating another event or changing settings. A missing receipt does not prove failure.
KPI benchmark configuration
System owners can review all eight source definitions and save a complete versioned threshold configuration. Labels, directions and definitions are preserved. Female representation is informational and excluded from supplier performance status.
Source defaults are not a saved configuration. Saving thresholds does not recalculate KPI snapshots, resolve missing deadline/baseline provenance, enable daily jobs or complete dashboard migration. No reports are sent.
Technical JSON imports
Development testing with approved synthetic records only. This technical import accepts normalized JSON containing suppliers, events, staff and shifts. It does not accept the manpower Excel workbook or CSV files; workbook mapping, replacement and publication are not available here.
Staging validates and saves the snapshot without importing operational records. Committing creates new records and accepts exact existing matches. Conflicting records refuse the entire import. New named bookings require current staff clearance.
Template download — synthetic JSON example with one supplier, event, staff member and unassigned shift. Replace the example identities and values before use. No PIN is included. Downloading does not import records.
The commit needs reconciliation. Check the original request before starting another import. A missing response does not prove failure. Checking replays the original confirmed request and may complete an interrupted or previously refused import.
Read-only financial context
Attendance uses the current normalized session calculation. Complete unapproved proposals can be saved with explicit rates. Original financial rounding, the billing ledger and currency configuration remain outstanding. Financial approval, purchase orders, invoices and credits are unavailable.
Legacy proposals · approval unavailable
Legacy daily releases and financial links
Try a 12-hour test timesheet
Supplier timesheets
Publish completed attendance for one supplier, event and date. Publication freezes the original released hours and cannot replace an existing release. Open sessions, future shifts and empty attendance are refused by the server. Review original attendance in Daily operations first.
Approving a correction records a review decision only. It does not change attendance, released hours, rates, payroll, purchase orders or invoices. Financial adjustment application remains a separate workflow.
Publish original attendance
Discrepancy history
Proposed timestamps include their UTC offsets. Original rows above use the event timezone. Draft and reviewed proposals cannot receive another decision.
A Management timesheet change is unconfirmed. Check its saved result before changing scope or making another decision. A missing receipt does not prove failure.
Supplier submissions
All submitted dates for the selected event. Acknowledging receipt does not approve or apply allocations.