The core problem: spreadsheets cannot manage the April 26 switch timeline
When the new phase goes live with staggered enforcement dates from April 2026, models must switch by date, year, activity, and profession. Static spreadsheets usually miss that transition.
That is why teams get band-drop shocks after go-live even though pre-switch reports looked healthy.
Top 5 repeated spreadsheet mistakes
- Keeping one parameter table with no effective_from/effective_to for the staggered enforcement dates (April 19, April 26, May 31, June 30).
- Using stale c constants after go-live instead of year-specific 2026/2027/2028 values.
- Applying one threshold table instead of sector-specific c-value increases across all economic activity sectors.
- Counting sales/marketing below SAR 5,500, engineers below SAR 8,000, or procurement roles not meeting 70% toward Saudization.
- Publishing reports without pre-switch versus post-switch scenario comparison for each enforcement date.
The shift: from static files to time-aware scenario engines
What changes operationally?
Instead of periodic manual edits, teams version annual formula data and compare pre-switch vs post-switch outcomes before committing hires.
Direct management benefit
Fewer reclassification surprises, lower emergency correction costs, and a predictive workflow anchored to the go-live date.
Controls you should activate immediately
- Version formula parameters annually with precise effective dates per profession.
- Automate profession wage-floor and Saudization rate validation (SAR 5,500 sales/marketing, SAR 8,000 engineers, 70% procurement).
- Run direct pre/post simulations for each enforcement date plus 30/60/90-day projections.
- Trigger early warnings when projected post-switch band changes.
- Reconcile weekly with official Qiwa outputs.
Pre-hiring decision model
- Enter the proposed hire with profession and salary, and set the decision date relative to the staggered enforcement dates (April 19, April 26, May 31, June 30).
- Run a dual simulation: pre-switch output and post-switch output using the correct yearly constants.
- If the post-switch scenario shows band drop risk, pause approval or redesign the hiring mix first.
Execution takeaway
These spreadsheet errors are not formatting issues; they are date-transition failures. The fix is a dynamic system that tests decisions before and after April 26.