Google Docs for journalists on Mac: drafting, comments and revisions in 2026

What journalists use Google Docs for

Most reporters use Google Docs for three jobs. They draft a story, take comments from an editor, and check the history when a sentence changes. None of that needs an add-on. It needs the right shortcuts and a clear idea of what the doc protects and what it does not.

The best public data is broad. ICFJ's 2019 survey covered more than 4,100 newsroom managers and journalists in 149 countries. It looked at technology use across newsrooms, not at Google Docs alone. Treat it as context, not proof of how your desk works.

Google Docs shortcuts on Mac for reporters

Google publishes a full Mac shortcut list, and it is long. Learn three keys first. Press ⌘ / to open the common shortcuts inside Docs. Press ⌥ / to open the tool finder, which lets you type the name of a command.

• ⌘ / shows the common keyboard shortcuts inside Google Docs.
• ⌥ / opens the tool finder, so you can type a command name.
• ⌃ ⌥ T opens the Tools menu without the trackpad.
• ⌘ ⌥ M inserts a comment on the selected text.
• ⌘ ⌥ F inserts a footnote at the cursor.

Reach the menus from the keyboard

On a Mac, Google lists menu access as Ctrl plus Option, then one letter. ⌃ ⌥ F opens File. ⌃ ⌥ E opens Edit. ⌃ ⌥ V opens View. ⌃ ⌥ I opens Insert. ⌃ ⌥ O opens Format. ⌃ ⌥ T opens Tools. ⌃ ⌥ H opens Help. ⌃ ⌥ A opens Accessibility.

Here is a worked example. Say you need voice typing, and your hands are on the keyboard. Press ⌃ ⌥ T, then choose Voice typing. The full path is Tools > Voice typing. Learn the letters you use most, and skip the rest.

Suggesting mode and comments in Google Docs

Suggesting mode is how you send changes without overwriting a draft. Press ⌘ ⌥ ⇧ X to switch it on. Each edit then appears as a proposal. Your editor accepts or rejects it, one change at a time.

Edits made while Suggesting is off are direct edits. Your editor may not see that you changed a quote. Check the mode before every editing round, not just the first one.

Comments work the same way. Select a sentence, press ⌘ ⌥ M, and type the note. To review every open thread, press ⌘ ⌥ ⇧ A. Resolve a thread once the fix is in, so the list stays short.

When an editor rejects a suggestion, the text goes back to its old wording. Do not retype it from memory. Use revision history to find the exact words.

Revision history in Google Docs for corrections

Revision history answers the question that follows a correction. Who changed this line, and when? Press ⌘ ⌥ ⇧ H to open it. Use it to check the draft before you answer a question about an edit.

When an editor asks what changed in the last round, do not answer from memory. Open revision history, find the version from that round, and compare it with the live text. Then fix the live text, not the old version.

Revision history is a record, not a backup. It lives inside the same Doc that Google can read. Keep your original notes, recordings and source contacts somewhere else, as the privacy section explains.

Voice typing in Google Docs on Mac

Voice typing lives under Tools > Voice typing. It needs the latest Chrome, Edge or Safari. Voice commands only work in English, with an English account and an English document language. Your administrator can turn the feature off.

Lazur's dictation is a separate tool. Hold fn to dictate clean, formatted text at the cursor in any app. Use it for notes, drafts and quotes when you want the text cleaned up on the way in.

Offline editing in Google Docs on Mac with Chrome

Offline editing needs Google Chrome or Microsoft Edge on your Mac, plus the Google Docs Offline Chrome extension. Turn it on in Drive settings. Or open a document, click the status icon next to the file title, and select Turn on.

Setup needs an internet connection. Do it at home, not on the train. Write the steps in your notes app, so a colleague can help if an administrator has blocked the feature.

Three limits catch people out. Only one account for each browser profile can have offline enabled. You cannot use private browsing. An administrator can block the feature for a work account.

Large files may fail to sync. Google suggests splitting a long document into smaller ones. Its offline help page does not mention offline comments, real-time collaboration or shared drives, so do not assume those work offline.

Google Docs length limits for long investigations

A Google Doc can hold up to 1.02 million characters, according to Google Drive Help. A plain text file converted to Google Docs format can be up to 50 MB. Google lists no page, image or comment limits on that page.

A long investigation can get close. Interview transcripts, source lists and several draft versions add up. One doc per chapter, plus one for notes, keeps each file easy to open and easier to sync offline.

Here is a practical split. The story draft stays in one Doc. Transcripts go in a second Doc. Source details stay out of Google entirely. Put a short index at the top of the draft, so you can find each file fast.

A single feature story, even a long one, is a small fraction of that limit. The limit matters when you keep every transcript and every draft in one file. Check the length of the biggest file each week, and split it before it gets unwieldy.

What Google can see in Google Docs

Documents inside a Google Workspace domain are not end-to-end encrypted, according to the Freedom of the Press Foundation. Google can generally read the contents. Administrators may be able to see them too.

The same article cites 2022 data. Google received 111,608 US government requests covering 207,360 accounts. The article says Google provided data in roughly 84% of them. Those numbers describe government requests in general, not any one newsroom.

The article also describes a reporter whose working Google Doc was frozen in 2017. No clear violation was identified, and the freeze was apparently for a terms-of-service issue. The advice is to keep source details elsewhere, in end-to-end encrypted services or local storage.

Lazur's privacy rules describe Lazur only. Lazur listens and looks at the screen only while you hold the shortcut. Audio and the screenshot go to AI providers to answer, and they are not stored. Content is never used to train AI models. None of that changes what Google can read in your Doc.

Fact-checking around the draft

Google Docs holds your draft. It does not check facts for you. The ICFJ survey found that more than 50% of journalists surveyed regularly use digital tools to fact-check information.

Build the check into the doc. Keep a table with each claim, its source and the date you checked it. Editors can then see the trail in one place, without a second file.

• Claim: the sentence as it will be published.
• Source: the document, person or record it came from.
• Checked by and date: your initials and the day.
• Status: confirmed, corrected or still open.

Keep the table under the draft, or in a Doc of its own. Link it in the first comment, so editors find it fast.

Google Docs templates for news stories

The templates I found for news are basic. Docsandslides offers a free news article template with places for headlines, leads and body text. It is aimed at reporters, bloggers and journalism students.

The license is free for personal and business use, and attribution is required. I did not find a newsroom workflow template, such as a corrections log or a source sheet. Build those yourself and keep a copy in your Drive.

Start from the news template for the draft. Copy the fact-check table into a second template. Then keep a third template for corrections, with the date, the error, the fix and the editor.

Mistakes that cost reporters time

• Editing with Suggesting mode off, so an editor cannot see your changes.
• Trusting offline sync for a long file before testing it on a train.
• Keeping source names in a shared Doc, where Google can read them.
• Dictating in another language and expecting voice commands to work.
• Blaming Docs for lag on a Mac without testing with a long draft first.

The one typing lag report I found is from an iPad app. The user saw lag after about five minutes in a document. An update made it worse, and the thread closed with no confirmed fix. I found no confirmed Mac report.

Test your own setup. Paste in a long draft, type for a few minutes, and watch the cursor. If lag shows up, check the browser version and try a fresh Chrome profile.

How Lazur helps while you stay in the doc

Lazur is a voice assistant for the Mac that lives in the notch. Hold ⌥ ⌘ to ask about anything on screen, and Lazur answers out loud. Ask where a control is, and Lazur draws a circle and a label around it.

Ask how to do something, and Lazur guides you one click at a time. It waits for each click. Lazur does not click buttons, edit files or operate other apps for you.

Lazur is not a plugin or add-in for Google Docs. It runs as its own app on your Mac. Research jobs run in Lazur's own Chrome tabs, through the Lazur for Chrome extension, and come back with a summary and a report.

For the voice side of this, read the Google Docs on Mac page. For drafting habits, see the writers guide. Students can check the students guide. Lazur has a Pro trial with no credit card, and you can compare plans on the pricing page.

Your next steps

1. Open Google Docs in Chrome and press ⌘ / to see the shortcut list.
2. Press ⌘ ⌥ ⇧ X before your next editing round, and check the mode again.
3. Test offline on a short draft before you leave Wi-Fi.
4. Split any file you think is too big, and move source details out of the doc.
5. Hold ⌥ ⌘ and ask Lazur to walk you through the shortcuts you still forget.