Avery Brooks
Kitchen Manager · Sunset Hospitality Group
Public ID B0D8E34C6F511421CB67B263F4 tracks 1 application, 0 attachments, and merge state Clean.
- Kitchen Manager · New · 2026-03-29
Nashville, TN
Weekdays, Weekends
I like coach-heavy kitchens and have been the closing lead in a scratch concept for the last three years.
Immediately
site_apply
Not provided
Not provided
Certs: None listed
Systems: None listed
No strengths note provided.
candidate
2026-03-29T11:10:00+00:00This application stays owned in the hiring app. Master AI should link here, read the safe summary, and use the signed contract for writes.
- application public id: 4D49FA7BF5377AE93DFA71B8DD
- candidate public id: B0D8E34C6F511421CB67B263F4
- job public id: 53F1E43A9192801B8C45E70240
- location public id: 01HW0LOC00000000000000002
- org public id: 6703546DAC346582F3370E2609
This is the small context block the agent app should embed or reference when it opens this record. Final edits still happen here through the hiring workflow and the signed contract lane.
Avery Brooks applied for Kitchen Manager. Status: New. Evidence-based fit signals: Flexible availability (Weekdays, Weekends) fits restaurant scheduling needs. Candidate gave role-specific motivation rather than a blank apply..
- Flexible availability (Weekdays, Weekends) fits restaurant scheduling needs.
- Candidate gave role-specific motivation rather than a blank apply.
- Earliest start confirmed: Immediately.
- Candidate location provided (Nashville).
- Phone number on file — quick outreach is possible.
- Review the candidate packet and move to Review if this looks like a fit.
- Use the first outreach to confirm service style depth and years of hospitality experience.
Kitchen Manager
- Experience: Not provided
- Availability summary: Weekdays, Weekends
- Service styles: Not provided
- Certifications: None listed
- Systems: None listed
No notes yet. This is where manager readouts and agent-reviewed observations should live.
Kitchen Director · Next 24 hours
Build the hire packet here before moving this candidate to hired.
Keep the post-apply lane warm with a visible next step and at least one logged candidate update.
- No logged follow-up yet
No hire decision package is saved yet. Assemble the final decision lane before candidate trust cools off.
- No logged follow-up yet.
- Log a candidate-facing follow-up so the trust lane stays visible after the interview.
Add one or more candidate-facing interview slots, one per line, in datetime-local format. Once the candidate books a slot, the remaining open slots automatically close so the schedule stays clean.
No interviews scheduled yet. Create the first interview here so the scorecard flow has a clear anchor.
Keep the final candidate-facing update explicit once the decision path is real.
Review proof blockers: The team is keeping the next update visible here.
Blocker / watch: The team is keeping the next update visible here.
Candidate lane: The next logged update from the team will appear in this portal.
- Latest message: No candidate-facing communication has been logged yet.
- Carry-through: Avery Brooks — Watch: Keep the final candidate-facing update explicit once the decision path is real.
- Proof watch: The team is keeping the next update visible here.
The next final-stage update should come directly from the team once the decision is ready.
What they should expect next: The next logged update from the team will appear in this portal.
- What they should expect next: The next logged update from the team will appear in this portal.
- No logged follow-up yet: No candidate-facing communication has been logged yet.
- The next logged update from the team will appear in this portal.
- The team is keeping the next update visible here.
No communication timeline yet. Save a template-based draft to start outreach, reminders, or rejection language from one place.