Reported Speech in Technical Documentation

When reporting speech in written documentation (post-mortems, meeting notes, incident reports), English uses the backshift rule: the tense moves one step into the past. Present simple ("restarts") → Past simple ("restarted"). So: "The developer said that the service restarted every 30 seconds." Option A keeps the original tense — acceptable in informal contexts but less formal. Option C uses future tense — backshift of "will restart" to "would restart" would be correct, but "will restart" is wrong here. Option D uses past continuous — incorrect backshift. Backshift tenses: present simple → past simple; present continuous → past continuous; will → would; can → could. In technical documentation, backshifted reported speech adds professionalism to incident summaries and meeting minutes.

Option A uses the present tense throughout — and that is correct here. The backshift rule does NOT apply when reporting a permanent fact or a currently valid specification. Rules and specs that are still in effect use present tense: "The spec states that tokens expire after 24 hours." The key is the reporting verb: states / says / specifies / indicates (present) → no backshift required. Backshift applies when the reporting verb is past: "The spec stated that tokens expired…" — this implies the spec may no longer be valid. In technical documentation, prefer present-tense reporting for active specifications: "The RFC specifies that…", "The contract defines that…", "The error message indicates that…"

"suggested that we add" is correct. After verbs of suggestion and recommendation (suggest, recommend, propose, advise), English uses the subjunctive in the that-clause: the verb stays in base form regardless of subject. "She suggested that we add…", "The team recommended that the service be restarted." Option B uses past tense ("added") — wrong in a subjunctive clause. Option C uses "will add" — wrong, future not appropriate. Option D uses "suggested us to add" — this structure is incorrect in English (unlike "advised us to add"). Technical documents often use reported suggestions: "The reviewer recommended that the function be refactored", "The architect proposed that the database be sharded."

"The error indicates that the connection was refused" is the standard form for reporting system errors and log messages in technical write-ups. When describing what an error, log, or message shows, use indicate / show / suggest (present) + past passive for the event: "The log indicates that the service was restarted", "The trace shows that the request was dropped", "The alert indicates that memory was exhausted." Option B incorrectly uses "is refusing" (continuous). Option C uses active voice ("refuses") — the connection is not doing the refusing; it was refused by the server. Option D uses "has been refusing" — continuous perfect, not appropriate for a discrete event. In bug reports and incident summaries, this pattern is ubiquitous: "The error indicates that X was Y."

"couldn't deploy" is the correct backshift of "can't deploy" in reported speech when the reporting verb is past tense ("agreed"). Backshift: can → could; can't → couldn't. "The team agreed that they couldn't deploy on Fridays." Option A keeps "can't" — acceptable in informal notes but not standard in formal minutes. Option C uses "cannot deploying" — grammatically incorrect (modal + base verb, never gerund). Option D uses "agreed to not deploying" — wrong structure; correct would be "agreed not to deploy." In formal meeting minutes and retrospective documentation, report decisions with: "The team agreed that…", "The stakeholders decided that…", "The engineers confirmed that…" — always with appropriate backshift when the reporting verb is past.