When Google Forms inserts a new response row, formulas can drift, jump to the wrong row, or keep pointing at the row above. The safest fix is to separate raw response columns from a clean formula pattern, then decide whether the logic should be an array formula, a processing tab, or a model-row copy workflow.
If formulas move after a new Google Forms submission, check whether the formula should be a fixed reference, an array formula, or a row-by-row copy. For row-specific logic, keep one clean model row and copy that pattern into each new response row. Then test one real submission before trusting the sheet.
The formula probably copied with the wrong relative reference, or it was placed in a row that does not match the inserted response row.
The new response row may not have inherited the helper-column pattern, or the copied formula may be pointing at a blank source cell.
Google Forms controls where the response row lands. That means a formula that felt stable in a normal spreadsheet table can behave differently once a fresh submission inserts a row.
A submission is added by the form, so the spreadsheet is not behaving like a person filled the next blank cell by hand.
If a copied formula uses the wrong relative row, it can keep pointing at the old row or the row above the one you expected.
Some rows may be manually edited, some dragged down, and some inserted by Google Forms, which makes the model hard to trust.
Even when the math still works, helper columns, colors, and validation cues can stop lining up with the newest response row.
Usually row 2, or the first complete row that already contains the formula pattern you want copied.
Move thresholds, lookup tables, and constants into fixed ranges or another tab so they do not drift.
Use one real form response and inspect the newest row before sharing the workflow widely.
For simple columns, an array formula or a separate processing tab may be cleaner than copying formulas into every response row. That is often the right path when the logic is purely analytical and does not depend on per-row formatting or backfill.
Simple calculations, text cleanup, and whole-column logic that does not depend on one row carrying its own status or formatting.
Dashboards, pivots, and reporting sheets that should stay separate from the raw Google Forms response tab.
That usually means the copied pattern used a relative reference that moved differently than you intended. Recheck the row model and the newest response row together.
You can for a tiny sheet, but it is fragile. New submissions can still land in a way that leaves helper cells blank or misaligned.
No. Use absolute references for constants and lookup ranges, but keep row-relative references where each response should evaluate its own row.
Yes, use backfill after the source row is verified. Start with a small range first if the sheet is important.