1. What staff do you need?
2. Where do you need staff?
3. When do you need them?
4. Add optional notes and contact method only if useful.
Restaurant name, contact name, and email can come later.
Tell us who you need first. Start with the role, the location, and when you need staff. We only ask for extra venue details later if they are actually needed.
1. What staff do you need?
2. Where do you need staff?
3. When do you need them?
4. Add optional notes and contact method only if useful.
Restaurant name, contact name, and email can come later.
Tell us the role, location, and timing first.
Your request is saved as a website draft.
Mobile app coming soon. For now, everything works in your browser.
For now, everything works in your browser. No app install required.
Starting your staff request draft…
Candidate names, CVs, phone numbers, and emails do not show publicly here.
Candidate visibility and consent still control what can be shared later.
No guaranteed staff and no public-group style request wall.
Role: Floor staff
City: Hobart
When: This weekend
Continue via: saved website draft
Restaurant name: later if needed
Email: later if needed
Restaurant Support Candidate Profile
Name, city, target roles, venue experience, availability, work rights, and certificates.
Clean format for restaurant review.
Shared only after explicit candidate consent.
Venue type, shift pattern, certificates, and restaurant details still matter, but they should not block the first ask.
Candidate profiles remain consent-first and private.
This is a quick-start request path, not a promise of instant staffing or guaranteed matches.
No. Start with the role, location, and timing first. Extra details can come later if needed.
No. This is a private request flow, not a public manager group.
Yes. The public manager flow stays on the website and saves your request draft as you go.
No. Restaurant Support helps with a faster request flow, but does not guarantee staff or instant fills.