Email writing occupies a unique position in TCS placement preparation because it operates at the intersection of two things that matter at completely different stages of your career. During placement, it appears in verbal ability assessments and interview evaluations as a proxy for your professional communication judgment. After joining, it becomes the medium through which almost every professional relationship is built and maintained. A fresher who cannot write a clear, correctly formatted professional email is a liability to every team they join. This guide covers both dimensions fully: the format, scenarios, and evaluation criteria that matter for placement, and the tone, templates, and etiquette principles that make you effective once you are inside TCS.

TCS Guide

The Status of Email Writing in TCS Assessment

TCS previously included a dedicated email writing section in its recruitment test where candidates were given a scenario and asked to compose a complete email. While this dedicated section has been deprioritised in the current NQT pattern, email writing skills continue to be tested in two indirect ways that matter equally.

Through Verbal Ability questions: Sentence ordering (para jumble) questions frequently use professional email extracts as their passage. Error identification questions regularly feature sentences drawn from formal business communication. Comprehension passages sometimes present corporate memos or client emails. A candidate who is familiar with how professional emails are structured will perform better on these questions than one who has never studied the format.

Through the interview: Both Technical and HR interviewers evaluate your communication ability throughout the conversation. For candidates advancing to Digital and Prime profiles, communication quality carries specific weight because these profiles involve client-facing work. An interviewer who asks you to “describe a situation where you communicated a technical issue to a non-technical person” is evaluating the same competency that formal email writing tests. Your ability to be concise, organised, and appropriately formal in spoken communication mirrors your ability to produce effective written communication.

The professional value of strong email writing is even more direct: every TCS project involves daily written communication with teammates, leads, clients, and stakeholders. Freshers who arrive with professional writing skills get noticed earlier, are trusted with client communication sooner, and advance into visible roles faster than those who rely entirely on spoken communication.

The Formal Email Structure: Every Element Explained

A professional email has six structural components. Each serves a specific function and has specific rules.

1. The Subject Line

The subject line is the most underestimated element of professional email writing. It is read before the email body and determines whether the email gets opened promptly, gets deprioritised, or gets missed entirely. It also serves as the navigational reference when the recipient needs to find the email again later.

What makes a good subject line:

Specific rather than vague. “Request for Invoice Status - Vendor XYZ - PO 45231” is better than “Invoice Query.” The specific subject tells the recipient exactly what the email is about before they open it.

Action-oriented when a response is needed. “Approval Required: Q3 Report Submission - Deadline Friday” communicates both the subject and the urgency without needing the body to do that work. “Action Required” and “Response Needed by [date]” are standard corporate signals.

Status prefix for updates. “Update: Database Migration - Phase 2 Complete” tells the recipient immediately that this is a status communication, not a request. “FYI:” prefix works similarly for informational emails that require no response.

Brief. Subject lines should be under 60 characters to display fully in most email clients. Long subjects get truncated and lose their clarity.

Common subject line failures to avoid:

  • Blank subject lines - force the recipient to open the email to understand its purpose
  • “Hi” or “Hello” as a subject - provides no information
  • “URGENT” applied to everything - desensitises the recipient and loses its meaning for genuinely urgent items
  • Question as subject without context - “Is the report ready?” as a subject line is confusing without knowing which report

2. The Salutation

The salutation opens the email body and establishes the register of the communication.

Formal salutations (for clients, senior management, external recipients):

  • “Dear Mr. / Ms. / Dr. [Last Name],” - the gold standard for formal correspondence
  • “Dear [Full Name],” - appropriate when gender is uncertain or the person uses a non-binary title
  • “Dear Sir / Madam,” - for formal letters where the recipient is known by role but not name

Semi-formal salutations (for colleagues at the same level, team leads, internal recipients with an established relationship):

  • “Hi [First Name],” - standard and appropriate for most internal corporate communication
  • “Hello [First Name],” - slightly more formal than “Hi” but still warm

Group salutations:

  • “Dear Team,” - for emails addressed to an established team
  • “Hi All,” - informal, appropriate for internal team communications
  • “Dear Colleagues,” - semi-formal group address

What to avoid:

  • “To Whom It May Concern” - use only when the recipient is completely unknown and even then, try to find a specific contact
  • “Hey” - too informal for any professional email
  • Omitting the salutation entirely - acceptable only in rapid internal message-chain replies, never for a fresh email
  • “Respected Sir/Madam” - this phrasing is a South Asian English convention that is not standard in international professional communication; use “Dear Sir/Madam” instead

3. The Opening Line

The first sentence of the email body should state the purpose immediately. Corporate readers scan emails quickly - they should understand within five seconds what you need or what you are communicating.

Effective opening lines by email type:

Request: “I am writing to request approval for [specific request].” Follow-up: “I am following up on my email of [general reference - ‘last Tuesday’ or ‘last week’] regarding [subject].” Response: “Thank you for your email regarding [subject]. I have [completed the action / reviewed the document / investigated the issue].” Information: “Please find below a status update on [project/task].” Problem report: “I am writing to bring to your attention an issue with [specific issue] that requires your input.” Confirmation: “I am writing to confirm [the details of / our agreement regarding] [subject].”

4. The Body

The body delivers the substance of the email. It should be structured, concise, and complete.

Structure the body logically:

For a request email: context (why you need this) → specific request → any supporting details → timeline or deadline → call to action.

For a problem report email: description of the issue (what happened, when, how discovered) → impact of the issue → what has been done so far → what you need the recipient to do.

For an update email: current status → what was completed → what remains → any blockers or risks → next expected update or milestone.

Concision principles:

One idea per paragraph. Three to four sentences per paragraph. If a paragraph is running to six or seven sentences, it contains more than one idea - split it.

Use bullet points or numbered lists when presenting three or more items. “The affected systems include the inventory database, the customer portal, and the payment gateway” becomes clearer as three bullets when the list is longer.

Avoid padding. Phrases like “I hope this email finds you well,” “Please do not hesitate to contact me should you have any questions or concerns,” and “I would like to take this opportunity to express my sincere gratitude” add length without adding content. Professional communication is valued for precision, not for warmth-padding.

Tone calibration within the body:

Match your language to the relationship and context. An email to a client about a service disruption should be apologetic and precise. An email to a team lead requesting leave should be respectful and direct. An email to a peer offering help should be warm and casual. The same facts can be expressed across a wide tonal range.

5. The Closing Line

The closing line signals that the email is complete and typically includes one of: a call to action, an expression of availability, or an acknowledgment.

Effective closing lines:

“Please let me know if you need any additional information.” “I look forward to your response.” “Please feel free to reach out if you have any questions.” “I will proceed with [action] unless I hear otherwise by [timeframe].” “Thank you for your assistance with this matter.” “Please confirm receipt of this email.”

6. The Sign-off and Signature

Formal sign-offs:

  • “Regards,”
  • “Best regards,”
  • “Sincerely,” (more common in formal letters than emails)
  • “Yours faithfully,” (for correspondence where the recipient is not known by name)
  • “Yours sincerely,” (for correspondence where the recipient is known by name)

Semi-formal sign-offs:

  • “Best,”
  • “Thanks,” (appropriate when the email includes a thank-you element)
  • “Warm regards,”

What to avoid:

  • “Love,” - inappropriate in any professional context
  • “Cheers,” - acceptable in some cultures, questionable in others; avoid in client and senior management communication
  • “Ciao,” - too informal for corporate communication
  • No sign-off at all - abrupt and signals poor communication judgment

The signature block for workplace emails typically includes:

  • Full name
  • Designation and department
  • Company name
  • Phone number
  • Email address (sometimes optional within the company if it is in the “From” field)
  • Office location (optional)

For placement test email writing, include your name as the sign-off. The signature block is not typically required in test scenarios.

Evaluation Criteria for Email Writing in Assessments

When TCS or any assessor evaluates a written email, the scoring framework covers five dimensions:

1. Format Compliance

Is the structural format correct? Subject line present and appropriate? Salutation correct for the context? Opening line establishes purpose? Sign-off appropriate? Each missing structural element costs marks.

2. Grammar and Spelling

Is the email grammatically correct? No subject-verb disagreement, no tense inconsistency, no misplaced modifiers, no spelling errors. A single grammar error per paragraph is typically tolerated in assessment contexts; multiple errors signal poor language control.

3. Tone Appropriateness

Is the tone appropriate for the scenario? Formal where formality is required? Professional without being stiff? A common mistake is over-formality in internal communications (“I humbly request that you kindly consider”) or under-formality in external communications (“Hey, just checking in about that invoice”). Tone-matching is a communication intelligence signal.

4. Completeness

Does the email address everything required by the scenario? A complaint email that describes the problem but omits a request for resolution is incomplete. A leave application that gives the dates but omits the reason is incomplete. Read the scenario requirements carefully and ensure every required element is in the email.

5. Concision and Clarity

Is the email the right length? Not so brief that it misses required content, not so padded that key information is buried. A 300-word email that answers the question is better than a 600-word email that buries the answer in paragraphs of context. Assessors evaluate whether a reader could extract the core message in 30 seconds.

Type 1: Complaint Emails

Complaint emails are among the most commonly tested email types in placement assessments. They require balancing assertiveness (clearly stating that something is wrong) with professionalism (avoiding aggressive or accusatory language).

Model Complaint Email: To a Service Vendor About Delayed Delivery

Subject: Complaint: Delayed Delivery of Office Supplies - Purchase Order 78421

Dear Mr. Sharma,

I am writing to formally raise a concern regarding the delivery of office supplies ordered under Purchase Order 78421, placed on [general reference such as “three weeks ago”].

As per the agreed terms, delivery was expected within seven business days of order placement. To date, the items have not been received, and no communication has been provided from your team regarding the delay. Multiple follow-up calls to your customer service line have not resulted in a confirmed delivery date.

This delay has impacted our office operations, as the ordered items include materials required for an ongoing project.

I request that you provide a confirmed delivery date by [timeframe - “within two business days”] and an explanation for the delay. If delivery cannot be confirmed within this window, we will need to explore alternative suppliers for this and future orders.

I trust this matter will receive your prompt attention.

Regards, [Name] [Designation]

Analysis of this email:

Subject: Specific - names the subject, the action type, and the reference number. A recipient scanning their inbox knows immediately what this is about.

Tone: Assertive without being aggressive. “Formally raise a concern” is stronger than “wanted to mention” but less adversarial than “complaining about your terrible service.”

Completeness: Describes the problem, states the impact, requests specific action, sets a timeline, and includes a consequence for non-compliance.

Grammar: Present tense for current situation (“items have not been received”), past tense for completed events (“order placed”).

Model Complaint Email: To a Police Station About a Theft

Some placement assessments include civic complaint letters. These are formal correspondence to government or institutional recipients and require the most structured format.

Subject: Written Complaint Regarding Theft of Personal Property - [Your Name]

To, The Inspector, [Name] Police Station, [City]

Subject: Complaint Regarding Theft of Laptop and Mobile Phone

Respected Sir / Madam,

I, [Name], residing at [Address], wish to register a formal complaint regarding the theft of my personal property.

On [general time reference - “the morning of the incident”], my laptop computer (Make: Dell, Model: Inspiron, approximate value Rs. 45,000) and mobile phone (Make: Samsung, Model: Galaxy A52, approximate value Rs. 20,000) were stolen from my vehicle parked at [location], between [time range]. I discovered the theft upon returning to my vehicle and immediately checked the surrounding area before proceeding to file this complaint.

I request that the authorities investigate this incident and take necessary action to recover the stolen items. The serial number of the laptop is [serial number] and the IMEI of the mobile phone is [IMEI number].

I am prepared to provide any further information or assistance required for the investigation.

Yours faithfully, [Name] [Contact Number] [Address]

Analysis:

The letter-format complaint to a government body uses “To / Subject” header format rather than an email subject line, as these are often submitted as written letters or formal emails to official addresses. The salutation is “Respected Sir / Madam” rather than “Dear” in this specific formal government context - this is one of the few situations where that construction is appropriate in Indian formal communication. All relevant details (items, values, serial numbers) are included because they are necessary for an official complaint.

Type 2: Request Emails

Request emails must be clear about what is being asked, provide sufficient justification, and make the request easy for the recipient to act on.

Model Request Email: Leave Application to Manager

Subject: Leave Request - [Your Name] - [Date Range]

Hi [Manager’s Name],

I would like to request leave from [start date reference] to [end date reference] (three working days) for a personal family matter.

I have completed the [current project phase / pending tasks] and have briefed [colleague’s name] on the status of the remaining items so that work can continue uninterrupted during my absence. All pending deliverables scheduled within this period have either been completed in advance or have been handed over.

Please let me know if this request can be approved or if there are any concerns about the timing.

Thank you, [Name]

Analysis:

Tone: Appropriate for an internal request to a direct manager - semi-formal (“Hi”) rather than stiff. The tone signals professional maturity.

Completeness: States the dates, gives the reason (without over-explaining personal matters), demonstrates preparation (briefed colleague, completed deliverables), and makes a clear request.

Length: Three short paragraphs. Does not pad. A leave request does not require a 500-word essay.

Model Request Email: Requesting Information From a Vendor

Subject: Request for Product Specifications - Industrial Shelving Units

Dear Ms. Patel,

I am writing on behalf of [Company Name]’s Facilities team to request detailed specifications for your industrial shelving unit range, specifically units suitable for warehouse applications.

We are in the process of evaluating options for a storage expansion project and would appreciate the following information:

  • Load capacity per shelf (in kg)
  • Available configurations (number of shelves, height, width options)
  • Material and surface treatment
  • Lead time for bulk orders (50+ units)
  • Pricing for orders in the range of 50-100 units

Could you please provide this information at your earliest convenience, or direct me to the relevant product catalogue? We are aiming to finalise our shortlist within the next two weeks.

Thank you for your time.

Regards, [Name] [Designation] [Company Name] [Contact]

Analysis:

Uses a bullet list for the specific information requests - appropriate because there are five distinct items, each deserving equal visual weight. The closing sets a timeline without being demanding. The level of detail provided (quantity range, project context) helps the vendor provide the most relevant response.

Type 3: Inquiry Emails

Inquiry emails gather information before a decision is made. The key is being specific about what you need without committing to anything.

Model Inquiry Email: To a Training Institute

Subject: Inquiry - Advanced Java Certification Program

Dear Training Coordinator,

I am interested in learning more about your Advanced Java Certification Program and would like to request the following information:

  1. Program duration and schedule (weekday vs weekend batches)
  2. Prerequisites for enrolment
  3. Certification authority and recognition (industry or government accredited)
  4. Course fee and available payment plans
  5. Placement assistance provided upon completion

Could you also confirm whether the program is available in both online and classroom formats?

I would appreciate a response at your earliest convenience.

Regards, [Name] [Contact Number]

Type 4: Report and Update Emails

Status update emails and brief reports are among the most frequently written emails in corporate environments. They should be structured, scannable, and complete.

Model Status Update Email: Weekly Project Update to Manager

Subject: Weekly Status Update - Customer Portal Migration - [Week Reference]

Hi [Manager’s Name],

Please find below the status update for the Customer Portal Migration project for this week.

Completed This Week:

  • Database schema migration for modules 1-3 completed and verified
  • User acceptance testing for the login module - all 24 test cases passed
  • Deployment of build v2.3 to the staging environment

In Progress:

  • Performance testing for the dashboard module (expected completion: end of next week)
  • Documentation update for the API changes (50% complete)

Blockers:

  • The staging environment experienced intermittent latency issues on two occasions. The infrastructure team has been notified and is investigating. This may impact the performance testing timeline if unresolved.

Next Week’s Plan:

  • Complete performance testing and document results
  • Begin integration testing for the payment module
  • Internal demo to stakeholders (confirm date with you)

Please let me know if you have any questions or concerns.

Thanks, [Name]

Analysis:

Using bold headers within the email makes the update scannable. A manager reading twenty update emails per week should be able to extract the status in 20 seconds. The blocker section is particularly important - never bury a risk in a general paragraph. If something is at risk, it deserves its own clearly labelled section.

Model Escalation Email

Escalation emails require extra care because they involve raising an issue to someone above the normal chain of communication. They must be factual, not emotional, and must demonstrate that normal channels were already attempted.

Subject: Escalation Required: Unresolved Database Access Issue Affecting Project Timeline

Hi [Senior Manager’s Name],

I am escalating an access issue that has been unresolved for five business days and is now impacting our project delivery timeline.

Issue Summary: Three members of our development team (listed below) require read access to the production database for testing purposes. The access request was submitted through the standard IT helpdesk portal on [general reference - “last Monday”]. Despite two follow-up calls and an email to the helpdesk, no action has been taken.

Impact: The integration testing phase is scheduled to begin [next week]. Without this access, testing cannot proceed and the project milestone will be missed.

Attempted Resolution:

  • Helpdesk ticket raised: Ticket ID HELP-4521
  • Follow-up call to helpdesk: [date reference - “Wednesday and Thursday of this week”]
  • Email to helpdesk supervisor: [date reference - “yesterday”]
  • All contacts confirmed the ticket is under review but no timeline was given

Request: I would appreciate your assistance in expediting this request. The required access level is read-only, limited to the customer_transactions and inventory_audit tables.

Team members requiring access: [Name 1], [Name 2], [Name 3]

Thank you for your attention to this matter.

Regards, [Name]

Analysis:

This email is carefully calibrated. It does not attack the helpdesk or express frustration. It presents facts, documents the attempts made, quantifies the impact, and makes a specific, modest request. The “read-only, limited to two tables” detail demonstrates that the request is minimal and reasonable. Escalation emails that express frustration or make sweeping criticisms of teams or individuals create political problems; escalation emails that present clear facts and specific requests get resolved.

Type 5: Professional Acknowledgment and Confirmation Emails

Model Confirmation Email: Confirming a Meeting

Subject: Meeting Confirmation - Project Kick-off - [Date/Day Reference]

Hi [Name],

This email confirms our project kick-off meeting scheduled for [day, time, location / video call platform].

Agenda for the meeting:

  1. Project overview and objectives
  2. Team introductions and role assignments
  3. Timeline review and milestone discussion
  4. Q&A and open discussion

Please let me know if you would like to add any items to the agenda before the meeting.

Regards, [Name]

Model Acknowledgment Email: Acknowledging Receipt of a Document

Subject: Acknowledgment: Receipt of Financial Report - Q2

Dear Mr. Rajan,

I am writing to acknowledge receipt of the Q2 Financial Report submitted by your team.

The document has been received in its entirety (48 pages, including appendices). I will review the report and revert with any questions or comments within three business days.

Thank you for your prompt submission.

Regards, [Name] [Designation]

Professional Tone Calibration: Formal vs Semi-Formal vs Informal

Understanding when to use each register is one of the most important professional communication skills and one that freshers often get wrong in both directions.

The Tone Spectrum

Formal: Used for client communication, senior management, government bodies, legal or financial correspondence, first-contact communication with external parties. Characterised by: complete sentences, no contractions (use “I am” not “I’m”), no colloquialisms, precise vocabulary, full salutations and sign-offs.

Semi-formal: Used for internal team communication, routine colleague interaction, direct manager communication after a relationship is established. Characterised by: contractions acceptable, first names, slightly warmer tone, shorter sentences, “Hi” rather than “Dear.”

Informal: Used for messages to close colleagues you know well, team chat platforms (Slack, Teams), casual internal communication. Characterised by: fragments acceptable, emoji sometimes appropriate, abbreviations, casual openers.

The cardinal rule: When in doubt, go one register more formal than you think is needed. Being slightly too formal is almost never a problem. Being too casual in a formal context signals poor judgment.

Tone Calibration Examples

Scenario: Informing a client that a deliverable will be delayed

Over-formal (stilted): “I humbly write to inform you that, owing to unforeseen circumstances beyond our control, the deliverable in question shall experience a delay in its delivery timeline.”

Appropriately formal: “I am writing to inform you that the deliverable scheduled for [original date reference] will be delayed by two business days. The revised delivery date is [new date reference]. We apologise for any inconvenience this causes.”

Too informal for client communication: “Hey, just a heads up - the report will be a couple of days late. Sorry about that!”

Scenario: Asking a colleague for help with a task

Too formal for internal communication: “Dear Mr. Singh, I am writing to formally request your assistance with the task of data entry for the Q3 report, as described in the project plan.”

Appropriately semi-formal: “Hi Rahul, would you be able to help with the data entry for the Q3 report? I estimate it would take about two hours. Let me know if you’re available this week.”

Common Grammar Mistakes in Professional Emails

These errors appear most frequently in corporate email writing and should be actively avoided.

Subject-Verb Agreement With Business Nouns

“The team are working on the issue” - incorrect in formal business English. “The team is working on the issue” - treat collective nouns (team, management, committee, department) as singular units in formal writing.

“The data shows a 15% increase” - “data” is formally plural but widely accepted as singular in business writing. In formal correspondence, “the data show” is technically correct; “the data shows” is widely accepted.

Tense Consistency in Status Updates

“The testing has been completed. The team moves to integration phase and started documentation” - mixed tenses. Use: “Testing has been completed. The team has moved to the integration phase and started documentation.”

Incorrect Prepositions With Business Verbs

  • “Revert back to me” - “revert” means to return, so “back” is redundant. “Revert to me” or simply “respond to me.”
  • “Please do the needful” - this is a South Asian English idiom not used in standard global business English. Use: “Please take the necessary action” or “Please proceed accordingly.”
  • “Kindly do the same” - vague. Specify the action: “Please approve the request” or “Please provide the information.”

Passive Voice Overuse

Excessive passive voice makes emails feel evasive and harder to read. “Mistakes were made” does not tell anyone who is responsible or what will be done. “Our team identified an error in the configuration and has corrected it” is clearer and more accountable.

Use passive voice when the actor is genuinely unknown or unimportant: “The server was restarted at 3 AM” (who restarted it does not matter). Avoid passive voice when ownership and action matter.

Double Negatives and Convoluted Negations

“I cannot not attend the meeting” - redundant. “I will attend the meeting.” “The issue is not unlike the one we encountered last quarter” - unnecessarily complex. “The issue is similar to the one we encountered last quarter.”

Unnecessary Qualifiers

“In my humble opinion, I think it might perhaps be possible to consider…” - every qualifier weakens the statement. “I recommend considering…” is stronger and clearer.

Subject Line Optimisation: The 10-Second Rule

In a busy corporate inbox, your email has approximately 10 seconds to communicate its value before it is deprioritised. The subject line is almost entirely responsible for that first impression.

Subject Line Formulas That Work

[Action]: [Topic] - [Reference/Deadline] “Approval Required: Budget Proposal - Action Needed by Friday” “Review Requested: API Documentation v2.1”

[Status]: [Project] - [Phase/Date Reference] “Update: Customer Portal Migration - Testing Phase Complete” “Alert: Production Database Connectivity Issue - Investigation Ongoing”

[Topic]: [Specific Detail] - [Context] “Leave Request: Priya Sharma - March 15-17” “Invoice Query: TCS Order #78421 - Delivery Status”

What Weak Subject Lines Have in Common

  • Generic nouns: “Issue,” “Update,” “Question,” “Follow-up” with no specifics
  • No recipient value: the subject does not signal why the recipient should open it now
  • All caps: reads as shouting, professional emails do not use all-caps in subjects
  • Emoji in formal correspondence: inappropriate for client and formal internal communication

Email Etiquette for Freshers Joining TCS

These rules govern professional email behavior and are often learned through painful trial and error. Learn them before your first day.

The Reply-All Trap

Reply-All sends your response to every person on the original email thread. Before hitting Reply-All, ask: does every person on this thread need to read my reply? In most cases, the answer is no. If you are confirming a meeting time to one person, reply only to them. Reserve Reply-All for updates that genuinely affect all recipients.

CC and BCC Usage

CC (Carbon Copy): For people who need to be informed but are not the primary recipient and do not need to take action. Your manager might be CC’d on a client email so they are aware of the communication without being the primary recipient.

BCC (Blind Carbon Copy): For including someone in correspondence without the primary recipients seeing their inclusion. Common use: sending a mass announcement to a large group where you do not want all recipients to see each other’s email addresses. BCC yourself on important outgoing emails if you want a sent-folder record in your inbox.

Rule: Do not CC your manager on every email as a form of performance signalling. Do CC your manager on client communications they should be aware of, on escalations, and when explicitly requested. Excessive CC-ing is considered a sign of insecurity and poor communication judgment.

Response Time Expectations

Corporate email culture has informal response time norms:

  • Emails from clients or senior management: respond within 4 hours or by end of business day
  • Emails from direct team members: respond within the same business day
  • Emails that require no action but acknowledge receipt: a brief acknowledgment within 24 hours is professional
  • If you cannot fully respond within the expected window: send a brief acknowledgment (“I have received your email and will respond with full details by [timeframe]”)

Email Threads: When to Start a New Thread

If a conversation has evolved so that the subject line no longer accurately describes the current discussion, start a new email thread with an updated subject line. Continuing a thread titled “Meeting Confirmation - Q3 Review” to discuss a completely separate contract issue creates confusion for all parties and makes the thread impossible to locate later.

Signature Consistency

In the TCS workplace, your signature block should be consistent across all outgoing emails. Do not omit it from quick internal replies if company policy requires it. Do not add unprofessional elements (personal quotes, emoji, non-work social media links) to your work email signature.

Email Writing in the TCS Workplace: Common Scenarios

Writing to a Client About a Service Disruption

Subject: Service Alert: Portal Access Intermittent - Investigation Underway

Dear [Client Name/Contact],

We are writing to inform you that some users are experiencing intermittent difficulty accessing the [Portal Name] between [time reference]. Our technical team identified the issue at [time reference] and has been actively working on a resolution.

What We Know: The issue appears to be related to the load balancer configuration following routine maintenance performed earlier today.

Current Status: The technical team is working on a fix. We expect to restore full service within [estimated timeframe].

What You Should Do: Users experiencing access issues may retry after 10 minutes. If access is not restored within [timeframe], please contact our support desk.

We apologise for the inconvenience and will provide an update within [timeframe] or sooner if the issue is resolved.

Regards, [Name] [Designation] TCS [Account/Team Name]

Writing to an Internal Team About a Process Change

Subject: Process Update: New Deployment Approval Workflow - Effective [Day Reference]

Hi Team,

Please note that the deployment approval process has been updated, effective from [general day reference - “next Monday”].

What Has Changed: All production deployments now require sign-off from both the Technical Lead and the Account Manager before they can be scheduled. Previously, only Technical Lead approval was required.

Why This Change: Following last month’s incident, management has added the Account Manager approval step to ensure client communication alignment for all production changes.

New Process:

  1. Complete the deployment checklist (no change)
  2. Obtain Technical Lead sign-off (no change)
  3. NEW: Submit the deployment request form to the Account Manager for approval (form link below)
  4. Schedule deployment after both approvals are received

The updated process document is attached to this email. Please review it and reach out if you have questions.

Thanks, [Name]

Writing to HR About a Payroll Discrepancy

Subject: Payroll Discrepancy - [Month Reference] - Employee ID [Your ID]

Dear HR Team,

I am writing to bring to your attention a discrepancy in my payroll for [month reference].

My payslip shows a [deduction/addition] of Rs. [amount] under the category “[category name]” that I cannot account for. Based on my understanding of my compensation structure, I did not expect this [deduction/amount].

Could you please review my payslip and clarify the basis for this item? I have attached my payslip for reference.

I would appreciate your response at the earliest, as I want to ensure this is resolved before the next payroll cycle.

Thank you for your assistance.

Regards, [Name] [Employee ID] [Department] [Contact Number]

How Verbal Ability Questions Test Email-Adjacent Skills

Understanding the connection between email writing skills and Verbal Ability test performance helps you see why professional communication training has a direct test payoff.

Para Jumble Questions Using Email Extracts

Para jumble questions often use professional communication passages because emails and memos have predictable structural logic - they are purpose-built to communicate clearly and follow consistent organisational patterns. A candidate who understands that business emails always open with purpose, develop with detail, and close with action will recognise that structure in a jumbled passage faster than one who is encountering formal business prose for the first time.

Example para jumble from a status update email: (A) “Once the testing phase is complete, the deployment will proceed as planned.” (B) “We are currently in the final stage of the testing phase for the payment module.” (C) “This email provides a status update on the payment module integration project.” (D) “Two minor issues discovered during unit testing have been resolved by the development team.”

Correct order: C-B-D-A. The structure follows: purpose statement → current status → detail on status → next step. This is exactly the structure of a professional status update email.

Error Identification in Formal Contexts

Error identification questions in Verbal Ability frequently use sentences drawn from formal correspondence. Grammar errors in professional emails tend to be the same types tested in placement assessments: subject-verb agreement with business nouns, tense consistency in formal reporting, preposition usage with professional verbs, and parallel structure in bulleted lists.

Example error identification question: “(A) The management team / (B) have decided to / (C) postpone the annual review / (D) to next quarter.”

Answer: B. “Management team” is a collective noun acting as a single unit; the verb should be “has decided.”

This is identical to the kind of error that appears in poorly written business emails. Studying formal email grammar simultaneously prepares you for these questions.

Reading Comprehension From Business Passages

RC passages in placement tests frequently use corporate reports, business news articles, and professional communication excerpts. Familiarity with business vocabulary (reconciliation, escalation, deliverable, stakeholder, turnaround time, SLA) and business writing conventions makes these passages easier to navigate - you spend less time parsing unfamiliar language and more time answering the actual questions.

Practice Scenarios: Write These Emails

To build email writing fluency before your placement test or interview, practice writing complete emails for each of the following scenarios. Time yourself: a well-prepared candidate should complete a 150-200 word professional email in 8-10 minutes.

Scenario 1: You ordered a laptop for office use three weeks ago. The vendor confirmed delivery within five business days but it has not arrived. Write a formal complaint email to the vendor.

Scenario 2: You need to take three days of leave for a family event. Write a leave request email to your manager, ensuring a smooth handover.

Scenario 3: Your team discovered a bug in the production system on a Friday afternoon that is causing incorrect invoice amounts for approximately 5% of transactions. Write an escalation email to your senior manager.

Scenario 4: A client has reported that their data export function has not been working for two days. Write an acknowledgment email that confirms receipt of their complaint, outlines what is being done, and sets a timeline for resolution.

Scenario 5: Your department is relocating to a new floor in the office building next week. Write an announcement email to your team covering the move date, new location details, and any actions team members need to take.

Scenario 6: You attended a vendor presentation and want to request a formal proposal. Write an inquiry email requesting the pricing, timeline, and terms for their SaaS product.

Scenario 7: Write a formal complaint to the local municipal corporation about a water supply disruption that has been affecting your residential area for four days. Cover: the nature of the problem, the duration, any attempts already made to contact the authority, and your request.

Scenario 8: You are a project manager. Write a weekly status update email to your client contact covering: completed tasks, work in progress, blockers, and next week’s plan. Invent plausible project details.

Evaluate your practice emails against the five criteria: format compliance, grammar, tone appropriateness, completeness, and concision. Have a teacher, mentor, or English-proficient peer review them and mark specific improvement areas.

Quick Reference: Email Writing Rules Summary

Subject Line: Specific, informative, under 60 characters. Include action type (Request, Update, Alert), topic, and reference number where applicable.

Salutation: “Dear [Name],” for formal. “Hi [Name],” for internal. “Dear Sir/Madam,” when recipient is unknown.

Opening Line: State your purpose in the first sentence. No warm-up filler.

Body: One idea per paragraph. Three to four sentences maximum per paragraph. Bullet points for lists of three or more items.

Closing Line: State expected action or express availability. One sentence.

Sign-off: “Regards,” or “Best regards,” for formal. “Thanks,” or “Best,” for semi-formal.

Length: 150-300 words covers most professional email scenarios. Escalations and reports may run longer if complexity requires it.

Grammar rules to check before sending: Subject-verb agreement with team/management/committee. Tense consistency throughout. Prepositions correct for verbs (respond to, comply with, adhere to). No dangling modifiers.

Tone check: Would this email embarrass you if forwarded to your senior manager? If no, it is safe to send.

Final check before sending: Has every question in the scenario been addressed? Is the call to action clear? Is the subject line accurate? Is the salutation correct? Is the sign-off appropriate?

Email writing is a learnable skill that improves directly with practice. The professional who writes clear, correctly formatted emails stands out immediately in any team - not because the skill is rare, but because poor email writing is so common that good email writing becomes visible and memorable by contrast.

Type 6: Apology Emails

Apology emails are among the most difficult to write well because they must acknowledge an error without excessive self-flagellation, accept accountability without creating unnecessary legal exposure, and move forward with a solution. In the TCS workplace, these are written for delayed deliverables, service outages, miscommunications, and errors in documents or reports.

Model Apology Email: To a Client for a Data Error in a Report

Subject: Correction: Q2 Revenue Report - Error Identified and Resolved

Dear Ms. Kapoor,

I am writing to inform you that we have identified an error in the Q2 Revenue Report submitted to you earlier this week.

The revenue figures for the North Region on page 7 were incorrectly calculated due to a formula error in the source spreadsheet. The correct figures are reflected in the updated report attached to this email.

We sincerely apologise for this error and for any confusion it may have caused. We have reviewed the remainder of the report and confirmed that all other figures are accurate.

We have also implemented an additional verification step in our report generation process to prevent recurrence of this type of error.

Please review the attached corrected report and let me know if you have any questions.

Regards, [Name] [Designation]

Analysis: This apology is direct. It does not bury the error in softening language. It explains what happened (formula error), corrects it (attached updated report), apologises briefly and sincerely, describes the preventive action taken, and invites follow-up.

Model Apology Email: Internal - Missed a Deadline

Subject: Apology: Delayed Submission of Testing Report - [Project Name]

Hi [Manager’s Name],

I want to apologise for not submitting the testing report by yesterday’s deadline as committed.

The delay was due to unexpected complexity in the edge-case testing scenarios that required additional time to document accurately. I should have flagged this risk earlier rather than attempting to resolve it without raising it.

The report is now complete and I am attaching it to this email. I have also updated the project tracker with the current status.

To prevent this from recurring, I will flag potential timeline risks at least two days before the deadline in future.

I appreciate your understanding.

Thanks, [Name]

Type 7: Follow-Up Emails

Follow-up emails are professionally necessary but require care - you are reminding someone of a pending action without appearing demanding.

Model Follow-Up Email: After No Response to a Request

Subject: Follow-Up: Request for Database Access - Ticket HELP-4521

Hi [Name],

I am following up on the database access request submitted approximately one week ago, referenced under Ticket HELP-4521.

I have not yet received an update on the status of this request. The access is required for our integration testing phase, which is scheduled to begin next week.

Could you please provide a status update and an expected resolution date? I want to ensure we can meet our project timeline.

Thank you for your help.

Regards, [Name]

Analysis: This follow-up is neutral in tone. It references the original request specifically (ticket number), states the consequence of continued delay (project timeline), and makes a simple request (status update and expected resolution date). It does not use passive-aggressive language (“as I mentioned in my previous email”) or aggressive language. The goal is a response, not a confrontation.

Model Post-Interview Thank-You Email

Subject: Thank You - [Role] Interview - [Your Name]

Dear [Interviewer’s Name],

Thank you for the time you took to interview me for the [Role] position. I enjoyed our conversation about [specific topic from the interview - e.g., “the microservices architecture challenges on the platform”].

I remain very interested in the role and the team. Please let me know if you need any additional information from me.

I look forward to hearing from you regarding next steps.

Regards, [Name]

Advanced Grammar Rules for Professional Email Writing

These more nuanced grammar principles separate polished professional writing from merely adequate writing.

Dangling Modifiers

A dangling modifier is a phrase that modifies a noun not present in the sentence:

Dangling: “Having reviewed the report, several errors were identified.” - Who reviewed the report? The errors did not review it.

Correct: “Having reviewed the report, I identified several errors.”

Dangling modifiers appear frequently in business writing because writers use passive constructions to avoid naming responsibility, then add an active participial phrase that has nothing to attach to.

Parallel Structure in Email Lists

When bullets or numbered lists include actions, all items should be in the same grammatical form:

Non-parallel:

  • Review the attached document
  • Approval of the request
  • To schedule the follow-up meeting

Parallel (all imperative verbs):

  • Review the attached document
  • Approve the request
  • Schedule the follow-up meeting

Inconsistent parallel structure in lists reads as careless and makes the list harder to scan.

Nominalisations and How They Weaken Writing

Nominalisation converts a verb into an abstract noun, making writing unnecessarily complex:

Nominalised: “We have undertaken a review of the implementation of the system.” Clear: “We reviewed how the system was implemented.”

Nominalised: “The provision of adequate training is a requirement for successful deployment.” Clear: “Adequate training is required for successful deployment.”

Strong business writing uses active verbs. When you see sentences full of nouns ending in -tion, -ment, -ance, or -al, look for the verb buried inside and rewrite around it.

Sentence Length and Rhythm

Professional emails should mix sentence lengths:

Too choppy: “The server failed. It was at 3 AM. The team was alerted. They responded quickly. The issue was resolved by 4 AM.”

Well-balanced: “The server experienced a failure at 3 AM, detected immediately by our automated monitoring system. The on-call team was alerted and responded within 15 minutes. Root cause analysis identified a configuration issue, which was corrected by 4 AM.”

Writing for Different Stakeholder Types

Professional email writing requires audience awareness. The same information must be communicated differently to different recipients.

Technical vs Non-Technical Stakeholders

Technical colleague (same issue): “The load balancer health check interval was set to 30 seconds, causing the ALB to route traffic to the instance during the 25-second initialisation window. We have updated the instance warmup period to 60 seconds and adjusted the deregistration delay accordingly.”

Non-technical stakeholder (same issue): “Our team identified that new server instances were being connected to live traffic before they were fully ready, which caused brief errors for some users. We have updated the configuration so that servers are fully initialised before accepting traffic. The fix was deployed this morning and we are monitoring closely.”

Both emails describe the same technical resolution. Match your vocabulary and level of detail to what your audience needs to understand and act on.

Writing Upward vs Downward vs Lateral

Upward (to senior management): Lead with conclusion or recommendation. Be brief. Mention business impact. Avoid technical detail unless asked.

“The integration testing phase identified three high-priority defects that may impact the go-live date. We recommend a two-week extension to the testing window. Full details available upon request.”

Downward (to team members): More detailed, more directive, more context. Explain the why alongside the what.

“Please complete regression testing for modules 4-6 by Thursday EOD. Use the test case document in the shared drive (link below). Flag any failed test cases in the project tracker the same day they are found so the development team can begin fixes immediately.”

Lateral (to peers): Collaborative and direct. Does not need to be formal but must be specific.

“Hey, can you review the API documentation I shared yesterday? Looking specifically at whether the error codes section is clear enough for the client’s team to implement from.”

Email Templates for Common TCS Workplace Scenarios

Template: Requesting Project Resources

Subject: Resource Request: [Resource Type] - [Project Name]

Hi [Manager’s Name],

For the upcoming [project phase] of [Project Name], we require the following additional resources:

  • [Resource 1 with timeframe]
  • [Resource 2 with timeframe]

Without these resources, the [phase/milestone] is at risk of running beyond the planned timeline.

Please let me know if these can be arranged or if you would like to discuss alternatives.

Thanks, [Name]

Template: Reporting a Security Incident

Subject: URGENT: Potential Security Incident - [System/Account]

Hi [Security Team/Manager],

I am reporting a potential security incident requiring immediate attention.

What was observed: [Brief factual description] Time detected: [Time reference] Affected systems: [List] Immediate action taken: [What you have already done]

Please advise on next steps as a matter of urgency.

Regards, [Name] [Contact Number]

Template: Process Change Announcement

Subject: Process Update: [What is Changing] - Effective [Day Reference]

Hi Team,

Please note that the [process name] has been updated, effective from [day reference].

What has changed: [Specific change] Why: [Brief reason] New process: [Step-by-step or paragraph description]

The updated process document is attached. Please reach out with any questions.

Thanks, [Name]

Building Your Email Writing Habit

Email writing improves fastest through deliberate practice, not passive repetition.

Scenario sprint: Set a 10-minute timer. Pick one scenario from the practice list in this guide. Write the complete email within that time. Review it against the five criteria. Identify one specific improvement. Rewrite. This 20-minute cycle builds fluency faster than any other single practice.

Email autopsy: Save three examples of professional emails you receive and analyse them. What makes each email effective? What would you change? Where does the tone drift? What structural elements are present or missing? Learning from real emails - including their flaws - is more instructive than studying model examples alone.

Read before sending: After writing an email, read it from the recipient’s perspective. Would the purpose be clear within 10 seconds? Is the request specific? Is there any sentence that could be misread? Does the tone match the relationship and context? This 60-second review catches the majority of email writing errors before they are sent.

The professional who writes well stands out in every team they join. In a career that will involve thousands of emails, the investment in learning to write them well returns value every single day.

Do’s and Don’ts of Professional Email Writing: Complete Reference

The Do’s

Do use the recipient’s name. “Dear Priya” is warmer and more professional than “Dear Madam.” When you know the person’s name, use it. It signals that you have taken the basic care of addressing them directly rather than sending a templated communication.

Do state your purpose in the first sentence. Never make the recipient read through three paragraphs of context to understand why you are writing. The first sentence should answer “what is this email about?” unambiguously.

Do confirm receipt of important emails. When you receive an important document, approval, or assignment, a brief acknowledgment (“I have received the [document] and will review it by [timeframe]”) prevents the sender from wondering whether their email arrived.

Do use formatting to aid readability. Bold text for section headers within long emails, bullet lists for multiple items, numbered lists for sequential steps. These visual aids reduce the reading effort for your recipient.

Do proofread before sending. Read your email once for content (is everything included?), once for grammar (are there errors?), and once for tone (could anything be misread?). Three reads takes 90 seconds and prevents emails you will regret.

Do be specific about deadlines and timelines. “As soon as possible” means different things to different people. “By end of day Thursday” is unambiguous.

Do keep your promises. If you write “I will revert by tomorrow morning,” revert by tomorrow morning. Professional credibility is built on the reliability between what you write and what you do.

Do use a professional email address. In workplace contexts, use your company-assigned email address. In placement contexts, use a professional personal email - firstname.lastname@provider or a similar professional format. Addresses like “coolguy2000@” or “princessdreams@” undermine your professional presentation before the email is even opened.

Do archive or folder important email threads. Develop a simple folder structure for your inbox (by project, by client, by topic) so that important emails can be retrieved quickly. An overflowing, unorganised inbox causes missed follow-ups and wasted time.

Do consider your reply speed as a communication signal. A 24-hour response time for routine emails is professional. A 4-hour response to urgent or client emails signals reliability. Consistently slow responses signal disengagement or poor organisation, regardless of the email content.

The Don’ts

Don’t use all caps. ALL CAPS IN AN EMAIL READS AS SHOUTING. Even for urgent emphasis, avoid all caps in the body of professional emails. Use bold or an “URGENT” prefix in the subject line if urgency needs to be communicated.

Don’t send angry emails. If you are frustrated or upset about something, write the email, save it as a draft, wait at least 30 minutes, and re-read it. You will almost always revise it before sending. Emails sent in frustration create professional problems that take far longer to resolve than the original frustration.

Don’t use too many exclamation marks. One exclamation mark in an email is enthusiastic. Three in the same paragraph is exhausting. In formal external communication, avoid them entirely.

Don’t use unprofessional abbreviations. “BTW,” “FYI,” “ASAP,” “TBH,” and similar abbreviations are acceptable in internal informal communication and instant messaging. In formal emails to clients, external parties, or senior management, write out the words.

Don’t forward emails without context. Forwarding an email thread without an explanatory note (“Please see below for context on the issue we discussed”) forces the recipient to read the entire thread to understand why they are receiving it. A one-sentence context note is always appreciated.

Don’t CC people unnecessarily. CC overloading means people stop reading emails they are CC’d on, which means they miss the ones where their input actually matters. CC selectively and purposefully.

Don’t use “per my last email” or similar passive-aggressive phrases. These phrases signal frustration but damage professional relationships. If someone missed something in your previous email, assume good intent (they were busy, the email was unclear) and re-state the information directly.

Don’t mark everything as urgent. “Urgent” is a signal. When every email is marked urgent, the word loses its meaning and people start ignoring the flag. Reserve it for genuinely time-sensitive situations.

Don’t ignore emails. A brief “Thank you, I’ll revert by [date]” acknowledgment is better than silence. Silence creates uncertainty, follow-up emails from the sender, and reputational damage.

Don’t use “as per” when “as” is sufficient. “As per our conversation” is a bureaucratic construction. “As we discussed” or “as agreed” is cleaner and more professional.

Email Writing in the TCS NQT Verbal Ability Section: Detailed Analysis

The relationship between email writing proficiency and NQT Verbal Ability performance operates through three specific question mechanisms. Understanding these mechanisms helps you prepare for both simultaneously.

Para Jumble Questions Using Business Communication Passages

Para jumble questions in the NQT Verbal section frequently use passages drawn from corporate communications - meeting minutes, status update emails, policy announcements, and business correspondence. These passages follow predictable structural logic that candidates with email writing training can recognise faster than those without it.

The email paragraph structure they test:

Most business communication passages follow a consistent architecture:

  1. Purpose or context statement (what this is about)
  2. Background or current situation detail
  3. Specific information or action items
  4. Consequence, timeline, or call to action
  5. Closing acknowledgment or invitation for follow-up

Recognising this structure in a jumbled passage narrows down the possible orderings significantly before you even analyse individual sentence connections.

Example: A jumbled email about a software upgrade

(A) Users will need to clear their browser cache after the upgrade to ensure the new version loads correctly. (B) The planned maintenance window is between 11 PM and 2 AM on Saturday night. (C) We will be upgrading the customer portal to version 3.2 this weekend. (D) This upgrade includes performance improvements and security patches based on feedback from the previous quarter. (E) Please contact the helpdesk at helpdesk@company.com if you experience any issues after the maintenance window.

Correct order: C-D-B-A-E

Analysis: C is the purpose statement (what is happening). D provides the context for why (what the upgrade includes). B gives the specific timing. A gives a user action required. E provides a follow-up contact. This follows the email structure perfectly: announce, explain, specify, instruct, close with support option.

Sentence Error Identification in Formal Contexts

Error identification questions that use business writing contexts test the same grammar rules that appear in professional emails. The difference is that candidates who have studied professional email grammar arrive at these questions with a specific mental framework for detecting errors, rather than general grammar intuition.

The grammar rules most commonly tested through business writing contexts:

Subject-verb agreement with organisational nouns: “The management have decided to implement a new performance review system.” → Error in verb (should be “has decided” - management as a unit).

Tense consistency in formal reporting: “The team completed the migration and are now testing the new environment.” → Tense inconsistency (should be “is now testing” - present continuous matches the current state).

Correct preposition usage with professional verbs: “We need to adhere with the new security protocols.” → Incorrect preposition (should be “adhere to”). “The results are in compliance of industry standards.” → Incorrect preposition (should be “in compliance with”).

Parallelism in formal lists: “The project requires: completing the documentation, to conduct testing, and submitting the final report.” → Non-parallel (should be “completing the documentation, conducting testing, and submitting the final report”).

Vocabulary in Context from Professional Passages

When RC passages in the NQT use business or corporate writing contexts, vocabulary in context questions test the candidate’s familiarity with professional register vocabulary. Candidates who have studied and practised professional email writing have systematic exposure to this vocabulary range. Words like “escalate,” “mitigate,” “remediate,” “adhere,” “stakeholder,” “deliverable,” “turnaround,” “compliance,” “discrepancy,” and “reconciliation” appear naturally in both professional emails and NQT reading passages.

Strategy: When studying vocabulary for NQT preparation, include a category specifically for business and professional vocabulary. This investment serves both the test directly (vocabulary-in-context questions) and indirectly (faster passage comprehension when passages use professional language).

Email Etiquette Deep Dive: The Unwritten Rules

Beyond the formal rules of email structure and grammar, professional email culture has a set of unwritten norms that are learned through workplace experience - often through making mistakes. These rules are taught here so you do not have to learn them the hard way.

The 24-Hour Rule for Sensitive Emails

Before sending any email that involves criticism, dispute, escalation of a conflict, or emotional reaction, wait at least 24 hours after writing it. Read it again the next day. You will almost always soften it, make it more factual, or decide not to send it at all. The permanent nature of written communication means a poorly timed or poorly worded email can damage a professional relationship that would have resolved naturally through a brief conversation.

The Senior Management Copy Consideration

Before copying your senior manager on an email, consider: does this person need to be informed, or am I copying them to protect myself? Copying management as a form of implicit threat or self-protection is a well-understood corporate behaviour and it is poorly received by both the recipient of the email and the manager being copied. Copy management when they have a genuine need to know - not as a power move in a disagreement.

The Thread Context Rule

When forwarding or replying to a long email thread, provide a brief context summary for anyone joining the thread late. A new manager added to an ongoing thread should not need to read 30 emails to understand what is being discussed. “Adding [Name] to this thread for awareness - summary below:” followed by a 2-3 sentence summary is professional consideration.

Managing Expectations With Out-of-Office Responses

When you are unavailable for an extended period - leave, travel, training - set an out-of-office auto-reply that specifies: the dates of your absence, an alternative contact for urgent matters, and when you will respond to messages received during your absence. A professional out-of-office reply demonstrates planning and consideration:

“Thank you for your email. I am out of the office from [date range] and will respond upon my return on [date]. For urgent matters, please contact [colleague’s name] at [email]. Thank you for your patience.”

The Email Signature Update

Keep your email signature current. If you change roles, projects, or contact information, update your signature promptly. Receiving emails from someone whose signature lists them in a project they left six months ago creates confusion about who to contact and signals poor attention to detail.

Writing Formal Letters vs Writing Professional Emails: Key Differences

In placement assessments, some scenarios require a formal letter format rather than an email format. Knowing the differences prevents format errors that cost marks.

Format Differences

Formal letter (used for government communications, official complaints, legal correspondence):

[Your Name]
[Your Address]
[Date reference]

To,
The [Designation],
[Organisation Name],
[Address]

Subject: [Subject line]

Dear Sir/Madam, / Respected [Title],

[Body paragraphs]

Yours faithfully / Yours sincerely,
[Signature]
[Printed Name]
[Designation if applicable]

Professional email format:

Subject: [Subject line]

Dear [Name], / Hi [Name],

[Body paragraphs]

Regards,
[Name]
[Signature block with designation and contact]

Key differences:

  • Letters include the sender’s address and recipient’s address; emails do not
  • Letters use “Yours faithfully” (unknown recipient) or “Yours sincerely” (known recipient); emails use “Regards” or “Best regards”
  • Letters are formatted with indented or block paragraph style; emails use left-aligned paragraphs
  • Letters include the date explicitly; emails have a timestamp from the email system

When to Use Each in Assessments

If a scenario says “write an email to your manager,” use email format. If it says “write a formal letter to the Municipal Commissioner,” use letter format. If the scenario does not specify, use the format most appropriate to the recipient: government and official institutional recipients typically receive letters; corporate and business recipients receive emails.

Frequently Asked Questions: Professional Email Writing

How long should a professional email be? Most professional emails should be between 100 and 350 words. Brief internal messages can be 50-100 words. Detailed escalations or status reports may reach 400-500 words when complexity requires it. If an email approaches 600 words, consider whether an attached document would better serve the content, with the email as a brief introduction.

Should I use bullet points in formal emails to clients? Yes, when appropriate. Bullet points are not informal - they are structural tools that improve readability. Use them when listing three or more items, when presenting a structured request, or when outlining action items. Avoid them for continuous narrative that flows naturally as prose.

Is it appropriate to use “I” repeatedly in a professional email? Yes. “I am writing to inform you” is better than “This email is being written to inform you.” Active voice with first-person pronouns is clearer and more direct than passive constructions used to avoid “I.” The exception: official announcements often use “we” to represent the organisation.

What is the correct way to address someone whose name I do not know? “Dear Sir/Madam,” is the standard fallback. If you know the role but not the name, “Dear Hiring Manager” or “Dear Customer Service Team” are more specific alternatives. Make a reasonable effort to find the specific name before defaulting to generic salutations - a correctly named salutation demonstrates professionalism and effort.

When is it appropriate to use “Please do the needful”? This phrase is widely used in South Asian corporate English but is not standard in global professional communication. A clearer alternative: “Please proceed with the required action” or a specific request such as “Please approve the form and send it to HR.”

How should I professionally decline a request over email? Acknowledge the request, briefly explain the constraint, and where possible offer an alternative. “Thank you for thinking of me for this. Unfortunately, I am at capacity with the current sprint deliverables and would not be able to give this the attention it deserves. I would suggest reaching out to [colleague] who may have bandwidth for this.”

How do I handle a situation where I need to correct a misunderstanding in an email thread without embarrassing the other person? Address the misunderstanding factually and privately where possible. If the thread involves multiple people, a brief clarification (“To add some context here…”) is less confrontational than a direct correction (“That is incorrect because…”). Frame corrections as additions rather than refutations.

Can I use contractions in professional emails? In semi-formal internal communication, contractions (“I’ll,” “we’ve,” “it’s”) are acceptable and make the email feel more natural. In formal external communication (client emails, official correspondence), write out the words in full. When in doubt about the appropriate register, avoid contractions.

What should I do if I accidentally sent an email to the wrong person? Act quickly. If the email contained sensitive information, notify your manager and the information security team immediately. Send a follow-up to the unintended recipient acknowledging the error and requesting that they disregard and delete the email. The most important thing is transparency rather than hoping the mistake goes unnoticed.

Is it appropriate to use emoji in workplace emails? In formal external communication and senior management emails, never. In informal internal communication with colleagues you know well, occasionally appropriate if the team culture supports it. In placement assessments, never. When in doubt about whether emoji is appropriate in a specific professional relationship, err on the side of not using them.

Email Writing as an Interview Evaluation Signal

The TCS HR interview evaluates candidates across multiple communication dimensions simultaneously, and email writing ability - though rarely tested directly in the interview room - manifests in observable ways during the conversation.

How Interviewers Infer Written Communication Ability

When an HR interviewer asks “Tell me about a time you communicated a technical issue to a non-technical stakeholder,” they are partly assessing your spoken fluency and partly making inferences about your written communication ability. The underlying competency is the same: can you adapt a complex message to its audience, structure it so the key points land clearly, and choose language appropriate to the relationship?

Candidates who answer this question with a well-structured STAR response - situation, task, action, result - demonstrate the same organisational instinct that produces a well-structured email. Candidates who answer it with a rambling, chronological narrative demonstrate the same instinct that produces emails where the key information is buried in the fourth paragraph.

The implication: preparing for email writing and preparing for structured interview answers are not separate activities. Both require the skill of organising information purposefully, leading with the most important point, and calibrating language to audience. Developing one develops the other.

The Written Communication Test in Some TCS Interviews

For certain TCS profiles and roles, particularly those in client-facing or communication-intensive tracks, the technical or HR interviewer may ask you to write a brief email or response during the interview itself. This might be framed as: “Imagine a client has sent us an angry email about a service outage. How would you draft an initial response? Walk me through what you would write.”

This is not an invitation to write the full email on paper - it is a structured question about your communication thinking. A strong answer: “I would start with an acknowledgment of the issue and an apology for the impact. Then I would confirm what we know so far about the situation. I would give an honest timeline estimate for resolution, even if it is just ‘we will update you within two hours.’ I would close with a direct contact for their team to use if the situation worsens. I would avoid technical jargon in the opening because the client contact may not be technical.”

This answer demonstrates: structural awareness (acknowledgment, status, timeline, contact), audience awareness (avoid jargon), and professional judgment (honest timeline, even if uncertain).

The Connection Between Email Writing and TCS Workplace Success

Beyond the placement test, the value of strong email writing compounds through every stage of a TCS career.

Year 1: Establishing Your Professional Voice

In the first year at TCS, every email you send is an introduction to a new colleague, a new lead, or a new client. Freshers who send poorly formatted emails with grammar errors are quickly categorised as needing basic professional guidance. Freshers who send clear, correctly formatted, appropriately toned emails are categorised as ready for increasing responsibility. This categorisation happens rapidly and influences project allocation, trust level, and visibility within the account team.

The first year is when professional habits form. Building the habit of drafting, reviewing, and sending quality emails from Day 1 - rather than developing sloppy habits and trying to correct them later - is infinitely easier.

Year 2-3: Client Communication Access

In TCS’s service delivery model, direct client communication is a privilege that is earned. Team leads monitor the quality of written communication before granting freshers direct client access. Professionals who demonstrate professional email quality are trusted with client communication earlier, which in turn accelerates their visibility, learning, and growth.

The practical calculus: a junior developer who handles a client question about a technical issue through a clear, well-structured email that resolves the client’s concern demonstrates a competency that many senior developers do not have. This kind of visible performance creates career opportunities that technical skill alone cannot create.

Year 3-5: Documentation and Knowledge Management

In TCS project environments, written communication is organisational memory. Meeting decisions documented in emails, status updates filed systematically, issue reports that capture the full context of a problem - all of these form the institutional knowledge base that new team members rely on. Professionals who write well contribute to this knowledge base. Those who write poorly create gaps and ambiguities that cost the team time.

In this phase of a career, strong writing ability often translates into being the team member who documents the architecture decision, writes the handover document for a client transition, or drafts the project retrospective. These high-visibility deliverables are remembered and cited.

Complete Email Writing Quick-Test Practice

Before your TCS test or interview, verify you can complete each of the following in under 10 minutes. Write the full email, not just an outline.

Quick-test 1: Write a complaint email to a vendor who has delivered faulty equipment. Include: description of the defect, impact on your work, what you want them to do, and a deadline.

Quick-test 2: Write a leave request email to your manager for two days for personal reasons. Ensure handover is covered.

Quick-test 3: Write an email to your senior manager escalating a helpdesk issue that has been unresolved for one week and is blocking a project milestone.

Quick-test 4: Write a response to a client who has reported that a feature is not working as expected. Acknowledge, describe the investigation status, and commit to a timeline.

Quick-test 5: Write a status update email for a project you are working on, covering completed work, work in progress, blockers, and next steps.

Quick-test 6: Write a formal complaint to the police regarding a lost wallet containing your ID and bank cards. Include a description of the items, where and when it was lost, and your request.

Quick-test 7: Write an apology email to a client for a report that contained an error. Include what the error was, the correct information, and what you have done to prevent recurrence.

Quick-test 8: Write an announcement email to your team about a new process for document approvals that comes into effect next week.

After writing each email, review it against these five questions: Is the subject line specific? Does the first sentence state the purpose? Is the tone appropriate? Does the email address everything the scenario requires? Is it under 350 words?

If you can answer yes to all five questions for all eight emails within the time limit, you are prepared for both placement assessment email writing and the first day of professional communication at TCS.

Final Word: Why Email Writing Matters More Than Most Candidates Think

The placement process correctly treats email writing as a signal of professional readiness, not as a standalone skill. A candidate who cannot structure a professional email reveals something about how they will perform in client-facing roles, in documentation tasks, in escalation handling, and in all the daily written communication that makes a TCS professional effective.

The good news is that email writing is entirely learnable. Unlike aptitude, which requires sustained long-term development, or coding, which requires months of practice, email writing improves rapidly with focused study of format rules, grammar principles, and tone calibration. Two weeks of deliberate practice - studying model emails, writing practice scenarios, and reviewing against the five criteria - is enough to build a professional standard.

The better news is that this investment pays dividends for decades. Every email you send for the rest of your career will benefit from the clarity, structure, and professional instinct built during this preparation.

Start with the format. Master the grammar rules. Calibrate the tone. Practice the scenarios. Then walk into your TCS placement, your first day, and every client interaction that follows with the confidence of someone who communicates well in writing. That confidence, more often than most people realise, is what separates the professionals who advance from those who plateau.