> ## Documentation Index
> Fetch the complete documentation index at: https://docs.workmore.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# How your process handles many things

> Records — one trip through your steps for each item of work.

Most recurring work isn't one thing — it's *many* things handled the same way.
Forty new signups. A dozen form submissions. Each one needs the same treatment.

In Workmore, each item of work travels through your steps as a **record**. If last
week had forty signups, forty records flow through the same process, and each one
gets the same steps applied to it. You describe the work *once*; it happens for
*each*.

## Why this matters to you

You don't write your process forty times. You write it once — "take a signup,
summarize it, add it to the list" — and Workmore runs it for every signup that
came in. That's the whole point of making work repeatable.

## When you want "each" vs. "all"

Sometimes you want to act on **each** item on its own:

> "Send a welcome email to *each* new signup."

Other times you want the **whole set** together:

> "Email the team *one* summary of *all* last week's signups."

Workmore lets you do both. When you need to handle items one at a time, you
**split** the list into separate records; when you need to bring them back
together, you **combine** them into one. If you just want to use the whole list as
it is — like counting it for a summary — you don't split at all.

You'll reach for these only when a step needs them. Until then, the simple case —
one item, one trip through the steps — is the default, and it's usually all you
need.