The useful outcome

A status request should report the existing task rather than launch a second copy. The useful answer names completed steps, remaining work and any issue that needs your input.

An example request

This is an illustrative request, not a customer result or a promise that every connected service supports every step.

What is the status of the supplier comparison already running? Do not restart it. Tell me whether you need a decision or more information.

A practical sequence

  • Identify the existing task
  • Ask for its current state
  • Respond only to the named blocker or choice

What to check

Check whether the task is running, finished, cancelled or waiting for input. A progress statement should not imply fresh work was started.

A mistake to avoid

Do not repeat the original request just to get an update if that could create duplicate external actions.

Using Bris for this work

Bris supports background work, reminders and requested public-web watches. Define the outcome, timing and notification conditions together. Ask for the status when needed and revise or cancel the task if circumstances change. A progress message is not a completed result.