ARROW EXECUTION

One work list for every consultant, across every client

The plan says this month. What is actually being done this week?

The delivery products say what was committed and to whom. Execution is the layer underneath that — the day-to-day work that discharges those commitments, and the record of what was actually done against them.

What Arrow Execution does

  • One list per consultant, across every delivery product
  • What was done, by whom, against which commitment
  • Reads the suite over Arrow rather than keeping its own copy

Who it is for

Consultants and team leads who work across recurring, project and retainer clients and would rather work from one list than three.

How it connects to the suite

Reads from

Standalone, Execution answers its own question. Inside Arrow it shares one sign-in, one people directory and one licence store with every other product.

Questions

Arrow Execution FAQ

Does Arrow Execution keep its own copy of the work?

No. It reads the commitments from Delivery, Projects and Retainer through Arrow, so every task exists once, in the product that owns it.

How do consultants record what they did?

From the same list: a project task books hours, a recurring task is marked done with a note, and the record goes back to the product the commitment came from.

See Arrow Execution on your own work.

Thirty minutes, a live system, and the products that matter to you.