Jordan Reyes
General Manager · Cedar House Collection
Public ID 168BA73EB4FEF66EF3CDB21DA4 tracks 1 application, 0 attachments, and merge state Review required.
- General Manager · New · 2026-04-03
Chicago, IL
nights
Because hospitality.
Immediately
site_apply
3_5
full_service
Certs: None listed
Systems: None listed
Guest care
Languages: Englishcandidate
2026-04-03T02:04:34+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: 56AAAA24D97AA27B968B185E9D
- candidate public id: 168BA73EB4FEF66EF3CDB21DA4
- job public id: A69CA9599C94E52C72DCBC82F5
- location public id: 01HW0LOC00000000000000001
- org public id: F9A2523C3AA20885DC2C9EEBEF
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.
Jordan Reyes applied for General Manager. Status: New. Evidence-based fit signals: Candidate gave role-specific motivation rather than a blank apply. Hospitality experience noted: 3_5..
- Candidate gave role-specific motivation rather than a blank apply.
- Hospitality experience noted: 3_5.
- Service background covers full_service.
- Candidate named specific service or operations strengths.
- Languages listed: English.
- Earliest start confirmed: Immediately.
- Candidate location provided (Chicago).
- Phone number on file — quick outreach is possible.
- Only one availability slot listed (nights) — scheduling may be limited.
- Review the candidate packet and move to Review if this looks like a fit.
General Manager · Chicago, IL
- Experience: 3_5
- Availability summary: nights
- Service styles: full_service
- Certifications: None listed
- Systems: None listed
- Languages: English
Guest care
No notes yet. This is where manager readouts and agent-reviewed observations should live.
No follow-up tasks yet. Add the next manager action so candidate movement stays visible.
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: Jordan Reyes — 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.