Which statement about iterative documentation in an engineering notebook is most accurate?

• A. It is optional and rarely used.
• B. It should only occur after the final design is complete.
• C. It documents personal reflections unrelated to the project.
• D. It documents changes, rationale, test results, and next steps after each iteration.

Answer: (D)

Iterative documentation records the evolution of a design after each cycle: what changed, why the change was made, the test results that informed it, and the planned next steps. This keeps a clear, data-backed trail of decisions and outcomes, which is essential for understanding how the design evolved and for guiding future work. Documenting after every iteration ensures you capture the reasoning behind each move and the evidence from tests, so teammates and mentors can follow the progress and replicate or build on it. Waiting until the end loses valuable context and the justification for early design choices, and jotting down personal reflections or treating documentation as optional won’t provide the project-wide, test-backed record that an engineering notebook is meant to be.