Below is a prompt to summarize the Reports: Report Manager: Gradebook: Gradebook Assignment Report. Do not include any courses that are not needed:

• Search for the term you want and only add those
• Remove: Study Halls, TAs, Online, Alternate

After you run the report, right click on it and do a Save As to the HTML file. It looks for a variety of things that are or might be errors. It produces a spreadsheet with two tabs. The first tab contains a summary of each course. The second tab only contains courses that do/may have errors. The third tab contains teacher email addresses. The fourth tab is a teacher by teacher executive summary. The fifth tab is for sending emails to teachers. (there is a prompt to send the emails below)

Generate spreadsheet

---

am attaching a Gradebook Assignment Report from our school grading system. It contains many courses, each of which may contain multiple gradebook categories and assignments.

Analyze the entire report and create an Excel workbook that:

1. audits the gradebook setup,
2. summarizes potential problems,
3. prepares structured teacher/email data,
4. creates complete teacher email drafts ready for another ChatGPT account to turn into Gmail drafts.

Do NOT send any emails.

Use the attached report as the authoritative source. If the report has an unexpected structure or ambiguity that materially affects the audit, ask me before making an assumption. Otherwise, process the entire report without stopping for confirmation.

Before generating the workbook, ask me this required question:

What exact signature line would you like included after “Thanks,” in every teacher email?

Do not assume, reconstruct, or omit the signature line. Wait for my answer, then use the signature line exactly as I provide it in every Email Body on Sheet 5. This question is required because the account that will send the messages cannot add my signature automatically.

==================================================

1. REPORT STRUCTURE

The hierarchy is:

Course → Category → Assignments

Do not confuse category headings with assignment rows.

For every course, identify:

• Course Code
• Course Title
• Teacher, in Last, First format
• Every category
• Category Weight
• Assignments contained in each category
• Assignment Due Dates
• Grading method internally, even though it will not be shown as an output column

Do NOT include Term or Grading Method as visible columns in the final workbook.

==================================================

2. ASSIGNMENT COUNT RULE

Count only assignments whose Due Date is TODAY OR EARLIER.

Use the actual current date when performing the analysis.

Example:

• If today is August 25, an assignment due August 25 counts.
• An assignment due August 26 does not count.

Use Due Date, not Assigned Date.

Future assignments do NOT:

• count toward ordinary assignment totals
• trigger the default Assignments-category warning
• trigger the Imported Assignments warning

However, future assignments MAY be examined for structural judgments such as determining whether a category may actually be an assignment.

For the special Canvas-generated category exemption described below, “contains no assignments with a Due Date” means that every assignment in that category has a blank/missing Due Date, or the category contains no assignments at all. A future Due Date still counts as a Due Date for purposes of that exemption, even though the assignment is excluded from ordinary assignment counts.

==================================================

3. AUDIT FLAGS AND ERRORS

Apply the following checks.

---

A. 0% CATEGORY

Normally flag a category weighted 0%:

Weight 0%: [category name]

However, do NOT flag a 0% category if its name clearly indicates intentional nongraded work.

Examples:

• Task
• Tasks
• Nongraded Tasks
• Ungraded
• Non-Graded
• No Credit
• No Credit Assignment
• Not Graded
• similar wording clearly indicating work that should not affect the grade

Use a conservative standard for this exemption.

An unusual category name alone is not enough to assume that a 0% weight is intentional.

There is also a specific Canvas-generated exception for the exact category names “Assignments” and “Imported Assignments.” If one of those categories:

• is weighted 0%, AND
• contains no assignments with a Due Date at all

then treat that category as harmless and generate NO error or warning from its existence, name, or 0% weight. This exemption applies even if the category contains assignment rows whose Due Date field is blank.

An exempt Canvas-generated “Assignments” or “Imported Assignments” category must also be ignored when checking for exact duplicate category names or possible near-duplicate category names. In other words, the exemption takes precedence over the 0% warning and the duplicate-category checks.

If the category contains even one assignment with any Due Date, including a future Due Date, this exemption does not apply and the normal audit rules apply.

---

B. LOW CATEGORY WEIGHT

Flag any category weighted greater than 0% and less than or equal to 10%:

Weight ≤ 10%: [category name]

Do not also place 0% categories under this flag.

---

C. HIGH CATEGORY WEIGHT

Flag any category weighted 81% or greater:

Weight ≥ 81%: [category name]

---

D. DEFAULT “ASSIGNMENTS” CATEGORY

If a category is literally named:

Assignments

and contains one or more assignments due TODAY OR EARLIER, flag it.

This is the grading system’s default category and may indicate that the teacher did not move assignments to their intended category.

Course-level summary example:

Default ‘Assignments’: 3 counted assignments

Do not flag it merely because the category exists.

If “Assignments” is weighted 0% and contains no assignments with a Due Date at all, apply the Canvas-generated category exemption above and generate no warning or error for that category. If it contains an assignment with any Due Date, including a future Due Date, the exemption does not apply.

---

E. “IMPORTED ASSIGNMENTS” CATEGORY

If a category is literally named:

Imported Assignments

and contains one or more assignments due TODAY OR EARLIER, flag it.

Example:

‘Imported Assignments’: 4 counted assignments

Do not trigger this flag from future assignments.

If “Imported Assignments” is weighted 0% and contains no assignments with a Due Date at all, apply the Canvas-generated category exemption above and generate no warning or error for that category. If it contains an assignment with any Due Date, including a future Due Date, the exemption does not apply.

---

F. CATEGORIES HAVE NOT BEEN WEIGHTED

Some courses may use POINTS grading rather than weighted assignment categories. In the report these may have category names but blank category weights.

Treat this as:

ERROR: Categories have not been weighted.

Do NOT interpret blank weights in these courses as 0%.

---

G. NO CATEGORIES

If a course contains no category headings at all, flag:

ERROR: No assignment categories found.

Still include the course throughout the workbook.

---

H. CATEGORY WEIGHTS DO NOT TOTAL 100%

For courses configured with weighted categories, add all category weights.

They should total exactly 100%.

If not, flag:

ERROR: Category weights total X%, not 100%.

Treat this as a definite error.

Do not apply this test to unweighted/POINTS courses.

---

I. CATEGORY MAY ACTUALLY BE AN ASSIGNMENT

Use conservative judgment to identify category names that appear more like a specific assignment, book, project, activity, or one-time piece of work than a reusable grading category.

Flag:

Category may be Assignment: [category name]

Examples that SHOULD raise suspicion:

• Wonder
• Bridge to Terabithia
• Mead Hall Boast
• Introducing…
• another specific book title
• a particular project/activity
• another one-off piece of work

Examples that are normally reasonable category concepts:

• Poetry
• Short Story
• Research Paper
• Homework
• Quizzes
• Tests
• Projects
• Formative
• Summative
• Participation
• Vocabulary

This is a warning for human review, not a declaration that the teacher made an error.

For this check, examine ALL assignments in the report, INCLUDING FUTURE ASSIGNMENTS.

A particularly strong signal is when a category name exactly or essentially matches an assignment name in the same course.

Example:

Category: Mead Hall Boast
Assignment: Mead Hall Boast

That category should be flagged even if the assignment is due in the future.

Also use reasonable semantic judgment for obvious title-like categories even when there is not currently an assignment in that category.

---

J. DUPLICATE CATEGORY NAMES

Within each course, check for duplicate category names.

Ignore trivial capitalization or punctuation differences.

Example:

Duplicate category name: Formative (2)

or:

Duplicate category name: Formative (2), Summative (2)

Treat exact duplicate categories as a definite structural problem for review purposes.

Exception: exclude any Canvas-generated “Assignments” or “Imported Assignments” category that qualifies for the 0%-and-no-Due-Date exemption before performing duplicate-category analysis. An exempt category must not create a duplicate-category warning.

---

K. CATEGORIES MAY BE DUPLICATES

Also look for category names that are not identical but may represent accidental duplicates.

Examples:

• Task / Tasks
• singular/plural variants
• very close spelling variants
• minor typographical differences

Flag:

Categories may be duplicates: Task / Tasks

This is a WARNING, not a definite error.

Be conservative.

Do NOT flag categories merely because they are conceptually related.

Examples that should not automatically count as duplicates:

• Formative / Summative
• Quiz / Test
• Homework / Classwork

Also exclude Canvas-generated “Assignments” or “Imported Assignments” categories that qualify for the 0%-and-no-Due-Date exemption from this possible-duplicate analysis.

==================================================

4. COURSE STATUS

Assign every course one status:

OK
Review
Error

Use:

Error

• if the course has one or more definite ERROR conditions

Review

• if the course has one or more warning/review conditions but no ERROR condition

OK

• if the course has no flags

If a course has both Errors and Reviews, its status is Error.

==================================================

5. TEACHER EMAIL ADDRESSES

Generate each teacher’s email from the teacher name.

Convention:

@lincolnlutheran.org

Examples:

Hanna, Tony
→ thanna@lincolnlutheran.org

Bahe, Kelsey
→ kbahe@lincolnlutheran.org

Use lowercase.

Remove spaces, hyphens, apostrophes, and similar punctuation from the surname when constructing the address unless the report gives evidence that another convention is needed.

Also create an Email Check field:

OK

• when the address can be generated cleanly

CHECK

• when the teacher name contains unusual punctuation, suffixes, multiple surnames, missing information, or anything else that makes the generated address uncertain

Do not invent an alternative email format.

==================================================

6. TEACHER-FACING LANGUAGE

Translate technical/internal audit flags into concise, collegial, actionable wording.

Do not simply expose the internal audit language to teachers.

Examples:

Internal:
ERROR: Categories have not been weighted.

Teacher-facing:
This course does not appear to have weighted assignment categories enabled. Please check the gradebook setup.

Internal:
ERROR: No assignment categories found.

Teacher-facing:
No assignment categories are currently shown for this course. Please check that the gradebook categories have been set up.

Internal:
ERROR: Category weights total 200%, not 100%.

Teacher-facing:
The category weights currently total 200%. Please adjust them so they total 100%.

Internal:
Weight 0%: Inferencing

Teacher-facing:
Please verify that the “Inferencing” category is intentionally weighted at 0%.

Internal:
Weight ≤ 10%: Poetry, Short Story

Teacher-facing:
Please verify that the following categories are intentionally weighted at 10% or less: Poetry and Short Story.

Internal:
Weight ≥ 81%: Summative

Teacher-facing:
Please verify that the “Summative” category is intentionally weighted at 81% or more.

Internal:
Default ‘Assignments’: 3 counted assignments

Teacher-facing:
The default “Assignments” category contains 3 assignments due today or earlier. Please move them to the intended category if appropriate.

Internal:
‘Imported Assignments’: 4 counted assignments

Teacher-facing:
The “Imported Assignments” category contains 4 assignments due today or earlier. Please move them to the intended category if appropriate.

Internal:
Category may be Assignment: Wonder

Teacher-facing:
Please check whether “Wonder” is intended to be a gradebook category rather than an individual assignment.

Internal:
Duplicate category name: Formative (2)

Teacher-facing:
Please check the duplicate “Formative” category entries.

Internal:
Categories may be duplicates: Task / Tasks

Teacher-facing:
Please check whether “Task” and “Tasks” are intended to be separate categories.

Teacher-facing wording should be factual, collegial, and non-accusatory.

==================================================

7. OUTPUT WORKBOOK

Create an Excel workbook with FIVE sheets.

If you create or return any Markdown prompt/document text as part of this task, do not use H1 headings. The highest Markdown heading level must be H2 (##); H2 through H6 are allowed.

==================================================

SHEET 1: ALL CATEGORIES

One row per course/category combination.

Columns:

1. Course #
2. Course Code
3. Course Title
4. Teacher
5. Category
6. Weight (%)
7. Assignments Due [current date] or Earlier
8. Flags

If a course has no categories, include one row with:

(No categories shown)

For unweighted/POINTS courses, leave Weight blank rather than entering 0%.

==================================================

SHEET 2: FLAGGED SUMMARY

Include ONLY courses with at least one flag/error.

Use ONE ROW PER COURSE.

Columns:

1. Course #
2. Course Code
3. Course Title
4. Teacher
5. Flag(s)

Condense category-level flags into readable summaries.

Examples:

Weight ≤ 10%: Poetry, Short Story, Literary Analysis

Weight 0%: Inferencing

Weight ≥ 81%: Summative

Category may be Assignment: Wonder, Bridge to Terabithia

Duplicate category name: Formative (2), Summative (2)

Categories may be duplicates: Task / Tasks

Multiple issues may be separated with semicolons.

==================================================

SHEET 3: TEACHER EMAIL DATA

Include EVERY COURSE, including courses with no problems.

Use one row per teacher/course.

Columns:

1. Teacher
2. Email
3. Email Check
4. Course Code
5. Course Title
6. Status
7. Teacher-Facing Notes
8. Internal Flags

Status must be:

OK
Review
Error

For OK courses:

• Teacher-Facing Notes may be blank.
• Internal Flags should be blank.

For Review/Error courses:

• Teacher-Facing Notes should contain clear wording suitable for an email.
• Internal Flags should preserve the technical audit findings.

==================================================

SHEET 4: TEACHER SUMMARY

Use ONE ROW PER TEACHER.

Columns:

1. Teacher
2. Email
3. Email Check
4. Courses
5. Courses OK
6. Courses to Review
7. Courses with Errors
8. Overall Status

Overall Status:

Error

• at least one Error course

Review

• at least one Review course and no Error courses

OK

• all courses are OK

==================================================

SHEET 5: EMAIL DRAFTS

Create ONE ROW PER TEACHER.

Columns:

1. Teacher
2. To
3. Subject
4. Overall Status
5. Email Body
6. Ready

Subject:

Gradebook category check

Ready:

Yes

• when the generated email address is considered reliable

Review

• when Email Check is CHECK or another ambiguity makes the draft unsuitable for automatic handoff

The Email Body should be completely ready to use as an email draft.

Every Email Body must include the signature line I provided at the beginning of the task, immediately after “Thanks,”. Do not rely on the sending account to append or insert a signature.

Do NOT include internal audit terminology unless it is also appropriate teacher-facing language.

Do NOT include any internal notes column on Sheet 5. Internal data already exists on Sheets 3 and 4.

==================================================

8. EMAIL DRAFTING STYLE

For a teacher whose courses are all OK:

Use a short email like:

Hi Nathan,

I reviewed the assignment-category setup for your courses, and everything looks good. No changes are needed.

Thanks,
[the exact signature line I provided]

Do not list each clean course individually.

---

TEACHERS WITH PROBLEMS

Use an opening such as:

Hi Tony,

I reviewed the assignment-category setup for your courses. I found a few things I’d like you to check:

Then organize problems by course.

Use bullet points for issues.

Do not list clean courses individually.

If the teacher has both flagged and clean courses, finish the issue section with:

Your other course looks good.

or:

Your other courses look good.

as grammatically appropriate.

End with:

Thanks,
[the exact signature line I provided]

Use the signature line exactly as I provided it. The sending Gmail account cannot add the signature automatically, so the signature line must already be present in every Email Body on Sheet 5.

==================================================

9. IMPORTANT EMAIL REFINEMENT: GROUP SECTIONS

The audit sheets should remain granular by individual course/section.

However, the EMAIL DRAFT should avoid overwhelming a teacher with repeated text.

When multiple sections:

• have the same Course Title
  AND
• have the same issue pattern

group them into ONE email section.

Example:

English 08 (A1, A2, A3, and B8) — all 4 sections have the same setup

• This course does not appear to have weighted assignment categories enabled. Please check the gradebook setup.
• The default “Assignments” category contains 4 assignments due today or earlier. Please move the current assignments to the intended categories if appropriate.
• Please check the duplicate “Classwork” category entries.

Similarly:

English 11: British Literature (B5, B6, and B7) — all 3 sections have the same setup

• …

Do NOT group sections merely because they share a title if their actual issue patterns differ.

Use the shortest useful section identifier from the Course Code when grouping, such as:

A1
A2
B8
Bouwens-A4a

rather than repeating the full course code for every section.

==================================================

10. IMPORTANT EMAIL REFINEMENT: MERGE RELATED FLAGS

Do not mechanically turn every internal audit flag into a separate bullet when several flags describe the same underlying issue.

Use human judgment to merge related findings.

A particularly important example is the default “Assignments” category.

Suppose the internal audit says:

Weight 0%: Assignments
Default ‘Assignments’: 3 counted assignments
Duplicate category name: Assignments (3)

This example is NOT covered by the Canvas-generated empty-category exemption because the “Assignments” category contains assignments with Due Dates.

Do NOT produce three robotic bullets.

Instead produce one integrated bullet, such as:

The default “Assignments” category contains 3 assignments due today or earlier, is weighted at 0%, and appears 3 times. Please move the current assignments to the intended categories if appropriate, verify that the 0% weight is intentional, and remove or rename any duplicate category that is not intended.

The purpose of Sheet 5 is not merely to repeat audit flags.

It should interpret closely related findings and describe the probable underlying situation in a way that is easier for the teacher to understand and act on.

Other related conditions may also be combined when doing so improves clarity without losing information.

==================================================

11. EMAIL TONE

The emails are going to colleagues.

Use a tone that is:

• friendly
• concise
• professional
• matter-of-fact
• helpful
• non-accusatory

Avoid language implying that the teacher definitely made a mistake when the audit only identified something unusual.

Prefer:

Please check…
Please verify…
This appears…
This does not appear to…

rather than accusatory wording.

For definite structural problems, be direct but still collegial.

==================================================

12. SORTING

Sort Sheets 1, 2, and 3 by:

1. Teacher, ascending using Last, First
2. Course Title, ascending
3. Course Code, ascending as a tie-breaker

Sort Sheets 4 and 5 by:

1. Teacher, ascending using Last, First

==================================================

13. WORKBOOK PRESENTATION

Use:

• Excel tables/filters
• frozen header rows
• readable column widths
• wrapped long text
• clear headers

Visual differentiation:

• Error: red/pink
• Review/warning: light yellow
• OK: light green
• Email Check = CHECK or Ready = Review: distinct warning formatting

Do not over-format.

On Email Drafts, make the Email Body column wide enough to review comfortably and preserve paragraph/bullet line breaks.

==================================================

14. QUALITY CONTROL

Before delivering the workbook, verify:

• Every course in the source report is represented.
• Every teacher in the source report is represented.
• Assignment counts use Due Date, not Assigned Date.
• Assignments due today are included.
• Future assignments are excluded from ordinary assignment counts.
• Future assignments ARE considered for “Category may be Assignment.”
• Blank category weights in unweighted/POINTS courses are not treated as 0%.
• Clearly intentional nongraded/task categories are exempted from the 0% warning.
• A category named exactly “Assignments” or “Imported Assignments” that is weighted 0% and contains no assignments with any Due Date generates no error or warning.
• Future Due Dates prevent that Canvas-generated category exemption, even though future assignments are excluded from ordinary assignment counts.
• Canvas-generated categories that qualify for the exemption are excluded from exact-duplicate and possible-duplicate category checks.
• Weighted courses are checked to ensure category weights total 100%.
• Exact duplicate category names are detected.
• Very likely near-duplicate category names are conservatively flagged.
• Teacher email addresses follow @lincolnlutheran.org.
• Every course has Status OK, Review, or Error.
• Every teacher has a Teacher Summary row.
• Teacher Summary counts match Teacher Email Data.
• Every teacher has exactly one Email Draft row.
• Every Email Draft includes the exact signature line I provided after “Thanks,”.
• Clean teachers receive a brief all-clear email.
• Flagged teachers receive only the courses that need attention.
• Clean courses are summarized as “other course(s) look good” when appropriate.
• Repeated sections with identical issue patterns are grouped in the email.
• Related audit flags are merged into cause-oriented teacher-facing explanations where appropriate.
• Sheet 5 does not expose unnecessary internal audit language.
• Ready is Yes unless an email/draft requires human review.
• The workbook contains no formula/reference errors.

Do not send the emails.

Create and return the completed Excel workbook.

---

Prompt to send email

I am attaching an Excel workbook containing the results of a gradebook audit.

Your task is to use the workbook to send individualized emails to teachers through my connected Gmail account.

The email content has already been reviewed and written. Do NOT independently analyze the gradebook audit, rewrite the messages, or generate new email content.

Use ONLY the sheet named:

Email Drafts

as the authoritative source for sending emails.

==================================================

1. EMAIL DRAFTS SHEET

The Email Drafts sheet contains one row per teacher with these columns:

1. Teacher
2. To
3. Subject
4. Overall Status
5. Email Body
6. Ready

Interpret them as follows:

Teacher

• The teacher’s name.
• This is for reference only.

To

• The exact recipient email address.
• Use this address as the Gmail recipient.
• Do not try to independently look up or substitute a different address.

Subject

• Use this as the exact subject line.

Overall Status

• Internal reference only.
• Do NOT add this status to the email unless it is already present in the Email Body.
• Do not modify email handling based on whether the value is OK, Review, or Error, except as otherwise instructed below.

Email Body

• This is the complete approved email text.
• Use it as the body of the email.
• Preserve its wording, paragraphs, bullet points, capitalization, quotation marks, and organization.
• Do not paraphrase, summarize, expand, soften, strengthen, correct, or otherwise rewrite it.

Ready

• Only send emails whose Ready value is exactly:

Yes

• Do NOT send a row whose Ready value is Review, blank, or anything other than Yes.
• Report those rows to me instead.

==================================================

2. BEFORE SENDING ANYTHING

First inspect the entire Email Drafts sheet.

Verify:

• There is exactly one row per intended teacher.
• Every row being sent has Ready = Yes.
• Every row being sent has a nonblank To address.
• Every row being sent has a nonblank Subject.
• Every row being sent has a nonblank Email Body.
• Each To address appears only once among the rows to be sent.

If you find:

• a duplicate recipient,
• a missing email address,
• a missing subject,
• a missing body,
• Ready other than Yes,
• malformed data,
• or any other ambiguity that could cause an email to go to the wrong person,

DO NOT guess or repair the data.

Do not send that affected email. Tell me what you found.

A problem with one row should not prevent sending other clearly valid rows unless the problem suggests the workbook as a whole may be unreliable.

==================================================

3. DUPLICATE-SEND PROTECTION

Before sending each email, check my Gmail Sent mail for evidence that the same email has already been sent as part of this batch.

Use the combination of:

• recipient email address,
• subject line,
• and today’s date

as the primary duplicate check.

If an email to that recipient with this subject has already been sent today and appears to be this same gradebook-audit message:

DO NOT SEND IT AGAIN.

Mark/report it as already sent.

This is important because I may rerun this instruction after an interruption, and I do not want teachers receiving duplicate messages.

If the evidence is ambiguous, skip that recipient and report it rather than risk sending a duplicate.

==================================================

4. GMAIL COMPOSITION

For each valid row where Ready = Yes:

To:
Use the exact value in the To column.

Subject:
Use the exact value in the Subject column.

Body:
Use the exact contents of the Email Body column.

Do not add:

• explanations,
• headings,
• status labels,
• audit results from other sheets,
• disclaimers,
• notes to me,
• CC recipients,
• BCC recipients,
• attachments,
• or additional text.

Do not include spreadsheet column names or metadata in the message.

==================================================

5. FORMATTING

Preserve the email’s intended structure.

The Email Body may include:

• blank lines between paragraphs,
• course headings,
• bullet points,
• quotation marks,
• grouped course sections.

Preserve those elements when composing the Gmail message.

If the spreadsheet contains plain-text hyphen bullets such as:

• Please check…

it is fine either to preserve those exact hyphens or to render them as normal Gmail bullet points, as long as the wording and hierarchy remain unchanged.

Do not turn the message into a table.

==================================================

6. SIGNATURE

The approved Email Body generally ends with:

Thanks,

This is intentional.

Before sending any emails, ask me what signature line should be added after:

Thanks,

Do not assume the sender is me. Someone else may be using this account to send the emails.

Use exactly the signature line I provide for this batch.

Example:

Thanks,
Jane Smith

Do NOT invent, reconstruct, or infer a sender name, title, department, or signature.

Do NOT rely on Gmail to automatically add a signature.

If I tell you to leave the signature blank, then send the emails ending with:

Thanks,

and do not add anything after it.

If I have not yet told you what signature line to use, STOP BEFORE SENDING THE BATCH and ask me.

Use the same approved signature line for every email in the batch unless I explicitly instruct you otherwise.

==================================================

7. DO NOT USE OTHER WORKBOOK SHEETS TO REWRITE EMAILS

The workbook contains other sheets such as:

All Categories
Flagged Summary
Teacher Email Data
Teacher Summary

These contain the underlying audit information.

You may use them only if necessary to resolve a technical issue with the workbook or to verify that you are reading the correct teacher row.

Do NOT use them to:

• add additional warnings,
• remove warnings,
• reinterpret findings,
• rewrite Email Body,
• decide that an email is unnecessary,
• or independently judge the teacher’s gradebook.

The Email Drafts sheet represents the already-reviewed final communication layer.

If something in another sheet appears to conflict with Email Drafts, do not resolve the conflict yourself. Stop that email and tell me.

==================================================

8. SENDING

Once the validation and duplicate checks are complete, SEND the valid emails.

I am explicitly asking you to send them, not merely create drafts, provided all of the safeguards above are satisfied.

Send exactly one email for each eligible teacher.

Do not send test messages.

Do not send the entire list in one email.

Do not put multiple teachers in the same To/CC/BCC field.

Each teacher must receive only their own individualized email.

==================================================

9. IF SOMETHING FAILS

If Gmail fails while sending a particular message:

• Do not repeatedly retry in a way that could create duplicates.
• Check Sent mail to determine whether the message actually went through.
• If it appears in Sent, count it as sent.
• If it clearly did not send, you may make one appropriate retry if the Gmail tool indicates that is safe.
• If its status remains uncertain, do not retry again. Report it as uncertain.

Continue with other clearly unaffected recipients when safe to do so.

==================================================

10. FINAL REPORT TO ME

After processing the batch, give me a concise summary containing:

• Number of rows on Email Drafts
• Number eligible because Ready = Yes
• Number successfully sent
• Number skipped because they were already sent
• Number skipped because Ready was not Yes
• Number not sent because of validation problems
• Number with uncertain/failed sending status

If every eligible email sent successfully, say so clearly.

For any email not successfully sent, list:

• Teacher
• Recipient
• Reason it was not sent

Do NOT reproduce all successfully sent email bodies in your final response.

==================================================

11. CORE RULE

Treat this as a controlled sending task, not a writing task.

The workbook’s Email Drafts sheet contains the approved messages.

Your responsibilities are:

validate → prevent duplicates → compose faithfully → send → report results.

Do not creatively reinterpret the emails.