Completing an Email and Workspace Project

Bring the course tools together in one consistent practice package and check content, permissions and readiness before real use.

Part 10 of 10 | Email and Google Workspace for Beginners

Learning goals

Assemble a complete fictional training-session project using the email and Google app skills developed in the course. Reconcile dates, titles, figures and file versions across all materials. Demonstrate a deliberate final review and prepare a realistic plan for improving any skill that remains untested.

Before you begin

Gather your practice email, Drive folder, agenda, register, slide deck, self-only event and unpublished feedback form. Keep the same fictional session throughout. No real invitation, sharing notification, form publication or customer contact is required. This assessment checks your workflow without turning a classroom exercise into an external communication.

Establish the project brief

Write a one-page brief stating the purpose, intended beginner audience and one-hour duration. Record the practice date and explicit time zone chosen in Part 8. Use the same session title everywhere. List the three learning activities and the result expected from each, such as a reviewed email draft or a correct access decision.

Identify assumptions and untested steps. For example, your practice account may support Calendar but not a feature demonstrated in an official guide. Record the limitation rather than claiming the feature was used. A successful project can include a clear unresolved item; it should not include a false statement that a test passed.

Check the files as a connected set

Open the agenda and presentation side by side if practical. Compare activity names, durations and next steps. Then check the register: Group A has 12 planned and 9 confirmed, Group B has 8 and 6, and Group C has 10 and 10. The totals are 30 planned, 25 confirmed and 5 remaining. Label the figures as fictional throughout.

Confirm that the formula test from Part 6 has been reversed and that no temporary value remains. Check the downloaded agenda and slide exports against their editable versions. A correct working document does not make an old export current. Rename obsolete practice exports clearly or separate them so you cannot accidentally attach the wrong version later.

Prepare a complete communication draft

Write an unsent project-review email with a meaningful subject and a specific request. Explain which files a reviewer would need and why. Keep real recipient fields empty and describe intended roles in your project notes. Decide whether the future reviewer needs an attachment, a restricted working-file link or both for different purposes.

Apply the final review checklist from Part 2. Inspect the sender account, intended recipients, body, dates, file versions and requested action. If a link is present, record the planned access role and whether recipient access has actually been tested. Do not describe an owner-only check as proof that a reviewer can open the file.

Audit the project's access plan

Review the Drive folder and file permissions you can inspect. The practice project should remain restricted and should contain no real participant information. Your written plan should distinguish an agenda commenter, a deck editor and an information-only viewer. Check that no whole-folder share is being used when a specific file would meet the need.

Review the feedback form separately. It remains unpublished, collects no real responses and has a clear plan for responder access. Keep its editing role distinct from its respondent role. Check that the fictional response analysis is labelled and totals five answers, with Drive selected three times. A form preview is not proof of published availability.

Rehearse the event without inviting people

Reopen the self-only calendar event and compare its date, duration and time zone with the brief. Rehearse the four-slide presentation locally. If you tested a Meet room alone, record the controls you actually checked; if you did not, mark that step as untested. Do not add attendees just to make the project look complete.

Write a fallback plan for a lost connection. Identify the already reviewed local materials you could use and the approved communication route you would confirm for a real session. Avoid promising that everyone can join by telephone, view a recording or access a paid feature unless those arrangements have been independently established.

Record evidence and resolve mistakes

Create a final checklist with an evidence column and a status column. Useful evidence includes an opened file, a checked formula result, a saved setting you inspected or a clearly labelled written plan. “Looks fine” is too vague to explain what was checked. Record the specific fact, such as the exported agenda containing all three activities.

Correct contradictions before signing off. If the email says 90 minutes while the event says one hour, decide which is approved in the fictional brief and update every dependent item. If a private file has broad access unexpectedly, investigate and correct only the practice item you control. Never alter unrelated work to complete this assessment.

Plan continued practice

Choose three skills to repeat over the next two weeks. A useful plan might include writing two clearer drafts, rebuilding the register from a blank sheet and reviewing the form settings again using official help. Give each action a date and a measurable result. Keep unresolved account or administrator questions separate from ordinary skills practice.

When you later use these tools for real work, check the current interface and account conditions, follow applicable organisational requirements and authorise each external communication deliberately. Finishing the course demonstrates beginner practice, not that every advanced feature or real recipient has been tested.

Guided capstone exercise

1. Assemble the brief and all seven project items. Mark any unavailable feature or untested step clearly.

2. Reconcile the session title, date, duration, activities and register figures across the agenda, event, slides and email.

3. Inspect files, exports, formulas and permissions. Keep a specific evidence note for each completed check.

4. Rehearse locally, review the unpublished form and confirm that no real notifications or invitations were sent.

5. Correct all contradictions and finish with three scheduled practice actions and a list of unresolved real-world checks.

Knowledge check

1. What are the restored register totals?

2. Does an owner's successful link opening prove recipient access?

3. What should you record when a feature cannot be tested?

Answer guide

1. Thirty planned, twenty-five confirmed and five remaining seats, all fictional.

2. No. Recipient access requires a separate appropriate test.

3. The limitation and planned next step, with status marked untested.

Completion standard

Submit the connected project, evidence checklist and continued-practice plan. Pass five checks: consistent information, accurate calculations, readable reviewed outputs, deliberate access choices and honest test status. Correct every mismatch before completion. Keep emails unsent, events self-only and the form unpublished throughout the assessment.

Sources and verification notes

Original practice project combining the skills and official guidance in Parts 1 to 9. Use fictional information and verify current account controls before real sharing or communication.