Plan Your Workday with Claude

Use Claude and Google Workspace to build a sourced daily work plan.

Introduction

30 Second Summary

A workday can start with priorities scattered across messages, meetings, notes, or trackers. A polished plan can still miss the task that matters most.

In this project, you will use Claude with Google Workspace to turn fictional office information into a reviewed plan for tomorrow. You will compare an incomplete answer with a complete sourced plan before creating a daily brief in Google Docs plus an action tracker in Google Sheets.

What You'll Build

You will open a practical workday brief beside an action tracker, with every priority tied to fictional evidence you can inspect.

By the end of this project, you'll have:

Your incomplete morning plan finds the design blocker in Gmail. It finds the launch review in Google Calendar. The absent Google Drive tasks expose the plan's blind spot.
Your complete sourced brief shows ordered priorities. It maps the day into a timed schedule. It surfaces meeting preparation. It flags risks from all four fictional sources.
You can open two saved Google Drive files: the Office Launch Daily Brief plus the Office Launch Action Tracker.
Secret Mission: You will apply a last-minute fictional update to the existing brief and tracker without creating duplicate files.

Are there any prerequisites?

You need an existing Claude account plus a personal Google account. Step 1 covers the Google Chrome check on Linux before you create any fictional practice data.

Before We Start

Safe planning with Claude starts with fictional Office Launch information in your personal Google account. This checkpoint commits you to reviewing cited sources plus proposed actions before you trust or approve anything.

Prepare the Fictional Office Workspace

Claude can only be judged against sources you already know are correct. A controlled workspace lets you spot missing or invented details without exposing private workplace information.

Google Chrome keeps your Claude sign-in plus your personal Google sign-in in one browser profile. Keep Claude separate from the sources until the workspace is ready.

In this step, get ready to:

Confirm the shared browser profile for your Claude account plus your personal Google account.
Create fictional communication inputs in Gmail plus Google Calendar.
Create fictional planning inputs in Google Drive with Google Docs plus Google Sheets.

Check Chrome and both sign-ins

The browser profile keeps both accounts available during the project. First, confirm that Chrome is ready on your Linux computer.

Use your Linux application menu to open Google Chrome.

✔️ Chrome opens

Google Chrome is ready for the sign-in checks below.

ⓧ Chrome is missing

Google offers two Linux package formats.

Debian or Ubuntu use .deb packages. Fedora or openSUSE use .rpm packages.

Visit the official Google Chrome Linux setup page.
Select the package that matches your Linux distribution.
Open the downloaded package with your system software installer.
Select Install.

The administrator password prompt is expected during a system install.

Enter your administrator password.
Open Google Chrome after the installation finishes.

Chrome installation stuck?

Confirm that the package format matches your Linux distribution.
Download the package again from the official setup page if the installer cannot read it.

Help me install Google Chrome on Linux.

Enter claude.ai in the Chrome address bar.
Complete the Claude sign-in if an account screen appears.
Open a new Chrome tab.
Enter drive.google.com in the address bar.
Complete the sign-in with your personal Google account if prompted.
Confirm that Claude plus Google remain signed in within the same Chrome profile.

That is the first hurdle cleared. Both accounts are ready in one Chrome profile.

Claude still has no access to your Google content.

Create the Gmail and Calendar inputs

The first source pair covers communication plus time commitments. Keeping the content fictional lets you inspect later results against facts you wrote yourself.

Open Gmail in a new tab within the same Chrome profile.
Select Compose.
Enter Office Launch: Design blocker in the subject field.
Enter The homepage hero image still needs Maya's approval. Please follow up by 10:30 AM tomorrow. in the message body.
Leave the message unsent.
Select Drafts.
Open the draft named Office Launch: Design blocker.

You should see The homepage hero image still needs Maya's approval. Please follow up by 10:30 AM tomorrow. in the draft body.

Your first source is safely parked in Drafts without sending a message.

Open Google Calendar in a new tab.
Select Create.
Enter Office Launch Review as the event name.
Set the event date to tomorrow.

The event editor should now show Office Launch Review on tomorrow's date.

Set the start time to 2:00 PM.
Set the end time to 2:30 PM.

The event editor should now show a thirty-minute meeting starting at 2:00 PM.

Enter Review launch readiness, open blockers, and the final QA status. in the description field.
Select Save.

You should see Office Launch Review on tomorrow's calendar from 2:00 PM to 2:30 PM.

Your fictional workspace now has a blocker plus a meeting for Claude to find later.

Create the Drive sources and verify the workspace

Google Drive holds the remaining fictional sources.

Google Docs captures the meeting notes. Google Sheets stores the task status in rows.

Switch back to Google Drive.
Select New.
Select Google Docs.
Name the document Office Launch Meeting Notes.
Enter Legal approved the disclaimer. The FAQ must be updated before the launch review. The QA checklist must be finished before 1:00 PM. in the document.

You should see the three meeting-note facts inside Office Launch Meeting Notes.

Return to Google Drive.
Select New.
Select Google Sheets.
Name the spreadsheet Office Launch Task Tracker.
Enter Task, Owner, Status, plus Due across the first row.

The first row should now show four headers for describing each task.

Enter Homepage copy, Sam, In progress, plus Tomorrow 12:00 PM across the second row.
Enter QA checklist, You, Not started, plus Tomorrow 1:00 PM across the third row.

The spreadsheet should now show one active copy task plus one unstarted QA task.

Enter Analytics tags, Priya, Done, plus Tomorrow 9:00 AM across the fourth row.

Before you check, which four Office Launch items do you expect to find across the three Google apps?

Switch back to Gmail.
Select Drafts.
Open Office Launch: Design blocker.
Confirm that the draft contains the hero-image approval message plus the 10:30 AM tomorrow follow-up deadline.
Switch to Google Calendar.
Open Office Launch Review.
Confirm that the event runs tomorrow from 2:00 PM to 2:30 PM.
Confirm that the description says Review launch readiness, open blockers, and the final QA status.

The communication sources now match the fictional schedule you planned.

Switch back to Google Drive.
Open Office Launch Meeting Notes.
Confirm that the document includes the legal approval, FAQ update, plus 1:00 PM QA deadline.
Return to Google Drive.
Open Office Launch Task Tracker.
Confirm that the spreadsheet has the Task, Owner, Status, plus Due columns.
Confirm that the spreadsheet contains the Homepage copy, QA checklist, plus Analytics tags rows.
Return to Google Drive to confirm that both Office Launch file names appear together.

That is your controlled test workspace complete. Every future result can be checked against these known facts.

Your fictional sources are ready. Next, you will let Claude read only the message plus meeting sources to reveal what missing context does to a polished plan.

Build an Incomplete Morning Brief

Your fictional Office Launch workspace is ready across Gmail, Google Calendar, Google Docs, and Google Sheets.

Now you will use connectors to let Claude read only Gmail and Google Calendar. A plan based on two sources can look convincing while silently missing work stored in Google Drive.

In this step, get ready to:

Connect Gmail and Google Calendar to Claude.
Create a tomorrow work plan using only those two sources.
Check the plan for facts hidden in the unconnected sources.

Connect only Gmail and Google Calendar

Account authorization can feel broad. Claude mirrors your existing Google permissions for the connected account.

Keep the Workspace Fictional

Selecting Connect to Claude opens Google account authorization. You will use the personal account from earlier.

Keep this practice inside your personal Google account.
Leave confidential workplace data out of every connector search.

Switch back to the Claude tab from earlier.
Select Customize in Claude's left navigation.

You should see Connectors as one of the available customization options.

Select Connectors.
Select Discover.

The connector directory includes a Search connectors field for finding each service.

Enter Gmail in the Search connectors field.
Select Connect to Claude for Gmail.

Google opens an authorization window for account selection. It also shows the access request you are approving.

Choose the personal Google account from earlier.
Approve the requested access.

Gmail is now available when a Claude request needs to read your fictional draft.

Return to the connector directory.
Enter Google Calendar in the Search connectors field.

You should see the Google Calendar connector in the search results.

Select Connect to Claude for Google Calendar.
Choose the same personal Google account.
Approve the requested access.

Google Calendar can now provide the fictional event when Claude needs it.

Return to the Connectors page.
Find Gmail and Google Calendar under Your connectors.
Confirm that each connector displays Connected.
Confirm that Google Drive, Google Docs, and Google Sheets are not connected.

You have kept the test clean by connecting only Gmail and Google Calendar.

Connector Not Showing Connected?

Confirm that the authorization window used your personal Google account.
Complete any unfinished Google authorization request.
Return to Your connectors to check the status again.

Help me troubleshoot this connector setup.

Ask for the limited plan

Your source selection controls the context Claude can use. Prompt specificity gives this test a clear boundary.

Start a new Claude conversation.

You should see a blank conversation with no previous Office Launch messages.

Select + beside the message box.
Select Connectors.

The conversation now shows controls for choosing which connected sources Claude can use.

Turn on Gmail.
Turn on Google Calendar.
Confirm that Google Drive, Google Docs, and Google Sheets remain off.
Add the planning request by pasting this prompt into the message box:

Using only my Gmail and Google Calendar, make a short work plan for tomorrow. List my meetings, urgent messages, and three priorities. Name the source behind each item.

How This Prompt Sets the Test

The opening sentence limits Claude to the two enabled sources.
The requested categories make the plan easy to inspect.
Source names let you trace each factual item back to its origin.

Before you send it, consider whether two sources contain enough evidence for a complete Office Launch plan.

Send the message.
Select Allow once if Claude asks before reading a connected source.

Claude produces a short plan based on the Gmail draft and Calendar event it can access.

Claude Cannot Read a Source?

Confirm that the Gmail toggle is on for this conversation.
Confirm that the Google Calendar toggle is on for this conversation.
Select Allow once if Claude requests source approval again.

Help me restore access to the two connected sources.

Inspect the planned shortfall

Source checking means comparing Claude's answer with the information available across your original sources. This check reveals which facts the limited plan can prove.

Before you inspect the answer, consider which details Gmail and Google Calendar can prove on their own.

Locate the item sourced to Office Launch: Design blocker.
Confirm that the item mentions Maya's approval for the homepage hero image.
Confirm that the follow-up is due by 10:30 AM tomorrow.
Locate the Office Launch Review event.
Confirm that the review starts at 2:00 PM tomorrow.
Search the response for the FAQ update.
Search the response for the QA checklist deadline.

You should find the design-approval follow-up and the launch-review event in Claude's plan.

The response should not identify the FAQ update or the 1:00 PM QA checklist deadline. Those facts remain inside the unconnected Google Docs and Google Sheets sources.

Why the Shortfall Matters

Claude can use the sources available to the current conversation. Missing sources leave missing evidence.

A polished format does not prove full source coverage. Source checking exposes the gap before you trust the plan.

You caught the hidden context gap before trusting the plan. Next up, you will add the missing sources and turn this limited answer into a complete work brief.

Connect the Missing Context and Create the Plan

Your first plan from Claude found the design blocker. It also found the launch review.

The polished result still missed the FAQ update. It also missed the QA deadline.

Those facts live in Google Drive. Google Docs contains the meeting notes.

Google Sheets contains the task tracker. You will add these sources before rebuilding the plan.

In this step, get ready to:

Connect the missing Google sources to Claude.
Rebuild the Office Launch plan with all four fictional sources.
Create two Google files from the reviewed plan.

Connect the missing Google sources

A connector lets Claude use information from a linked account when your request needs it. Each connection should use the personal Google account that contains your fictional workspace.

Connecting a source authorizes Claude to use information from that account. You can review the requested access before approving each connection.

Return to the Claude tab in Chrome.
Select Customize.
Select Connectors.
Select Discover.
Find Google Drive with Search connectors.
Select Connect to Claude for Google Drive.
Approve access with your personal Google account.
Confirm that Google Drive appears under Your connectors with the status Connected.

Good progress. Claude can now reach the Drive account that holds your fictional files.

Find Google Docs with Search connectors.
Select Connect to Claude for Google Docs.
Approve access with your personal Google account.
Confirm that Google Docs shows Connected.
Find Google Sheets with Search connectors.
Select Connect to Claude for Google Sheets.
Approve access with your personal Google account.
Confirm that Google Sheets shows Connected.

Your original Gmail connector should remain connected. Your Google Calendar connector should also remain connected.

Choose the tab that matches your connector result.

✔️ All three sources connected

The missing sources are ready. Enable them in the conversation that already contains your limited plan.

Switch back to the existing Office Launch planning conversation.
Select +.
Select Connectors.
Turn on Google Drive.
Turn on Google Docs.
Turn on Google Sheets.
Confirm that Gmail remains on.
Confirm that Google Calendar remains on.

The conversation now has access to all five Google sources. That closes the source gap that limited your first plan.

ⓧ A Drive source is unavailable

A temporarily unavailable connector does not block the review workflow. You can provide the same fictional evidence directly in the existing conversation.

Switch back to the existing Office Launch planning conversation.
Select +.
Select Connectors.
Turn on each available Drive-based connector.
Confirm that Gmail remains on.
Confirm that Google Calendar remains on.
Add the missing fictional evidence by pasting the content below:

Office Launch Meeting Notes
Legal approved the disclaimer. The FAQ must be updated before the launch review. The QA checklist must be finished before 1:00 PM.

Office Launch Task Tracker
Task | Owner | Status | Due
Homepage copy | Sam | In progress | Tomorrow 12:00 PM
QA checklist | You | Not started | Tomorrow 1:00 PM
Analytics tags | Priya | Done | Tomorrow 9:00 AM

Why keep the source labels?

The headings preserve the origin of each fact.
The table preserves each task's owner.
The table also preserves each task's status.
The final column preserves each deadline.

Send the labeled source information.
Confirm that both source names appear in the conversation.

Good recovery. The conversation now contains the same fictional evidence that the unavailable connector would have supplied.

Missing a source after pasting?

Paste the missing source again under its original heading. Keep every tracker value separated by a vertical bar.

Ask for help if the labels or rows are unclear: Help me format the fictional Office Launch sources for Claude.

Build and check the complete brief

Multi-source context gives Claude the evidence stored across several places. Requiring a source name for every factual item makes the result easier to check.

Add the complete planning request by pasting this prompt into the existing conversation:

Rebuild tomorrow's Office Launch plan using Gmail, Google Calendar, Office Launch Meeting Notes, and Office Launch Task Tracker. Include: three ordered priorities, a timed schedule, preparation needed before the 2:00 PM review, blockers or risks, and a source name for every factual item. Do not invent missing details.

Why this prompt works

The request names every source Claude should use.
The requested structure turns the facts into a timed work plan.
The source requirement makes each factual item traceable.
The final instruction prevents guesses from entering the plan.

Before you send the request, which Drive-based facts do you expect to appear this time?

Send the planning request.
Select Allow once if Claude asks to read a connected source.

Claude should now produce a fuller plan with traceable facts. Check the response against the fictional workspace before creating any files.

Check for the hero-image approval follow-up by 10:30 AM tomorrow.
Check for Sam's homepage-copy deadline at Tomorrow 12:00 PM.
Check for the FAQ update before the launch review.
Check for the QA checklist deadline before 1:00 PM.
Check for the completed analytics-tags task owned by Priya.
Check for the Office Launch Review from 2:00 PM to 2:30 PM.
Check that every factual item has a source name.
Check that the plan contains no added facts from outside the fictional sources.

Is a source fact missing or incorrect?

Reply with the missing fact from its fictional source.
Ask Claude to revise the plan before creating any files.
Compare the revision with the original source.

Ask for help if the revised plan still misses a fact: Help me diagnose the missing source fact.

Create the Google files

The reviewed plan still lives inside a conversation. A daily brief turns it into a workday reference.

An action tracker turns the unfinished work into rows you can update. Both files keep the source trail visible.

Add the file-creation request by pasting this prompt into the same conversation:

Using the reviewed plan, create a Google doc named Office Launch Daily Brief with sections for priorities, schedule, meeting preparation, risks, and sources. Also create a Google sheet named Office Launch Action Tracker with columns Task, Owner, Status, Deadline, Next action, and Source. Use the existing fictional facts only.

What will this request create?

The daily brief organizes the reviewed plan into sections for the workday.
The action tracker gives each task a status.
The action tracker also gives each task a next action.
The final sentence limits both files to facts you already checked.

This is the point where Claude can write files to Google Drive. You stay in control because every proposed action waits for your approval.

Before you send the request, where do you expect the FAQ update plus QA deadline to appear in each file?

Send the file-creation request.
Review the first proposed action from Claude.
Check the proposed file name.
Check the requested change.
Select Allow once only when the proposal matches your instruction.
Repeat the review for the second proposed action.

Claude should now show one file card for the daily brief. It should also show one file card for the action tracker.

Before you inspect the files, which source facts should prove that the context gap is closed?

Open the Office Launch Daily Brief file card in Claude.
Select Open in Google if you want to inspect the document in a full browser tab.
Compare the daily brief with all four fictional sources.
Return to the existing planning conversation.
Open the Office Launch Action Tracker file card in Claude.
Compare the action tracker with the reviewed plan.

What should you see?

The daily brief contains priorities plus a timed schedule. It also contains meeting preparation plus risks.

The daily brief includes the hero-image approval follow-up by 10:30 AM tomorrow.
The daily brief includes Sam's homepage-copy deadline at 12:00 PM tomorrow.
The daily brief includes the FAQ update before the launch review.
The daily brief includes the QA checklist deadline before 1:00 PM.
The daily brief includes Priya's completed analytics-tags task at 9:00 AM.
The daily brief includes the Office Launch Review from 2:00 PM to 2:30 PM.
The action tracker contains the columns Task, Owner, Status, Deadline, Next action, and Source.
The action tracker includes the unfinished homepage copy, FAQ update, and QA checklist tasks.
The action tracker includes the completed analytics-tags task.

Do the generated files need a correction?

Return to the same Claude conversation.
Name the incorrect fact or missing section.
Ask Claude to update the existing file.
Review the proposed edit before selecting Allow once.

Ask for help if the correction still does not match the source: Help me correct the generated Office Launch file.

That closes the context gap. Your verified daily brief plus action tracker now live in Google Drive.

Secret mission

Process a Last-Minute Update

A last-minute update changes the Office Launch priorities after your files are complete. Update the existing daily brief and action tracker while preserving one reviewed source trail with no duplicate files.

Clean Up Your Resources

This practice workspace costs $0 on Claude Free, subject to usage limits. Choose whether to keep it available, pause connector use, or remove the fictional items and disconnect Claude.

Resources you used:

Two unsent Gmail drafts named Office Launch: Design blocker and Office Launch: Copy approved.
One Google Calendar event named Office Launch Review.
Two Google Docs files in Google Drive named Office Launch Meeting Notes and Office Launch Daily Brief.
Two Google Sheets files named Office Launch Task Tracker and Office Launch Action Tracker.
Five Google connectors authorized in Claude for Gmail, Google Calendar, Google Drive, Google Docs, and Google Sheets.

Keep everything running

No action is required. Choose this option if you want to continue practicing with the fictional Office Launch workspace.

Keep the two unsent drafts available for future planning exercises.
Retain the Office Launch Review event in Google Calendar.
Leave all four Office Launch files in Google Drive.
Leave all five Google connectors connected in Claude.
Return to the existing Office Launch conversation whenever you want to continue.

Pause - I'll come back to this later

Pause connector use in the existing conversation while keeping every fictional item ready for your return.

Return to the existing Office Launch conversation in Claude.
Select +.
Select Connectors.
Turn off Gmail.
Turn off Google Calendar.
Turn off Google Drive.
Turn off Google Docs.
Turn off Google Sheets.

The conversation stops using the five connectors. Your Google sign-in remains active.

Delete - I don't want to use this again

Remove the fictional items from active use. Disconnect Claude from the five Google connectors.

Deleted Drafts Cannot Be Recovered

Deleting the drafts can feel drastic. Gmail cannot recover a deleted draft from Trash.

Delete the Gmail Drafts

Select Drafts in Gmail.
Open the Office Launch: Design blocker draft.
Select Delete draft.
Return to Drafts.
Open the Office Launch: Copy approved draft.
Select Delete draft.

Delete the Calendar Event

Open Office Launch Review in Google Calendar.
Select Delete event.

Move the Google Docs Files to Trash

Find Office Launch Meeting Notes using Google Drive search.
Right-click Office Launch Meeting Notes.
Select Move to Trash.
Find Office Launch Daily Brief using Google Drive search.
Right-click Office Launch Daily Brief.
Select Move to Trash.

Move the Google Sheets Files to Trash

Find Office Launch Task Tracker using Google Drive search.
Right-click Office Launch Task Tracker.
Select Move to Trash.
Find Office Launch Action Tracker using Google Drive search.
Right-click Office Launch Action Tracker.
Select Move to Trash.

Open Connector Settings

Return to Claude.
Select Customize.
Select Connectors.

Disconnect Gmail and Google Calendar

Open Gmail under Your connectors.
Select Disconnect.
Open Google Calendar under Your connectors.
Select Disconnect.

Disconnect Google Drive and Google Docs

Open Google Drive under Your connectors.
Select Disconnect.
Open Google Docs under Your connectors.
Select Disconnect.

Disconnect Google Sheets

Open Google Sheets under Your connectors.
Select Disconnect.

The drafts and event are removed. The four files now sit in Google Drive Trash.

Cleanup complete. Claude is disconnected from all five Google connectors.

Nice Work!

You pulled it off! You used Claude with Google Workspace to turn scattered fictional office information into a reviewed daily brief plus an action tracker. Your finished workflow gives you a repeatable way to review changing information before Claude updates your files.

You've learned how to:

Created a safe fictional workspace across Gmail, Google Calendar, Google Drive, Google Docs, plus Google Sheets.
Proved the missing-context risk by comparing a limited plan with a complete plan grounded in every sample source.
Turned the reviewed plan into Office Launch Daily Brief plus Office Launch Action Tracker. Controlled each file action with Allow once before treating the outputs as complete.
Secret Mission: Updated both existing outputs from the Office Launch: Copy approved draft. Preserved one daily brief plus one action tracker in Drive.

Ready to quiz yourself?