Skip to content
Job.com
Apply now

AI at work

Claude at work

Choose a work task, try the sample, and check the result.

A useful place to start

Turn meeting notes into decisions and actions with AI

A traceable decision log and action list that keeps unknown owners and dates visible.

Start this lesson

Practice with

  • Meeting transcript
  • Meeting answer key

Practice files, reusable prompts, and review checks come with each lesson. Check the prerequisites before starting.

Before you begin

Use the sample files first. Follow your employer’s AI policy before adding workplace information. Review every result before sharing it.

Build your first workflow

Start with a small task

Follow the lessons in order, using their fictional inputs and review checks.

  1. Turn meeting notes into decisions and actions with AI
  2. Summarize a document in Claude with checkable quotations
  3. Draft work emails without inventing commitments
  4. Build a weekly status report in Claude Docs
  5. Create an interactive onboarding checklist in Claude

What do you need to get done?

Bring the workflow to your team

Practice with your team

Compare how people review the same source. Agree who checks the result before using it.

About Claude at work

Use Claude for a work task you can inspect from beginning to end. Pick an outcome, read the sample inputs, and follow the walkthrough before substituting approved workplace material. The goal is a result you can check against its source, with uncertainty still visible when the source does not settle a question.

Start with meeting notes or an email draft if you are new to this way of working. Then try a task that uses files, a structured output, or reusable context. Each lesson names its prerequisites and provides fictional inputs, an illustrative result, and checks specific to the task. You do not need to connect an inbox or use real employee records to practice.

Example outputs and completed product tests are different things. Read the testing information before relying on detailed instructions, and treat an unverified step as something that still needs validation. If a feature is unavailable in your account, use the troubleshooting guidance rather than assuming another product surface behaves the same way.

For team practice, compare how people review the same input. Agree who confirms facts, approves an external action, and maintains the source material. A copied prompt or downloaded file shows an interaction, not that a workplace task succeeded.