Central Question
Why are there so many communication features, and how do I decide which one belongs in a requirement?
The goal is not to memorize six feature definitions. The goal is to recognize the thing that initiates or defines the communication.
Part 1
Start With the Requirement, Not the Email Type
Do not begin with “Which email feature should I click?” Begin with a more architectural question: What fact causes this communication to matter?
| Business requirement begins with… | Start thinking about… | Why |
|---|---|---|
| When this record changes… | Notification / Triggered Custom Email | A record event is the important thing. |
| Every Monday at… | Scheduled Custom Email | A common calendar schedule is the important thing. |
| Send me this report… | Subscription | The report itself is the important product. |
| Three days before this record's Due Date… | Reminder | A date stored on each record provides the clock. |
| Quickbase needs to tell me something about the app/platform… | Alert | Quickbase itself is generating the communication. |
Remember This
Prefer the mechanism whose abstraction most closely matches the requirement
A feature is not better merely because it is newer or more configurable. Extra capability becomes extra machinery when the requirement never asked for it.
Parts 2–3
The Event-Driven Family
Notification and Triggered Custom Email belong to the same broad family because both begin with record activity. Their difference is not what starts the automation—it is how much control the communication requires after the event qualifies.
Notification — Something Happened to This Record
Notifications are event-oriented communication. Their natural question is “What just happened?”
Typical language includes “when Status becomes Complete,” “when Due Date changes,” or “when one of these fields changes and the resulting record satisfies these conditions.”
Review Lessons 2–3 for the event, watched-field, state, and Boolean mechanics.
Triggered Custom Email — Same Event, More Communication Control
The initiating concept remains a record event, but Custom Email becomes attractive when the requirement needs richer composition, recipient handling, permission policy, native change presentation, or other modern controls.
The choice between Notification and Triggered Custom Email happens only after the requirement has already been classified as event-driven.
Event-Driven Decision
A Record Event Matters
How Rich Must the Communication Be?
Notification
Simple event-driven communication
Triggered Custom Email
Richer communication and delivery control
Part 4
Scheduled Custom Email — The Clock Says Communicate
Scheduled Custom Email begins from a shared schedule. Its natural question is “What is true now that this scheduled time has arrived?”
WHEN
The common schedule.
WHAT
The reports that define current information.
WHO
The intended recipients.
HOW
The composed communication.
Remember This
Scheduled Custom Email is especially strong when the communication itself is the product
“Every Monday send leadership a briefing containing Open Tasks, Tasks Due Soon, and Completed Tasks” is stronger than simply saying “send this one report.” The email itself has become a composed operational briefing.
Part 5
Subscriptions — This Report Is the Product
Subscription is intentionally simpler. That simplicity is a strength when the requirement is fundamentally: “I want this report delivered periodically.”
Report
Delivery Schedule
Recipients
Delivery
If the business says “Every week send the Participant role the Open Tasks report,” an elaborate Scheduled Custom Email may introduce composition and maintenance work that the requirement never asked for.
Ongoing Lab Observation
Subscription PDF, CSV, and email/text-oriented delivery formats are still being observed. Lesson 6 deliberately does not pretend to know the final recipient experience until those scheduled tests are complete.
Parts 6–7
Reminders — This Record Is Approaching Its Date
Reminders are also time-based, but the time does not come from one shared schedule. Each record carries its own temporal reference.
Task A Due Date
↓
minus 3 days
↓
Reminder
Task B Due Date
↓
minus 3 days
↓
Reminder
Task C Due Date
↓
minus 3 days
↓
Reminder
Remember This
Where does the time come from?
If the time comes from one common calendar schedule, Scheduled Custom Email is a strong candidate. If the time comes from a date stored on each individual record, Reminder is the natural abstraction.
Common Schedule
“Every morning at 8:00, send management all Tasks due within three days.”
The dominant concern is the shared 8:00 AM schedule. Scheduled Custom Email plus a report is a strong candidate.
Record-Relative Schedule
“Remind each Assigned To user three days before their individual Task is due.”
The dominant concern is each Task's position relative to its own Due Date. Reminder expresses that requirement directly.
Part 8
Alerts — Quickbase Is Talking to You
Alerts are worth learning mostly so students do not confuse the terminology. In the Help material used for this lesson, Alerts describe Quickbase-generated messages such as invitations, transfer requests, and storage-limit warnings.
Your Application Logic Communicates
Notifications, Custom Emails, Subscriptions, and Reminders are builder-facing mechanisms used to express application communication requirements.
Quickbase Communicates About Quickbase
Alert terminology belongs to platform/application administration messages generated by Quickbase itself rather than another record-automation design choice.
Part 9
Recognize Reused Logic Instead of Relearning It
The appearance of ALL, ANY, conditions, and groups inside another Quickbase feature is not evidence of another logic language. It is evidence that the mental model from earlier lessons is transferring.
Criteria
Define the facts that matter.
Boolean Evaluation
Combine them with all/any and grouping.
Qualification
Determine whether the record or communication qualifies.
You are no longer learning “Reminder Boolean logic.” You are recognizing Quickbase Boolean logic appearing inside a Reminder.
Part 10
The Communication Decision Tree
Start with one question: What makes the communication necessary?
What Makes the Communication Necessary?
A Record Changed
Notification or Triggered Custom Email
A Common Time Arrived
Scheduled Custom Email
A Report Needs Distribution
Subscription
A Record Approaches Its Own Date
Reminder
Quickbase Reports a Platform / Administrative Condition
Alert
When two choices overlap, ask a second question:
What is the actual product being delivered?
“This report”
Subscription becomes attractive.
“This composed briefing with several views”
Scheduled Custom Email becomes attractive.
Part 11
These Boundaries Are Design Heuristics, Not Quickbase Laws
Quickbase features can overlap. A requirement may be technically implementable more than one way. The lesson therefore does not teach “Requirement X must always use Tool Y.”
Identify the dominant requirement and choose the mechanism that expresses it most naturally.
Architecture follows business meaning rather than product-menu familiarity. A simpler abstraction is often better precisely because it contains less machinery the requirement does not need.
Before the Quiz
Five Fast Classification Checks
Send me Open Tasks every Friday.
Likely Subscription — one report is the product.
Every Friday send leadership Open, overdue, and recently completed Tasks with explanatory text.
Likely Scheduled Custom Email — the composed briefing is the product.
Notify the Task owner immediately when Status becomes Complete.
Likely Notification or Triggered Custom Email — a record event initiates the requirement.
Notify Assigned To two days before each Task's Due Date.
Likely Reminder — each record supplies its own date-based clock.
Quickbase warns an administrator that the app is approaching a storage limit.
Alert — Quickbase itself is communicating an administrative/platform condition.
Remember This
The assessment is WHY, not WHERE
A student who can identify the correct menu but cannot explain why the requirement belongs to that communication model has not yet learned the design skill this lesson is trying to teach.
Lesson 6 Interactive Assessment
Choose the Tool — Then Understand Why
These questions avoid menu-click trivia. Each one asks you to identify the dominant requirement and choose the Quickbase communication abstraction that expresses it most naturally.
Progress
0/10
A supervisor needs an email immediately when a Task's Status becomes Complete.
Which communication family should you evaluate first?
Every Monday morning, leadership wants one email containing Open Tasks, Tasks Due Soon, and Completed Tasks with explanatory text between the sections.
Which mechanism most naturally expresses the requirement?
The Participant role simply needs the existing Open Tasks report delivered every Friday.
Which feature best matches the requirement with the least unnecessary machinery?
Each Task has its own Due Date. Assigned To should receive an email exactly three days before that particular Task is due.
Where does the important time reference come from?
Quickbase sends an administrator a warning that an application is approaching a platform storage limit.
How should Lesson 6 classify that message?
A builder sees all/any conditions and grouped criteria again while configuring a Reminder.
What is the strongest conceptual response?
Every morning at 8:00, management wants one list of all Tasks currently due within three days.
Which time model dominates this requirement?
An existing Notification already sends a simple, correct email when Status changes to Complete. A new builder notices that Custom Email is newer.
What is the best design conclusion?
One requirement says, 'Every Friday send leadership the Open Tasks report.' Another says, 'Every Friday send leadership a narrative briefing with Open Tasks, Overdue Tasks, and Recently Completed Tasks.'
What distinction should drive the tool choice?
A requirement could technically be implemented in more than one Quickbase email feature.
What rule should guide the final design decision?
Ready to evaluate your design reasoning?
Answer all 10 questions before submitting. The explanations use full sentences because the assessment is about architectural reasoning, not remembering a feature name.
Lesson 6 Final Principle
Requirement First. Tool Second.
Ask what makes the communication necessary: a record event, a common schedule, a report, a record-relative date, or a Quickbase administrative condition. Then choose the mechanism whose abstraction most naturally expresses that fact.
That is a transferable design skill. It is more valuable than memorizing where six different email options happen to live in the interface.