Writing job descriptions for hotel roles: a template with front office and housekeeping examples

A hotel job description is a one-page document that states why a role exists, who it reports to, its main duties in order of importance, the decisions it may take alone, the records it keeps and its compliance duties. It is a boundary document for the team, not a recruitment advert or a task list.

For example: two housekeepers disagree about who restocks the minibar. A guest is charged for a bottle nobody logged, the front desk says housekeeping owns it, housekeeping says the front desk does, and nobody can produce a document. The general manager decides, again, and the same argument returns next month.

A job description copied from somewhere, filed at hiring and never read again does no work. This article gives you a working hotel job description template: seven blocks, two worked examples for a front desk agent and a room attendant, and the connection to your SOPs, onboarding and yearly review.

What is a hotel job description actually for?#

It is a boundary document: it says what a role owns, what it may decide alone and where the next role takes over. Hiring is only one of its uses.

The page does three jobs. It settles the boundary between two roles before the argument reaches the general manager. It gives onboarding a target to reach, so a new starter knows what "good at this job" means. And it gives the appraisal a fixed reference that does not move with the season.

Be clear about what it is not. It is not the employment contract, which is a legal document with its own rules. It is not the standard operating procedure, which holds the steps of each task. It is not a training plan, and it is not a list of personality traits the manager hopes for.

Apply the one-page rule. If the draft does not fit on one page, the writer is describing procedures, and procedures belong in the SOP. A page that is read on day one and checked at appraisal beats a three-page document that is filed and forgotten.

Write it with the person doing the job, not for them. The department head drafts, the general manager and HR sign, and the page carries a version date and a named owner. The person who cleans the rooms knows exactly where her work crosses into the front desk's, and that crossing point is the most valuable sentence in the document.

Keep one description per role, not per person. In a small hotel one person may hold several roles, and the description of each role should state which other roles that person also holds. That makes cover during leave and seasonal peaks explicit rather than improvised.

If you are also mapping who decides what across the hotel, start with the hotel organisation chart and write the descriptions from it.

The one-page template, section by section#

Seven blocks cover a hotel role: purpose, reporting line, main duties in order, decisions allowed alone, records kept, compliance duties and working pattern.

Purpose is one sentence that starts with an outcome, not a task. For example: so that every arriving guest is registered, informed and in the right room. If the purpose sentence could apply to any role in any hotel, it is not finished.

Reporting line names who the role reports to, who covers when that person is off, and, in small hotels, which other roles the same person also holds. The test is that no one has two bosses on the same shift.

Main duties are five to eight, ordered by how much of the week they take or how much damage a missed one causes. Each duty names the SOP that holds the steps. If a duty has no SOP behind it, either the duty is too vague to check or the procedure is missing; both are worth fixing before publishing.

Decisions allowed alone need two numbers and one list: a money limit, an in-kind limit and the exceptions that must be escalated. The next section covers this in detail.

Records kept state what the role writes down and where: guest bill entries, room status, lost property, the shift handover note. This is what makes the role checkable afterwards, and it is the block most copied templates leave out.

Compliance duties are named as duties only. In Türkiye every stay involves a payment, a fiscal document (an invoice or e-document), a guest identity notification (KBS, the misafir kimlik bildirimi system) and personal data (KVKK, the personal data protection law). The description says who does which part, the SOP says how, and dates, scope and your own case should be confirmed with your accountant or legal adviser.

Working pattern covers shift, weekend and public holiday cover, break pattern, and who the role hands over to at the end of the shift.

For the "how" behind each duty, pair the description with your procedures; the guide to writing hotel SOPs that staff actually follow covers that half of the pair.

What may the role decide alone, and where does it stop?#

Give every role two numbers and one list: a money limit, an in-kind limit and the exceptions it must escalate.

The money limit is a stated figure in the local currency. For example, a front desk agent may reduce a bill by up to a set amount to close a complaint; anything above that goes to the duty manager. Without a currency and a figure, the limit is a sentence, not a rule.

The in-kind limit covers things without a price on the spot: a free upgrade within rooms already available, one comped minibar item, a late checkout to a stated hour. These are the gestures that make service feel generous, and they are also the ones that cost money quietly when nobody has a limit.

The escalation list names the exceptions: refunds above the limit, any change to a rate for a future date, anything involving a guest's identity documents, any safety incident, any suspected theft. Name the escalation target and the time, not just the department. "To the duty manager before the shift ends" is a rule; "to management" is a wish.

Separate a decision from a duty. Answering the telephone is a duty; waiving a charge is a decision. Only decisions need limits, and mixing the two makes the list unusable.

Review the limits when prices, the rate structure or the system change. A figure set two seasons ago may now approve far more than the manager intended, because everything around it has become more expensive.

Worked example: front desk agent#

A front desk agent owns the arrival and departure of every guest, the accuracy of the bill at check-out and the first written record of anything unusual during the shift.

The table below is an illustrative example, not a standard. Your hotel's limits, SOP names and shift pattern will differ.

Notice what is not in the table: the steps of a check-in, the wording of a complaint response, the layout of the folio. Those belong in the hotel check-in procedure and its SOP, which this page points to.

Worked example: room attendant#

A room attendant owns the condition and the reported status of an assigned set of rooms, and the record that tells the front desk which rooms can be sold.

Again, this is an illustrative example. Write your own limits and your own room status codes.

One note on room status: codes such as ready, not ready and out of order are common practice, but hotels and systems name and use them differently. Write your hotel's own codes into the description and keep the definitions in the SOP, so the front desk and housekeeping are reading the same words.

The honesty of the status report is the heart of this role. A room marked ready when it is not is the housekeeping equivalent of an unposted charge: it creates a failure someone else discovers in front of a guest.

How does the description connect to SOPs, onboarding and the yearly review?#

The description says what the role owns, the SOP says how the work is done, onboarding proves the person can do it, and the review checks the description is still true.

One duty, one SOP. If a duty has no SOP behind it, either the duty is too vague to check or the procedure is missing; both are worth fixing before publishing.

Build the onboarding checklist from the duty list, not from the SOP index. Each duty is signed off by a supervisor who has watched the person do it once. That is a checklist a new starter can finish in a week, and it maps directly to the page they were handed on day one. The seasonal staff onboarding first-week checklist shows how this works department by department.

Use the decisions list and the records list in the appraisal. Did the person stay inside the limits, and were the records complete? That is a fairer conversation than a general impression, and it protects both sides.

Run change control on the page. When a system, a rate structure or an SOP changes, the named owner checks the description in the same week and moves the version date. For seasonal staff, add a short seasonal addendum naming which duties are dropped and which are added, rather than writing a second document.

Treat the yearly review as a check, not the only moment for change. Roles drift during the season, one favour at a time, and the drift is what causes the arguments.

What to do next#

Pick one role this week and draft the one-pager with the person who does the job, not for them: purpose, reporting line, duties in order, the two limits and the escalation list, the records, the compliance duties and the working pattern. Test it on someone from another department, then have the general manager confirm the limits. Once that page exists, the SOP, the first-week checklist and the yearly review all have something fixed to point at, and the argument about the minibar has a place to end.