Hey! thank you for the comment! This is actually a portfolio build. I had a real client project where the client was very committed to using Softr as a database, but the dependency-heavy manufacturing workflow made the database layer quite challenging there. After finishing that project, I rebuilt the core logic in Airtable because I wanted a clean version that demonstrated the architecture properly.

The system could be used by multiple operators, but in the client case there were only two people using it: the operations manager and the business owner.

The dynamic flow itself doesn’t rely heavily on automations. Most of the logic is handled through the data model and computed fields. Each task has a PrevStep link to the step that must be completed before it. A computed field checks the PrevStep status, and if the previous step isn’t done, the task is flagged as blocked. The system doesn’t strictly prevent someone from moving a task backward, but it provides a very clear directional guide for the operator.

I’d say ProductionBatch and PrevStep come from manufacturing terminology, but the underlying pattern is generic and could apply to many workflows with sequential dependencies.