Skip to lesson
Lesson 14 / 2024 min readUp to date as of 19 October 2026

Examples of company workflows

Choose an example close to your work

Follow one example from problem to result. Check the data, tools and approval point, then measure the benefit in your own company.

Reading time is approximate. Allow extra time for the exercises; practice estimates are shown with the workshops.

After this lesson
  • Choose a process that fits your team
  • Define sources, output and the approval point
  • Plan a trial and measure time and quality
Section being translated

The chrome and course program are available in English. Deep training modules (prompt library, AI glossary, playbooks) are being translated - some content below is still in Polish.

Edition date and feature availability

Material revised: 19 October 2026; The interface and folder guide was revised on 19 October using supplied screenshots and OpenAI’s public plugin repositories; this does not reverify product access. The models in Chat, Work and Codex were checked on 16 October 2026, and the GPT-5.5 retirement date and Word access rules on 14 October 2026; other prices and availability were not fully reverified. Check the documentation and your account before using a feature: access depends on plan, region and administrator settings. Use the examples for practice and review the results yourself.

See how it works

A workflow example is a hypothesis to test

  1. Before

    Record current time and common errors.

  2. Trial

    Run the workflow on a representative example.

  3. Review

    Assess quality and include revision time.

  4. Comparison

    Base the conclusion on your measurement.

A concrete example

Illustrative measurement: before 30 min; AI 5 min + review 10 min = 15 min. A 15 min saving in this trial, not a guarantee for every business.

Can you omit review time?

No, when evaluating process cost. Include review, revisions and error risk.

Lesson 14 · Illustrative scenarios

Evaluate a process on your own data

These examples are not customer references or documented company results. Use them to plan a pilot and measure your own outcome.

  1. Before

    Manually draft posts from a catalogue.

  2. AI task

    AI creates 3 drafts using only the current catalogue.

  3. Human review

    A person checks products, prices, material rights and tone before publishing.

  4. Measurement

    Time to an accepted draft and number of revisions.

Your pilot measurement (minutes)

Enter all three values to compare total time.

Check quality separately. Faster execution does not justify accepting a wrong result.

Showcase - What you can do in a company

8 complete ChatGPT Work workflows

In shortChoose a process close to your work. Each card shows the required data, steps, output and review before approval.

One example is enough for a first trial. Read its conditions, use test data and record review time as well as execution time.

PROBLEM

The board deck gets built the night before. Data sits in three files, the conclusions live in one person's head, and the slides are glued together in a rush.

GOAL

A finished slide set with a narrative, charts built only from the data provided, and speaker notes.

WORKFLOW

INPUTSource files + meeting goal
ANALYSISWhat the data supports, what is missing
ACTIONOutline → slide copy → charts
QAEvery number sourced, one idea per slide
OUTPUTSlides + speaker notes

INPUT

  • Source material: report, spreadsheet, notes
  • Audience and meeting context
  • The one sentence that must stick
  • Target number of slides

TOOLS

Reading PDF / DOCX / XLSX filesData analysis and chartsReading Google Slides via the Google Drive connectorWeb search for market context

OUTPUT

  • Slide outline approved before any copy is written
  • Full slide content with speaker notes
  • Charts together with the data behind them
  • List of spots marked [TO BE FILLED IN BY A HUMAN]

PROMPT

Full workflow: ROLE / GOAL / INPUTS / TOOLS / PROCESS / OUTPUT / CONSTRAINTS / QA / APPROVAL GATE

ROLE
You are a consultant who builds board-level decks. You write tersely and always tie numbers back to a source.

GOAL
Build a presentation on [TOPIC] for [AUDIENCE] for the meeting [WHEN / CONTEXT]. Final result: a finished slide set with speaker notes.

INPUTS
- Source material: [UPLOADED FILES / LINKS / PASTED TEXT]
- The one message that must stick: [ONE SENTENCE]
- Number of slides: [e.g. 10-12]
- Language and tone: plain, factual, no marketing fluff

TOOLS
- Reading the uploaded files
- Data analysis and charts
- Web search only to fill in missing market context
- Reading an existing deck through the Google Drive connector, if it is connected.
- Deliver the result as a downloadable deck file or as a document with the slide structure. Do not assume you can write changes straight into a Google Slides file - if that is not available, say so plainly and hand me the file.

PROCESS
1. Read all material and list what it actually supports and what is absent from it.
2. Propose a storyline: problem → data → conclusion → recommendation → next step.
3. Show me the slide outline (title + one sentence per slide) and STOP.
4. After my approval, write the full slide content plus speaker notes.
5. Add charts only where I gave you numbers. Never chart data you were not given.
6. Finish with a "Questions we must be able to answer" slide.

OUTPUT
- Slide outline (step 3)
- Full slide content + speaker notes
- List of charts with the data behind each
- List of spots marked [TO BE FILLED IN BY A HUMAN]

CONSTRAINTS
- Do not invent numbers, client names or quotes. No data = write "no data".
- Max 6 lines of text per slide.
- Do not copy whole paragraphs from sources - summarize.

QA
Before showing the result, check and report under a "QA" heading:
- does every number name its source (file + location),
- does every slide carry one idea,
- does the narrative lead to the recommendation,
- what was missing from the material for the deck to be complete.

APPROVAL GATE
Stop after the outline and wait for my "OK". Do not create or overwrite any deck file without my explicit approval of a specific location.

SAFETY - where the agent must stop

  • Stop after the outline - copy is written only after approval.
  • Writes a deck file only to a named location and only with consent.
  • Never overwrites existing decks.
  • The deck does not leave the company without a human decision.

READ → DRAFT → REVIEW → APPROVE → WRITE / SEND

EXERCISE

Take one report you recently presented. Run the workflow and compare the agent's outline with your own. Write down 3 differences.

KPI - does this automation make sense?

Time saved: hours this deck used to take vs. now

Manual steps: how many times you had to switch between files

Errors: how many slide numbers needed a fix after verification

Delivery time: from receiving the data to a finished file

Measure these four on your own process. We do not publish invented savings numbers.

My progress

PROBLEM

The export sheet has 12,000 rows, three date formats and duplicates. Half a day goes by before anyone computes anything meaningful.

GOAL

A short report answering one business question, with metrics, charts and clearly flagged uncertainty.

WORKFLOW

INPUTSpreadsheet + business question
ANALYSISQuality audit: gaps, duplicates, outliers
ACTIONClean a copy + metrics and comparisons
QAControl totals match the original
OUTPUTReport: metrics, charts, recommendations

PROBLEM

A list of 200 trade-show leads sits in a sheet. The rep contacts the names they recognize; the rest go stale.

GOAL

A weekly priority ranking based on public buying signals, plus drafted first outreach.

WORKFLOW

INPUTLead list + ICP
ANALYSISPublic buying signals + scoring
ACTIONTOP N + email drafts
QALinks work, zero invented facts
OUTPUTRanking + drafts to send manually

PROBLEM

The team reads the same newsletters, everyone misses something different, and an important industry change lands two weeks late.

GOAL

One message a day, readable in 3 minutes - only what can actually affect our work.

WORKFLOW

INPUTSources + keywords + time
ANALYSISFilter duplicates and promo content
ACTIONMax 5 items: fact / meaning / link
QALinks work, dated within 24h
OUTPUTDigest in Slack or mail

PROBLEM

At month end someone digs through the mailbox, hunts for invoice attachments and retypes amounts into an accounting summary.

GOAL

All invoices in one folder, consistent file names, a roll-up summary and a gap list.

WORKFLOW

INPUTMailbox + date range + folder
ANALYSISRead numbers, dates and amounts from PDFs
ACTIONRename plan → copy files
QANet + VAT = gross, no duplicates
OUTPUTSummary + gap list

PROBLEM

We learn about a competitor's price change from a customer during a sales call - usually too late to prepare a response.

GOAL

An alert only when something material changes: pricing, packages, offer headline, a new feature or a new market.

WORKFLOW

INPUTURLs + definition of material change
ANALYSISComparison against the baseline
ACTIONAlert only on a listed change
QARule out A/B tests and regional variants
OUTPUTBefore / after / link / hypothesis

PROBLEM

A market entry decision rests on a few articles someone read over the weekend. Nobody knows what is fact and what is somebody's opinion.

GOAL

A report with a clear split: what we know and from where, what is merely likely, and what we do not know at all.

WORKFLOW

INPUTResearch question + material
ANALYSISResearch plan → gather and grade sources
ACTIONContrast contradictions, build the report
QAPrimary vs secondary sources, working links
OUTPUTFacts / hypotheses / gaps + recommendation

PROBLEM

Picking a tool or vendor ends with two quotes and a rushed decision, because nobody had time to compare terms.

GOAL

A comparison of at least three options against agreed criteria, plus a recommendation and a realistic alternative.

WORKFLOW

INPUTNeed + requirements + budget
ANALYSISWeighted criteria table for approval
ACTIONCollect 3+ options and compare terms
QASame scope, total cost, price sources
OUTPUTRecommendation + alternative + risks

Availability depends on your plan, region, workspace and administrator configuration.

Check your understanding

How do you check whether a rollout example fits your business?

This is a self-assessment. Mark the lesson complete after doing the exercise and reviewing the result.

Do this now

Choose one scenario close to your team's work. Define an owner, test data and output. Measure the whole trial, including review and corrections.

How to know you can do it

Keep as evidence: A trial record for one workflow.

  • You have a baseline without AI.
  • You include review and correction time.
  • The decision follows quality and time measurements.

Mark the lesson complete after the exercise and review. Reading progress and quiz answers alone do not confirm practical skill.

Lesson status
In progress — 0% of the page scrolled
Next