Write a project delay update email to a client

Answer A is highly appropriate for the context. It acknowledges the delay honestly, takes responsibility without being defensive, avoids blame, and respects the client relationship. The note that no external commitments are affected is a smart, reassuring addition. Slightly technical phrase about data structures is a minor issue.

The delay, cause, revised date, and next steps are all clearly stated. The explanation of the cause is plain and accessible. The two risk-reduction steps are clearly labeled and easy to follow. Minor jargon ('data structures require additional mapping') slightly reduces clarity for a non-technical reader.

Excellent structure: opening statement of delay, explanation, revised timeline, two numbered steps, reassurance, call invitation, and warm closing. Each paragraph has a clear purpose and flows logically. The email reads as a complete, well-organized document.

Two concrete, credible actions are described (dedicated senior engineer on critical path; daily internal checkpoints). The call invitation is specific: 20 minutes, early next week. The revised date is precise. All actionable elements are present and well-defined.

The tone is professional, warm, and human. It balances accountability with confidence and reassurance. The closing ('I value our partnership and your trust') is genuine without being sycophantic. The email reads as written by a real person who knows the client.

Well suited to the scenario: it is realistic, client-facing, accountable, and aligned with a three-year relationship that values direct communication. It avoids blame and mostly stays in plain business language.

The delay, cause, responsibility, revised date, and next steps are easy to understand. One sentence about data structures and mapping is slightly more technical than necessary but still understandable.

Very well organized: clear subject line, direct opening, explanation, revised timeline, mitigation steps, reassurance, and call request. Paragraph flow feels natural and purposeful.

Provides a specific revised delivery date and two concrete steps to reduce risk, plus a specific 20-minute call invitation for early next week. This makes follow-up easy.

Professional, candid, and human. It conveys accountability without defensiveness and helps preserve confidence through empathy and reassurance.

The email is highly appropriate for the situation. It addresses a long-term, important client with the right level of formality and directness. It correctly balances honesty with reassurance, fulfilling the prompt's requirements perfectly.

The email is exceptionally clear. The subject line is direct, the reason for the delay is explained in simple but specific terms ("data structures require additional mapping and testing"), and the new timeline is precise.

The structure is excellent. It follows a logical flow: update, bad news, explanation and ownership, new plan, risk mitigation, reassurance, and a clear next step. It's easy to follow and well-organized.

The email is highly actionable. It provides a clear new date and proposes a very specific next step: a "20 minute" call "early next week". This specificity makes it very easy for the client to respond and schedule.

The tone is perfectly calibrated. It's professional yet human, direct yet empathetic. The use of "I" ("I wanted to reach out," "I take full responsibility") creates a strong sense of personal accountability, which is excellent for relationship management.

Answer B is appropriate overall but slightly less tailored to the relationship context. The apology is present but the tone feels more generic. The placeholder name is a notable appropriateness failure for a client-facing email. The explanation avoids blame well but is slightly less direct.

Answer B is clear in structure and the revised date is explicit. The cause explanation is slightly vaguer ('unique architecture of the older system'). The two steps are clearly enumerated. Overall clarity is good but slightly below Answer A.

Answer B also has a logical structure with clear paragraphs for each element. The enumerated steps are well-placed. However, the closing is weaker and the placeholder name disrupts the professional finish. Structure is solid but slightly less polished than Answer A.

Two actions are present (additional senior engineer with legacy expertise; daily stand-ups on integration). These are credible. However, the call invitation is vague ('sometime next week') and the overall next-step clarity is lower. Actionability is adequate but less precise than Answer A.

Answer B's tone is professional but more formal and slightly impersonal. The apology is appropriate but the overall warmth is lower. The placeholder name significantly undermines the personal, relationship-aware tone the task requires. It reads more like a template than a tailored client communication.

Appropriate overall and professionally aligned with the task, but it reads more templated and less tailored to the stated relationship context. Some wording is a bit formal and less natural for a trusted long-term client.

Generally clear and easy to follow, with the revised date and cause stated plainly enough. Clarity is reduced slightly by abstract phrasing like unique architecture and tailored approach.

Clean and logical structure with all key sections present. It is organized well, though the flow feels more formulaic and the closing is less sharply actionable.

Includes a revised date and two mitigation steps, which is useful. The invitation to talk is less specific, and the action plan feels somewhat standard rather than sharply operational.

Polite and professional, but more formal and generic. It lacks some of the warmth and relationship-preserving nuance expected for an important long-term client.

The email is also very appropriate. The tone is slightly more formal ("Dear Maria") which is acceptable but perhaps less fitting for a 3-year relationship than A's approach. It handles the sensitive topic professionally.

The email is very clear, but slightly less specific than A. The explanation for the delay ("unforeseen complexities," "unique architecture") is a bit more generic. The call to action is also less specific ("a brief call" vs. "20 minutes").

The structure is also excellent and follows the same effective, logical flow as Answer A. It is well-organized and easy for the client to understand.

The email is actionable, providing a new date and suggesting a call. However, the call to action ("a brief call sometime next week") is less specific than A's, making it slightly less easy for the client to act on.

The tone is very good and professional. However, it feels slightly more corporate and less personal than A. The use of "We" for taking responsibility is fine, but A's use of "I" feels more accountable in this context.