Reuse a run you have already done

When you create a run, turn on Start from a previous run’s workflow and choose which one.

What copies

The plan, in full: every zone, every task with its instructions, estimates, priorities and dependencies, and every gear case. All of it fresh — the new run owns its copy, and editing it doesn’t touch the run you copied from.

What doesn’t

Last time’s helpers, requests, completed work and sign-offs.

None of that comes across, and it shouldn’t: it happened on a different day with different people. Copying it would produce a run that claims work was done before anyone arrived, and a report that’s fiction.

So the copy arrives as a clean plan with nothing done yet, which is exactly what you want.

It arrives already reviewed

Because you reviewed this plan when you ran it the first time, the copy comes through reviewed. Helper invitations work straight away — you can create a run and send the link in the same minute.

That’s the whole point of reusing: the setup you run every week shouldn’t cost you a planning session every week.

Edit it and it asks again

The moment you change the copied plan, it asks for a fresh review before invitations reopen.

That isn’t bureaucracy. The thing you reviewed is no longer the thing you’d be inviting people into, and the review is a specific claim — I read this and it’s right for this run. A changed plan needs that claim made again.

Until you review it, the last reviewed version stays live. Nobody sees a half-finished edit.

When not to copy

If the space changed, the team changed, or the last run went badly, write it fresh. Copying a plan that didn’t work reproduces the plan that didn’t work, and the second run is where you’d have fixed it.

The report from the last run is the right thing to read first — particularly what was not done, which is usually a list of what the plan got wrong.