> For the complete documentation index, see [llms.txt](https://sp.jerrygems.tech/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sp.jerrygems.tech/volume-xi-conditionals-si-clauses-and-reported-speech/66-reported-speech-and-temporal-backshifting.md).

# 66. Reported Speech: Temporal & Deictic Backshifting

> **Estilo Indirecto: Relaying Gossip and Shifting Dimensions**

Reported Speech (*Estilo Indirecto*) is the linguistic machinery of gossip, business memos, and journalism. When you tell someone what another person said in the past (*"She said that..."*), reality must step backwards in time.

***

## 🔄 The Tense Backshifting Engine

When the reporting verb is in a past tense (*dijo que...*, *comentó que...*, *aseguró que...*), the verb inside the quote must backshift according to this exact hierarchy:

| Direct Speech (What they originally said)       | Reported Speech (*Dijo que...*)         | Example Direct $\rightarrow$ Reported |
| ----------------------------------------------- | --------------------------------------- | ------------------------------------- |
| **Presente Indicativo** (*"Tengo hambre"*)      | $\rightarrow$ **Imperfecto Indicativo** | *Dijo que **tenía** hambre.*          |
| **Pretérito Indefinido** (*"Compré pan"*)       | $\rightarrow$ **Pluscuamperfecto**      | *Dijo que **había comprado** pan.*    |
| **Pretérito Perfecto** (*"He terminado"*)       | $\rightarrow$ **Pluscuamperfecto**      | *Dijo que **había terminado**.*       |
| **Futuro Simple** (*"Iré mañana"*)              | $\rightarrow$ **Condicional Simple**    | *Dijo que **iría** al día siguiente.* |
| **Presente Subjuntivo** (*"Quiero que vengas"*) | $\rightarrow$ **Imperfecto Subjuntivo** | *Dijo que quería que **viniera**.*    |
| **Imperativo (Command)** (*"¡Hazlo ya!"*)       | $\rightarrow$ **Imperfecto Subjuntivo** | *Me ordenó que lo **hiciera** ya.*    |

***

## 📍 Deictic Shifts (Space and Time Anchors)

You can't just change the verbs; you have to shift the spatial and temporal landmarks:

* **hoy** (today) $\longrightarrow$ **aquel día / ese día** (that day)
* **mañana** (tomorrow) $\longrightarrow$ **al día siguiente** (the following day)
* **ayer** (yesterday) $\longrightarrow$ **el día anterior** (the day before)
* **aquí / acá** (here) $\longrightarrow$ **allí / allá** (there)
* **este / esta** (this) $\longrightarrow$ **aquel / aquella / ese / esa** (that)

***

## 🌟 Multi-Level Field Examples

### 🟢 Level 1 (A1–A2: Casual Gossip)

* **Direct:** *Marta: «Estoy enferma y no puedo ir a trabajar».*\
  **Reported:** *Marta me dijo que **estaba** enferma y que no **podía** ir a trabajar.*\
  **English:** Marta told me that she was sick and couldn't go to work.

### 🟡 Level 2 (B1–B2: Broken Workplace Promises)

* **Direct:** *El jefe: «Mañana publicaremos las listas de ascensos».*\
  **Reported:** *El jefe nos aseguró que al día siguiente **publicarían** las listas de ascensos.*\
  **English:** The boss assured us that the following day they would publish the promotion lists.
* **Direct:** *Mamá: «¡Lava los platos antes de salir!»*\
  **Reported:** *Mamá me exigió que **lavara** los platos antes de salir.*\
  **English:** Mom demanded that I wash the dishes before heading out.

### 🔴 Level 3 (C1–C2: Legal Depositions & Press Releases)

* **Direct:** *El portavoz: «Hemos tomado medidas y no permitiremos que se repita el incidente jamás».*\
  **Reported:** *El portavoz aseveró que **habían tomado** medidas pertinentes y que bajo ninguna circunstancia **permitirían** que **se repitiese** semejante ultraje.*\
  **English:** The spokesperson asserted that they had taken pertinent measures and that under no circumstance would they allow such an outrage to be repeated.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://sp.jerrygems.tech/volume-xi-conditionals-si-clauses-and-reported-speech/66-reported-speech-and-temporal-backshifting.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
