Claude cheat sheet

A one-page reference for using Claude well at work; strong with long documents and structured drafting. UK English. Check anything that matters against a trusted source.

Key capabilities by level

Foundations

• Draft, rewrite and summarise everyday writing in plain English.
• Attach or paste a long document and ask questions of it.
• Ask it to quote the exact line, so you can check its answer fast.

Practitioner

• Refine bigger outputs in the Artifact side panel, editing in place.
• Keep related chats and reference files together in a Project.
• Turn on web search and Research for current facts, then verify the links.

Power User

• Give a Project shared instructions so every chat inside it stays on-brief.
• Use Claude Cowork or Claude Code for multi-step tasks over your files.
• Compare model options when you need faster replies or deeper reasoning.

Tier map in three lines

• Free: chat, web search, memory and basic use across web and mobile.
• Individuals: Pro adds higher limits, unlimited Projects, Research and more; Max adds 5x or 20x more usage again.
• Organisations: Team adds central billing and admin; Enterprise adds SCIM, audit logs and stronger security.

See the current Claude pricing for what each plan includes today.

Five best prompts

1. I've pasted the Fernway policy document below. Summarise it in ten bullets, then quote the exact line on data retention. [paste]
2. Read the attached contract and tell me what it says about cancelling. Quote the wording and flag anything ambiguous.
3. Turn the key actions from these meeting notes into a checklist with owners and due dates. [attach]
4. Act as a critical reviewer of my report draft. List what's unclear, unsupported, or likely to be challenged. [paste]
5. Compare these three options in a table (cost, effort, and risk), then recommend one and say why. [paste details]

Top three mistakes

• Retyping a document by hand. Attach the file or paste the text; that's what Claude is built for.
• Trusting a summary blindly. Ask it to quote the source lines and check the important ones yourself.
• Ignoring the Artifact panel. If an answer opens to the side, that's the version to edit and reuse, not to copy back into the chat.