Session 2: Calendar & Forms
A calendar that reminds you before things go wrong, and forms that collect information into a spreadsheet automatically — the two tools that remove the most repeated manual effort.
Learning objectives
By the end of this session you will be able to do each of these without prompting.
- Use Google Calendar as a system rather than a place to occasionally write dates
- Set reminders and notifications that actually change your behaviour
- Build forms that collect clean, usable responses
- Understand the forms-to-sheets connection and why it matters
- Use both together to replace manual chasing and manual recording
The taught content
A calendar you do not trust is a calendar you do not use
Most people's relationship with a calendar is that they write important dates in it and then forget to look. The reason is not laziness; it is that the calendar does not do anything unless you open it. A date in a calendar is a note, not a commitment — until it interrupts you at the right moment, which is what a reminder is for.
So the shift is from recording to being reminded. Every event gets a notification set deliberately: a meeting needs fifteen minutes, a deadline needs a day or more, a flight needs several days. The default is usually ten minutes for everything, which is useless for a deadline and too noisy for a meeting. Set the reminder to match the lead time you actually need to act, not a single default applied to all of life.
Then the habit that makes it stick: if it has a time, it goes in the calendar, immediately, at the moment you agree it. Not later, not on a scrap of paper, not in a message you intend to act on. The gap between agreeing something and recording it is where everything gets lost, and closing that gap to zero is the single highest-value change in this session.
Scheduling and reminders: reducing the back-and-forth to nothing
A large share of scheduling effort is the exchange — 'are you free Tuesday?', 'not Tuesday, how about Thursday?', 'Thursday works, what time?' — which costs several messages and often a day. The tools that collapse this are worth learning properly because they compound: every meeting arranged this way saves ten minutes on both sides.
Appointment schedules let you publish available slots and let people book one directly, which removes the exchange entirely for anything repetitive — client consultations, student meetings, interviews. Shared calendars let a small team see each other's availability without asking, which is the difference between a team that coordinates and one that collides. And event invitations carry the time, the location or link, and the RSVP, so the details live in one place rather than across a thread of messages.
Two supporting habits matter more than they sound. Put the link or location in the event, because 'we agreed to meet' without the address generates a phone call twenty minutes beforehand. And schedule the preparation, not just the meeting — a presentation at 2pm needs a block at 10am, and if that block is not in the calendar it will be given to something else.
Forms: the tool that stops you retyping other people's information
A form collects structured information from people and puts it in one place automatically. The alternative it replaces is the one most people currently use: asking by WhatsApp, receiving twenty replies in twenty different formats, and typing them into a spreadsheet by hand. That transcription is pure waste, and it introduces errors at every keystroke.
The design principle is that a form's quality is determined by its questions, not by its appearance. Ask only what you need, because every unnecessary question loses responses. Make questions required where the answer is essential. Use multiple choice and dropdowns rather than free text wherever the answers come from a known set — a dropdown of states produces clean data, while a free-text state field produces 'Lagos', 'lagos', 'Lagos State' and 'LGS' and you will spend an hour cleaning it.
Then the two settings people miss. Collect email addresses if you need to contact people or prevent duplicate submissions — but be aware this makes responses identifiable, which carries a privacy obligation. And write a confirmation message that tells people what happens next, because a form that ends with a blank screen generates 'did it go through?' messages you did not need to receive.
Forms to Sheets: the connection that makes both tools worth using
Every form can write its responses directly into a spreadsheet, one row per submission, arriving automatically. This is the mechanism that makes forms genuinely transformative rather than merely convenient, and it is worth understanding precisely because it changes what becomes practical.
What it means concretely: responses become data you can work with immediately. Sort by date, filter by category, total an amount, count submissions per option, chart a trend — without a single keystroke of transcription. An attendance register, an order form, a survey, an event registration all become things you can analyse the moment the last person submits.
Two practical points follow. The sheet updates live, so you can watch responses arrive rather than polling people for updates. And you should design the form knowing the sheet is the destination — which is another argument for dropdowns over free text, because a spreadsheet full of inconsistent text cannot be sorted or counted reliably. Design for the analysis you want to do, not for the questions you find easy to ask.
Using them together: the automation most people never build
Calendar and forms solve the same underlying problem from two directions: they remove the manual step between something happening and you having a record of it. Used together they replace a surprising amount of everyday chasing, and the combinations are worth seeing because they are the ones you will actually build.
An event registration form collects names and numbers into a sheet, and the event itself lives in the calendar with reminders — so registration and attendance stop being two separate manual processes. A recurring deadline in the calendar with a long reminder replaces the habit of remembering to remember. A client intake form replaces the twenty-message conversation that currently precedes every new engagement, and it produces consistent information every time rather than whatever you happened to ask.
The honest framing is that none of this is technically impressive, and that is exactly why it works. The value is in the repetition: a form that saves ten minutes of transcription, used weekly, saves eight hours a year, and it never makes a typing error. Look for the tasks you do repeatedly and manually, and ask whether a form plus a calendar entry replaces them. That question, applied honestly, is what this course is really teaching.
Instructor demonstration
We build a calendar you can rely on and a form that collects real responses into a spreadsheet — using your own actual commitments and an actual thing you need to collect.
- 01
Open your calendar and look honestly at what is in it
Most people find a handful of events and a great many things they meant to add. That gap is the problem this session fixes, and seeing it plainly is what motivates the habit change.
- 02
Add every commitment you can think of, right now
Work deadlines, appointments, bills, family events, anything with a date. Do it in one sitting rather than promising to do it later, because 'later' is precisely where these things are lost.
- 03
Set reminders to match the lead time each event needs
Fifteen minutes for a meeting, a day for a deadline, several days for anything requiring preparation or travel. Do not accept a single default for everything — a ten-minute warning for a deadline is worthless.
- 04
Put the location or link inside every event
The address, the meeting link, the phone number. 'We agreed to meet' without the details generates a phone call twenty minutes beforehand, every single time.
- 05
Schedule the preparation, not just the event
A presentation at 2pm needs a working block at 10am. If the preparation is not in the calendar, something else will take that time and you will discover it at 1:45pm.
- 06
Make an event recurring where it repeats
A weekly meeting, a monthly bill, a quarterly review. Set it once with a repeat rule rather than re-entering it, and it will still be there in six months when you have forgotten to add it.
- 07
Create an appointment schedule for something repetitive
Client consultations, student meetings, or interviews. Publish your available slots so people book directly, removing the entire 'are you free Tuesday' exchange for anything that happens regularly.
- 08
Share a calendar with someone you coordinate with
A colleague, a partner, a teammate. Set it to show availability rather than details if the content is private. The point is coordinating without asking, which is what prevents collisions.
- 09
Send a real invitation with RSVP
Include time, location or link, and request a response. The details now live in one place and in both calendars, rather than across a message thread neither of you will re-read.
- 10
Open the calendar on your phone and confirm notifications fire
This is the test that matters. A calendar that does not interrupt you at the right moment on the device you carry is a calendar you will forget to open. Verify it actually notifies.
- 11
Create a form for something you genuinely need to collect
An attendance register, an order form, a survey, an event registration. Use a real need, because you will keep the result and the habit forms around something you actually use.
- 12
Use dropdowns and multiple choice wherever answers come from a set
A dropdown of Nigerian states rather than a free-text field. Free text gives you 'Lagos', 'lagos', 'Lagos State' and 'LGS'; a dropdown gives you one value you can count and sort.
- 13
Mark essential questions required and cut the rest
Every unnecessary question loses responses. Ask what you need and nothing more — a short form with a high completion rate beats a thorough form nobody finishes.
- 14
Decide deliberately whether to collect email addresses
It prevents duplicates and lets you reply, but it makes responses identifiable and therefore carries a privacy obligation under NDPA 2023. Choose based on need, not convenience.
- 15
Write a confirmation message that says what happens next
'Thank you — we will contact you within one working day.' A form that ends with a blank screen generates 'did it go through?' messages you did not need to receive.
- 16
Connect the form to a spreadsheet
Choose the responses destination so submissions write one row each. This is the step that converts a form from a collection box into a data source you can actually work with.
- 17
Submit three test responses with deliberately messy data
Use different options, leave optional fields blank, submit quickly. Watch the rows appear in the sheet and confirm the data arrives clean — which is the payoff for using dropdowns.
- 18
Sort, filter and total the responses in the sheet
Count submissions per option, total any amounts, filter by date. None of this required transcription, which is the entire argument for forms over asking people by message.
- 19
Share the form and collect real responses
Send the link to the people who actually need to respond. Real submissions arriving in the sheet without you typing anything is the moment this stops being an exercise.
- 20
Add the follow-up to your calendar
A reminder to review responses and act on them. A form nobody reviews is a form nobody benefits from, and the review is as much a scheduled task as any meeting.
Guided practice
Build a calendar you trust and a form that collects real data
Turn your calendar into something that interrupts you at the right time, and build a form that collects real responses into a spreadsheet you can analyse.
- 01Open your calendar and note honestly how much is missing from it.
- 02Add every commitment you can think of in one sitting, not later.
- 03Set each reminder to match the lead time that event actually needs.
- 04Put the location, link or phone number inside every event.
- 05Schedule preparation blocks for anything requiring work beforehand.
- 06Make repeating events recurring rather than re-entering them.
- 07Create an appointment schedule for something that happens regularly.
- 08Share a calendar with someone you coordinate with, at availability level if the content is private.
- 09Send a real invitation with RSVP and confirm the details appear in both calendars.
- 10Verify on your phone that notifications actually fire — this is the test that matters.
- 11Create a form for something you genuinely need to collect.
- 12Use dropdowns and multiple choice wherever answers come from a known set.
- 13Mark essential questions required and remove every unnecessary one.
- 14Decide deliberately whether to collect email addresses, weighing the privacy obligation.
- 15Write a confirmation message stating what happens next.
- 16Connect the form to a spreadsheet and submit three test responses with messy data.
- 17Sort, filter and total the responses without transcribing anything.
- 18Share the form and collect real responses from real people.
- 19Add a calendar reminder to review and act on the responses.
The standard we hold you to
A calendar populated with every current commitment in one sitting, reminders matched to each event's required lead time, locations and links inside events, preparation blocks scheduled, repeats set for recurring items, an appointment schedule published, a calendar shared at availability level, a real invitation sent with RSVP, and **notifications verified to fire on the phone**; a form built for a genuine need using dropdowns for known sets, essential questions required, a deliberate email-collection decision, and a confirmation message stating next steps — connected to a spreadsheet, tested with messy submissions, sorted and totalled without transcription, shared for real responses, with a calendar reminder set to act on them.
Common mistakes and how to fix them
Writing dates down and then never looking at the calendar
Fix: The calendar does nothing unless it interrupts you. Set reminders to match the lead time each event needs — a date without a notification is a note, not a commitment.
Accepting the default ten-minute reminder for everything
Fix: Ten minutes is useless for a deadline and too noisy for a meeting. Match the reminder to the time you actually need to act, per event.
Recording commitments later rather than at the moment you agree them
Fix: The gap between agreeing and recording is where everything is lost. Put it in the calendar immediately, on the device in your hand, before the conversation ends.
Using free-text fields for answers that come from a known set
Fix: A free-text state field produces 'Lagos', 'lagos', 'Lagos State' and 'LGS'. A dropdown produces one value you can sort and count. Design for the analysis you want to do.
Asking more questions than you need
Fix: Every unnecessary question loses responses. A short form with a high completion rate is worth more than a thorough form nobody finishes.
Collecting email addresses by default without considering it
Fix: It prevents duplicates and enables replies, but makes responses identifiable and carries obligations under NDPA 2023. Decide based on need rather than convenience.
Leaving the form's confirmation screen blank
Fix: Write what happens next. A blank ending generates 'did it go through?' messages, which is manual work you created by omitting one sentence.
Building a form and never reviewing the responses
Fix: Schedule the review in your calendar. A form nobody acts on benefits nobody, and the review is a task like any other meeting.
Expert notes
The habits that separate someone who can do this from someone who does it well.
- Record commitments at the moment you agree them, on the device in your hand. That single habit closes the gap where almost everything gets lost, and it costs nothing — the discipline is the whole skill.
- Use dropdowns for anything drawn from a known set. It feels like a small design choice and it determines whether your responses are analysable data or an hour of cleaning inconsistent text later.
- Verify that calendar notifications actually fire on your phone before trusting the system. A calendar that does not interrupt you on the device you carry is a calendar you will forget to open, however complete it is.
- Look for tasks you do repeatedly and manually, and ask whether a form plus a calendar entry replaces them. The value is in the repetition — ten minutes saved weekly is eight hours a year, with no typing errors.
Key terms
- Reminder lead time
- How far ahead of an event a notification fires. It should match the time you actually need to act, which differs for a meeting, a deadline and a flight.
- Appointment schedule
- A published set of available slots that people book directly, removing the back-and-forth exchange for anything that happens regularly.
- Shared calendar
- A calendar others can view, often at availability level only. It lets a small team coordinate without asking each other.
- Google Form
- A tool collecting structured responses into one place automatically, replacing asking by message and transcribing replies by hand.
- Response destination
- The spreadsheet a form writes into, one row per submission. This connection is what converts a form from a collection box into analysable data.
- Required question
- A form field that must be answered before submission. Used only where the answer is genuinely essential, since each one slightly reduces completion.
- Confirmation message
- The text shown after submission, ideally stating what happens next. Its absence generates avoidable follow-up messages.
- Structured response
- An answer constrained to a known set of options, such as a dropdown. It produces clean data that can be sorted and counted without cleaning.
Homework before the next session
Populate and trust your calendar
Add every current commitment with reminders matched to required lead time, locations inside events, and preparation blocks scheduled. Verify notifications fire on your phone, and record what you changed.
Build and share one real form
For something you genuinely need to collect, using dropdowns for known sets, required questions only where essential, and a confirmation message stating next steps. Collect at least five real responses.
Analyse the responses without transcribing
In the connected spreadsheet, sort, filter and total the responses. Write two sentences on what the data tells you that asking by message would not have.
Identify one repetitive manual task to automate
Name a task you do repeatedly by hand, describe the form and calendar entry that would replace it, and estimate the time saved per week. Then build it.
Assessment rubric
How this session is marked. The certificate for Digital Productivity is awarded on the deliverable, not on attendance.
| Criterion | Passing | Excellent |
|---|---|---|
| Calendar reliability | Events were added. | Every commitment recorded, reminders matched to lead time per event, locations and links inside events, preparation scheduled, and notifications verified on the phone. |
| Scheduling efficiency | Can create events and invitations. | Uses appointment schedules for repetitive meetings, shares calendars at availability level, and has eliminated at least one recurring back-and-forth exchange. |
| Form design | A form was created. | Dropdowns used for known sets, only essential questions required, deliberate email-collection decision, and a confirmation message stating what happens next. |
| Data handling | Responses were collected. | Form connected to a spreadsheet, tested with messy submissions, responses sorted filtered and totalled with no transcription, and real responses collected. |
| Automation thinking | Used both tools. | Can identify repetitive manual tasks and replace them with a form plus calendar entry, with the review of responses itself scheduled. |
Session questions
I always forget to look at my calendar. How do I fix that?+
Stop relying on looking. Set reminders to match the lead time each event needs and verify they fire on your phone. A calendar that interrupts you at the right moment does not require you to remember to check it.
Should I collect email addresses on my form?+
Only if you need to reply or prevent duplicates. It makes responses identifiable, which carries obligations under NDPA 2023, so decide based on need rather than collecting it because the option is there.
Why do my form responses look messy in the spreadsheet?+
Usually free-text fields where a dropdown would have constrained the answers. Change those questions to multiple choice or dropdowns — you will lose nothing and gain responses you can sort and count.
Can people edit their responses after submitting?+
Only if you enable it, and it requires collecting their email address. Most forms do not need it; if yours does, that is a further reason to collect emails deliberately rather than by default.
Is an appointment schedule worth setting up for occasional meetings?+
For occasional one-off meetings, no — an invitation is simpler. For anything recurring, such as consultations or interviews, yes: it removes the scheduling exchange entirely every single time.
This session is part of
Digital Productivity
2 weeks · 4 sessions · ₦30,000 · you leave with a working personal system