In short
- For UK businesses training 10 or more people
- Around 16 people per workshop, with multiple sessions for larger groups
- Delivered on-site anywhere in the UK, or live online
- A scoping call confirms tools, licences, tasks and format
- Price depends on group size and format
About this course
Practical Google Gemini training for UK teams using Google Workspace. We show your people how to use Gemini inside Docs, Sheets, Gmail, Slides and Meet to draft faster, analyse data, summarise meetings and remove busywork — with real examples from your day-to-day.
See it in action
What a Google Gemini session actually looks like
Choose a tool and explore a sample task, from brief to draft to human review.
A consultancy turning discovery-call notes into a client workshop proposal.
Sample brief
Brief
Prompt — workshop proposal for Harlow & Finch
Written by the account lead
You are helping me draft a workshop proposal.
Reader: Head of Operations. Decision: approve a pilot.
Discovery call notes: 40-person ops team, monthly supplier reports take two days.
Sections: context, proposed sessions, what changes, next step.
Rules: no invented figures, flag every assumption, under 700 words.
Sample draft
AI-assisted draft
Draft proposal — Harlow & Finch
Generated from the brief above
1. Context
Your operations team of roughly 40 spends about two days a month assembling supplier reports from several sources.
2. Proposed sessions
Session A — drafting and summarising with agreed house rules.
Session B — the supplier report, worked end to end on your own template.
3. Assumptions
Assumption: attendees can sign in to Claude on your current plan.
Assumption: the report template can be shared with sample data removed.
Sample review
Human review
Review pass — before it leaves the building
Account lead's edits
"Two days a month" checked against the call notes — kept, wording softened to "around two days".
Assumption about licences moved to the top so it is not missed.
Session B renamed to match the client's own term for the report.
Removed a sentence implying a saving the team has not measured.
Signed off by the person who owns the relationship, not by the tool.
A cross-department Teams meeting turned into owners, actions and a follow-up email.
Sample brief
Brief
Meeting notes — warehouse handover review
Teams recording and chat notes
Tuesday, 45 minutes. Operations and Customer Service.
Night-shift handover sheet keeps arriving incomplete.
Priya to look at the template; Marcus unsure who owns the printer list.
Agreed: trial a shorter sheet from the start of next month.
Someone mentioned a customer complaint — detail not captured.
Sample draft
AI-assisted draft
Actions extracted by Copilot
Decisions separated from discussion
Decisions
Trial a shortened handover sheet from the 1st.
Actions
Priya — redraft the handover template — by Friday.
Marcus — confirm who maintains the printer list — by Wednesday.
Open questions
Which customer complaint was referred to? Not stated in the recording.
Sample review
Human review
Follow-up email — checked, then sent
Drafted in Outlook by the meeting chair
Subject: Handover review — decisions and actions
The due dates in the draft (Friday, Wednesday) were not in the meeting — they are assumptions, and were confirmed with Priya and Marcus before the email went out.
Owners confirmed with each person; anything unconfirmed stayed marked as proposed.
Open question left in the email rather than guessed at.
One "agreed" downgraded to "proposed" — the recording did not show agreement.
Prompt saved to the team library so the next chair reuses it.
A campaign brief becoming a customer email, then a fact and tone review.
Sample brief
Brief
Campaign brief — spring service reminder
Written by the marketing lead
Audience: existing customers, last service over 12 months ago.
Purpose: book a service slot online.
Tone: plain, warm, no hard sell, British spelling.
Must include: booking link, opening hours, cancellation terms.
No customer data pasted in. No discount claims — none approved.
Sample draft
AI-assisted draft
Email draft, version 1
Plus two alternative openings
Subject: Time for your annual service?
It's been a while since we last saw your vehicle. Booking takes a minute and slots are open through April.
Alt opening A: leads on the reminder.
Alt opening B: leads on the booking link.
Marked: "slots open through April" needs confirming with the workshop.
Sample review
Human review
Fact and tone review
Checked by the marketing lead
Availability confirmed with the workshop before the claim stayed in.
Cancellation terms corrected against the current policy page.
Opening B chosen — shorter, and the ask is visible on a phone.
Removed an implied guarantee about same-week slots.
Final wording approved by a person before scheduling.
Scattered project notes becoming a Workspace-style summary, then verified.
Sample brief
Brief
Project notes — office move, week 6
Google Docs bullets and a Meet summary
Fit-out contractor confirmed for the second week of June.
Desk count still under discussion — sheet says 62, facilities said 58.
IT cutover date not yet agreed.
Summary needed for Thursday's steering group. No supplier names outside the team.
Sample draft
AI-assisted draft
Draft summary in Docs
Structure agreed first: status, decisions needed, risks
Status
Fit-out is scheduled for the second week of June. Desk numbers are unresolved.
Decisions needed
Confirm the desk count (sheet: 62 / facilities: 58).
Agree an IT cutover date.
Conflict shown rather than averaged or silently resolved.
Sample review
Human review
Verification before sharing
Project manager's pass
Both desk figures checked against the sheet's latest tab.
Contractor dates confirmed with the email thread, not the summary.
Supplier name removed — the document goes wider than the team.
Structure saved as a template for next week's update.
Explore the curriculum
Pick a topic, see how it is taught
Four of the topics covered in Google Gemini training: pick one to see a sample exercise and what attendees take away.
Drafting in Google Docs
Sample exercise
Bullet notes and a meeting summary are turned into a structured update, with the structure agreed before drafting.
What attendees leave with
A reusable document structure saved as a template.
Questions in Sheets
Sample exercise
A summary is written that cites the sheet, and every figure is traced back before it is shared.
What attendees leave with
A short worked pattern for a recurring sheet summary.
Gmail and Meet in the working week
Sample exercise
A recap is produced from a Meet summary, then corrected against what was actually said.
What attendees leave with
A recap prompt the team can reuse after each meeting.
Verification before sharing
Sample exercise
A summary containing two conflicting figures is reviewed, and the team agrees how conflicts should be shown.
What attendees leave with
An agreed rule for handling conflicting or missing information.
What you'll learn
- How Gemini works inside Google Workspace and the standalone Gemini app
- Drafting, rewriting and summarising in Google Docs and Gmail
- Using Gemini in Sheets for analysis, formulas and clean-up
- Generating slides, images and speaker notes in Google Slides
- Capturing notes, actions and summaries in Google Meet
- Combining Gemini with Drive content responsibly across your team
How we deliver this training
Instructor-led workshop
A practical, hands-on session led by a Day Seven trainer. Run in-house for your team, or join an open workshop in Leeds. UK-based, jargon-free, and built around the work your team does.
Get a training proposalExample exercises we can scope for your team
We agree the exercises with you before the session, so they match the work your team does.
- A set of reusable prompts for the Workspace tasks your team repeats most, written so a colleague can follow the same brief and review step
- One end-to-end workflow worked through in Docs, Sheets or Gmail — for example a weekly report or a customer reply — reviewed by a person before it goes out
- A short checklist for checking Gemini output: what to verify, who signs it off, and what should never be pasted in
- A shared team prompt library with a simple naming convention
What we need from you beforehand
- A short scoping call to agree the tools your team uses, the tasks that matter and the format that fits your week.
- Confirmation that attendees can sign in to the tool on their team's current plan or licences before the day.
- Two or three real, non-sensitive examples per team — a typical document, report or email thread — so exercises use your own work.
- A named internal contact for room, kit and joining details, plus anything your IT or security team needs to approve first.
How to tell whether it worked
- Agree at scoping which two or three tasks the training should make faster or easier, so there is something concrete to look at afterwards.
- Compare the time taken and the quality of the output on one selected task before and after the session, so there is a performance measure alongside how people feel.
- Capture a simple confidence rating from attendees before and after the session on those same tasks.
- Ask managers a month later whether the agreed tasks are being done with the tool, and how often.
- Keep the team's shared prompt library as a visible sign of use — an empty library a month on is a useful signal in itself.
Our guide on measuring AI training ROI sets this out in more detail.
Who it's for
Frequently asked questions
Before you buy
If you are still building the business case, our guides cover what AI training costs in the UK, how to choose an AI training provider and how to measure the return on AI training.