On Feb 18, 2026, client feedback raised concerns about the Daily Margin Anomaly Email. Extreme deviation percentages — values like 33,853% and many exact 100.00% entries — made the report difficult to interpret and not actionable.
Investigation revealed three compounding issues:
All 7 requested enhancements implemented:
| 1 | Dollar amounts shown alongside deviation % (current margin, 15-day avg, $ change) |
| 2 | $500 minimum change threshold in addition to 20% deviation filter |
| 3 | New cost activity separated from deviations — $0-to-nonzero items reported as new line items |
| 4 | Test events excluded (Chris Test Lead, etc.) |
| 5 | Margin direction shown — Improving vs. Deteriorating |
| 6 | Severity tiers — color-coded CRITICAL / ALERT / WATCH based on % + $ impact |
| 7 | Event status filter — only Confirmed or Proposal Released events shown |
V2 has been running daily. Currently sending to Diego for review.
Jonathan & Bob: Review and approve the V2 format so we can switch recipients and disable V1.
Based on stakeholder feedback from the Feb 20, 2026 meeting, managers needed a more interactive time tracking report to replace the static XLSX-based one. Specific asks:
New Lambda (time-entry-by-resource-v2) with native Google Sheets output:
[COB] and highlighted with light orange backgroundScheduled to run every Monday. Hour totals validated against V1 output.
Currently only Diego as recipient.
Confirm additional recipients for the weekly report (Jonathan? Amanda? Department managers?).
On Mar 4, 2026, Amanda Filsinger requested: "We have added Robert Deleonibus as a Designer option in Direct. Can you add him into Nutshell as well?"
Robert (Bobby) Deleonibus added to the designers mapping table in PostgreSQL. End-to-end verified: assigning Robert as Assignee on Nutshell lead #5926 correctly created event 19143 in HMR Direct with him as Designer.
On Mar 3, 2026, Amanda flagged: "These notifications are going to the wrong person. Emily is producer for Jason (with Greg). Brittanie's producers are Hadley & Leo W."
Producer-to-designer email mapping corrected. PR #35 merged to hmr-aws-lambda-functions on Mar 3. Amanda confirmed: "Thank you!"
On Mar 3, 2026, Amanda reported: "Can you please fix the spelling of Mari's last name? It's Noga (not Nago)."
We traced the root cause to the IBIS/iVerticle system:
users table: Last name = "Noga" — correctdepartments table (ID 17, "Production - Shop"): Coordinator = "Mari Nago" — typo hereOur emails pull from the department coordinator field, so the fix must happen in iVerticle’s system.
Request Jacques / iVerticle to update the coordinator name for "Production - Shop" (dept ID 17) from "Mari Nago" to "Mari Noga". Our emails will auto-correct on the next sync.
On Feb 25, 2026, Mal requested: "Can you please update Nutshell event types to match the ones from Direct?" — provided a screenshot of the Direct event types for reference.
All old event types were mapped to new ones and the changes were implemented. Mal confirmed on Feb 26: "Great!!! Thank you!!"
Mal asked about removing unused templates from Direct before renaming the rest: "There are so many — can we remove the ones we aren't using and then I can go in and change names?" This is pending on Mal / Jacques (iVerticle) to clean up the Direct template list.
When a lead remains in Nutshell "Inquiry" stage without being moved, the system should:
| Day | Action |
|---|---|
| Day 10 | Send first reminder email to Designer (CC Mal) |
| Day 21 | Send second reminder email to Designer (CC Mal) |
| Day 30 | Automatically move lead to "Dead" |
Logic implemented per approved spec. Sample auto-generated reminder emails:
Are there any exceptions? Specific lead types or tags that should be excluded from the auto-dead schedule?
Nutshell's automated notifications only go to the Assignee (whoever entered the lead). Custom logic needed so both the Designer AND their Producer(s) receive notification emails.
| Designer | Producer(s) |
|---|---|
| Burt | Michael |
| David | Michael |
| Mal | Michael |
| Jason | Emily AND Greg |
| Brittanie | Hadley AND Leo |
| Corrin | None (on her own) |
| TW | None (on her own) |
We recommend a webhook-driven notification flow: Nutshell webhooks trigger the backend, latest lead details are fetched, compared against a stored snapshot, and emails sent only for specific field change scenarios chosen by HMR. This approach is deterministic, auditable, and prevents unnecessary email volume.
Jonathan asked for the details behind the "Sched vs Actual Hours — Feb 2026" report and wants to review with Amanda how hours are being generated. Additionally, he requested COB hours be broken out as a separate summary alongside project-related hours.
What it compares: The report pulls two numbers for each event and department: the estimated hours (what was scheduled/budgeted upfront) and the actual hours (what was actually logged by the team). It covers the full prior month.
How variance is calculated:
Variance = (Actual − Estimated) / Estimated
Examples from the Feb report:
| Department | Actual | Estimated | Variance | Interpretation |
|---|---|---|---|---|
| Warehouse - Glass | 198 | 69 | +189.4% | Over budget |
| Art | 237 | 377 | -37.2% | Under budget |
| Event Installation | 579 | 583 | -0.7% | On target |
Red = over budget • Green = within/under budget
"Jobs Within budget: 69.6%": This counts how many events came in at or under their estimated hours. Out of all events in February, 69.6% had actual hours ≤ estimated hours. Events with no estimate are counted as "within."
Department view vs Event view:
COB hours: Currently COB shows as a department row like any other. Jonathan has requested we break this out as a separate COB vs project-hours summary so that COB time is clearly distinguished from project-related time in one consolidated view.
Nutshell (Rachel Oellig) has built a sandbox/test instance for HMR. This allows us to test any new Nutshell functionality before rolling it out to the active production environment.
Login invites sent to diegos@hmrdesigns.com and analytics@hmrdesigns.com. Ready for Bob, Jonathan, and Mal to be added as well.