diff --git a/WorkflowsOrdersPurging.md b/WorkflowsOrdersPurging.md
new file mode 100644
index 0000000..47fa1aa
--- /dev/null
+++ b/WorkflowsOrdersPurging.md
@@ -0,0 +1,7 @@
+# Order Purging
+
+To ensure that each customer order is handled properly should be considered the responsibility of the workflow and general user training.  However neither may be perfect (although ideally the workflow/UI would be as close as possible), and it may be that some orders manage to occasionally slip through the cracks.  Such situations may be helped or possibly even avoided with the following measures.
+
+## Stale Orders
+
+Most likely the easiest way to catch an order which has eluded the normal workflow would be based on the amount of time since its last logged event.  Of course some stages in the workflow will last longer than others, so a rather custom query would be required to discover "stale" orders at each of the various workflow stages.  What happens to stale orders will vary as well.  One step would likely be to set `OrderProduct.status` to "inactive" or similar; if that's all that's required then essentially this is just a [[manual update|WorkflowsOrdersManualUpdates]].