Lessons

What happens to unfinished work when an automated workflow moves on?

What a failed quarter change taught me about unfinished work, and how the lesson applies to project phases, reporting periods, and procurement packages.

When your project moves to a new phase, a new procurement package or a new reporting period, where do the open items from the last stage go?

If an automated workflow is involved, pointing it at the new folder, tab or period doesn’t answer that question. Those leftover records still need somewhere to go.

I ran into this during a quarter change in a content-production workflow. The automation had been pointed at the new quarter’s tab, while an older staging record still referred to an item on the previous quarter’s tab.

The workflow searched the current tab, found no matching row, and then tried to perform an update without a row number. The run failed.

I approved two checks before the update. Records without a matching row on the current tab now get skipped. I chose not to have the workflow look back at the previous tab, so the older items get cleared by hand as a separate follow-up.

Why this matters for project coordination

The incident came from content production, not a design project. What carries over to architecture and interior design is how unfinished work gets handled at a transition.

A design practice might hit the same question when changing project phases, issuing a new procurement package, or opening a new reporting period.

The answer should be explicit. An item might stay in its original register, move through a reviewed carry-forward process, or become an exception assigned to a named person.

Changing the active destination doesn’t tell the system which of those is right.

Checks I’d make before a transition

First, identify the records still open in the previous stage, and check whether any downstream process still expects to find them there.

Next, verify the new destination. In another part of the same quarter change, the new quarter’s tab was missing a status dropdown that the previous tab had. A familiar layout didn’t mean all the operating controls were there.

Then test a missing match on purpose. The workflow should respond in a defined way when the item it expects can’t be found.

Finally, update the instructions and links people actually use. A repaired workflow plus an outdated procedure leaves the operator with conflicting guidance.

A successful run is only part of the check

Preventing an invalid update fixes the immediate failure. It doesn’t, by itself, finish the older work.

So the acceptance check needs two parts: confirm the workflow handles the exception correctly, and confirm someone can still see and resolve the outstanding item.

For a project manager, that’s the practical value. The transition should make it clear what’s moved forward, what’s still open, and what needs a decision.

Find out where your work waits.The Workflow Blueprint maps it in two to three weeks.
Book a Workflow Blueprint