1.2 General vs Technical Communication & The Seven Cs

General Communication vs Technical Communication

Every conversation you have is communication. But not every conversation is technical communication. The two differ in audience, purpose, content, structure and language.

Quick test

• A friend texting "You won't believe what happened today!" — general.
• A developer writing "After the v2.3 deployment, login error rate rose from 0.4% to 2.1%; suspect cause is the session-token TTL change." — technical.

The same person uses both forms in a single day — even in a single conversation. The skill is knowing which is appropriate when.

---

Nature and Features of Technical Communication

A well-written piece of technical communication has these identifying features:

---

The Seven Cs of Effective Communication

Originally developed by Scott M. Cutlip and Allen H. Center in Effective Public Relations (1952), the Seven Cs are a checklist every piece of communication should pass. Every IPU-style exam puts this directly into a 12-mark question.

Memory aid (acronym): Clear Concise Concrete Correct Coherent Complete Courteous

1. Clarity

The single most important C. If the receiver does not understand, every other C is wasted.

Bad: "Due to the prevailing circumstances and unforeseen externalities affecting our operational paradigm, the deliverable schedule may experience a deviation."

Good: "The release will be delayed by two weeks because the vendor missed their delivery."

Practices:

• Short sentences (15-20 words on average)
• Familiar words over fancy ones
• One idea per sentence
• Active voice ("We tested" not "Testing was performed by us")

2. Conciseness

Cut every word that does not earn its place. Conciseness ≠ rudeness — short is polite, padded is wasteful.

Bad: "In the event that the team is in a position to complete the task..."

Good: "If the team can finish the task..."

Common padding to cut:

• "due to the fact that" → because
• "in order to" → to
• "at this point in time" → now
• "in the near future" → soon
• "make use of" → use

3. Concreteness

Use specific facts, figures, names, and examples — not vague abstractions.

Bad: "Sales have improved significantly."

Good: "Sales grew 28% in Q2, from ₹4.2 cr to ₹5.4 cr."

The concrete version is more credible, more actionable, and more memorable.

4. Correctness

Three dimensions:

• Factual correctness — numbers, dates, names, references
• Grammatical correctness — subject-verb, tense, punctuation
• Tone correctness — formal-vs-casual appropriate to context

A single factual error in a report destroys trust in the rest of it.

5. Coherence

Sentences should follow logically; paragraphs should build on each other. The reader should never wonder "Why are we suddenly talking about this?"

Tools for coherence:

• Transition words — therefore, however, additionally, in contrast
• Topic sentences — each paragraph starts with its main idea
• Consistent structure — chronological, problem-solution, cause-effect
• Pronoun references — "it" / "this" must clearly refer back

6. Completeness

The reader should not have to guess or follow up to get the basics.

A complete meeting invite has:

• Who is invited
• What the meeting is about
• When it is
• Where (room or link)
• Why the meeting is needed
• How to prepare

A complete report has: objective, scope, methodology, findings, conclusions, recommendations.

7. Courtesy

Be polite even when delivering bad news. Courtesy includes:

• "Please" and "thank you" where appropriate
• Acknowledging the other person's effort
• Avoiding accusations or blame language
• Using the right title and salutation
• Responding promptly

Bad: "You did the calculation wrong. Fix it."

Better: "Could you please re-check the calculation on row 14? I'm getting a different total."

---

Some Sources Add Two More Cs (Total 9 Cs)

But the standard list is 7. If asked, give 7; mention 9 as an extension only if the question explicitly asks.

---

Applying the Seven Cs — Example

Bad email (fails several Cs)

Subject: Update Hi team, So as you all may or may not be aware, there has been some discussion regarding the project. We will probably need to do something about it sometime in the coming days or so. Please be prepared.

Fails: clarity (what update?), conciseness (padded), concreteness (no specifics), completeness (when, what action?).

Improved email (passes all 7)

Subject: Sprint Review Postponed to Wednesday 28 May, 3 PM Hi team, The sprint review originally scheduled for Monday 26 May has been moved to Wednesday 28 May at 3 PM in Conference Room B. The client requested an extra two days to review our demo build. Action items by Wednesday morning: 1. Final test pass on the staging environment 2. Slides ready for the demo (template attached) 3. Each lead to prepare a 2-minute team update Please reply with any conflicts by EOD today. Thank you. Regards, Priya

Clear (postponed sprint review), concise, concrete (date, time, room, actions), correct, coherent (each paragraph builds), complete (all 5W+H), courteous (please, thank you).

---

Study deep

1. The Seven Cs are interconnected. Improving clarity often improves conciseness. Adding concreteness often improves completeness. Treat them as a system, not a checklist.

1. Courtesy is the C that is hardest to fake. Polite words alone don't make a message courteous — tone, choice of channel, and acknowledgement of the receiver's situation all signal real respect.

1. Cultural calibration of courtesy. What feels polite in one culture can feel formal-and-distant in another. Indian business English tends toward formality; American business email toward directness. Calibrate to your audience.

1. The cost of poor communication is invisible but huge. A SHRM study estimated US companies lose $62 billion/year to poor communication. The Indian IT industry estimate is comparable as a share of revenue.

1. Modern adaptations. Slack and Teams culture have pushed communication toward conciseness — but at the cost of completeness. A useful Slack message still passes all 7 Cs.

Key Terms — Lesson 1.2

The terms below define the general-vs-technical distinction and the canonical Seven Cs — every Unit-I PYQ on these expects fluent use.

General Communication — Everyday communication used for personal, social, or non-technical professional purposes — chats with family, social-media posts, casual emails, small-talk. Audience is broad, tone is conversational, vocabulary is general, structure is loose, and the goal is usually relational rather than informational.

Technical Communication — Communication of specialised technical content — engineering, science, technology, business analysis — to a defined audience for a specific purpose. Audience is narrow and informed, tone is objective, vocabulary is precise and domain-specific, structure is organised, and the goal is to inform, instruct, or persuade with accuracy.

Subject-Specific Vocabulary — The specialised terms used inside a technical domain — HTTP, encapsulation, cohort, titration. Technical communication assumes the reader understands these (or defines them on first use); general communication avoids them.

Audience Awareness — A core requirement of technical communication: adapting content, vocabulary, depth, and tone to who is reading or listening. A user manual for developers reads differently from one for end users.

Objectivity — Presenting information factually and impersonally, without rhetorical flourish or emotional colouring. Achieved by neutral phrasing, data-driven claims, and avoidance of "I/we" in many genres. Contrast with general communication, which often values personality and warmth.

Conciseness — Saying what needs to be said with as few words as necessary. Conciseness is one of the Seven Cs and a hallmark of technical writing. Cuts include redundant phrases ("in order to" → "to"), filler ("basically", "actually"), and elaborate constructions where a short word would do.

Precision — Using the exact right word for the exact intended meaning. "Approximately 100 users" is precise; "many users" is vague. Precision is what separates a useful technical document from a frustrating one.

Standardised Format — Technical genres (reports, memos, manuals, papers) follow conventional structures — abstract, introduction, method, results, discussion, conclusion for a paper; YYYY-MM-DD for dates; ISO units for measurements. Standardisation lets readers find information quickly.

Action-Oriented Content — Technical communication usually prompts the reader to do something — follow steps, take a decision, sign off. Procedures use imperative verbs ("Click Next", "Run the migration"); reports culminate in recommendations.

Seven Cs of Effective Communication — The classical checklist for any message: Clarity, Conciseness, Concreteness, Correctness, Coherence, Completeness, Courtesy. Developed by Scott M. Cutlip and Allen H. Center in Effective Public Relations (1952). The most-quoted framework in technical communication and a guaranteed PYQ topic.

Clarity — The first C: the message is easy to understand on first reading. Achieved by short sentences, common words, one idea per sentence, active voice, and concrete subjects.

Conciseness (C) — The second C: no wasted words. Removes redundancy, filler, and verbose constructions while preserving meaning. Famous compressions: "due to the fact that" → "because"; "at this point in time" → "now".

Concreteness — The third C: specific, vivid, and tangible language instead of vague abstractions. "Sales rose 17%" is concrete; "sales improved a lot" is abstract. Concrete writing trusts the reader with specifics.

Correctness — The fourth C: factual accuracy + grammatical correctness + appropriate format. Wrong dates, broken links, typos, and bad data all destroy credibility. Proofreading is a non-negotiable step.

Coherence — The fifth C: logical flow. Each sentence connects to the previous; each paragraph builds on the one before; the document moves from problem to evidence to conclusion. Achieved through topic sentences, transitions, and consistent terminology.

Completeness — The sixth C: all necessary information is present. The 5W+H test — Who, What, When, Where, Why, How — catches missing pieces. An incomplete message forces the reader to come back with questions.

Courtesy — The seventh C: the message is respectful of the receiver's time, expertise, and feelings. Achieved by polite phrasing, acknowledgement of context, avoidance of blame, and prompt response. Particularly important in cross-cultural and remote-work contexts.

Credibility (8th C, optional) — Some sources extend the list: the sender is trustworthy and the source is reliable. Built over time through accurate communications, kept commitments, and admission of mistakes.

Capability (9th C, optional) — The receiver is capable of acting on the message — the message is pitched at the right level of detail. Too-detailed = boring; too-summarised = unactionable.

Active vs Passive Voice — Two grammatical voices with different effects. Active voice ("The team shipped the build") is direct, clear, and concise; preferred in most technical writing. Passive voice ("The build was shipped by the team") is wordier and obscures the actor, but is sometimes appropriate (when the actor is unknown or unimportant: "The bug was introduced in v3.1").

5W+H — The journalistic heuristic for completeness: Who, What, When, Where, Why, How. Useful when drafting any informational message — if any of these is missing, ask whether the reader will be left with that question.

Tone — The emotional / attitudinal colour of a communication — formal, friendly, urgent, neutral, apologetic. Tone is set by word choice, sentence structure, punctuation, and channel. The same content with different tone can land as helpful or condescending.

Register — The level of formality appropriate to the situation — academic register, business register, conversational register, intimate register. Skilled communicators shift register fluidly between channels.

Plain Language Movement — The advocacy for clear, accessible writing in government, legal, and corporate communication — short sentences, common words, active voice, no jargon. Promoted by plainlanguage.gov, UK Gov.UK style guide, and influential in modern technical writing.

Communication Audit — A periodic review of an organisation's internal and external communications for clarity, consistency, and effectiveness. Audits identify barriers, redundant channels, and gaps before they become problems.

---

Common exam question (very high frequency): "Explain the Seven Cs of communication with examples." — List all 7; one-line definition per C; one bad / one good example per C; close with "they form a checklist for effective communication".

Common exam question: "Differentiate general and technical communication." — Tabulate 8-10 differences (audience, purpose, content, style, vocabulary, structure, use of data, tone, examples).

Common exam question: "What are the features of technical communication?" — List 8-10 features (subject-specific, audience-aware, purposeful, accurate, objective, concise, structured, uses visuals, standardised, action-oriented).

Worked Example — Applying the Seven Cs

Task: Tighten this status email so it satisfies the Seven Cs.

"Respected Sir, I am writing to inform you that as per our discussion the other day regarding the thing we talked about, the work is more or less going on and will hopefully be done sometime soon. Kindly do the needful."

Diagnosis: it fails Clarity ("the thing"), Concreteness ("more or less", "soon"), Conciseness (padding), Completeness (no deliverable, no date), and courtesy-by-vagueness ("do the needful").

Revision:

"Dear Sir, The payroll-module testing we discussed on Monday is 70% complete. I will share the final test report by Friday, 3 July. Please tell me if you need the interim results sooner. Regards, ..."

Why it now passes: Clarity (names the module), Concreteness (70%, Friday 3 July), Conciseness (three sentences), Completeness (deliverable + date + offer), Correctness and Coherence (logical order), and Courtesy (specific, respectful). A single revision can touch all seven Cs — which is exactly how an exam answer should demonstrate them rather than merely listing them.

Self-check

Recall the general-vs-technical split and the Seven Cs — answer, then check.

1. Who developed the Seven Cs, and in which 1952 book? (Scott M. Cutlip and Allen H. Center; Effective Public Relations)
2. State the Seven Cs in order. (Clarity, Conciseness, Concreteness, Correctness, Coherence, Completeness, Courtesy)
3. Which C is called "the single most important C"? (Clarity)
4. Which heuristic tests completeness, and what does it stand for? (5W+H — Who, What, When, Where, Why, How)
5. Name the two optional extra Cs that extend the list to nine. (Credibility, Capability)
6. Is a WhatsApp family chat general or technical communication? (general)