The useful outcome

A correction should identify the task and precisely describe what changes. Restate any important constraints that must remain stable so the revised request does not accidentally replace the original goal.

An example request

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

For the venue research that is running, change capacity to 30 people. Keep the date and budget unchanged, and tell me whether earlier findings still qualify.

A practical sequence

  • Identify the running task
  • State the changed and unchanged constraints
  • Review the updated status before relying on the result

What to check

Check whether the correction reached the intended task and whether the work was stopped, revised or completed before it arrived.

A mistake to avoid

Do not assume a new chat message silently cancels every other job you have asked the assistant to do.

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.