Plantilla gratuita
Plantilla de status report semanal en inglés (para PMs y líderes técnicos)
Un formato para reportar el avance de tu proyecto cada semana en inglés: lo importante primero, riesgos con dueño y mitigación, y decisiones claras. Incluye un ejemplo completo, el vocabulario RAG y cómo resumirlo en un párrafo para ejecutivos.
Para guardarla como PDF: botón Descargar PDF → destino Guardar como PDF.
1. La plantilla para completar (parte 1)
Copia esta estructura en tu correo, Confluence o Notion y reemplaza los corchetes.
| [Project name] — Weekly Status Report Week of [date] · Prepared by [name] | Encabezado: proyecto, semana y autor. |
| Overall status: [Green / Amber / Red] Previous week: [Green / Amber / Red] | Estado RAG general, y el de la semana anterior para mostrar la tendencia. |
| Summary: We are [on track / behind schedule] for [milestone] on [date]. [One sentence on the main achievement]. [One sentence on the main risk or decision needed]. | Bottom line up front: si solo leen esto, ya saben lo esencial. |
| Progress this week: • Completed [task / milestone]. • [Task] is [X%] complete. | Lo que avanzó, en bullets cortos con verbos en pasado. |
| Next week: • Start [task]. • Finish [task] by [day]. | Plan para los próximos días. |
2. La plantilla para completar (parte 2)
| Risks & issues: • [Risk / issue] — Impact: [High / Medium / Low] — Owner: [name] — Mitigation: [action] — Due: [date] | Riesgo = puede pasar. Issue = ya está pasando. Siempre con dueño y acción. |
| Decisions needed: • [Decision] — from [person / committee] — by [date] — Options: [A] / [B] — Recommendation: [A] | Qué necesitas que decidan, quién, para cuándo y qué recomiendas. |
| Dependencies: • Waiting on [team / vendor] for [deliverable] by [date]. | Lo que depende de otros equipos o proveedores. |
| Budget: [On budget / X% over budget] (optional) Key dates: [milestone] — [date] | Opcional, según lo que tu sponsor necesite ver. |
3. Ejemplo completo: migración a la nube (parte 1)
Proyecto ficticio: migrar las aplicaciones internas de una empresa a AWS.
| Cloud Migration — Weekly Status Report Week of [date] · Prepared by [your name] | Encabezado. |
| Overall status: Amber (previous week: Green) | Bajó de verde a ámbar: hay que explicar por qué. |
| Summary: We are slightly behind schedule for the Phase 2 cutover, planned for the end of the month. The HR and finance apps were migrated successfully this week. The main risk is a delay in the firewall changes, and we need a decision on the cutover window by Thursday. | Bottom line up front: estado, logro, riesgo y decisión en tres frases. |
| Progress this week: • Migrated the HR and finance applications to AWS with no downtime. • Completed load testing for the reporting service. • Database replication for the CRM is 70% complete. | Avance concreto. |
| Next week: • Finish CRM database replication. • Run the disaster recovery test. • Prepare the cutover runbook for Phase 2. | Plan. |
4. Ejemplo completo: migración a la nube (parte 2)
| Risks & issues: • Issue: The firewall rule changes are one week late. Impact: High. Owner: Network team lead. Mitigation: Daily follow-up and a temporary VPN route for testing. Due: Wednesday. • Risk: The legacy billing app may not be compatible with the new database version. Impact: Medium. Owner: Backend lead. Mitigation: Compatibility testing in staging this week. | Un issue (ya pasa) y un riesgo (puede pasar), cada uno con dueño y mitigación. |
| Decisions needed: • Approve the cutover window — from the IT steering committee — by Thursday. Options: Saturday night (lower user impact) or Tuesday night (more support staff available). Recommendation: Saturday night. | Decisión con opciones y recomendación. |
| Dependencies: • Waiting on the security team for the final penetration test report. • Waiting on the vendor for updated license keys. | Dependencias externas. |
5. Vocabulario RAG
| Green: on track, no major issues. | Verde: todo según el plan. |
| Amber: at risk, but we have a plan to recover. | Ámbar (en EE. UU. también "yellow"): hay riesgos, pero bajo control. |
| Red: off track, we need help or a decision to recover. | Rojo: no se cumplirá el plan sin intervención. |
| The project moved from green to amber this week. | Cambio de estado. |
| We expect to be back to green by [date]. | Plan de recuperación. |
| The status is red because [reason], and we need [action] to recover. | Rojo siempre con motivo y pedido. |
| Watermelon project | Verde por fuera, rojo por dentro: no lo hagas. Reporta el estado real. |
6. Frases para levantar riesgos
| I want to flag a risk that could affect the go-live date. | Introducir un riesgo. |
| If [event] happens, we could lose [X] days. | Explicar el impacto. |
| The likelihood is low, but the impact would be high. | Probabilidad vs. impacto. |
| To mitigate this, we are [action]. | Qué estás haciendo al respecto. |
| This has now become an issue, and it's blocking [task]. | Un riesgo que se materializó. |
| We need to escalate this to [person / committee]. | Escalar. |
7. Frases para pedir decisiones
| We need a decision on [topic] by [date] to stay on schedule. | Decisión con fecha límite. |
| There are two options: [A], which [pro / con], or [B], which [pro / con]. | Presentar opciones. |
| Our recommendation is [A], because [reason]. | Recomendar, no solo preguntar. |
| If we don't decide by [date], the impact will be [consequence]. | Costo de no decidir. |
| Could you confirm whether we can go ahead with [option]? | Pedir aprobación. |
| Please let me know if you'd like to discuss this in more detail. | Ofrecer una conversación. |
8. Versión ejecutiva en un párrafo
Para un director o un sponsor con poco tiempo: estado + logro + riesgo + pedido, en ese orden y en cuatro frases como máximo. Deja fuera el detalle técnico.
| [Project] is [Green / Amber / Red]. This week we [main achievement]. The main risk is [risk], which could delay [milestone] by [time]. We need [decision / support] from [person] by [date]. | Plantilla. |
| The cloud migration is amber. This week we moved the HR and finance apps to AWS with no downtime. The main risk is a delay in firewall changes, which could push the Phase 2 cutover by one week. We need the steering committee to approve the cutover window by Thursday. | El ejemplo anterior, resumido. |
Sigue practicando
Para reuniones con stakeholders, negociación de plazos y más vocabulario de gestión, lee Inglés para project managers en el blog de Ingles4IT.