How does probeo handle content work across many pages?

At scale describes how probeo handles volume, not a separate job. The same stages that produce one new page run across many questions at once. Every page still goes through its own approvals.

What probeo produces

Nothing beyond what each page produces: a planned outcome for every question, then a brief, research, an outline and a draft for each one you approve. The difference is that they move in batches rather than one at a time.

How it works

• Planning. Probeo plans every question in your question bank, five at a time by default. Each question gets its own outcome and rationale (see opportunities).
• Adding questions. You can submit up to 25 questions at once.
• Running stages. Work waiting at the same stage is picked up together, up to 25 items per batch. Items that need different stages run in separate batches.
• Repeat runs. A stage that has already produced its output for an item reuses it rather than producing a second one.

Batching changes how work runs, not how it is reviewed. Each item’s next stage still waits for an approval of that item’s exact output.

What this does not cover

There is no bulk publishing and no step that skips review. Each draft ends at its own final approval, and publishing is yours to do.

Common questions

Does a large batch lower the quality of each page?

Each item runs through the same stages and checks as a single page would. The batch only groups items that are at the same stage.

Can one failed item hold up the rest?

Each item has its own status. A failed item is marked as needing attention and can be run again on its own.

Is there a limit on the size of the question bank?

Planning reads the whole bank. The limits above apply to how many questions you add at once and how many items run in one batch.