Umiejętności pisania zawodowego

Język angielski w zastosowaniu zawodowym

Autor

Afiliacja

Ben Stanley

Wydział Nauk Społecznych, Uniwersytet SWPS

Opublikowano

25 kwietnia 2026

Foundations: three documents, three purposes

Before you sit down to write, ask yourself three questions:

Purpose — inform, persuade, or present findings?
Audience — internal colleague who knows the context, external client who does not, or a time-pressed decision-maker?
Register — how formal, how hedged, how much conviction?

Only once you know the answers do you choose the structure and expressions.

Document	Purpose	Audience	Register	Voice
Email	Communicate, request, follow up	Internal or external; single or few	Neutral to formal	Active; contractions acceptable only in low-stakes internal emails
Memo	Inform, request, confirm	Internal colleagues	Professional, direct	Active; occasional passive for policy
Proposal	Persuade — secure agreement, funding, contract	External client / decision-maker	Confident, client-focused	Active; minimal hedging
Report	Present findings objectively; support decisions	Internal or external; decision-makers	Formal, objective, data-driven	Passive for findings; active for recommendations; calibrated hedging

Read this table every time you are about to write a business document in English. Purpose determines everything else — structure, vocabulary, modals, hedging, sign-off. A well-structured memo written in proposal register reads as over-selling; a well-structured proposal written in report register reads as uncommitted.

Vocabulary: professional writing

These twenty terms will appear in both the in-class exercises and in the homework (gap-fill). Master their meaning and their typical context of use — not all of them are interchangeable.

Term	Definition	Typical context
Executive summary	A brief overview capturing the key points of a longer document	Proposals, reports — always first section
Call to action	A statement directing the reader to take a specific next step	Memos, proposals — always final paragraph
Deliverables	Tangible outcomes or products provided at project milestones	Proposals — quantified, listed
Return on investment	A measure of profitability relative to the cost of an investment	Proposals, business cases
Hedging	Language acknowledging uncertainty (“the data suggests”)	Reports — essential; proposals — avoid
Stakeholders	Individuals or groups affected by an organisation’s actions	Reports, strategic documents
Feasibility study	An assessment of whether a plan is viable and practical	Pre-project reports
Compliance	Adherence to rules, policies, and regulations	Memos (internal), reports (audit)
Recommendation	A suggested course of action based on analysis	Reports — each one specific and owned
Methodology	The research approach and data collection techniques used	Reports — stated in introduction
Scope	The defined boundaries and extent of a project	Proposals (set), reports (declared)
Evidence-based	Grounded in data and research rather than intuition	Recommendations, strategic memos
Draft	A preliminary version of a document before finalisation	Any document — expected to be revised
Proofread	To review a document carefully for errors and inconsistencies	Final stage before sending
Concise	Direct and to the point, without unnecessary words	Memos especially; applies to all
Objective	Presenting facts without personal bias	Reports — default register
Formal tone	A professional style avoiding colloquialisms and contractions	Reports, external proposals, senior emails
Appendix	Supporting material placed at the end of a report	Reports — charts, raw data, questionnaires
Executive committee	Senior leadership group responsible for major decisions	Memos (“the Executive Committee has mandated…”)
Actionable	Specific enough to be implemented immediately	Recommendations, calls to action

Collocations worth memorising:

draft and finalise a document
proofread for errors; edit for style
compile, present, and circulate a report
submit, endorse, and approve a proposal
cascade information (pass it down the hierarchy in a memo)
flag an issue; escalate a concern
set, agree and deliver against a timeline

Business emails

Email is not the main focus of the seminar, but it is the genre you will write most often — so we start with it.

Structure template

Subject: [Specific, informative, ≤ 8 words]

Dear [Name],       ← formal / external / first contact
Hi [Name],         ← neutral / internal / ongoing
[Name],            ← informal / established thread

[Opening line: reason for writing, in one sentence]

[Body: 1–3 short paragraphs. One topic per paragraph.
One clear request or piece of information per email.]

[Closing line: call to action + deadline if any]

Best regards,       ← formal / external
Kind regards,       ← neutral default (safe everywhere)
Best,               ← informal / internal
[Your name]
[Title, company] (if external)

Fixed expressions

Openings — reason for writing:

I am writing to enquire about…
I am writing to confirm…
I am writing with reference to your email of 14 April…
Further to our conversation this morning, …
Thank you for your email of 12 April. In response, …

Requesting information or action:

Could you please confirm whether…?
I would be grateful if you could send me…
Would it be possible to arrange…?
Please could you let me know by Friday whether…
I would appreciate your feedback on the attached draft.

Providing information:

Please find attached…
As requested, I am sending you…
For your reference, the figures are as follows: …

Apologising:

I apologise for the late reply.
I am sorry for any inconvenience this may have caused.
Please accept our apologies for the delay.

Closings — call to action:

I look forward to your reply.
Please let me know if you need any further information.
I would appreciate a response by end of play Friday.

Length and register norms

Dimension	Internal email	External email
Length	30–150 words	80–200 words
Greeting	Hi [first name]	Dear [Mr/Ms Surname] or Dear [First name] if prior contact
Contractions	I’ll, we’re acceptable	Avoid
Sign-off	Best, Kind regards	Kind regards, Best regards, Yours sincerely if very formal
Reply latency	Same working day	≤ 24 working hours

Warning for Polish speakers: “I am writing in connection with…” is safe but slightly heavy. “Regarding…” is more neutral in modern business English. Avoid “With regard to…” (slightly formal), and never write “With regards to…” — this is a common error that mixes two different phrases.

Business memos

Purpose and style

Purpose: inform, request, confirm, or (occasionally) persuade.
Audience: internal colleagues who already know the context.
Register: professional but direct. Concise over flowery. No greeting, no sign-off.
Voice: active for commitments (“We will implement…”); occasional passive for policy (“Expense reports must be submitted by Friday.”).

Document skeleton

MEMORANDUM

To:      [Recipient(s) --- role or name]
From:    [Your name, title]
Date:    [DD Month YYYY --- spell out the month]
Subject: [Specific, informative, actionable --- not "Policy update"]

[Opening paragraph: context in 1 sentence + purpose in 1 sentence.]

[Heading 1]
- Bullet point
- Bullet point
- Bullet point

[Heading 2]
- Bullet point
- Bullet point
- Bullet point

[Closing paragraph: call to action with deadline + contact(s) for questions.]

Required sections (in order)

Header — To / From / Date / Subject. Subject must be specific and time-anchored where relevant.
Opening (1–2 sentences) — context (what happened or what is at stake) + purpose (what this memo does).
Body — organised with headings and/or bullet points. One heading per theme. Parallel structure across sections.
Closing — call to action (specific, actionable, with a deadline) + contact details for questions.

Fixed expressions

Subject lines — good:

Mandatory cybersecurity training, 1–31 May 2026
New expense claim procedures, effective Q3 2026
Office closure, 2–4 June (renovation works)

Subject lines — avoid:

Policy update (not specific)
Important (not informative)
FYI (says nothing)

Openings:

Following the security incident reported on 3 April, the Executive Committee has mandated…
This memo sets out the new procedures for expense claims, which take effect from 1 July 2026.
As you are aware, our client-retention figures have declined over the past two quarters. This memo outlines the remedial steps agreed at last week’s Board meeting.

Introducing sections:

What is required
Your responsibilities
Key changes
Next steps
Timeline

Closings:

For questions about [topic], please contact [name] at [email].
Please cascade this information to your teams by [date].
Kindly confirm receipt by [date].

Length and register norms

Dimension	Norm
Length	150–250 words of body text. One page maximum.
Register	Formal but direct. No contractions. No greeting, no sign-off.
Modals	Must for obligations; should for advice; please for polite requests.
Voice	Active by default; passive for institutional policy.

Self-check checklist

Criterion	What to look for
Header	Complete; subject line is specific and informative
Opening	Purpose clear in the first two sentences
Body	Logical organisation; headings or bullets; language concise
Call to action	Specific, actionable, with a deadline or next step

Annotated memo exemplar

The memo below illustrates the structure and register of a well-written business memo. It also demonstrates how to deploy modal verbs (Lesson 3), sentence adverbials (Lesson 2), and ethics vocabulary (Lesson 3) in an authentic workplace document. The annotations explain why each element works.

Adnotacja

MEMORANDUM

To: All Department Heads From: Anna Nowak, Chief Compliance Officer Date: 15 April 2026 Subject: New whistleblower procedures and revised code of ethics, effective 1 May 2026

Annotation: header

Clear document-type label at the top (MEMORANDUM) so the reader knows immediately what they are looking at.
The subject line is specific and dated. “Policy update” would be a fail; the reader must be able to decide in three seconds whether to act now or later.

Following the board’s review of the Q1 risk assessment, the Executive Committee has adopted a revised code of ethics and updated whistleblower procedures. This memo sets out the key changes, your responsibilities as department heads, and the timeline for implementation.

Annotation: opening

Two sentences: context (what happened) plus purpose (what this memo does).
“has adopted” — present perfect (L1). A recent action with ongoing consequence: exactly what the present perfect is for.

What is changing

Consequently, from 1 May 2026:

All staff must complete mandatory compliance training (online, approximately 60 minutes)

All staff must disclose any potential conflict of interest using the new digital form

A confidential whistleblower platform will be available for reporting suspected breaches

Due diligence requirements for external partnerships have been tightened

Annotation: “What is changing”

“Consequently” — sentence adverbial (L2, connective). Signals that what follows derives from the opening.
Modal verbs (L3): must for obligation; will for certainty.
“have been tightened” — passive voice (L4). Used where the actor (the Committee) is less important than the change itself.

Your responsibilities

Cascade this memo to all team members by 20 April 2026

Ensure at least 90% training completion within your department by 15 May

Return the signed acknowledgement form to HR by 22 April

Importantly, flag any capacity or resource concerns to me directly before 25 April

Annotation: “Your responsibilities”

Numbers wherever possible. Deadlines specific.
“Importantly” — sentence adverbial (L2, focus adverbial). Marks the one item that requires more than mechanical action.

Why this matters

These changes reflect our commitment to integrity, transparency, and accountability — values that our stakeholders, clients, and regulators increasingly expect us to demonstrate. Furthermore, robust compliance infrastructure is itself a competitive advantage: our most recent client due diligence review identified it as a positive differentiator.

Annotation: “Why this matters”

A short “why” section is optional but valuable in change-management memos — it pre-empts the “why now? why this?” question.
Recycles ethics vocabulary (L3): integrity, transparency, accountability, stakeholders.
Recycles strategy vocabulary (L2): competitive advantage, due diligence.
“Furthermore” — sentence adverbial (L2, additive). Adds a second reason without sounding like a list.

For questions about the training platform, please contact IT (ithelp@company.pl). For questions about the code of ethics or whistleblower procedures, please contact the Compliance Office (compliance@company.pl).

Annotation: closing

No flowery sign-off. Specific contacts for specific questions. Respects the reader’s time.

Why this works:

Subject line is specific and dated. The reader knows what the memo is about and when they need to act.
Opening uses present perfect (Lesson 1) to signal a recent action with continuing relevance.
Modal verbs are mixed deliberately (Lesson 3): must for obligation, will for certainty, may implicitly absent because this is directive, not advisory.
Sentence adverbials (Lesson 2) mark the logical structure: Consequently, Importantly, Furthermore.
Passive voice (Lesson 4) is used once, in “have been tightened”, where the agent is understood.
Ethics vocabulary (Lesson 3) used naturally in context: whistleblower, code of ethics, conflict of interest, compliance, integrity, transparency, accountability, due diligence.
Length: ~230 words of body text. That is usually enough.

Business proposals

Purpose and style

Purpose: persuade — secure agreement, funding, or a contract.
Audience: external (usually) — a busy decision-maker who may not read past page 1.
Register: professional, confident, client-focused.
Voice: predominantly active; avoid hedging; quantify wherever possible.

Document skeleton

[TITLE PAGE]
  Project title
  Prepared for: [Client company]
  Prepared by:  [Your company]
  Date: [DD Month YYYY]

EXECUTIVE SUMMARY
  [3–5 sentences: client situation → engagement → quantified benefit.]

PROBLEM STATEMENT
  [Client's pain points, in their language, quantified.
   Final sentence: what is at stake in financial terms.]

PROPOSED SOLUTION
  [Concrete phases. The reader should be able to visualise
   what happens each week / month.]

  - Phase 1 (Weeks 1–2): [activity → deliverable]
  - Phase 2 (Weeks 3–4): [activity → deliverable]
  - Phase 3 (Weeks 5–6): [activity → deliverable]

KEY BENEFITS AND DELIVERABLES
  Deliverables (what the client physically receives):
  - [Report / workshop / roadmap / shortlist]

  Projected outcomes (what the client can expect to achieve):
  - [Quantified ranges, not single numbers]

TIMELINE AND INVESTMENT
  Engagement: [duration], beginning [start window]
  Total fee:  [£ figure], invoiced in [N] tranches
  Projected ROI: [multiple or % figure]

NEXT STEPS
  [Specific meeting duration + specific week + specific contact person]

Required sections (in order)

Title page — project title, company names, date.
Executive summary — the “elevator pitch”: situation → engagement → quantified benefit.
Problem statement — client’s pain points, quantified, in their language, ending with what is at stake.
Proposed solution — concrete phases or components; what you will actually do.
Key benefits and deliverables — two lists: (i) what the client receives; (ii) what they can project to achieve.
Timeline and investment — schedule, cost, payment structure, ROI.
Next steps (call to action) — specific meeting, specific week, specific contact.

Types of proposals

Solicited — responding to a direct request (RFP, RFQ).
Unsolicited — proactively presenting solutions.
Renewal — extending or modifying existing agreements.

Fixed expressions

Executive summary openers:

[Client]’s rapid growth — from X to Y in Z years — has outpaced its current [process].
[Client] is facing [situation]. This proposal sets out a [N]-week engagement to [goal].
Our six-week operational efficiency review will identify bottlenecks in three priority areas…

Problem statement — linking problem to stakes:

These figures suggest that [current process] is now a constraint on further growth — and on the renewal of contracts worth an estimated £X annually.
If unaddressed, [problem] is likely to compromise [strategic goal] within [timeframe].

Solution — signalling structure:

Our [duration] engagement will deliver:
The engagement comprises three phases:
In Weeks 1–2, we will [activity]. In Weeks 3–4, we will [activity]. In Weeks 5–6, we will [activity].

Benefits — with credible hedging:

Based on comparable engagements, we project…
Typical outcomes include X–Y% [improvement].
Clients in similar situations have achieved…

Next steps — specific call to action:

We would welcome a 30-minute call in the week of [date] to discuss the proposal and answer any questions.
Please contact [Name] at [email] or [phone] to arrange a meeting.

Expressions to avoid in proposals:

We hope that… (undermines conviction)
It is possible that… (hedging in the wrong place)
Significant savings (not quantified)
Improved efficiency (not quantified)
A leading provider of innovative solutions (generic consulting language)

Length and register norms

Dimension	Norm
Length	Short proposal: 500–800 words. Full proposal: 1,500–3,000.
Register	Formal, confident, client-focused. No contractions.
Modals	Will for commitments (“We will deliver…”); avoid should and might in deliverables.
Voice	Active throughout. Passive reads as evasive.
Numbers	Every benefit quantified. Ranges are acceptable; vague adjectives are not.

Self-check checklist

Criterion	What to look for
Value proposition	Client benefit clear within 30 seconds
Pain points	Concrete, quantified, in client’s language
Solution	Specific to this client, not generic
Deliverables and benefits	Outcomes quantified (%, £, time)
Tone and conviction	Confident; minimal hedging; active voice

Annotated proposal exemplar

The proposal below illustrates a well-structured short proposal for a market-entry engagement. Note how it deploys globalisation vocabulary (Lesson 1), strategy vocabulary (Lesson 2), finance vocabulary (Lesson 4), first conditionals (Lesson 1), and sentence adverbials (Lesson 2). The annotations explain the persuasive techniques at each stage.

Nordic-Baltic Market Entry Study for PolMeble S.A.

Prepared by: Meridian Strategy Partners

Date: 12 April 2026

Executive summary

PolMeble’s sustained growth in Poland — market share rising from 4.1% to 9.3% over five years — has created both the opportunity and the imperative to expand beyond the domestic market. Our ten-week Nordic-Baltic market-entry study will identify the highest-potential country for initial expansion (Lithuania, Estonia, or Sweden), assess tariff and non-tariff barriers, and deliver a prioritised entry roadmap. Based on comparable engagements, we project that a well-executed entry could secure a 2–4% target-market share within 24 months, generating an estimated €12–18 million in new revenue.

Annotation: executive summary

Four sentences. Sentence 1 names the client’s situation in their own numbers (present perfect: “has created”); sentence 2 names the engagement; sentence 3 names deliverables; sentence 4 quantifies outcomes.
Globalisation vocabulary (L1) woven in naturally: market share, tariff, non-tariff barriers, revenue.
This is the elevator pitch — the part of the proposal a busy decision-maker is most likely to read in full.

Problem statement

PolMeble’s domestic market share has grown threefold since 2021, but the Polish furniture market as a whole has matured — overall growth has slowed from 9% (2020) to 2% (2025), and three new entrants, all backed by venture capital, have secured meaningful market share in the mid-price segment. Consequently, organic growth alone is unlikely to deliver the 20% annual revenue increases that PolMeble’s investors expect. Expansion into the Nordic-Baltic region offers a realistic path to sustained growth: the Baltic economies have experienced sustained GDP growth of 3–5%, and Swedish consumers’ preference for Central European furniture has doubled since the post-2022 supply chain reconfiguration.

Annotation: problem statement

Problem stated in the client’s own numbers. That builds credibility in two sentences.
“Consequently” — sentence adverbial (L2). Links the problem to its strategic implication.
Vocabulary from Lessons 1–4: market share, venture capital (L2), GDP growth (L1 context), supply chain (L2).
Present perfect (L1) throughout to signal ongoing developments: “has grown threefold”, “have secured”, “have experienced”.

Proposed solution

Our ten-week study will deliver:

A diagnostic phase (Weeks 1–3): country selection based on tariff regimes, consumer spending on furniture, existing trade bloc participation, and competitive density. Interviews with 25 local retail buyers.

A benchmarking phase (Weeks 4–6): comparison of three potential entry modes (joint venture with a local distributor, greenfield subsidiary, or franchising), with due diligence on three candidate partners per chosen country.

A roadmap phase (Weeks 7–10): prioritised 24-month implementation plan, first-mover advantage assessment, scalability stress-test of the operational model, and intellectual property protection review.

Annotation: proposed solution

Concrete phases, concrete deliverables. The reader can visualise what happens in each three-week segment.
Strategy vocabulary (L2): joint venture, due diligence, scalability.
Innovation vocabulary (L4): first-mover advantage, IP.
Vocabulary deployed where it fits the analysis, not as decoration.

Key benefits and deliverables

On completion, PolMeble will receive:

A written diagnostic report identifying the highest-potential country and entry mode

A 24-month implementation roadmap with sequencing, resource requirements, and investment phasing

A shortlist of three qualified local partners (distributor, retailer, or operator) with preliminary due diligence dossiers

A half-day workshop with PolMeble’s senior team to present findings and agree next steps

Based on comparable engagements, typical outcomes include:

If PolMeble enters the target market by Q3 2026, it will capture first-mover advantage over two competitors currently scoping the same region.

A 2–4% target-market share within 24 months

A 35–45% improvement in working capital turnover in international operations through a more efficient supply chain

An estimated ROI of 2.8–3.4× over a five-year horizon

Annotation: key benefits and deliverables

Deliverables (what the client physically receives) separated from outcomes (what the client can project). Two different lists; do not blend them.
First conditional (L1) in bold: “If PolMeble enters… it will capture…” projects a consequence the client can anticipate.
Ranges (2–4%, 35–45%, 2.8–3.4×) signal credible hedging while preserving conviction.
ROI (L2) and working capital (L4) used in authentic context.

Timeline and investment

Engagement: 10 weeks, beginning within 3 weeks of contract signature. Total fee: €85,000, invoiced in three tranches (contract signature, Week 5, final delivery). Projected first-year ROI based on conservative entry-market revenue alone: 2.5×.

Annotation: timeline and investment

Short, transparent, quantified. ROI stated in plain terms.

Next steps

Strategically, we recommend a 45-minute call in the week of 21 April to discuss the proposal. Please contact Julia Kowalska at julia@meridianstrategy.eu or +48 22 555 0199.

Annotation: next steps

“Strategically” — sentence adverbial (L2). Signals the authority of the recommendation.
Specific meeting duration, specific week, specific person — no friction for the reader.

Why this works:

Every section quantifies. Percentages, market share, GDP, timeline, fees, ROI.
Pain points use the client’s own data (market share, growth rates). That builds credibility.
Lessons 1–4 vocabulary used in context, not as jargon. Globalisation (tariff, trade bloc, joint venture, supply chain), strategy (market share, due diligence, competitive advantage, ROI), finance (revenue, working capital), innovation (first-mover advantage, IP, scalability).
Grammar used deliberately. Present perfect for recent trends; first conditional for projected outcomes; sentence adverbials (Consequently, Strategically) for logical signposting.
Conviction throughout, with credible hedging. Ranges (2–4%, 2.8–3.4×) signal honesty without undermining confidence.

Business reports

Purpose and style

Purpose: present findings objectively; support evidence-based decision-making.
Audience: internal or external; decision-makers and specialists.
Register: formal, objective, data-driven.
Voice: passive for findings (“A significant decline was observed in Q3”); active for recommendations (“We recommend restructuring…”); hedging for uncertainty.

Document skeleton

[TITLE PAGE]
  Report title
  Prepared for: [Recipient]
  Prepared by:  [Author / team]
  Date: [DD Month YYYY]

EXECUTIVE SUMMARY
  [A self-contained 4–6-sentence paragraph: purpose → key findings → recommendations.
   A reader who stops here must know the report's conclusions.]

INTRODUCTION
  - Background: [context, reason for the report]
  - Purpose:    [what this report does]
  - Scope:      [what it covers --- and explicitly, what it does not]
  - Methodology: [data sources, sample sizes, analytical approach, in 1–2 sentences]

FINDINGS
  [Each finding = mini-heading + data + interpretation + implication.
   4–6 findings is typical for a short report.]

  Finding 1: [Mini-heading as a claim]
  [Data → interpretation → implication]

  Finding 2: [Mini-heading as a claim]
  [Data → interpretation → implication]

  …

CONCLUSIONS
  [What the findings MEAN --- not a restatement of findings.
   Where does responsibility lie? What is within the client's control?]

RECOMMENDATIONS
  1. [Action heading]. [Justification sentence.]
  2. [Action heading]. [Justification sentence.]
  3. [Action heading]. [Justification sentence.]

APPENDICES
  [Supporting data, charts, methodological detail, raw survey responses.]

Required sections (in order)

Title page.
Executive summary — self-contained; a decision-maker who reads only this paragraph must know what the report concludes and recommends.
Introduction — background, purpose, scope (including what is not covered), methodology.
Findings — data presented and analysed, organised by theme; each theme a mini-heading.
Conclusions — what the findings mean; explicit on responsibility and control.
Recommendations — specific, actionable, each with a justification.
Appendices — supporting data, charts, questionnaires.

Types of reports

Type	Purpose	Examples
Informational	Present facts without analysis	Annual reports, progress reports
Analytical	Examine data; provide conclusions and recommendations	Market research, feasibility studies, audit reports
Proposal (report-format)	Recommend a specific course of action	Budget proposals, strategic plans

Fixed expressions

Presenting findings (often passive):

The data reveal(s) that…
Analysis of the results indicates that…
A significant trend was observed in…
Between [date] and [date], [metric] fell from X to Y.
Free-text comments consistently mention “…”, “…”, and “…”.

Drawing conclusions (active, but tempered):

Based on the evidence presented, it can be concluded that…
The findings suggest that…
It is evident from the data that…
Together, these findings indicate that the decline is driven by internal rather than market factors.

Making recommendations (active, specific, modal-varied):

It is recommended that the company…
The following actions should be considered:
Based on these findings, we propose that…
[Action heading]. This intervention addresses [driver] and can be implemented within [timeframe].

Hedging — calibrated, not reflexive:

The data suggest(s) that… (pattern visible but not definitive)
It appears that… (preliminary interpretation)
This may indicate… (causal inference plausible but unproven)
The findings are consistent with… (supporting a hypothesis without claiming to prove it)
Typically… / In most cases… (generalising cautiously)
Findings may not generalise to [other context] (explicit scope-hedging)

Length and register norms

Dimension	Norm
Length	Short analytical report: 800–1,500 words + appendices. Full report: 3,000–8,000.
Register	Formal, objective. No contractions. Third-person and passive common.
Modals	Recommendations mix must, should, could deliberately.
Voice	Passive for findings; active for recommendations and conclusions.
Hedging	Present but calibrated — not every sentence, only where warranted.

Self-check checklist

Criterion	What to look for
Executive summary	Self-contained; purpose, findings, recommendations all present
Findings vs conclusions	Clearly separated; findings present data, conclusions interpret it
Recommendations	Specific, owned, each with a justification
Hedging	Calibrated — present where warranted, absent where not
Modals	Mix of must, should, could; not uniform

Annotated report exemplar

The report below illustrates a short analytical report on HR retention and innovation pressures at a mid-sized tech firm. Note how it deploys people-management vocabulary (Lesson 4), innovation vocabulary (Lesson 4), reported speech (Lesson 4), passive voice for findings (Lesson 4), and mixed modal verbs in the recommendations (Lesson 3). The annotations explain the analytical and linguistic choices.

Retention and Innovation Pressures at SparkLogic Sp. z o.o.

A twelve-month review commissioned by the Board, prepared by HR Insights Consulting

Report date: 2 March 2026

Executive summary

Engineer churn at SparkLogic has risen from 12% to 27% over the past two years, while the sector median has held at 13–15%. The data suggest three principal drivers: a collapse in onboarding quality following the 2024 reorganisation, chronic burnout in the core product teams, and a perceived shortfall in upskilling and career-progression opportunities. Consequently, time-to-market on the last three product releases has doubled, and two competitors have launched disruptive products that directly target SparkLogic’s revenue base. Three recommendations follow: (1) the board must approve a revised retention strategy within four weeks; (2) SparkLogic should restructure onboarding around a 90-day competency framework; (3) the firm could pilot a four-day working week in one product team to test burnout mitigation.

Annotation: executive summary

Four sentences: purpose, findings, and recommendations.
Present perfect (L1): “has risen”, “have held”, “have launched” — recent trends with current relevance.
“Consequently” — sentence adverbial (L2) connects findings to consequences.
People-management vocabulary (L4): churn, onboarding, burnout, upskilling. Innovation vocabulary (L4): time-to-market, disruptive.
Mixed modals (L3): must, should, could — three recommendations at three different levels of strength.

Introduction

This report examines engineer retention and its relationship to product-delivery capability at SparkLogic Sp. z o.o. over the period March 2024 to February 2026. It draws on HR records (n = 243 leavers; n = 189 stayers), exit interviews (n = 147), the company’s internal engagement survey (n = 512), and benchmarking data from the Polish Software Industry Association. The scope is limited to engineering and product roles; findings may not generalise to other functions. The report was commissioned by the Board after the CFO flagged concerns about the impact of retention on cash flow and revenue forecasts.

Annotation: introduction

Scope named explicitly, including what is not covered (“may not generalise to other functions”).
Methodology summarised in one sentence.
Reported speech (L4): “the CFO flagged concerns”.

Findings

Churn has risen sharply and asymmetrically. Engineer churn rose from 12% to 27% over two years, while churn in non-engineering functions held at 9–11%. The 90-day attrition rate for new hires doubled, from 7% to 15%. The data suggest that post-onboarding retention is where the system is breaking.

Annotation: finding 1 (churn)

Mini-heading encapsulates the finding — it states the claim, not the topic.
Hedging: “The data suggest” is authoritative but not over-committed.
No passive voice here: the findings are stated in active voice for clarity.

Onboarding quality has deteriorated since the 2024 reorganisation. In the internal engagement survey, 68% of new hires reported that onboarding was inadequate (up from 22% in 2023). Exit interviews identified the same theme: 74% of leavers in their first year cited “unclear role expectations” or “limited support during ramp-up”. The Head of People acknowledged in her December briefing that onboarding resources had been reduced by 40% in the 2024 cost-cutting round.

Annotation: finding 2 (onboarding)

Reported speech (L4): “The Head of People acknowledged… that onboarding resources had been reduced”.
Tense backshift: past simple → past perfect (“had been reduced”).
Reporting verb “acknowledged” signals concession — not a neutral statement.
Passive voice (L4): “had been reduced” — the agent (management) is implied.

Burnout is systemic in three of five product teams. Sick-leave days rose 120% over two years, concentrated in the Platform, Payments, and Data teams. The engagement survey’s burnout index moved from “elevated” to “severe” in these three teams. Several team leads have stated that workloads have not been rebalanced since the 2024 restructure.

Annotation: finding 3 (burnout)

Reported speech with reporting verb “stated” — neutral, appropriate for a formal report.
Present perfect: “have stated” because the statements remain relevant.
Passive voice: “have not been rebalanced” — the failure is structural, not about any single actor.

Upskilling and career progression are perceived as inadequate. In exit interviews, 61% of leavers cited a lack of upskilling opportunities or unclear promotion paths. Benchmarking data from the Polish Software Industry Association indicate that sector-median training investment per engineer is 2.3× SparkLogic’s level. Furthermore, the ratio of senior to junior engineers has shifted from 1:3 to 1:6, constraining mentoring capacity.

Annotation: finding 4 (upskilling)

“Furthermore” — sentence adverbial (L2) adds an additional finding.
Vocabulary: upskilling (L4), benchmarking (L2).
Passive implicit in “are perceived”.

Time-to-market has doubled. Average time-to-market on the last three product releases was 14 months, compared with 7 months on the three releases preceding the 2024 reorganisation. In the interim, two competitors have launched products in adjacent categories that directly target SparkLogic’s core revenue base.

Annotation: finding 5 (time-to-market)

Direct connection between the people issue (churn, burnout) and the business issue (time-to-market, revenue).
The two-competitor finding frames the strategic stakes — this is what makes the retention problem a board-level concern, not merely an HR concern.

Conclusions

The data indicate that SparkLogic’s retention problem is not driven by market-wide conditions — the sector median has held steady — but by internal factors that are within the firm’s control. Three drivers (onboarding, burnout, upskilling) account for the majority of reported reasons for leaving, and each is directly linked to the 2024 reorganisation. The secondary consequences (time-to-market, competitive erosion) suggest that the retention problem is now a strategic, not merely operational, concern. If SparkLogic does not act in the current quarter, the recovery horizon is likely to extend well beyond twelve months.

Annotation: conclusions

Conclusions are not a repetition of findings — they say what the findings mean: where responsibility lies and what is at stake.
First conditional (L1) in the last sentence projects the cost of inaction: “If SparkLogic does not act… the recovery horizon is likely to extend…”.
Hedging: “is likely to” preserves authority without over-committing.

Recommendations

The board must approve a revised retention strategy within four weeks. The current trajectory threatens SparkLogic’s ability to deliver the 2026 product roadmap and therefore its Q4 revenue guidance. Delay increases cost.

SparkLogic should restructure onboarding around a 90-day competency framework. A structured framework, with explicit milestones and mentor assignments, addresses the single biggest cited driver of first-year attrition. Implementation within one quarter should be feasible given existing HR resources.

SparkLogic could pilot a four-day working week in one product team to mitigate burnout. This intervention carries implementation risk and may not generalise, but a small-scale pilot would generate evidence within six months. If the pilot demonstrates productivity neutrality or improvement, the approach ought to be considered for wider rollout.

Annotation: recommendations

Mixed modals (L3) deployed deliberately:
- Recommendation 1 uses must (obligation — non-optional for business survival).
- Recommendation 2 uses should (advice — the recommended approach, though alternatives are conceivable).
- Recommendation 3 uses could (possibility) and ought to (stronger moral/business advice for the follow-up).
Each recommendation has a heading (the action) and a justification. Owned, specific, actionable.

Why this works:

Executive summary is a self-contained document. A decision-maker who reads only the first paragraph knows what the report concludes and what is being recommended.
Findings are separated from conclusions. Findings present data; conclusions say what the data mean.
Hedging is calibrated. “The data suggest”, “is likely to”, “may not generalise” — used where warranted, not in every sentence.
Reported speech (L4) is used naturally when summarising stakeholder inputs (the CFO, the Head of People, team leads).
Passive voice (L4) is used where the agent is implicit or secondary: “had been reduced”, “have not been rebalanced”.
Sentence adverbials (L2) mark the logical structure: Consequently, Furthermore.
Modal verbs (L3) are deliberately mixed across recommendations: obligation, advice, possibility.
Vocabulary (L4): churn, onboarding, burnout, upskilling, time-to-market, disruptive, revenue, cash flow — naturally in context.

Style rules that apply across all three genres

1. Clarity

Put the key message first. Memos and emails: first paragraph. Proposals: executive summary. Reports: executive summary.
One idea per paragraph. If a paragraph does two things, split it.
Name what you mean. “A number of issues” → “Three issues: class quality, equipment availability, opening hours.”

2. Conciseness

Every word should earn its place. Polish writers in English often inherit sentence-level constructions from Polish that over-specify. Compare:

Verbose	Concise
In order to be able to…	To…
Due to the fact that…	Because…
At this point in time…	Now
It should be noted that…	Note that… (or drop entirely)
In the event that…	If…
For the purpose of…	To… or for…
A significant number of…	Many…
We are currently in the process of reviewing…	We are reviewing…

3. Active vs. passive voice

Active is the default. Passive is a diplomatic and structural tool, not a formality:

Situation	Preferred voice	Example
Personal commitment	Active	“We will deliver the report by Friday.”
Giving praise	Active	“Your team exceeded all targets.”
Sensitive feedback	Passive	“Deadlines have been missed on two projects.”
Institutional policy	Passive	“Expense claims must be submitted within 30 days.”
Report findings	Passive (often)	“A significant decline was observed in Q3.”
Recommendations	Active	“We recommend restructuring the marketing department.”

Rule of thumb: active for praise and commitments; passive for criticism and policy.

4. Modal verbs in recommendations

Modal	Strength	Use when…
must	Obligation	Non-negotiable; action is required
should	Advice	Preferred course; alternatives exist
could	Possibility	One option among several
may	Hedged possibility	Acknowledges uncertainty in outcome
will	Commitment	Used in proposals for what you will do

Calibration principle: mix modals deliberately. A report using only should reads as uniformly advisory; one using only must reads as prescriptive. A proposal using might reads as uncommitted.

5. Hedging

Hedging serves three purposes:

Acknowledging uncertainty without undermining authority.
Preserving room to revise if new evidence emerges.
Distinguishing pattern from proof.

Phrase	Use when…
The data suggest(s) that…	Pattern visible but not definitive
It appears that…	Preliminary interpretation
This may indicate…	Causal inference plausible but unproven
The findings are consistent with…	Supporting existing hypotheses rather than proving them
Typically… / In most cases…	Generalising cautiously
Findings may not generalise to…	Explicit scope-hedging

Discipline of hedging: use it to preserve authority in the face of uncertainty. Do not use it to avoid taking a position. A report that hedges every sentence reads as unsure; a report that hedges nowhere reads as over-confident. Calibrate.

6. Headings and bullets vs. paragraphs

Use headings/bullets when…	Use paragraphs when…
Information is list-like or parallel	Argument requires continuous reasoning
Reader is scanning (memos, executive summaries)	Reader is reading linearly (conclusions)
Items need to be counted, compared, or ticked	Transitions (“however”, “consequently”) matter

Memos tend toward bullets and headings. Reports blend: bullets for findings or recommendations; paragraphs for introduction and conclusions.

7. Sentence adverbials (linkers)

Use them deliberately. Overuse looks formal but empty.

Function	Adverbials
Addition	Furthermore, in addition, moreover
Contrast	However, nevertheless, on the other hand
Cause/effect	Consequently, therefore, as a result
Sequence	First, subsequently, finally
Clarification	That is, in other words, specifically
Conclusion	In conclusion, overall, on balance

8. Tone calibration by genre

Dimension	Email (internal)	Memo	Proposal	Report
Formality	Neutral	Professional	Professional	Formal
Contractions	Acceptable	Avoid	Avoid	Avoid
First person	I / we	We (institutional)	We (the firm)	The analysis / this report
Conviction	Moderate	Moderate	High	Calibrated
Hedging	Minimal	Minimal	Minimal	Essential
Modals	Could, would	Must, should	Will	Mixed

Common mistakes to avoid

In all three document types

Failing to define the purpose in the opening.
Burying the key message under context or preamble.
Using overly complex language where simpler alternatives exist.
Neglecting to proofread.
Inconsistent formatting (mixing bold headings and underlined headings; inconsistent bullet punctuation).

In memos specifically

Vague subject lines (Policy update).
Opening that restates the subject rather than giving context.
Calls to action without deadlines.
Greeting or sign-off imported from emails (Dear colleagues, … Kind regards). Memos do not use them.

In proposals specifically

Generic consulting language that could apply to any client.
Unquantified benefits (significant savings, improved efficiency).
No explicit next step.
Hedging in the executive summary, which undermines conviction at the most important point.
Listing company credentials before naming the client’s problem.

In reports specifically

Merging findings and conclusions (findings = what the data show; conclusions = what they mean).
Recommendations that are vague (“Improve training”) or unowned (“Training should be improved” — by whom?).
Either no hedging (reads as over-confident) or hedging every sentence (reads as unsure).
Executive summary that is not self-contained (requires the reader to read further to understand the conclusions).
Methodology hidden in an appendix when it belongs in the introduction.