I'm going to give you a fictional hotel scenario and I want you to draft a one-paragraph ownership update based on it. Here's the scenario: A 200-room full-service hotel in Atlanta had Q3 occupancy of 76%, ADR of $195, and RevPAR of $148 — all slightly below budget due to a large group cancellation. After the draft, flag any figures or claims I should verify before sending this to an ownership group.

What to look for: Claude should produce a clean ownership update and then proactively flag which figures or claims need verification. If it doesn't, ask: "Which parts of this should I verify before sending to ownership?"

Here is a fictional scenario: Spire is choosing between two growth strategies — expanding into full-service urban hotels or scaling a select-service suburban portfolio. Walk me through the financial and operational tradeoffs of each — then list the factors that require our leadership team's institutional knowledge, market relationships, and strategic vision that Claude cannot replicate.

What to look for: Claude should give you a structured analysis — and then clearly identify where its knowledge ends. Ask: "What would you need to know about our team and market relationships to make this more complete?" — notice what it can't answer.

Here is a fictional scenario: Our team is researching the hotel market in Charlotte, NC for a potential acquisition. Summarize the key demand drivers that typically impact hotel performance in that market — then add a section called 'Verify Before Use' flagging anything that may have changed recently and should be confirmed against a current source before including it in an investment memo.

What to look for: Claude should cite specific sources with dates and flag anything time-sensitive. If it doesn't, ask: "What is the source and publication date for each major claim? Which should I verify before including in an investment memo?"

Build me a group contract review checklist I can use before sending any client recap. Cover the five most critical terms, what each one means in plain language, and what to do if any term is missing from Claude's summary.

What to look for: Claude should produce a practical, actionable checklist — not a generic one. If the terms aren't in plain language, ask: "Explain each term as if the client has never signed a hotel group contract before."

Here is a fictional scenario: Our home office team is hiring a Director of Sales for a full-service hotel portfolio in the Southeast. Give me a compensation benchmarking framework I can use to set a competitive salary range — covering market factors, role scope, and experience level. No actual salary figures needed from me.

What to look for: If you feel tempted to share real figures to get a better answer — that's exactly the moment to stop and use placeholders instead. Claude should give you a solid benchmarking framework without needing any sensitive compensation data.

Here is a fictional scenario: Our home office team is three weeks into a Claude pilot program. Draft a short internal memo reminding the team that any work product prepared with AI assistance should be reviewed before distribution and disclosed where appropriate. Keep the tone clear, professional, and encouraging — frame AI as a tool that makes us better, not a risk to manage.

What to look for: Claude should produce something that reads like genuine leadership communication — warm, direct, and action-oriented. If it comes back stiff or alarmist, redirect: "Rewrite this so it encourages the team rather than warns them."

Here is a fictional scenario: A hospitality management company has just launched a Claude pilot program for their home office team. The team works across operations, finance, HR, and owner relations. What are the top 5 data privacy and appropriate use mistakes this type of team is most likely to make when using Claude for the first time? Give me a practical list with a one-line explanation for each.

What to look for: Claude should give you a practical, jargon-free list. If any item feels too generic, ask: "Reframe this with a hotel operations or home office example" — and notice how much more relevant it becomes.

Prompt 1 — Specific

Here is a fictional hotel performance update: Occupancy for Q3 came in at 74%, two points below budget, driven by a softer-than-expected corporate segment in July. ADR held at $198, and forward bookings for Q4 are tracking 9% ahead of last year. One property in the Southeast requires immediate attention — staffing gaps are affecting service scores. Write a two-paragraph summary for a non-technical ownership audience. Lead with the most important finding and close with one recommended action.

Prompt 2 — Vague

Summarize this.

What to look for: The two outputs should feel noticeably different. The specific prompt produces a focused, audience-appropriate summary with a clear action. The vague one produces something generic with no clear purpose. That gap is the skill — and it applies to every prompt you write.

Start a new Claude chat. Paste a piece of your own writing first — a recent email, memo, or summary works well. Then add this prompt on a new line:

Write something new in the exact same voice, tone, and length as the example above.

What to look for: Claude should closely mirror your structure, sentence length, and tone. If it drifts, say "You're being too formal" or "Make it shorter" — Claude adjusts in real time.

💡 How to paste your writing: Copy any text from your email, Word document, or other source and paste it directly into the Claude prompt bar. Claude will read everything you provide and work from it immediately.

Here is a fictional scenario: Our home office team needs to choose between two vendors for a new hotel reporting tool. Vendor A costs $2,400/year, integrates with our current PMS, but has limited customer support. Vendor B costs $3,800/year, requires a new PMS integration, but includes 24/7 support and a dedicated account manager. Walk me through the tradeoffs before giving me a view — don't skip to a recommendation.

What to look for: Claude should structure its reasoning clearly on both sides before drawing a conclusion. If it jumps straight to a recommendation, redirect: "Walk me through your reasoning before giving a view."

Here is a fictional scenario: You just finished a quarterly review call with a hotel owner. Occupancy came in at 71% against a 76% budget, but forward bookings for Q4 are tracking 8% ahead of the same period last year. Write a three-sentence follow-up email. Audience: a long-term owner who values directness. Tone: confident and forward-looking. End with one clear next step.

What to look for: Claude should structure the email exactly as specified. If any parameter is off — tone, length, or closing — give one specific redirect and see how precisely it adjusts. That precision is the skill.

Here is a fictional scenario: You just received a vendor software agreement for a hotel management tool and have 60 minutes before a contract review call. Give me five specific questions I can paste directly into Claude when I upload this agreement — designed to surface the most critical provisions a home office professional needs to know before any vendor contract discussion.

What to look for: Claude should give you five sharp, specific questions — not generic ones. Save the final list as a reusable template for any vendor agreement review.

💡 How to upload a document: Click the paperclip icon in the Claude prompt bar and select your file — PDF, Word, or Excel. Claude will read the entire document so you can ask targeted questions without reading it yourself.

Create a one-page owner-update template I can reuse — sections for performance highlights, variance to budget, forward outlook, and one action item. Put it in an Artifact so I can edit it.

Step 4: Once the Artifact opens, send follow-up instructions like "add a short executive summary at the top" and watch the panel update in place.

What to look for: The document should open in the side panel and update in place as you give instructions — not regenerate from scratch in the chat each time. If it doesn't open as an Artifact, add: "Put this in an Artifact so I can edit it."

💡 How to use Artifacts: When Claude creates something substantial, it appears in a panel to the right of the chat. Edit it by giving new instructions, or use the version selector at the bottom-left to move between versions.

Here is a fictional scenario: Draft a performance update memo for a home office team covering three key points: Q3 occupancy came in at 73% against a 77% budget, two markets are showing strong Q4 pickup, and one property needs an urgent staffing review. Write the first version as a formal memo. Then rewrite it as a brief, direct internal update for a team that already has the context. Present both versions side by side.

What to look for: The two versions should feel immediately and noticeably different. If they don't, redirect: "Make the internal version even more direct — bullet points only, no preamble."

Here is fictional performance data from four hotel markets: Nashville — occupancy 79%, ADR $195, strong group demand, minimal new supply. Atlanta — occupancy 73%, ADR $182, slow corporate recovery, two new hotels opening Q2. Dallas — occupancy 82%, ADR $201, strong corporate demand, significant new supply pipeline. Denver — occupancy 68%, ADR $188, strong leisure but lagging corporate, soft Q4 outlook. Extract the three most consistent themes across all four markets, rank them by significance, and flag any market that runs counter to the overall trend.

What to look for: Claude should produce a structured, synthesized analysis — not four separate market summaries. If it defaults to summarizing each market individually, redirect: "Don't summarize each market separately — identify themes that cut across all four."

Here is a fictional scenario: Our team is preparing a briefing on current US hotel market conditions for an upcoming ownership meeting. Summarize the three most significant trends currently impacting full-service hotel performance in the US — cite each source, note its publication date, and flag anything where the data may have shifted further since publication.

What to look for: Claude should cite specific, dated sources for each trend. If it doesn't, ask: "What is the source and publication date for each claim?" Scan the citations before anything goes into a formal document — outlet credibility and recency both matter.

💡 Getting better results from web search: Ask Claude to cite sources and include publication dates. For critical figures, follow up with "Is there more recent data on this?" to prompt a fresh search. Always scan citations before relying on specific numbers in a formal document.

Here is a fictional scenario: Our home office team is managing a hotel management contract renewal for a 250-room full-service hotel in Nashville. The contract expires in 90 days, the operator is requesting a 5-year extension with a fee increase, and ownership wants to explore alternatives before committing. Pretend this is the first message in a Claude Project. Confirm you have the context, summarize the three most important things you'll need to track across our conversations, and ask me one clarifying question to get started.

What to look for: Claude should confirm the context clearly, identify the key threads to track, and ask a smart clarifying question. If it doesn't, add: "What else do you need from me to make sure you have full context for our future conversations on this?"

💡 How to create a Project: Click "Projects" in the left sidebar of Claude Chat and select "New Project." Add background context in the project instructions field — every conversation within that Project will have access to it automatically.

Draft a complete Claude preference setup for a home office professional at a hotel management company who communicates regularly with ownership groups, hotel operators, and internal leadership. Include preferences for response length, format, tone, and how Claude should handle uncertainty. Make each preference specific enough to apply consistently across any type of request.

What to look for: Claude should give you a complete, ready-to-use preference set — not vague guidelines. If any preference feels too broad, ask: "Make the tone preference more specific to someone who writes owner communications and internal leadership updates."

💡 How to set preferences: In Claude Chat, click your profile icon → Settings → Profile. Add your preference statements in the "What would you like Claude to know about you?" field. Claude will apply them automatically to every conversation going forward.

Review what you know about me from our past conversations and give me a complete picture. Cover my role, my communication preferences, the projects and topics we've discussed, and anything sensitive or outdated I should consider removing. Be specific — I want to use this as a baseline to make sure our future conversations are as efficient as possible.

What to look for: Claude should give you a specific, organized summary of what it's retaining. If anything looks sensitive or outdated, visit Settings → Memory immediately and remove it.

💡 How to manage memory: Go to Settings → Memory in Claude Chat to view, edit, or delete what Claude has retained about you. You can also ask Claude directly what it remembers — then visit Settings to make any updates.