Managing academic scheduling across multiple sheets is a familiar struggle, and this reader's story captures the exact moment when a well-intentioned workbook starts fighting back. The core issue is straightforward: manual status entries on a secondary sheet become untethered when the primary data table is reordered. That is not a user error, it is a design limitation that many spreadsheet administrators eventually face.
The reader has done the hard work of building helper columns and INDEX-MATCH formulas to link the Release Tracking sheet to the Master Schedule. The problem is that those formulas rely on relative row positions, which collapse the moment anyone sorts or filters the primary table. The status in column I stays put while the data it references moves elsewhere. This is the kind of frustration that makes someone wonder if they are wasting their time.
Here is the honest answer: the approach is on the right track but needs one structural change. The unique ID generated in the Master Schedule helper column uses `ROW()`, which is inherently tied to the row number. When the table is sorted, that row number changes, and the link breaks. A better solution is to generate a static unique identifier that does not depend on row position. For example, combining a fixed prefix with a value from the row itself, such as the course CRN or a concatenation of date and course code, would create an ID that survives sorting. The condition in column C could then trigger that ID only when the condition is met, and the Release Tracking sheet could match on that static ID instead of a row-based reference.
This change preserves the reader's design goals: status entries remain on the secondary sheet, the Master Schedule stays lean, and filtering remains possible. It does require rebuilding the ID column and adjusting the lookup formulas, but those fifteen to twenty hours already spent troubleshooting relative positioning suggest the investment will pay off. The workbook is not broken, it just needs a more durable anchor.