Creating and Reviewing Documents in Google Docs

Prepare a readable agenda, use structured headings and practise reviewing changes without losing the original.

Part 5 of 10 | Email and Google Workspace for Beginners

Learning goals

Create and format a short Google document, review a proposed edit and distinguish a current document from an exported copy. Use version information carefully and build a quality checklist based on the reader's needs. The result is the agenda for your fictional beginner training session.

Before you begin

Open the correct authorised account and use your restricted practice folder. The agenda should contain no real addresses or participant details. Plan a one-hour session with three learning activities and breaks or transitions as needed. Any timings are fictional planning choices, not a real event invitation.

Plan the content before formatting

Write the session purpose in one sentence: participants will practise an email draft, identify a safe sharing choice and review a short action list. Then outline the sections: purpose, preparation, activities and next steps. A reader should understand what to bring and what they will do without having to interpret decorative formatting.

Use short paragraphs for explanations and lists for parallel actions. Give each activity a name, estimated duration and expected result. For example, an email-review activity might end with an unsent message that has a clear subject and request. A specific output makes the agenda easier to teach and assess than a broad item such as learning computers.

Create and name the document

Open docs.google.com and create a blank document. Name it Practice_Training_Agenda before you add much content, then place it in the intended practice folder. Enter the planned text and inspect the saving status before closing. If the connection is interrupted, do not assume every recent change has already synchronised.

Use a title style for the document name and heading styles for main sections rather than making ordinary text large one line at a time. Keep body text readable and spacing consistent. Google Docs supports editing, formatting and undo or redo; use these controls to correct an accidental change while checking the result on the actual text.

Review for meaning and usability

Read the agenda from beginning to end as a first-time participant. Check that the total planned time matches the advertised session length. Confirm that a beginner knows the required device, whether an account is needed and that messages remain drafts. Remove unexplained abbreviations and instructions that require skills not yet taught.

Check headings and lists for consistency, but do not let appearance distract from facts. A neatly styled agenda with conflicting times is still wrong. If you add a link, describe its destination clearly and verify that it opens the intended official resource. Do not add images simply to fill space; use an image only when you have the right to use it and it helps the reader.

Practise feedback without overwriting everything

Use a comment to ask a specific question about selected text, such as whether an activity needs more time. A useful comment identifies the issue and the decision needed. Avoid tagging real people during practice, because notifications can be sent. Keep the comment within your own fictional project.

In Suggesting mode, proposed edits can be reviewed before acceptance. Check the mode indicator so you know whether you are directly editing or proposing a change. Make one small suggestion in the practice document, inspect it and accept or reject it deliberately. The exercise demonstrates a review process; it does not require another person to join the document.

Use history carefully

Version history can help inspect earlier changes where your access permits it. On a disposable practice copy, make a small edit, inspect the earlier version and compare the difference. Do not restore an older version of a real shared document merely to experiment, because that can change the current work for others.

Record what you observed and whether you actually tested restoration. History is useful evidence of changes, but it is not a substitute for an agreed review process or every kind of backup. Know which file is current and keep a clear record when a version has been approved for use.

Export and inspect the result

If the reader needs a fixed copy, use the document's download options to create a suitable format such as PDF. Give the exported copy a versioned name. Open it separately and check headings, line breaks, missing text and any page layout changes. An export is a separate file, so later edits to the Google Doc do not automatically update that downloaded copy.

Keep a delivery note that identifies the editable working document and the reviewed export. If an export cannot be opened or visually checked on your device, record that limitation rather than marking it complete. Do not publish or share the agenda publicly during this exercise.

Guided exercise

1. Plan a one-hour fictional session with named activities, durations and outputs. Check that the durations add up correctly.

2. Create Practice_Training_Agenda with a title and four structured sections. Save it in your restricted project folder.

3. Add one useful comment and one suggested wording change without tagging anyone. Review the suggestion deliberately.

4. Inspect version history on a disposable copy and record one observable difference. Keep the main agenda intact.

5. Export a fixed copy, open it and complete a checklist for content, timing, readability and layout. Record any unperformed check honestly.

Knowledge check

1. Why use heading styles rather than only enlarged text?

2. Is a suggestion automatically an accepted change?

3. Does a downloaded PDF update when the Google Doc changes?

Answer guide

1. They provide consistent structure and make the document easier to navigate.

2. No. It is a proposed edit for review.

3. No. It is a separate copy and needs to be exported again if required.

Completion standard

Submit the agenda, a correct timing check, evidence of a reviewed suggestion and a separately inspected export. Keep the main document intact during history practice. Mark any missing practical step clearly, and do not represent an unreviewed export as ready for distribution.

Sources and verification notes

How to use Google Docs. Checked 15 September 2026. Basic document creation, editing and collaboration guidance. This course uses the computer browser workflow.

Find changes in Google files. Checked 15 September 2026. Official version-history guidance. Use a disposable practice copy for restoration exercises.

Suggest edits in Google Docs. Checked 15 September 2026. Suggestion mode requires suitable access. Suggestions are proposed changes and must be reviewed.