When using answer/subquestion randomization in LimeSurvey, authors cannot keep specific codes fixed in their
original positions. As soon as randomization is enabled, all items are treated the same and fully shuffled.

This creates several limitations:

• It is not possible to keep “special” options (e.g. “Don’t know”, “Other”, “None of the above”) consistently at the bottom while randomizing the rest.

• It is not possible to keep a particular option always first (or at a fixed index) while shuffling all other options.

• It is not possible to keep certain subquestions fixed within arrays or multiple‑choice questions while randomizing the remaining subquestions.

  These constraints apply across all question types that support randomization:

• Single-choice: List (radio), List dropdown, List with comment, Ranking.

• Multiple-choice and similar: Multi choice, Multi choice with comments.

• Array families and multi‑text/number questions that support random_order.

  Authors currently have to choose between:

• No randomization (fixed, biased order), or

• Full randomization (losing control over the position of key items).

• custom scripts managing exceptions

  There is no built-in way to declare “these specific codes must keep their original order/position; randomize
  everything else around them.”