A practical example

A request.
A task.
An owner.

A client asks for a website change. Here’s how an agreed workflow could organise the handoff.

Illustrative walkthrough with fictional data. This page does not connect to an inbox, create real tasks or change a website.

The straightforward case

The details are there.
The next step is clear.

Original requestFictional client
“Please change our weekday hours to 9 am–5 pm on the contact page.”
Assume the sender, client website and authorised website team are already known.
  1. Check the request

    Identify the client, affected page and requested change. Confirm that this request has not already been handled.

  2. Prepare the task

    Create “Update contact page hours,” retain the original message and include the proposed new hours.

  3. Assign the owner

    Route the task to the agreed website team. The team reviews the request and makes the website change.

  4. Record the handoff

    Keep the source request and task reference together so someone can trace what happened and follow up.

When it isn’t straightforward

Some requests need
a second look.

The request is missing details
“Can you update the hours?”

Next step: ask for clarification. The request stays in review until the page and new hours are supplied. A person owns that follow-up; the workflow does not guess the change.

The same request arrives again

Next step: check the existing task. A known source request should reference the task already created. The agreed duplicate checks are tested against the actual systems before launch.

The task system stops responding

Next step: alert the owner and check the result. If a task may already exist, reconcile that outcome before retrying. Use the agreed manual fallback while the connection is unavailable.

A similar handoff
in your business?

We can walk through one example with you and check whether your tools already support it.

Book a 30-minute call

Review scope and payment terms