Building the 30-prompt front-office library

A property that has built a 30-prompt front-office library has done in 90 days what most properties never get around to. The library is a property asset — versioned, shared, improved over time, owned by the operations director. The economics are unambiguous: 12-18 hours of authoring effort produces 200-400 hours of saved time per year, indefinitely.

What 30 prompts covers

A well-built front-office library has prompts grouped into five categories:

How to build the library

Week 1: identify the 30 use cases by polling the front-office team — "what do you write or rewrite repeatedly that you wish was faster?" The actual list will be very specific to the property.

Weeks 2-4: author one prompt per day. Each prompt follows the 5-part structure (role, task, voice, constraints, input) and includes 2-3 example inputs and the desired outputs. Each prompt gets reviewed by the operations director and the relevant department head before being added to the library.

Weeks 5-8: deploy. The library lives in a shared document (Notion, Google Doc, or a dedicated prompt-management tool like Promptables). The front-office team is trained on how to find and use each prompt. The library is referenced by name in shift huddles.

Weeks 9-13: refine. The team flags prompts that produce poor output. Each flag triggers a revision. By week 13, 80% of the library produces shippable output on the first run.

The asset that compounds

A property with a 30-prompt library that has been refined over 6 months has front-office staff who write responses in 60 seconds that used to take 6 minutes. Multiplied across hundreds of touchpoints per week, the saved time funds either lower headcount (a true cost saving) or higher-quality work on the same headcount (a true service improvement). Both outcomes are worth the investment.