Word for business analysts on Mac: specs, templates and Track Changes in 2026

Word is where a lot of waterfall-style analysis ends up. A business analyst writes the approach plan, the business case, the requirements and the functional spec, then routes each file through review. Most of that work is structured text, tables and a few diagrams pasted in as pictures. Word handles that well, if you set it up before you start.

The documents business analysts write in Word

A business analysis guide for waterfall projects lists five core deliverables. They are the Business Analysis Approach Plan, the Business Requirements Specification, the Business Case, the Functional Specification and the Non-Functional Specification. Those five are a good map for the Word files you will open on a waterfall project.

The Business Requirements Specification usually holds a stakeholder model, a business domain model, business use cases, business activity diagrams and business requirements. The Functional Specification adds system use cases, user requirements, system activity diagrams, class diagrams and functional requirements. Give each of those sections its own heading, so reviewers can jump between them.

• Approach plan: how you will run the analysis, who signs off and when
• Business case: why the change is worth the cost and the time
• Business requirements specification: what the business needs, in business terms
• Functional specification: what the system must do to meet those needs
• Non-functional specification: quality rules such as performance and security

If your team runs agile sprints, user stories often live in a tracker, not in Word. Word can still hold the business case or the approach plan. Check which tool your team uses before you build a template, so you do not design for the wrong files.

Set up a Word template before you write the first page

Start from a template, not a blank page. Open File > New from Template, then pick the template you want. Microsoft's template guide describes that path for starting a new document. Build the template once, then reuse it for every spec in the project.

On a Mac, Word saves templates by default in a Group Containers folder under User Content and Templates. If you want them somewhere easy to find, change the location. Go to Word > Preferences > File Locations and pick a folder your backups cover.

Here is a setup that works for a Business Requirements Specification. Make Heading 1 the main sections: Introduction, Scope, Stakeholders, Business requirements, Assumptions and open questions. Make Heading 2 the requirement groups under each one. Put the project name and version in the header, and page numbers in the footer. Then save the file as a template.

For the full steps, read How to create a template in Word on Mac and How to apply heading styles in Word on Mac.

Why attaching a template to an old spec breaks

This is the mistake that costs the most time. You have a spec from last quarter, and you want the new look. You attach the new template through the old menus and expect the whole file to change. It usually does not.

In a Microsoft Q&A thread from April 2020 about Word for Mac, a user found that attaching a template only imported styles. Headers, footers and page setup did not come across. A moderator in that thread said copy and paste is the only way to get the full setup into an existing file.

So start a fresh file from the template, then copy content into it. Work in sections, not in one big paste. Copy one section, check its headings, then move on to the next.

1. Open a new document with File > New from Template and pick your template.
2. Save it under the new version name, with the date in the file name.
3. Copy one section at a time from the old file.
4. Paste as plain text if the old formatting fights with the new styles.
5. Check that each heading uses a template style before you copy the next section.

Track Changes on Mac: toggle it, view it and read it

Track Changes runs most review cycles. On a Mac, press ⌘⇧E in the document text area to turn it on or off. Microsoft's screen reader guide documents that shortcut. Click into the body text first, or the shortcut may not reach the document.

Microsoft recommends Print Layout View with All Markup for reading and editing. Simple Markup is the default, so change it before a review. With All Markup set, every change shows on screen, and reviewers see what you see.

Newer Word builds change the button. Track Changes now offers Track Everyone and Track Just Mine instead of a plain on or off switch. Pick the option that matches the review. In a narrow window, the arrow may open a dropdown, so click Track Changes inside that palette.

In a Microsoft Q&A thread about turning Track Changes off, one user reported accepting a change after every line they added. The suggested fix was to accept all changes, then turn tracking off. The thread shows no accepted answer and no planned fix, so check the state before every send.

Compare two versions of a spec without losing track

Compare shows what changed between v2 and v3, especially when a stakeholder edits outside Track Changes. For the steps, use How to compare two documents in Word on Mac. Before you run it, save both versions with clear names and dates, so you know which one is the base.

Microsoft's known-issues page lists 'Files are grayed out when using the compare feature in Word for Mac' with a workaround. If your files look grayed out, read that page before you assume the file is broken.

A simple habit prevents most compare confusion. Do not compare two copies that were both edited after the last save. Keep the base file with a v2 label and do not edit it again. Work only in the new copy.

Comments and questions for reviewers

Use comments for questions and Track Changes for wording. A comment asks a stakeholder to decide something. A tracked change proposes new text. Mixing the two makes reviews hard to close. For the steps, see How to add a comment in Word on Mac.

Good comments name the decision you need. Write 'Refund approval: who signs off?' instead of 'check this.' The reviewer can answer in one line, and you can search for the comment later.

Where your time goes in Word, and what the data says

Microsoft's Work Trend Index is cross-industry data, not business analyst data. Its chart gives Word 10% of average total work time. The telemetry covers a rolling 28-day period ending in March 2023, so the figure is dated. The same page says 62% of respondents struggle with time spent searching for information.

Searching is the cost you can cut. Clear structure, consistent headings and a working table of contents save time on every review. Readers can jump to a requirement group instead of scrolling. For the table of contents steps, see How to insert a table of contents in Word on Mac.

The same Microsoft page says 68% of people lack enough uninterrupted focus time during the workday. Writing a spec in one sitting helps with that. Put the document in its own window, and close the mail and chat windows while you draft.

Mistakes business analysts make in Word on Mac

• Attaching a template to an old file, then expecting headers and page setup to change.
• Leaving Track Changes on in the final version, or off during a review.
• Choosing Track Everyone when you meant Track Just Mine, or the reverse.
• Typing headings in Normal style, so the table of contents stays empty.
• Comparing two copies that were both edited after the last save.
• Pasting drafted requirement text without checking it against stakeholder notes.

The last mistake matters most when you use AI help. Drafted text is a starting point. You still own the requirement, the scope and the wording. Read every line against the notes from the workshop before it goes into the file.

Known problems to check before a deadline

Microsoft's known-issues page for Word for Mac lists problems that can cost you a whole morning. It lists a prompt to save locally saved documents after the file sits idle with no edits. It also lists a case where saving a document as a PDF to an online location changes the file to .docx. Read the workaround on that page before you need it.

Check your subscription status in your Microsoft account before you rely on a file for sign-off. If the status looks wrong, ask whoever manages your Office licenses. For PDF output, read How to save as a PDF in Word on Mac. For a file that vanished, read How to recover an unsaved document in Word on Mac.

Where Lazur fits while you work in Word

Lazur is a voice assistant for the Mac that lives in the notch. Hold Option and Command together to ask about anything on your screen. Lazur answers out loud. It looks at your screen only while you hold the shortcut, and the audio and screenshot are not stored after they answer.

Ask where something is, and Lazur draws a circle and a label around it. It does not click the button for you. Ask how to do something, and Lazur guides you one click at a time, waiting for each click. That helps when a control moves, as the Track Changes button did in newer builds.

Lazur is not a plugin or add-in for any app. It works across apps on your Mac, so you keep Word open and in your control, and you decide every edit.

Dictate and draft spec sections by voice

Hold fn to dictate clean, formatted text at the cursor in any app. Dictation lands where your cursor sits, so it works in Word the same way it works in Mail. Add project names and product terms to the personal dictionary once, so they stop getting misspelled.

Use voice for the first draft of a use case. Say the actor, the precondition, the main flow and the exceptions, in that order. Then ask Lazur to draft a clean version. Review it line by line, and check every step against your interview notes before you paste it in.

For example, say: use case, a customer requests a refund, actor is the service agent, the order is already paid, the agent checks the order and approves it. Then ask for the steps as a numbered list. You get a first pass to edit, and the wording still needs your judgment.

A repeatable routine for every spec review

1. Open the template with File > New from Template, not the old file.
2. Save the new version with a clear name and the date.
3. Set All Markup in Print Layout View before anyone reviews.
4. Press ⌘⇧E to turn Track Changes on, then choose Track Everyone or Track Just Mine.
5. Add comments for questions and tracked changes for wording.
6. Accept all changes and turn tracking off before you export the final PDF.

Keep the routine short. Most of it is one click or one shortcut once the template exists. The same steps work for a business case, a functional spec or an approach plan, so you only build the routine once.

Get Word for Mac set up, then try Lazur

Check your version first. Open Word > About Word to see your build. Microsoft's update history lists Word for Mac build 16.114.4 (build 26110224) as the most recent, released November 4, 2026. If you are behind, update through Microsoft AutoUpdate.

Then build the template, set All Markup and save a PDF before your first review. Once that works, try Lazur on the parts that stall you, such as a hard sentence or a menu you cannot find. Lazur has a free trial with no credit card, and you can download it here.