The roster
Who works here, in what role, in which department, with what availability and what target hours. Certifications are tracked with their expiry so a lapsed food handler's card is a warning rather than a surprise.
For restaurants / Team
Build the week against roles, availability and target hours. Invite staff to the studio with their own account; a chef's profile lists every house they have cooked in, confirmed by the venue, shown as they choose.
Who works here, in what role, in which department, with what availability and what target hours. Certifications are tracked with their expiry so a lapsed food handler's card is a warning rather than a surprise.
Drag shifts onto the grid against each person's availability and role. Conflicts surface as you build — double-booked, over target, unavailable — and the estimated cost of the week moves as you work. Publish when it is ready, and not before.
Invite a chef and they accept with their own Cartelier account. The roster row links to their profile, and your house appears on it as a role you confirmed — a stronger claim than a printed menu. They choose which roles to show. When they leave, the role closes with its date and the history stays theirs.
And the record
Careers become traceable across houses, which is how the archive can answer who was in the kitchen when a menu was served.
One record, not eight products.
Your restaurant is probably already in the archive. Claiming it opens the studio on your existing record.