Technical Communication in Engineering: A Place-Based Approach

Technical Communication in Engineering: A Place-Based Approach connects professional writing and design with the relationships and responsibilities of engineering in place. Richard Branscomb's 2026 adaptation builds on Suzan Last's work, with Jordan Dearsley contributing. Six main chapters and three included appendices connect rhetorical problem-solving, inclusive style, accessible design, teamwork, research, Indigenous partnerships, and engineering document genres.

Chapter-wise summaries and study tasks

1. Technical Communication: A Place-Based Approach

Technical communication takes place within relationships among people, institutions, technologies, and the lands affected by engineering decisions. The opening chapter makes place central rather than treating it as background to a supposedly universal technical problem. Two-Eyed Seeing introduces a way to consider Indigenous and Western knowledge together without assuming that one absorbs or replaces the other. The four-R framework of respect, relevance, reciprocity, and responsibility asks how a communication practice contributes to relationships rather than merely extracts information.

Rhetorical problem-solving connects audience, purpose, context, and constraints with a designed response. The seven-Cs conventions support clarity, but the three Ps—positionality, privilege, and power—ask whose definition of the problem is shaping the document. Writing and revision are iterative design processes. Case studies show how technically competent communication can remain unresponsive when it ignores affected people or prevents concerns from influencing action. The discussion of generative AI adds questions about evidence, accountability, learning, and social impacts. A fluent generated passage does not establish accuracy, local understanding, or permission to speak for a community.

Study task. Map a fictional engineering communication situation by place, affected people, purpose, and decision authority. Identify your assumed position, apply the four Rs, and explain what consultation must occur before drafting a solution.

2. Professional and Intercultural Style

Professional style is reader-centered and intercultural, joining precision with attention to how language positions people. Persuasive communication should provide an understandable case, relevant evidence, and a respectful path for disagreement. Inclusive language concerning disability, gender, and racialized communities requires attention to context and people's own preferences rather than a mechanical substitution list. Indigenous terminology also concerns relationships, nation-specific identities, and ways of knowing; a broad label can conceal distinctions that matter to the people involved.

The chapter connects word choice with voice and perspective. Active voice can clarify responsibility, while passive voice can be useful when the process or result is the focus; neither should be imposed as an absolute rule. Precision identifies actions, quantities, conditions, and limits so readers can evaluate a claim. Difficult situations and unwelcome news require an honest message with appropriate explanation and consideration of the relationship. Softening should not hide the decision, and directness should not become an excuse for disrespect. Effective revision asks how a particular reader may understand both the information and the stance taken toward them.

Study task. Revise a fictional notice about an unfavorable project decision for two audiences. Check inclusive terminology, responsibility, evidence, voice, and next steps; explain what local language preferences you would verify instead of assuming.

3. Communication Design

Communication design helps readers locate, interpret, and use technical information. Genre conventions set expectations, while up-front organization makes the main purpose and important information available early. Visual hierarchy signals relationships through headings, placement, spacing, and other consistent choices. These features should serve a reader's task rather than reproduce a template automatically. Lists need a clear function and parallel structure; numbering should indicate sequence or another meaningful ordering when one exists.

Visualizations require choices about which relationship to show, which data to include, and how to represent scale and uncertainty. Tables, charts, graphs, and illustrations solve different problems. Integrating a visual means introducing it, labeling it, documenting its source, and explaining what the reader should notice without overstating the evidence. Alternative text and longer image descriptions provide access to different kinds of visual information and should suit the figure's purpose. A beautiful document can remain inaccessible or misleading. Testing whether a reader can find an answer and interpret a key figure provides stronger evidence than the designer's confidence alone.

Study task. Redesign a fictional engineering brief with up-front organization, a usable heading hierarchy, and a justified chart or table. Add source information and accessible descriptions, then ask a reader to answer a specific decision question.

4. Teamwork and Communication

Collaborative writing is a coordinated thinking process, not only the division of page counts. Teams need agreement about the problem, audience, evidence, structure, responsibilities, and how separate contributions will become one coherent document. Planning shared research and revision reduces contradictions and gaps that appear when members work in isolation. Integration deserves time and ownership rather than becoming an unpaid final task assigned to whichever person notices problems.

Team models offer different lenses on development, goals, roles, interactions, processes, behavior, and conflict. They should help identify questions, not fix colleagues into personality labels. Conflict can arise from unclear expectations, unequal work, competing interpretations, or interpersonal difficulties and requires a response matched to its cause. Peer review adds an opportunity to test whether the writing works for its intended reader. Useful feedback identifies a specific passage or design choice, explains its effect, and prioritizes a substantive improvement. Receiving feedback also requires judgment: a team should understand the reader's difficulty before accepting or rejecting the proposed fix.

Study task. Create a collaborative writing plan with a shared outline, source record, review criteria, integration stage, and conflict process. Practise feedback that connects a specific problem to its effect on the intended reader.

5. Conducting Technical Research and Consultation

Technical research begins with a decision or question, an appropriate scope, and methods capable of producing relevant evidence. Concept mapping can reveal relationships and gaps before the project becomes too broad. Secondary-source evaluation considers authority, methods, relevance, reasoning, and limitations. Primary methods such as interviews, surveys, and observation introduce responsibilities concerning participants, consent, privacy, and applicable research review. AI-generated claims and references must not be treated as verified research simply because they sound plausible.

The chapter gives consultation and Indigenous partnerships substantive roles in engineering knowledge. Identifying stakeholders, partners, rights, protocols, and decision influence requires more than sending a generic survey. Sustaining a relationship includes reciprocity, responsibilities over time, and attention to how contributions will be used. The source's discussion of the Honourable Harvest and its four-R and three-P frameworks encourages reflective practice rather than a universal checklist for all Indigenous nations. Synthesis then connects evidence from multiple sources while distinguishing agreement, tension, and gaps. Quotation, paraphrase, summary, and IEEE documentation help make the writer's use of evidence traceable.

Research quality includes what a project leaves out and whose account can change its direction. A consultation exercise is not automatically meaningful if a decision has already been finalized. Record what is uncertain, what participants have authorized, and how results will be communicated back. Current legal duties and nation-specific protocols require separate authoritative guidance; the textbook provides an educational framework rather than permission to assume them.

Study task. Design a fictional research-and-consultation plan with a scoped question, evidence sources, participant protections, partnership responsibilities, and real decision influence. Draft a synthesis paragraph with traceable IEEE-style citations using sources you have actually read.

6. Communicating Technical Information: Common Genres

Engineering genres organize information for different actions and responsibilities. Emails, memos, and letters communicate within particular relationships and need suitable subject lines, context, requests, and records. Technical descriptions explain an object's or system's purpose, components, specifications, and operation at a level appropriate for the reader. Selecting scope matters: a detailed inventory can still fail to explain what the reader needs to understand.

The reports material distinguishes purpose and structure across report types. Lab reports connect a question, method, results, and interpretation. Incident and inspection reports require factual observations, clear timing, relevant conditions, and separation of evidence from inference; careful wording avoids assigning unsupported blame. Progress reports explain completed and remaining work, problems, and schedule implications. Longer design, feasibility, and recommendation reports compare alternatives using explicit criteria and justified evidence. Weighted comparisons can make judgments transparent, but their apparent precision depends on defensible criteria, scores, and weights.

The linked PDF includes numbered subsections 6.1, 6.2, and 6.5 with several report subtypes; the numbering does not establish that omitted subsections are present. Learn the available genres by connecting each with its intended decision rather than assuming every report needs the same headings. Across formats, show the basis for claims, preserve relevant uncertainty, and give readers enough information to act responsibly.

Study task. Outline a technical description, incident report, and recommendation report for a fictional system. State each audience and purpose, distinguish observations from interpretations, and explain how one shared fact would be presented differently in each genre.

Appendix A: Indigenous Peoples in Canada - A Brief History

The historical appendix introduces Indigenous peoples in Canada, pre-colonial contexts, colonial history and its continuing effects, and treaties. Its purpose within an engineering communication text is to challenge the assumption that dominant institutional histories are complete or neutral accounts of place. Readers should recognize the diversity of peoples and relationships rather than infer a single Indigenous experience. Historical learning can explain why ownership, jurisdiction, terminology, and trust require attention in a project. A short overview cannot replace nation-specific sources or relationships with the people whose territories and rights are involved. Treat the appendix as an entry point for more responsible inquiry, not a credential that authorizes a writer to represent communities.

Study task. Identify three questions about a fictional project's place that the appendix cannot answer alone. Propose appropriate nation-specific or authoritative sources and distinguish historical learning from current legal advice.

Appendix B: Towards Truth and Reconciliation

Truth and reconciliation requires engagement with the history and continuing consequences of residential schools, including the experiences and testimony of Survivors. The appendix asks readers to consider what responsible response means rather than treat reconciliation as a ceremonial phrase. In communication work, this raises questions about whose knowledge is heard, how institutions describe their past and present responsibilities, and whether a proposed partnership permits meaningful influence. The material can be distressing and should be approached with care and respect for personal boundaries. A technical document cannot accomplish reconciliation by adding terminology while leaving its underlying power relationships unchanged.

Study task. Examine a fictional institutional reconciliation statement for specific responsibilities, evidence, and follow-through. Identify what would need to change in a project's communication and partnership practices for the commitment to become assessable.

Appendix E: Sentence Structures

Sentence structure helps technical writers show relationships and responsibility. Identifying subjects, verbs, and clauses supports the distinction between independent and dependent statements and helps diagnose fragments or run-ons. Simple sentences can emphasize a central point, compound sentences can balance ideas, and complex sentences can express conditions, causes, concessions, or unequal emphasis. The best choice depends on the intended meaning rather than a preference for either long or short prose. During revision, check whether a grammatical relationship accurately represents the technical one. A misplaced qualification or unclear subject can change how a reader understands an obligation or finding.

Study task. Rewrite the same technical claim as a simple, compound, and complex construction; explain the changed emphasis and check that conditions and responsible actors remain clear.

How to study this book

1. Begin each project by identifying place, affected people, purpose, knowledge needs, decision authority, and your own assumptions.
2. Use the four-R and three-P frameworks reflectively; learn local protocols and preferences rather than generalizing from a broad category.
3. Keep sources, permissions, consultation outcomes, and unresolved questions traceable throughout research and drafting.
4. Test organization and visual accessibility with a defined reader task, then revise substance before polishing sentences.
5. Build a small portfolio of genres around a fictional project, explaining why audience and purpose require different choices.
6. Approach the historical appendices with care and continue learning through appropriate Indigenous and authoritative sources.

Questions for reflection

• Whose definition of the engineering problem controls the communication?
• Can participants genuinely influence the decision, or are they only being informed?
• What does a design choice make easy to see, and what does it hide?
• How are responsibilities, uncertainty, and evidence represented in the document?
• Does a statement about reconciliation correspond to a change in practice?

Source edition and coverage

The guide follows the linked 2026 PDF of Technical Communication in Engineering: A Place-Based Approach, adapted by Richard Branscomb with Jordan Dearsley contributing and Suzan Last credited as original author. It covers six main chapters and the three included appendices, labeled A, B, and E. Numbering gaps in the source are not filled with invented sections. Indigenous histories, rights, and protocols require context-specific learning; this educational guide does not replace current legal guidance or community relationships. These are original study explanations and learning tasks. Read the complete book at the official source.