ENC3213: Writing for Managers

Course Description

ENC3213 is the upper-division writing course for students who will write in a workplace rather than for a literature class. It teaches the documents professionals actually produce — reports, proposals, instructions, correspondence, summaries — and the analytical habit those documents require: identifying who will read this, what they need to do with it, and how to arrange it so they can.

The course is offered at approximately six Florida institutions, including the University of West Florida, Florida Atlantic University, Florida International University, Keiser University, Seminole State College and Everglades University.

⚠ The title varies substantially and signals a genuine difference in emphasis. The statewide inventory records it as Writing for Managers. The University of West Florida titles ENC 3213 Professional and Technical Writing. Other institutions use Business Writing, Professional Writing or Technical Communication. These are all recognisably the same course — workplace writing for an upper-division audience — but the framing shifts what gets emphasised, and Special Information sets out what to check.

UWF's description is the fullest available: students learn an overview of professional and technical writing principles, current communication issues, research practices and emerging technologies, focusing on communication skills essential for success in technical and professional communication, including audience analysis, collaboration and document design, and producing documents such as letters, manuals, reports and proposals used in a variety of workplace environments. The prerequisite is ENC 1101 and ENC 1102 — the full composition sequence.

The central adjustment students must make is that workplace writing is not academic writing, and the habits that earned good grades in composition actively hurt here. An academic essay builds toward a thesis, rewards developed paragraphs, and assumes a reader obliged to finish. A professional document opens with the conclusion, is structured to be skimmed rather than read, uses headings and lists because readers navigate rather than progress, and assumes a reader who will stop as soon as they have what they need. Students who write beautiful prose frequently do worse in this course than students who write plainly, because the standard is usability rather than elegance.

The second adjustment is that the reader is not a professor. Academic writing is addressed to someone who knows more than the writer and is evaluating the writer's understanding. Professional writing is usually addressed to someone who knows less about the specific matter, is busy, has a decision to make, and did not ask for a demonstration of thoroughness. Audience analysis is therefore the course's foundational skill, and it is the one most students have never been asked to perform.

Learning Outcomes

Required Outcomes

• Conduct audience analysis, identifying primary and secondary readers, their purposes, their technical level and the decisions they must make.
• Determine a document's purpose and select a genre and structure appropriate to it.
• Apply the conventions of professional style — concision, clarity, plain language, active voice where appropriate, and the elimination of unnecessary abstraction.
• Organise information for readers who navigate rather than read, using front-loaded structure, informative headings, and effective use of lists and white space.
• Apply document design principles — typography, alignment, grouping, contrast and consistency — and explain how visual arrangement carries meaning.
• Write professional correspondence: email, letters and memoranda appropriate to positive, negative and persuasive purposes.
• Write clear instructions and procedures that a reader can follow without the writer present, and test them on a real user.
• Write reports in standard workplace forms, including informational, analytical and recommendation reports.
• Write a proposal that establishes a need, specifies a solution, and addresses cost and feasibility.
• Write an executive summary that stands alone and states the conclusion first.
• Conduct workplace research, evaluate sources for credibility and currency, and integrate and document them appropriately.
• Present quantitative information in tables and graphics that are accurate, clear and not misleading.
• Write collaboratively, managing division of work, version control, consistency of voice, and review.
• Give and receive substantive peer review, and revise on the basis of it.
• Apply ethical standards in professional communication, including accuracy, appropriate representation of data, avoidance of misleading emphasis, and the writer's responsibility for consequences.
• Apply accessibility and inclusive communication practices to documents and digital content.
• Adapt writing for digital and emerging channels while maintaining professional standards.
• Edit and proofread to a professional standard of correctness.

Optional Outcomes

• Produce employment documents — résumé, cover letter and professional profile — and prepare for interviews.
• Write for international and cross-cultural audiences, including writing for translation.
• Produce user documentation or a technical manual for a real product.
• Deliver an oral presentation supported by professional visual materials.
• Complete a client-based or service-learning writing project.
• Apply usability testing methods to a document.
• Produce content for organisational websites and social channels.
• Write in a discipline-specific genre relevant to the student's major.

Major Topics

Required Topics

• The rhetorical situation at work. Purpose, audience, context and constraints; how workplace writing differs from academic writing in structure, tone and length; the reader as a busy decision-maker.
• Audience analysis. Primary, secondary and tertiary audiences; technical level and the problem of the mixed audience; what the reader will do with the document; reader-centred versus writer-centred organisation.
• Professional style. Concision and the elimination of filler; concrete over abstract; active and passive voice and when each is right; plain language principles; jargon — when it is precise shorthand and when it excludes; tone and register; positive and neutral phrasing.
• Organisation. Front-loading the conclusion and the direct approach; the indirect approach for negative or resistant audiences; chunking; informative headings; parallel structure; transitions in a document read out of order.
• Document design. The principles of proximity, alignment, repetition and contrast; typography for readability; white space; lists and tables; templates and organisational style guides; design as communication rather than decoration.
• Correspondence. Email conventions and the professional norms of subject lines, brevity and tone; memoranda; formal letters; good-news, bad-news and persuasive messages and the differing structures each calls for; the practical reality that email is a permanent, forwardable, discoverable record.
• Instructions and procedures. Task analysis; sequencing; imperative mood and step granularity; warnings, cautions and notes and their placement; visuals in instructions; usability testing on a real user, which reliably humbles the writer.
• Reports. Informational, analytical and recommendation reports; short and long report structure; front matter and back matter; the executive summary and why it must stand alone; progress and status reports; incident and trip reports.
• Proposals. Solicited and unsolicited; requests for proposals and responsive structure; establishing need; the solution and its feasibility; budget and schedule; qualifications; the persuasive logic of a proposal.
• Research for workplace documents. Primary and secondary sources; evaluating credibility, currency and bias; interviews and surveys for workplace purposes; documentation conventions and their variation by field; the professional consequences of unattributed use.
• Visual and quantitative communication. Selecting a chart type for a message; table design; honest representation of data — truncated axes, misleading scales, cherry-picked ranges; figure and table numbering and captioning; integrating visuals with text.
• Collaboration. Division of labour; establishing a shared style; version control and collaborative platforms; managing disagreement; the practical problem of a document written by four people that reads like it.
• Revision, editing and review. Levels of edit — substantive, copy, proof; peer review that is specific and useful; responding to review comments; the discipline of proofreading a document you wrote.
• Ethics. Accuracy and completeness; the difference between persuasion and misrepresentation; selective emphasis; liability and the legal weight of written statements; whistleblowing and professional obligation; the writer's responsibility when instructed to obscure.
• Accessibility and inclusion. Writing for screen readers; alternative text; heading structure; colour contrast and not relying on colour alone; plain language as an accessibility measure; inclusive and non-discriminatory language.
• Digital and emerging channels. Writing for the screen; collaboration and messaging platforms and their register; content management; the persistence and searchability of everything written at work.

Optional Topics

• Employment documents: résumés, cover letters, professional profiles and interviewing.
• Intercultural and international professional communication; writing for translation.
• Technical manuals and user documentation.
• Oral presentations and slide design.
• Grant and funding proposals.
• Usability testing and information architecture.
• Regulatory and compliance writing.
• Crisis and risk communication.

Resources & Tools

• Technical Communication by Mike Markel and Stuart Selber (Bedford/St. Martin's) — the most widely adopted text in this course.
• Technical Communication by John Lannon and Laura Gurak, and Technical Communication Today by Richard Johnson-Sheehan — common alternatives.
• Business Communication: Process and Product by Guffey and Loewy — the standard where the course is framed as business rather than technical writing, which the statewide title suggests some sections are.
• Handbook of Technical Writing by Alred, Brusaw and Oliu — an alphabetical reference rather than a textbook, and the one students actually keep after graduating.
• Free and open resources of real quality:
  • Open Technical Communication and Technical Writing Essentials — openly licensed textbooks used at institutions that have adopted open educational resources; genuinely good and free, which matters in a required upper-division course.
  • Purdue OWL — reliable on documentation styles and professional document conventions.
  • plainlanguage.gov — the U.S. federal plain language guidelines, free, practical and authoritative; the Plain Writing Act requires federal agencies to follow them, which makes this material directly professional.
  • Web Content Accessibility Guidelines (WCAG) and the Section 508 standards for the accessibility component.
  • Nielsen Norman Group articles on writing for the web and readers' scanning behaviour.
• Style manuals students will meet professionally: the Chicago Manual of Style, the Microsoft Writing Style Guide (free online and the de facto standard in technology), the AP Stylebook, and discipline-specific manuals such as the IEEE and APA guides. Knowing that organisations have house styles, and that you follow them rather than your preferences, is itself a professional lesson.
• Tools: Microsoft Word with styles and templates used properly — which most students have never done and which is a genuine employability skill; Google Workspace for collaboration; Adobe Acrobat for accessible PDFs; Canva or InDesign for design-heavy documents; Grammarly and similar editing aids, used critically; screenshot and simple graphics tools for instructions.
• Professional organisation: the Society for Technical Communication, which has student memberships and Florida chapters, and which is the professional home of the technical writing field.

Career Pathways

This is one of the few courses whose skill transfers to essentially every professional career, and it also leads to a specific and under-known occupation.

• Technical Writers (SOC 27-3042) — the most reliably employable writing occupation, and one most students do not know exists. Documentation, user guides, API references, procedures and compliance materials; software, medical device, aerospace and engineering firms all employ them.
• Writers and Authors (SOC 27-3043) and Editors (SOC 27-3041).
• Public Relations Specialists (SOC 27-3031) and communications staff.
• Management Analysts (SOC 13-1111) — consulting deliverables are documents, and the ability to write a clear recommendation is the product.
• Grant writers and development staff (SOC 13-1131) — the proposal content applies directly, and Florida's large non-profit sector employs them.
• Project managers and business analysts — requirements documents, status reporting and stakeholder communication.
• Engineers, scientists and healthcare professionals — for whom this course is preparation for a substantial and frequently unwelcome share of their actual working time. Engineers report spending a large fraction of their week writing, and the ones who do it well advance faster.
• Compliance, regulatory affairs and quality roles — where documentation is the regulated deliverable.
• Instructional designers and content strategists; UX writers, a growing specialisation.
• Government and public administration — where plain language is a legal requirement at federal level and a practical necessity at state level.

The employer-facing point is well documented and worth taking seriously. Employer surveys consistently rank written communication among the most desired graduate attributes and among the most frequently reported as deficient. That gap is the reason this course exists as an upper-division requirement in so many Florida programmes, and it is a genuine competitive advantage rather than a box to tick.

In Florida, the technical writing market concentrates in the Orlando simulation and technology sector, the Space Coast aerospace industry, Tampa Bay and South Florida technology and financial services, the defence contractors statewide, and the healthcare systems — which generate enormous volumes of procedural, regulatory and patient-facing documentation. State government in Tallahassee employs writers and communications staff across every agency.

Special Information

⚠ Title variation — check what your section actually emphasises

The statewide inventory title is Writing for Managers; the University of West Florida titles ENC 3213 Professional and Technical Writing. Others use Business Writing or Technical Communication.

These are the same course in the sense that matters — upper-division workplace writing, taught to non-majors, producing reports, proposals, correspondence and instructions — but the emphasis genuinely differs:

• A business or managerial framing weights internal correspondence, persuasive messages, meeting documentation and management reporting; the audience is colleagues and superiors.
• A technical framing weights instructions, procedures, specifications, documentation and the communication of technical content to non-technical readers; the audience frequently includes users and regulators.

The overlap is large and the transferable skill — audience analysis, front-loaded structure, document design, revision — is identical. But a student in engineering or the sciences is better served by a technically framed section, and a student in management or human resources by a business-framed one. Read the syllabus rather than the title, and if your programme lets you choose a section, choose deliberately.

Related numbers to distinguish: ENC 3241 (Writing for the Technical Professions / Technical Writing) and ENC 3250 (Professional Writing) appear at various Florida institutions and cover adjacent ground. They are different numbers and do not automatically substitute for each other, which matters when a programme requires one specifically. Check which number your degree audit names.

Prerequisites

UWF requires ENC 1101 and ENC 1102 — the full first-year composition sequence. That is the standard gate and it is appropriate: this course builds on general writing competence rather than teaching it, and it moves quickly into genre and audience work.

Some institutions also require junior standing, which is sensible — the course is considerably more useful to a student who has some sense of the field they are entering, because audience analysis is easier when you can picture the audience.

Position in the curriculum and who takes it

ENC3213 is an upper-division course normally taken in the junior or senior year. It is required in a wide range of non-English majors — engineering, computing, business, health sciences, criminal justice and public administration programmes across Florida commonly require an upper-division professional writing course — which means the classroom is disciplinarily mixed.

That mix is an asset and instructors generally exploit it. Having an engineering student, a nursing student and a management student each analyse the same document for their own audience makes the audience-analysis material concrete in a way a single-discipline classroom cannot.

Note that many Florida institutions attach a Gordon Rule writing designation or an upper-division writing requirement to this course. Where a Gordon Rule designation applies, a minimum grade of C is normally required to satisfy the writing requirement — meaning a D passes the course without satisfying it, the credit posts, and the gap surfaces at a graduation check. Verify at your institution.

Articulation and transfer

ENC3213 carries the same SCNS number across Florida public institutions and SCNS equivalency governs transfer of the credit. As an upper-division course it does not appear in A.A. programmes and is taken after transfer — though Seminole State College and Everglades University appear in the inventory, indicating availability within bachelor's programmes outside the university system.

Two things to verify: whether your programme requires ENC 3213 specifically or accepts ENC 3241 or ENC 3250, since the numbers are not interchangeable in a degree audit; and whether the course carries a writing designation at the receiving institution, since that determines the minimum grade.

Course format and workload

Three credit hours, approximately 45 contact hours; online sections are very common and work well for this material, since the deliverables are documents. Assessment is portfolio- and deliverable-based rather than examination-based: a sequence of documents, usually with drafting, peer review and revision built in, frequently culminating in a substantial report or proposal and sometimes a team project.

Expect five to seven hours a week outside class, concentrated around deliverable deadlines. Three pieces of practical advice:

• Take the revision cycle seriously. The course is designed around draft-review-revise, and students who submit first drafts as final work lose marks they could easily have kept. Professional writing is rewriting.
• Test your instructions on an actual person. Nothing else reveals as quickly that a step you thought was obvious is not.
• Keep the portfolio. A report, a proposal and a set of instructions that you can show are genuinely useful in a job search, and considerably more persuasive than claiming strong communication skills on a résumé.

⚠ What students most often get wrong

The characteristic errors are consistent, and naming them early helps:

• Burying the conclusion. Academic writing builds to a point; professional writing states it and then supports it. The reader may stop after the first paragraph, and that is a feature of the genre rather than a failure of the reader.
• Writing for the professor rather than the stated audience. If a document is addressed to a plant supervisor, it should be written for a plant supervisor — including omitting things the professor would find impressive.
• Confusing length with thoroughness. A shorter document that answers the question is better, and is graded better. Cutting is the hardest editing skill and the most valuable.
• Treating design as decoration. Headings, lists and spacing are structural. A wall of text is a usability failure regardless of the quality of the sentences in it.
• Passive voice as a default. Not because passive voice is wrong — it is often exactly right in technical and procedural writing — but because used indiscriminately it obscures agency, which is sometimes the point and sometimes an ethics problem.

AI Integration

No course in this repository is more directly affected by generative text than this one, and the honest treatment is neither prohibition nor enthusiasm.

The plain fact is that these tools produce competent professional prose. A model asked for a status report, a routine email, a set of instructions or a report outline will produce something serviceable — and workplaces are already using them for exactly that. Pretending otherwise in a professional writing course would be a disservice, because students will use them at work within a year.

What the course teaches is what remains scarce. The tools generate text; they do not decide what to say. The judgements this course develops are the ones that survive:

• Audience analysis. A model does not know that your primary reader is a sceptical director who was overruled last quarter, that the secondary audience includes legal, or that the real decision was made informally last week. The rhetorical situation is information you have and the model does not.
• Deciding what matters. Determining which of twelve findings belongs in the executive summary is the analytical act; generating prose around that decision is the easy part.
• Accuracy and accountability. Your name is on the document. Models fabricate figures, citations, product specifications and regulatory requirements with complete fluency, and a fabricated number in a professional document is your error regardless of how it got there.
• Voice and organisational fit. Generated prose converges on a neutral corporate register that reads as effort not taken — and in messages where the relationship is the point, that undercuts the message even when the content is fine.

Where these tools are genuinely useful, and the course should say so: generating a first draft to react against, which is often easier than starting blank; producing alternative phrasings; summarising a long source document you have read; checking a draft against a plain-language standard; and generating a hostile reader's objections so you can address them. Editing tools that flag passive constructions, long sentences and reading level are legitimate and have been for years.

Two cautions with professional weight. Confidential information must not be entered into consumer AI tools — client data, personnel matters, unreleased financials, proprietary technical detail. Organisations increasingly specify approved platforms, and violating that is a disciplinary matter. And disclosure norms are unsettled: some organisations require it, some are indifferent, and the safest professional position is to know your employer's policy and to never let a document go out under your name that you have not verified line by line.

A final observation worth making to students in this course specifically. If competent prose is now cheap, the differentiator is no longer fluent writing — it is knowing what to write, for whom, and being right about the content. That is precisely what this course grades, and it is a reason to engage with the audience analysis and revision work rather than to route around it. The students who will be valuable are the ones who can look at a generated draft and say what is wrong with it. Follow your instructor's syllabus, which governs and which in this course is likely to be thoughtfully specific.