Microsoft Word

What Microsoft Word is

Microsoft Word is Microsoft’s word processor for creating, reviewing and presenting documents. Its working unit is a file structured into paragraphs, styles, tables, images and references. It is part of Microsoft 365 and is also offered through one-time-purchase Office editions.

A word processor becomes particularly useful when a document must evolve: correcting a condition, reorganising chapters, incorporating review or producing a distribution copy. Editable content preserves possibilities that a page image cannot provide.

For OSH it supports procedures, reports and guides. Its role is documentary: professional appearance, an inserted signature or a shared file cannot replace technical validation and currency control. Quality depends on structure, sources and review.

Reference documentation: Microsoft Word: product and editions.

Origins and growth of the word processor

Word’s first version was released on 25 October 1983; Word for Windows followed in 1989. Its origins involve Charles Simonyi, formerly of Xerox PARC, and Richard Brodie. The project brought visual editing and mouse-based interaction to personal computing.

Its history spans DOS, Macintosh and other platforms; Microsoft Write was an adaptation marketed for Atari ST. During the Word 6.0 period, pursuing a common Windows and Mac codebase created difficulties later described by developer Rick Schaut, including cancellation of the Pyramid rewrite project.

Word became a reference point for document exchange as Office expanded. In 2014 the Computer History Museum released historical Word for Windows 1.1a code, with Microsoft’s permission, for non-commercial use. That historical release does not make current versions open-source software.

Later development combines local documents, cloud collaboration and AI assistance. To interpret an older feature, identify its edition and platform: product history is not a catalogue of capabilities available today.

Reference documentation: Microsoft Word history and timeline · Computer History Museum: Word for Windows source code and origins · Rick Schaut: Mac Word 6.0, archived developer account · Contemporary review of Microsoft Write for Atari ST.

DOC, DOCX and template formats

DOC is the historical binary format. DOCX is the usual XML format; DOCM supports macros. DOTX identifies templates and DOTM macro-enabled templates. These extensions represent functional differences rather than alternative names for an identical file.

A DOCX is a ZIP-based package containing related parts such as content, styles and resources. Office Open XML distinguishes profiles and compatibility rules. This structure explains how text, images and comments can persist as separate components.

For a procedure, retain an editable original and define a distribution copy. Renaming an extension is not format conversion. Verify opening, graphics and fields after any conversion.

Reference documentation: File format reference for Office · Library of Congress: DOCX structure and preservation.

Compatibility, ODT and distribution copies

Word can exchange ODT documents, but Microsoft documents fully supported, partly supported and unsupported features. Conversion can affect formatting, comments, controls or protection. Successful opening does not guarantee preservation of every property.

Separate three goals: continued editing, preserving a particular presentation and archiving evidence. The appropriate copy may differ. For tables, signatures or references, check the resulting file in the recipient’s application.

A visual review should cover the cover page, headers, footers, long tables and final page. Also check text search, links and reading order. A copy distributed as the current reference needs an identifier linking it to the approved original.

Reference documentation: Differences between ODT and DOCX.

Styles and long-document structure

Styles group formatting decisions that can be changed together. Structural headings organise the document and support an automatic table of contents. Multilevel numbering can be linked to headings to maintain a consistent hierarchy.

A long procedure should let readers find an answer without reading everything. Reserve one level for chapters and another for their sections; avoid arbitrary jumps. Distinguish execution steps, explanations and notes through clear roles rather than decorative changes.

After reorganising content, update the contents and check references. Manually typed page numbers and repeated titles create maintenance points. Stable structure supports review, translation and updating because each section has a recognisable identity.

Reference documentation: Customize or create new styles · Insert a table of contents · Number your headings.

Templates, forms and editorial consistency

A template creates new documents from a predefined structure. It can include styles, sections, common text and content controls such as text fields, lists or dates. The resulting document is saved separately from its template.

An OSH report template might require purpose, scope, evidence, conclusions and ownership. This helps detect omissions, but a completed field does not establish an observation’s accuracy. Instructions should distinguish required content from examples to remove.

Assign a version and maintenance owner. When a common section changes, decide whether it affects earlier reports or only new documents. Reusing an old copy can carry names, dates or conditions unrelated to the current case.

Reference documentation: Save a Word document as a template.

Tables, equations and bibliographic references

Word provides tables and an equation editor. It also records sources, inserts citations and generates bibliographies. It organises references but does not establish that a source supports a claim or that the edition is current.

For a technical report, define each variable, unit and criterion before presenting a formula. Separate measurement, calculation and interpretation. Tables need clear headings and a connection between each result and its source, date and method.

References should support verification through author or organisation, title, date and relevant location. Identify the edition of any standard or guide. Before release, check that in-text references match final entries and that no provisional placeholders remain.

Reference documentation: Write an equation or formula · Create a bibliography, citations and references.

Images, WordArt and page stability

Text-wrapping options position images relative to text. WordArt applies graphical effects to lettering. These features enrich documents but require checking how content behaves when paragraphs or tables change length.

A field photograph should include a caption, context and, where appropriate, a reference to the observation. Avoid images whose essential text becomes unreadable when reduced. Explanations should remain understandable with magnification or greyscale printing.

In long documents, check that related headings and paragraphs stay together and that continuing tables retain headings. Improvised manual breaks may work in one copy and fail after translation. Review the final version, not only the editing screen.

Reference documentation: Wrap text around a picture in Word · Insert WordArt.

Co-authoring, comments and tracked changes

Co-authoring supports joint work on a shared document; real-time behaviour depends on version and subscription. Track Changes records edits for acceptance or rejection. Comments discuss proposals and are a separate mechanism from revisions.

Agree who drafts, who validates technical content and who prepares the final copy. Comments should explain a question and its consequence, such as an instruction being ambiguous for a particular shift. Resolving a conversation does not itself approve the entire document.

With multiple reviewers, assign sections or criteria to prevent conflicting decisions. Preserve an internal review copy and an identifiable distribution version. Simultaneous editing supports collaboration but still needs closure rules.

Reference documentation: Collaborate with real-time co-authoring · Track changes in Word.

Proofing, language and assisted reading

Microsoft Editor suggests spelling, grammar and style corrections. Compatible Word editions also provide dictation and Immersive Reader. Availability and behaviour should be checked for the language and account in use.

Language correction does not replace technical precision. A dictionary-approved term may be inappropriate in prevention, while shortening a sentence can remove an essential condition. A shared glossary helps align Spanish, Catalan and English terminology.

Instructions benefit from concrete actions and identifiable responsibilities. Check that translations preserve conditions, exceptions, units and sequence. Reading aloud can reveal awkward sentences, but final review must consider the actual task and audience.

Reference documentation: Check grammar, spelling and more · Current Word web versus desktop feature comparison.

Document accessibility and comprehension

The Accessibility Checker helps identify issues during authoring. Headings, alternative text and coherent reading structure contribute to accessible preparation. Human review remains necessary: passing a checker does not establish that an instruction is understood.

In an induction guide, explain an image’s purpose rather than repeating its filename. Use links that identify their destination and avoid relying exclusively on colour. A table should make sense when its cells are read in order.

Test magnification and keyboard use, and ask someone outside the writing team to locate a specific answer. Accessibility also requires clear vocabulary, relevant examples and consistency between text, images and appendices.

Reference documentation: Make Word documents accessible.

Mail merge and content reuse

Mail merge combines a base document with a data source to produce personalised copies. Spike collects multiple cut fragments for pasting together. These are different reuse mechanisms: one substitutes fields, while the other assembles selected content.

For a campaign, the base document can retain a common message while varying site, contact or session. Before generating every copy, test an ordinary record, empty fields and a long name. Verify that nobody receives another person’s data.

Reused content needs checks for currency and context. A paragraph suitable for one installation may include conditions that do not hold elsewhere. Templates reduce repetition; checking applicability remains an editorial task.

Reference documentation: Use mail merge to personalise letters · Use the Spike to cut and paste multiple items.

Macros and document automation

VBA macros automate operations in compatible documents. Microsoft blocks certain internet-origin macros by default in Office for Windows. A file containing code requires a different trust decision from a text-only document.

A useful automation might apply an approved structure or check required fields. It needs an owner, version and test examples. Verify generated output, particularly changes to tables, links or repeated text.

For an ordinary procedure, consider whether executable code is necessary. Unnecessary dependencies complicate maintenance and review. Where a macro is needed, document inputs, intended changes and recovery of a previous copy.

Reference documentation: Internet macros blocked by default in Office for Windows.

Metadata, hidden text and protection

Document Inspector searches for hidden information and personal data, including properties and review content. Word also offers password protection. Restricting editing and controlling who can open a file address different needs.

Before distribution, work on a copy and decide what information to retain. A report may need author and date, but not internal comments or names inherited from a template. Preserve working history in its repository when required.

Confidentiality depends on the whole lifecycle: original location, permissions, delivery, copies and retention. A password does not prevent an authorised recipient from reproducing readable content. Defining the audience and minimising data supports purposeful distribution.

Reference documentation: Inspect hidden data and personal information · Protect a Word document with a password.

Copilot and AI-assisted editing

Copilot can draft, expand and rewrite content using references. Availability depends on licence, settings and platform. Edit with Copilot, formerly Agent Mode, changes content within the document and is rolling out gradually; accounts do not all have identical capabilities.

Current documentation identifies limits: assisted editing cannot accept or reject revisions or modify comments. The review process therefore needs to remain explicit. Fluent proposals can still contain incorrect numbers, citations or conditions.

For OSH, supply approved material and request a bounded transformation, such as clarifying an explanation while preserving its conditions. Compare output with the original, verify references and record relevant changes. Generated instructions need appropriate validation before operational use.

Reference documentation: Draft and add content with Copilot in Word · Edit with Copilot in Word: rollout and limitations.

Desktop, browser and support lifecycle

Desktop Word and Word for the web share editing, comments and collaboration but differ in advanced tools. Microsoft’s current comparison reserves capabilities such as mail merge and bibliography creation for desktop. Preserving a feature in a file does not mean every platform can edit it.

Office 2021 support ended on 13 October 2026. An installation continuing to open files does not establish that it receives fixes. Edition decisions should consider operating system, local work, collaboration and maintenance.

For multilingual teams, test the most demanding document before standardising: tables, equations, images and revisions. Agreeing a delivery version and checking application reduces differences between approval and the reader’s eventual experience.

Reference documentation: Current Word web versus desktop feature comparison · Office 2021 support ended in October 2026.

Historical features and older documentation

Older manuals mention AutoSummary, a removed feature distinct from current Copilot summaries. Microsoft Equation 3.0 was also removed in January 2018 and replaced by the modern equation editor.

These changes explain why older documents may retain objects requiring specific treatment. Before upgrading a library, inventory formats, macros and special elements. Convert and inspect a test file to detect losses before processing the collection.

Preservation should reflect documentary value: editable text for maintenance, a stable consultation copy and evidence of the approved state. Successful migration preserves meaning and traceability as well as opening the file.

Reference documentation: Removed features and Office compatibility issues · Removal of Microsoft Equation 3.0 in January 2018.

Practical applications in OSH

In occupational safety and health, it can support procedures, reports and reference documents with a consistent structure. Its potential role is making text review easier and keeping versions identifiable, while technical validity and approval remain the responsibility of the appropriate people. A document workflow still needs clear ownership and release criteria.

Other proposed uses include a site-visit report and an induction guide with common sections across locations. A report should distinguish observation, interpretation and agreed action. A guide template helps identify missing sections but does not establish that an instruction applies to a particular role. A responsibilities table should name a concrete function rather than relying on vague passive wording.

Worked example and result checks

For the reporting procedure, start from a copy identified as a draft. Structure its purpose, scope, channel, minimum information and follow-up using heading styles. Ask reviewers to explain in comments why they propose changing a condition, responsibility or deadline, so the operational effect can be assessed.

Resolve each amendment with the appropriate person and prepare a distribution copy. Check that unresolved questions have not entered the final wording and that names, links and references match. Test retrieval: someone uninvolved in drafting should find what to do and whom to contact. Finally, open the file the recipient will actually receive, inspect page breaks, tables and links, and record the approved version in the designated repository. A new export should be checked again when layout or essential content changes.

Limitations and conditions of use

A polished file does not prove approval or currency. Define owners and versions, review exports and avoid circulating outdated copies. Tracked changes may contain internal information: check which comments and metadata accompany the copy intended for other readers.

Microsoft explains that No Markup merely hides revisions: they must be accepted or rejected to remove them. Stopping the recording of new changes does not remove existing ones. Before distribution, inspect comments and properties in a copy while preserving necessary internal history.

Reference documentation: Accept or reject tracked changes.

When to choose it and how to complement it

Word fits long documents, detailed review and controlled page layout. Google Docs offers a comparison focused on a shared online document. PowerPoint supports an oral explanation of a procedure without turning the slides into its official documentary version.

Consider who will edit, the recipient’s required format, how approval is recorded and who maintains distributed copies. Test a document containing an actual table and image before deciding the delivery format.

Frequently asked questions

Does hiding markup remove changes?

No. Revisions remain in the file until accepted or rejected. Reopen the distribution copy and check its state.

Is a large title automatically a structural heading?

Not necessarily. Heading styles make hierarchy recognisable for navigation and assistive technologies; visual size alone does not provide that structure.

Is a shared document automatically current?

No. Current status requires a decision and a distribution process. Identify the version, owner and consultation location so readers can distinguish a draft from approved instructions.