Central Question
What if nothing changes on the record, but the business still needs communication at a specific time?
A Scheduled Custom Email is not simply a Notification with a clock attached. It is initiated by time rather than a record event and naturally communicates current state through reports.
Review Connection
The First Question Changes
Earlier lessons asked what just happened. Lesson 5A asks what Quickbase should communicate when a scheduled time arrives.
Event-Driven
Record Event
Evaluate Event / Change / State
Communicate Transition
Time-Driven
Time Arrives
Evaluate Current Information
Communicate Current State
Remember This
No Task has to be added, modified, or deleted for a Scheduled Custom Email to run
This is the conceptual break from Lessons 2–4.
Part 2
A Record Can Stay the Same While Its Meaning Changes
A Task may remain Open with a Due Date of September 10 while the calendar advances from September 7 to 8 to 9.
Stored State
Status = Open
Due Date = September 10
September 7
Stored values are unchanged, but the Task's relationship to today is different.
September 8
Stored values are unchanged, but the Task's relationship to today is different.
September 9
Stored values are unchanged, but the Task's relationship to today is different.
Remember This
Stored state can remain unchanged while current business significance changes over time
Reports, date criteria, and formula-derived values can reflect this current significance without requiring a record edit.
Part 3
Triggered Custom Email vs. Scheduled Custom Email
| Triggered Custom Email | Scheduled Custom Email |
|---|---|
| Initiated by a record event | Initiated by time |
| Has a triggering record | Has no triggering record |
| Naturally describes a transition | Naturally describes current state |
| Can answer “What changed?” | Better suited to “What is true now?” |
| Uses event/change/state conditions | Uses schedule + report data |
| Record context is central | Report context becomes central |
Remember This
A Scheduled Custom Email has no natural before → event → after record transition
That is why its architecture feels report-centric rather than record-centric.
Part 4
A Schedule Provides Temporal Initiation, Not Temporal Memory
“Every Friday, show me what changed” immediately raises a second question: since when?
Remember This
The schedule tells Quickbase when to evaluate; it does not automatically establish a historical comparison boundary
Historical comparison requires explicit design for the period, records, and changes that matter.
Part 5
WHEN, WHAT, WHO, HOW
WHEN
Schedule
When should Quickbase evaluate?
WHAT
Report(s)
What current information matters?
WHO
Recipients
Who should receive the communication?
HOW
Custom Email
How should the information be presented?
Part 6
Reports Define the Data Question
Reports are not merely visual objects pasted into an email. They define the current-state question.
Open Tasks Report
Which Tasks are Open right now?
Due Soon Report
Which Tasks currently qualify as due soon?
Completed Tasks Report
Which Tasks are currently Complete?
Part 7
Multiple Reports Can Become One Scheduled Briefing
Observed in Our Lab
Multiple reports were inserted into one Scheduled Custom Email
Observed qb-report Elements
<qb-report
data-table-id="bwa4dgkvc"
report-id="1"
show-title="true">
</qb-report>
<qb-report
data-table-id="bwa4dgkvc"
report-id="2"
show-title="true">
</qb-report>Requires Attention
[Report]
Due This Week
[Report]
Completed Work
[Report]
Remember This
The communication product can be the briefing, not the individual report
This becomes the key contrast with Report Subscriptions in Lesson 5B.
Parts 8–9
Empty Reports Are Still Information
Observed in Our Lab
An empty embedded report rendered its title, columns, and a visible 0
Tasks Requiring Attention
The recipient gets positive evidence that the report evaluated and returned zero matching records.
Exception Communication
“Only bother me when something needs attention.”
Suppressing an empty result may be appropriate.
Status Assurance
“Every Monday I need confirmation that the review occurred.”
Sending the empty report is more appropriate.
Remember This
Silence is ambiguous
No email does not prove that zero records matched. It can also mean delivery failed, permissions blocked delivery, the report or automation changed, or another configuration problem occurred.
Parts 10–11
Permission Checking Still Matters
Observed in Our Lab
An unauthorized recipient produced an administrator delivery error
With Check recipient permissions enabled, a test recipient lacking access caused Quickbase to report that the Scheduled Task Status Review could not be sent because access to the app or one of its tables was unavailable.
The message used “You don't have access,” even though the administrator receiving the error did have access. The controlled test strongly indicates the unauthorized recipient caused the failure.
Remember This
Troubleshooting may require reasoning from configuration, not reading the error message literally
This also reinforces why missing email cannot safely be interpreted as proof of an empty result.
Check recipient permissions
Recipient authorization is evaluated against the underlying information.
Ignore recipient permissions
Review Lesson 4 first. This is a data-governance decision, not merely a delivery preference.
Part 12
The UTC Trap: When 8:00 AM Doesn't Mean 8:00 AM
Business Time
Monday 8:00 AM Central
Quickbase Schedule
Corresponding UTC time
Daylight-saving changes can alter that relationship. A technically correct UTC schedule can still be operationally wrong for the business if the local conversion is misunderstood.
Parts 13–14
Custom Email Source Is Not a Formula Engine
Observed in Our Lab
Formula-like text rendered literally in the received email
Formula Test
Today()
[Task Name]
If(1=1,"FORMULA EXECUTED","FORMULA FAILED")None of those expressions were evaluated in the Scheduled Custom Email body.
Remember This
The email body is a presentation context, not an ordinary Quickbase Formula evaluation context
Put reusable business meaning in the data/report layer and let the communication layer present it.
Mental Model
Where formula logic belongs
Formula / Table Logic
Report
Scheduled Custom Email
Part 15
Strengths and Boundaries
Strengths
- Runs without a record mutation.
- Communicates current report state.
- Combines multiple reports into one briefing.
- Adds explanatory content around reports.
- Can visibly communicate an empty report.
- Supports explicit or supported dynamic recipients.
- Preserves recipient-permission checks.
Boundaries / Limitations
- No triggering-record transition.
- No automatic historical comparison boundary.
- No formula execution inside the email body in our test.
- UTC scheduling requires local-time translation.
- Missing email does not prove zero qualifying records.
Part 16
Requirement Decomposition
“Every Monday morning, send managers a summary of the Tasks they need to worry about this week.”
| Business phrase | Automation concern |
|---|---|
| Every Monday morning | WHEN |
| Tasks they need to worry about | WHAT |
| Managers | WHO |
| Summary | HOW |
Remember This
Clarify vague business language before configuring Quickbase
“Need to worry about” might mean Status is not Complete AND Due Date is within seven days—or something else entirely.
Parts 17–18
Design Scenarios
Scenario A — Exception Communication
“Only bother me when something needs attention.”
Empty report may justify suppressing the email, but silence remains operationally ambiguous.
Scenario B — Status Assurance
“Every Monday I need confirmation that the review occurred.”
Send even when the report is empty; the embedded report can visibly show 0.
Weekly Leadership Briefing
Outstanding Tasks
[Report]
Due This Week
[Report]
Completed Work
[Report]
Scheduled Custom Email fits because the unit of communication is a composed multi-report briefing.
Part 19
Evidence Board
DOCUMENTED
Quickbase Help
- Custom Emails can use recurring schedules.
- Recurrence can be Daily, Weekly, Monthly, or Yearly.
- Scheduled emails operate according to UTC.
- Scheduled emails can include the Report element.
- Empty-report send behavior can be configured.
OBSERVED
Our Laboratory
- Recurring schedule removed record-event controls.
- Multiple reports were inserted into one email.
- Each report produced a separate qb-report element.
- Populated reports rendered current Tasks data.
- Empty report rendered its structure and 0.
- Formula syntax rendered literally.
- Permission checking could prevent delivery.
- UTC misunderstanding caused an apparent schedule failure.
INFERRED
Working Architectural Model
Time initiates the process, reports define the current information scope, recipient rules determine who may receive it, and Custom Email determines presentation.
The permission failure is best explained by the deliberately unauthorized recipient, despite ambiguous admin-facing wording.
Part 20
Final Mental Model
Triggered Communication
Event
What Changed?
Does This Record Qualify?
Who Should Receive It?
Communicate the Transition
Scheduled Communication
Time
What Current Information Matters?
Which Reports Represent It?
Who Should Receive It?
Communicate the Current State
Lesson Outcome
What the Student Should Be Able to Reason About
Given a requirement such as “Every Friday morning send management the information they need about current Tasks,” the student should reason about WHEN it should run, WHAT reports define the information, WHO may receive it, HOW the communication should be assembled, and what operational limitations matter.
Next: Lesson 5B
Report Subscriptions
Scheduled Custom Email can already distribute one or more reports on a recurring schedule. So why does Quickbase also have Report Subscriptions?