Author: William Tygart

  • What Is Google Gemini? What It Is, How It Differs, and Who It’s For

    What Is Google Gemini? What It Is, How It Differs, and Who It’s For

    The short answer: Gemini is Google’s family of AI models, and it is also the name of the assistant those models power. It is the AI built into Google Search, Android phones, Gmail, Google Docs, and Google’s cloud platform — which means most people meet Gemini inside a product they already use, not on a website they have to go looking for. That distribution, more than any single capability, is what Gemini is.

    Gemini is two things with one name

    The word “Gemini” names a family of artificial intelligence models built by Google DeepMind, and it also names the consumer assistant — the app and chat experience — that those models power. The model is the engine; the assistant is one of the cars it drives. The same engine also drives features inside Search, Workspace, Android, and Google Cloud, which is why “Gemini” can mean a chatbot in one sentence and an entire platform in the next.

    This dual meaning is not a branding accident. Google’s strategy is to make one model family the intelligence layer across everything it ships, rather than a single destination product. When someone asks “what is Gemini,” the honest answer is: it is Google’s bet that AI should be a property of the tools you already have, not a separate tool you add.

    Gemini was built multimodal from the start

    Gemini was designed from the beginning to work across text, images, audio, video, and code as one system, rather than as a text model with media features bolted on afterward. In practice, that means a single conversation can move between a document, a photo, a spreadsheet, and a recording without switching tools or translating between them. Multimodality is not a feature list here; it is the architecture.

    The practical consequence is that Gemini is unusually comfortable with mixed inputs — a meeting recording plus the agenda doc plus the slide deck, handled as one body of material. Tasks that are really about one pile of stuff in several formats are where the design shows. Pure text-in, text-out work is the common denominator every major assistant handles; the mixed pile is Gemini’s home ground.

    Where you actually meet Gemini

    Most people encounter Gemini without ever opening the Gemini app. It is the technology behind the AI summaries at the top of Google Search results, the writing and summarizing help inside Gmail and Google Docs, the meeting notes in Google Meet, and the assistant built into Android phones. Gemini reaches users through surfaces Google already owns, which is a fundamentally different distribution model from an assistant you must deliberately visit.

    This matters for a simple reason: adoption follows placement. An assistant embedded in the inbox, the document, and the search box gets used by people who would never sign up for a standalone AI product. Whatever the capability race between model makers looks like in a given season, Gemini’s structural advantage is that it starts inside the workflow instead of asking to be added to it.

    How Gemini differs from ChatGPT

    ChatGPT is OpenAI’s assistant, and its center of gravity is the standalone conversation: you go to ChatGPT — the app, the site — and the conversation is the product. Gemini’s center of gravity is the ecosystem around the conversation: Search, Android, and Workspace are the product, and the assistant is woven through them. Choosing between them is less about which model is smarter this quarter and more about where your work already lives.

    The second difference is gravity of data. ChatGPT starts from what you bring to it — uploads, pasted text, connected apps you deliberately authorize. Gemini starts from what Google already holds for you: your mail, your documents, your calendar, your photos, if you let it. For a person deep in Google’s ecosystem, that starting position saves real setup work. For a person who keeps work deliberately outside Google’s walls, it is a reason to choose the other door.

    How Gemini differs from Claude

    Claude, built by Anthropic, competes on the quality of the thinking and writing inside the conversation — long documents, careful reasoning, code, and a tone professionals trust for drafting. Gemini competes on reach and integration: it is the assistant that is already present in the largest number of everyday surfaces. Both are serious tools; they are optimized for different definitions of “useful.”

    A fair way to frame the choice: if the work is a hard document, a long analysis, or a body of code, many professionals reach for Claude deliberately. If the work is spread across email, docs, meetings, and search in a Google-shaped day, Gemini is already standing where the work is. Plenty of operators run both, and use each where its center of gravity matches the task — the assistants are complements more often than they are rivals. If the choice between these two is the live question, we work it head to head in Claude vs Gemini.

    How Gemini differs from Microsoft Copilot

    Copilot is Microsoft’s assistant layer, and it is Gemini’s closest structural relative: an AI woven into a productivity suite — in Copilot’s case, Microsoft 365, Windows, and Teams. The Gemini-versus-Copilot question is therefore usually not an AI question at all. It is a suite question. A business runs on Google Workspace or it runs on Microsoft 365, and the assistant that comes with the suite is the one that sees the documents, the mail, and the meetings.

    That is why the honest comparison between Gemini and Copilot starts with an inventory, not a benchmark. Which suite holds the company’s files? Where do meetings and chat live? The assistant inherits the answers. Shops that choose deliberately are really choosing the platform; the AI layer is the platform’s new front door, and it should be evaluated as one. The suite decision worked out in full is here: Microsoft Copilot vs Google Workspace Gemini.

    The Google Workspace connection is the working layer

    For businesses, Gemini’s most consequential form is not the chatbot — it is Gemini inside Google Workspace. In Gmail, it drafts, summarizes long threads, and searches mail by meaning rather than keywords. In Docs, it drafts and rewrites in place. In Sheets, it builds and explains formulas and analyzes tables. In Meet, it takes notes and summarizes what was decided. Each of these is small; together they change where the time in a workday goes.

    The reason this layer matters more than the standalone app is context. A standalone assistant knows what you paste into it. Workspace Gemini works inside the actual artifacts of the business — the real thread, the real document, the real meeting — with the permissions those artifacts already carry. AI help stops being a separate step (“go ask the chatbot”) and becomes a property of the document you were already editing. For the document work specifically, we put it head to head in Notion AI vs Gemini for workspaces.

    Your data gets two different answers

    What happens to the things you tell Gemini depends on which side of Google’s house you are standing on, because Gemini ships under two different sets of terms. On a personal Google account, Gemini is a consumer service: Google’s Gemini Apps privacy terms say your conversations can be used to improve Google’s products — including review by human reviewers — unless you turn Gemini Apps Activity off. The free assistant is not sold for money; it is partly paid for in data.

    Inside Google Workspace, the terms are contractual, and they say the opposite. Google states that Workspace customer data — prompts included — is customer data under its data-processing terms, and that Workspace does not use customer data to train its generative AI models without the customer’s permission or instruction. The same assistant, under a work account, runs under a no-training commitment; under a personal account, it does not. Which regime your conversations live under is decided by which account you are signed into — which is why the consumer-versus-Workspace split, worked out in our governance comparison, matters more than any single feature.

    Who Gemini is for

    Gemini is for the person or business whose working life already runs on Google: Gmail for mail, Drive and Docs for files, Meet for calls, Android in the pocket, Search for everything else. For that person, Gemini is the lowest-friction serious AI available, because there is nothing new to adopt — the assistant arrives inside tools already open on the screen. The ecosystem is the onboarding. We drew that person in full in the Gemini user persona.

    Gemini is also for people whose work is heavy on mixed media — video to review, recordings to mine, images to interpret alongside documents — because its multimodal design treats those as first-class inputs rather than attachments. And it is for organizations on Google Cloud, where the same model family is available to developers as a platform for building their own applications, under enterprise controls. Developers weighing it against the field on code specifically can start from our coding benchmark comparison.

    Who should pick something else

    Gemini is a weaker fit for a business standardized on Microsoft 365, where Copilot holds the context advantage and Gemini would start every task empty-handed. It is a weaker fit for someone who wants one standalone assistant, deliberately separate from any suite, with the conversation itself as the whole product. And it is a weaker fit for anyone whose first requirement is keeping work outside Google’s ecosystem entirely — that is a legitimate architectural preference, and no feature list overrides it.

    Naming the non-fit is part of the definition. An assistant’s real specification is not what it can do in a demo; it is what it can see, where it lives, and what it costs you to feed it context. Gemini’s specification is: maximum reach inside Google’s world, minimum setup, multimodal by design. If your work lives somewhere else, the right answer is the assistant that lives there.

    What Gemini costs, in shape

    Gemini follows the pattern of the whole category: a free tier exists inside Google’s consumer products, and paid plans unlock higher limits, deeper Workspace integration, and the most capable models. Businesses typically meet Gemini as part of Google Workspace licensing or as a paid add-on tier, and developers pay for model access through Google Cloud on a usage basis. The exact prices and plan names change often enough that any figure printed here would rot; the durable fact is the shape — free to start inside products you already have, paid when you want it deeper in the work.

    One dated snapshot, so the shape has names: as of October 2026, Google’s consumer ladder runs Free, then Google AI Plus, Google AI Pro, and Google AI Ultra — Pro at $19.99 a month in the US, Ultra starting at $99.99 — and the plan older pages still call “Gemini Advanced” is the one now sold as AI Pro. Treat those names and numbers as this season’s, and check Google’s subscriptions page for the current set; the ladder underneath them is the part built to last.

    Plan US price (October 2026) What it is
    Free $0 Gemini inside Google’s consumer products — the assistant app and the AI features in Search.
    Google AI Plus $4.99 / month The entry paid rung: the same assistant with higher usage limits than Free.
    Google AI Pro $19.99 / month The full consumer tier — the plan older pages call “Gemini Advanced” — with the most capable models and deeper Workspace integration.
    Google AI Ultra from $99.99 / month The top rung: the highest limits and first access to Google’s newest capabilities.

    The cost question worth asking is therefore not “what does Gemini cost” but “what are we already paying for.” A Workspace business may find Gemini is an increment on a bill it already pays, while a Microsoft business would pay for Gemini as an entirely second stack. Same assistant, two very different real prices — because in this category, you rarely buy the model. You buy the position it occupies in your stack.

    The one-sentence version

    If every other assistant is a place you go, Gemini is the layer that arrives where you already are — and for the hundreds of millions of people and businesses whose work lives in Google’s products, that arrival is the whole story. For the wider field in one place — Gemini set against ChatGPT, Claude, and Perplexity — see our four-way alternatives comparison.

    Frequently asked questions

    What is Google Gemini, in simple terms?

    Gemini is Google’s AI: a family of models built by Google DeepMind, and the assistant those models power. It answers questions, writes and summarizes text, works with images, audio, and video, and it is built into Google Search, Android, Gmail, Google Docs, and other Google products — so most people use it inside tools they already have open.

    Is Gemini the same thing as Bard?

    Bard was the original name of Google’s consumer AI chatbot, and Google renamed it Gemini so the assistant and the models behind it carry one name. If you remember Bard, you already know what Gemini is: it is the same product line, renamed and substantially rebuilt since. There is no separate Bard product anymore.

    Is Gemini free?

    There is a free tier of Gemini available in Google’s consumer products, including the assistant app and AI features in Search. Paid plans raise usage limits, unlock the most capable models, and add deeper integration with Google Workspace apps like Gmail and Docs. Businesses generally get Gemini through Google Workspace plans or paid add-ons, and developers pay for model access through Google Cloud based on usage.

    What is the difference between Gemini and ChatGPT?

    ChatGPT is OpenAI’s assistant, built around the standalone conversation — you go to it, and the conversation is the product. Gemini is Google’s assistant, built around distribution — it lives inside Search, Android, Gmail, and Docs, and starts from the context Google already holds for you. The practical choice is usually about where your work already lives, not about which model wins a given benchmark.

    Does Gemini work inside Gmail and Google Docs?

    Yes — that integration is Gemini’s main business form. Inside Gmail it can summarize long threads, draft replies, and find mail by meaning. Inside Docs it drafts and rewrites in place. It also works across the rest of Google Workspace: summarizing meetings in Meet, analyzing tables in Sheets, and helping build presentations in Slides — always inside the documents and permissions a business already has.

    Does Google train Gemini on my data?

    It depends on the account. Under a personal Google account, Gemini is a consumer service, and Google’s Gemini Apps privacy terms say conversations can be used to improve Google’s products, including human review, unless you turn Gemini Apps Activity off. Under a Google Workspace account, the answer is contractual: Google states that Workspace customer data, prompts included, is not used to train its generative AI models without the customer’s permission. Work conversations belong on the work account for exactly this reason.

    Which is better, Gemini or Claude?

    They are optimized for different things. Claude, from Anthropic, is the deliberate-choice assistant many professionals pick for long documents, careful reasoning, writing quality, and code. Gemini is the assistant of reach: it is already present across Google’s products, starts from your existing Google context, and handles mixed media — documents, images, recordings — as one pile. Many operators use both, matching the assistant to the task rather than declaring a single winner.

  • Storm Updates: Quiet Pulse — Oct 25 Morning

    Storm Updates: Quiet Pulse — Oct 25 Morning

    As of this Sunday morning desk, October 25, 2026 (approximately 9:12 PM PDT Saturday / 4:12 AM UTC Sunday), the national picture remains a Quiet Pulse. The Storm Prediction Center holds a Marginal Risk of severe thunderstorms across portions of central and southern New Mexico and far west Texas on the Day 1 Convective Outlook valid through 1200Z Sunday. Isolated severe wind, hail, and a tornado remain possible early overnight as storms continue but instability decreases with nocturnal cooling. Severe Thunderstorm Watch 697 is expiring or has expired at 0400Z October 25. The Weather Prediction Center holds a Slight Risk of excessive rainfall over portions of West Texas, New Mexico, and Colorado into far western Kansas. No tropical storm or hurricane watch or warning is in effect on the U.S. coast or Gulf of America.

    Tropical: None · Severe: Marginal · Flood: Slight

    What Changed

    • Compared with yesterday afternoon’s pulse table (quiet-pulse-2026-10-24-afternoon: Severe: Marginal · Flood: Slight · Tropical: None): the SPC Day 1 Convective Outlook (0100 UTC October 25 / 8:07 PM CDT Saturday, October 24, 2026, valid 250100Z–251200Z, corrected) continues a MARGINAL RISK of severe thunderstorms across portions of central and southern New Mexico and far west Texas (roughly 84,000 sq mi, 2.5 million people including El Paso, Albuquerque, Las Cruces, Santa Fe, and Rio Rancho). Isolated severe wind/hail and a tornado remain possible this evening into early overnight; the environment is becoming less conducive with congealing storms and weakening instability.
    • Severe Thunderstorm Watch 697 (issued ~2055Z October 24 for NM and TX) expires at 0400Z October 25. Primary residual threats are isolated large hail and severe gusts as storms congeal. No new Mesoscale Discussions elevating the threat beyond isolated.
    • WPC Day 1 Excessive Rainfall Outlook (updated 0102 UTC Sunday October 25, valid 01Z–12Z October 25) holds a SLIGHT RISK for portions of West Texas, New Mexico, and Colorado into far western Kansas. Highest totals 1.5–3 inches possible, especially northeastern New Mexico and southeastern Colorado. No Moderate or above. Active Flash Flood Warnings and Flood Watches continue in central New Mexico on saturated soils.
    • No tropical storm or hurricane watch or warning on the U.S. coast or Gulf of America. Atlantic basin remains quiet with no tropical cyclones and no formation expected in the next 7 days (NHC 800 PM EDT Saturday outlook). Hurricane Vance (Eastern Pacific) continues well south of Mexico with no U.S. land threat.
    • Nothing material moved in the lanes overnight. Severe remains Marginal, flood remains Slight, tropical remains None. Quiet Pulse criteria are met. Primary residual ticket is isolated hail/wind and flash-flood runoff in New Mexico and far west Texas.

    Live Status

    SPC Day 1 lists a Marginal Risk (Level 1 of 5) of severe thunderstorms for central and southern New Mexico and far west Texas. Showers and thunderstorms continue across the Southwest. The most intense cells are across Far West Texas north into central New Mexico, where radar continues to suggest large hail and severe gusts remain possible. The 00 UTC Albuquerque sounding showed MUCAPE around 900 J/kg that has peaked and will weaken with low-level stabilization. Congealing storms and decreasing buoyancy lead to an increasingly sporadic severe threat overnight, though isolated large hail and severe wind gusts may still occur over the next couple of hours as of the 0100Z update.

    Local NWS offices have issued and expired Severe Thunderstorm Warnings overnight, with active or recent Flash Flood Warnings in counties such as Bernalillo, Santa Fe, Torrance, and Hudspeth for heavy rain and observed flooding. Flood Watches remain in effect until 6 AM MDT Sunday for portions of south-central New Mexico and southwest Texas.

    WPC maintains the Slight Risk of excessive rainfall. Rainfall rates of 1–1.5 inches per hour possible in the highest zones, capable of flash flooding in urban areas, roads, small streams, narrow canyons, and burn scars, especially where prior rainfall has saturated soils. No Moderate or higher ERO.

    Hotspots

    • Central New Mexico (Albuquerque, Santa Fe, Rio Rancho corridor): Marginal severe residual and WPC Slight. Ongoing or residual convection with isolated hail/wind possible into early overnight. Flash Flood Warnings active in sensitive terrain and urban areas on saturated soils.
    • Far west Texas and El Paso / Hudspeth County: Marginal severe overlap. Recent Severe Thunderstorm Warnings for gusts and hail. Flash Flood Warnings for west-central Hudspeth. Urban runoff risk under the Slight ERO.
    • Southeastern Colorado and northeastern New Mexico: WPC Slight Risk for excessive rainfall. Residual upslope and training potential. Lower severe threat. Sensitivity from earlier activity this week.

    Just-Hit

    Flash Flood Warnings remain or were recently active in Bernalillo, Santa Fe, Torrance, Lincoln, Cibola, and Hudspeth Counties, with observed flooding of roads, I-40 segments, and low-lying areas. Severe Thunderstorm Warnings have expired in Chaves and other counties as storms weakened below severe limits. No confirmed significant tornado reports. Localized flooding and wind/hail impacts ongoing or residual in the Southwest corridor.

    Pulse Table

    LaneStatusNotes (as of ~4:12 AM UTC Oct 25 2026)
    TropicalNoneNo tropical cyclones in the Atlantic. Hurricane Vance (EPAC) far south of Mexico. No U.S. coastal or Gulf watches or warnings.
    SevereMarginalSPC Day 1 Marginal Risk over central/southern NM and far west TX. Watch 697 expiring 0400Z. Isolated hail/wind/tornado possible early overnight. Threat decreasing.
    FloodSlightWPC Day 1 Slight Risk for portions of NM, southern CO, West TX. 1.5–3″ possible. Active FFWs and Watches. Residual sensitivity. No Moderate or higher.

    Restoration Read

    Residual restoration ticket is isolated hail and wind damage to roofs, vehicles, siding, and trees across central and southern New Mexico and far west Texas under the Marginal Risk. Secondary ticket is localized flash flooding and rapid runoff in urban corridors (El Paso, Albuquerque), small streams, canyons, and burn scars on already saturated soils. No widespread catastrophic damage expected; threats diminish overnight into Sunday morning.

    What This Is Not

    This is a Quiet Pulse. No SPC Slight or higher severe risk remains on the latest Day 1 outlook. No WPC Moderate or higher excessive rainfall. No tropical storm or hurricane watch or warning on the U.S. coast or Gulf of America. This desk summarizes public products from the SPC, WPC, NWS, and NHC. It is not an official warning.

    Looking Ahead

    Sunday (continuing Day 1 into Day 2): SPC Day 2 outlooks a Marginal Risk of severe thunderstorms from southern/eastern New Mexico into far west Texas for isolated large hail and an isolated tornado Sunday afternoon/evening. WPC maintains some excessive rainfall potential as the upper low progresses. The organized severe window closes overnight. Monitor local NWS offices for any lingering warnings.

    Rising Queries

    Trends unreachable.

    Sources

    Official products: Storm Prediction Center (Day 1 Outlook 0100Z Oct 25, Watch 697), Weather Prediction Center (Day 1 Excessive Rainfall Outlook), National Weather Service (watches, warnings, flood statements), National Hurricane Center (Atlantic quiet; Hurricane Vance Eastern Pacific). Previous desk: quiet-pulse-2026-10-24-afternoon.

    Informational only — not an official weather warning. Always check weather.gov for local forecasts and warnings. Turn around, don’t drown.

  • Storm Updates: Quiet Pulse — Oct 24

    Storm Updates: Quiet Pulse — Oct 24

    As of this Saturday evening update to the afternoon desk, October 24, 2026 (approximately 9:14 PM PDT / 12:14 AM EDT / 0414Z October 25), the national picture remains a Quiet Pulse. The Storm Prediction Center Day 1 Convective Outlook holds a Marginal Risk of severe thunderstorms across portions of central and southern New Mexico and far west Texas. Isolated severe wind, hail, and a tornado remain possible this evening as storms continue but instability decreases with nocturnal cooling. Severe Thunderstorm Watch 697 is valid until 0400Z October 25 (9 PM PDT). The Weather Prediction Center holds a Slight Risk of excessive rainfall over portions of West Texas, New Mexico, and Colorado. No tropical storm or hurricane watch or warning is in effect on the U.S. coast or Gulf of America.

    Tropical: None · Severe: Marginal · Flood: Slight

    What Changed

    • Compared with this morning’s pulse table (quiet-pulse-2026-10-24-morning: Severe: Marginal · Flood: Slight · Tropical: None): the latest SPC Day 1 Convective Outlook (0100 UTC October 25 / 8:07 PM CDT Saturday, October 24, 2026, valid 250100Z–251200Z) confirms a MARGINAL RISK of severe thunderstorms across portions of central and southern New Mexico and far west Texas. Isolated severe wind/hail and a tornado remain possible this evening; the environment is becoming less conducive with nocturnal cooling.
    • Severe Thunderstorm Watch 697 (issued ~2055Z October 24 for NM TX) remains valid until 0400Z October 25. Status reports indicate the severe weather threat continues in portions of central/southeast New Mexico and far west Texas. Primary residual threats are isolated large hail and severe gusts as storms congeal.
    • WPC Day 1 Excessive Rainfall Outlook (updated 0102 UTC Sunday October 25, valid 01Z–12Z Oct 25) holds a SLIGHT RISK for portions of West Texas, New Mexico, and Colorado into far western Kansas. Highest totals 1.5–3 inches possible. No Moderate or above. Active Flash Flood Warnings continue in El Paso/Hudspeth County TX and Bernalillo/Santa Fe area NM on saturated soils.
    • No tropical storm or hurricane watch or warning on the U.S. coast or Gulf of America. Atlantic basin remains quiet. Eastern Pacific hurricane activity (Vance) is well south of Mexico with no U.S. land threat.
    • Severe lane holds at Marginal. Flood lane holds at Slight. Quiet Pulse criteria met. Primary residual ticket is isolated hail/wind and flash-flood runoff in New Mexico and far west Texas.

    Live Status

    SPC Day 1 lists a Marginal Risk (Level 1 of 5) of severe thunderstorms for central and southern New Mexico and far west Texas. Showers and thunderstorms continue across the Southwest this evening. The most intense cells are across Far West Texas north into central New Mexico, where radar suggests large hail and severe gusts remain possible. The 00 UTC Albuquerque sounding showed MUCAPE around 900 J/kg that is peaking and will weaken with low-level stabilization. Congealing storms and decreasing buoyancy lead to an increasingly sporadic severe threat overnight.

    Watch 697 covers the core area in NM and TX until 9 PM PDT. Local NWS offices continue Flash Flood Warnings in southeastern El Paso County and western Hudspeth County TX (until ~1:30 AM MDT in some segments) and in Bernalillo, northwestern Torrance, and southwestern Santa Fe Counties NM (until ~11:15 PM MDT), with observed heavy rain of 1–3 inches and road impacts including I-40 segments.

    WPC maintains the Slight Risk of excessive rainfall. Rainfall rates of 1–1.5 inches per hour possible in the highest zones, capable of flash flooding in urban areas, roads, small streams, narrow canyons, and burn scars, especially where prior rainfall has saturated soils. No Moderate or higher ERO.

    Hotspots

    • Central New Mexico (Albuquerque, Santa Fe, Rio Rancho corridor): Marginal severe residual and WPC Slight. Ongoing convection with isolated hail/wind possible into the evening. Flash Flood Warnings active in sensitive terrain and urban areas on saturated soils. I-40 segments impacted.
    • Far west Texas and El Paso / Hudspeth County: Marginal severe overlap. Flash Flood Warnings for southeastern El Paso and western Hudspeth. Storms moving northeast. Urban runoff risk under the Slight ERO.
    • Southeastern Colorado and northeastern New Mexico: WPC Slight Risk for excessive rainfall. Residual upslope and training potential. Lower severe threat. Sensitivity from earlier activity this week.

    Just-Hit

    Flash Flood Warnings remain active or recently extended in southeastern El Paso County and western Hudspeth County TX, and in Bernalillo, northwestern Torrance, and southwestern Santa Fe Counties NM. Observed rainfall 1–3 inches in spots with flash flooding of creeks, urban areas, and highways. No confirmed significant tornado reports at this desk time. Localized flooding and residual wind/hail impacts ongoing in the Southwest corridor.

    Pulse Table

    LaneStatusNotes (as of ~9:14 PM PDT / 0414Z Oct 25 2026)
    TropicalNoneNo tropical cyclones in the Atlantic. Hurricane Vance (EPAC) far south of Mexico. No U.S. coastal or Gulf watches or warnings.
    SevereMarginalSPC Day 1 Marginal Risk over central/southern NM and far west TX. Watch 697 until 0400Z. Isolated hail/wind/tornado possible this evening. Threat decreasing overnight.
    FloodSlightWPC Day 1 Slight Risk for portions of NM, southern CO, and far west TX. 1.5–3″ possible. Active FFWs. Residual sensitivity. No Moderate or higher.

    Restoration Read

    Residual restoration ticket is isolated hail and wind damage to roofs, vehicles, siding, and trees across central and southern New Mexico and far west Texas under the Marginal Risk and closing Watch 697. Secondary ticket is localized flash flooding and rapid runoff in urban corridors (El Paso, Albuquerque), small streams, canyons, and burn scars on already saturated soils. No widespread catastrophic damage expected; threats diminish overnight.

    What This Is Not

    This is a Quiet Pulse. No SPC Slight or higher severe risk remains on the latest Day 1 outlook. No WPC Moderate or higher excessive rainfall. No tropical storm or hurricane watch or warning on the U.S. coast or Gulf of America. This desk summarizes public products from the SPC, WPC, NWS, and NHC. It is not an official warning.

    Looking Ahead

    Sunday (Day 2): SPC outlooks a Marginal Risk of severe thunderstorms continuing from southern/eastern New Mexico into far west Texas for isolated large hail. WPC maintains some excessive rainfall potential as the upper low progresses. The organized severe window closes overnight tonight. Monitor local NWS offices for any lingering warnings.

    Rising Queries

    Trends unreachable.

    Sources

    Official products: Storm Prediction Center (Day 1 Outlook 0100Z Oct 25, Watch 697), Weather Prediction Center (Day 1 Excessive Rainfall Outlook), National Weather Service (watches, warnings, flood statements), National Hurricane Center (Atlantic quiet; Hurricane Vance Eastern Pacific). Morning desk: quiet-pulse-2026-10-24-morning.

    Informational only — not an official weather warning. Always check weather.gov for local forecasts and warnings. Turn around, don’t drown.

  • Storm Updates: New Mexico Severe — Oct 24 Morning

    Storm Updates: New Mexico Severe — Oct 24 Morning

    Tropical: None · Severe: Marginal · Flood: Slight

    What Changed

    • SPC Day 1 (latest 0100Z Oct 25 / 0807 PM CDT Oct 24, valid 250100Z-251200Z) now Marginal Risk for central/southern New Mexico and Far West Texas, stepped down from daytime Slight Risk. Isolated severe wind/hail and tornado remain possible this evening as instability decreases.
    • Severe Thunderstorm Watch #697 remains active until 0400Z Oct 25 (9 PM MST) for central into SE NM and Far West TX. Threats: damaging winds, large hail (to 2″), isolated tornado.
    • Ongoing LSRs and warnings: hail to 1.25″, winds to 75 mph reported; multiple Severe TSTM and Flash Flood Warnings in NM/TX/CO as of late Oct 24.
    • WPC Day 1 ERO Slight Risk maintained for West TX, NM, CO (updated ~0732Z Oct 24). Flash Flood Warnings active, including considerable threats and road closures.
    • No change in tropical: none for U.S. Hurricane Vance (EP) no U.S. threat. Atlantic quiet.

    Pulse Table

    LaneStatusDetails (as of ~0212Z Oct 25 / evening Oct 24 PDT)
    SevereMarginalSPC latest Day 1 Marginal NM/Far West TX. Watch 697 live. LSRs hail 1″+ / winds 60-75 mph (Oct 24).
    FloodSlightWPC Day 1 Slight ERO. Active Flash Flood Warnings NM (Lincoln, Cibola etc.), TX, CO. I-40 impacts reported.
    TropicalNoneNo U.S. watches/warnings. Vance EP ~90 mph south of Mexico. Atlantic no cyclones.

    Official Outlooks

    SPC Day 1 latest (SPC AC 250107, 0807 PM CDT Sat Oct 24 2026): THERE IS A MARGINAL RISK OF SEVERE THUNDERSTORMS ACROSS PORTIONS OF CENTRAL AND SOUTHERN NEW MEXICO AND FAR WEST TEXAS. Isolated severe wind/hail and a tornado remain possible this evening. Storms continue but buoyancy weakening with nocturnal cooling; threat increasingly sporadic overnight.

    Earlier 1300Z outlook had Slight Risk for afternoon/evening. Watch 697 issued 155 PM MST covering the core. MD 2408 confirmed ongoing hail >1″ and 60-70 mph gusts into evening.

    WPC Day 1 ERO (Dolan, ~0732Z Oct 24, valid 12Z Oct 24-12Z Oct 25): SLIGHT RISK of excessive rainfall for portions of West Texas, New Mexico, and Colorado. 1.5-3″ possible, rates challenging flash flood guidance, especially on wet soils. Marginal elsewhere including Four Corners and SE Florida.

    NWS: Active Severe Thunderstorm Warnings and Flash Flood Warnings (observed flooding, considerable threats in places like Lincoln NM, Cibola with I-40 closed). SPC storm reports Oct 24: 1″ hail Canutillo TX / White Sands / Lincoln NM; winds 58-75 mph in Dona Ana / Otero NM.

    NHC: No tropical cyclones in Atlantic. Hurricane Vance Eastern Pacific holding ~90 mph, well south of Mexico, no U.S. impact. No TS/H watches for U.S. coast or Gulf.

    Rising Queries

    Trends unreachable.

    Informational only — not an official warning. Check latest SPC, WPC, NWS, NHC.

  • Receipts: 105 Dead Clicks — and Why We Changed Nothing

    Receipts: 105 Dead Clicks — and Why We Changed Nothing

    Our analytics flagged 105 dead clicks on our Claude pricing pages this week. Dead clicks are supposed to mean friction — people clicking things that don’t work. The fix, if you believe the dashboard, is a redesign ticket.

    So we watched the recordings. All of them, session by session. This video is that walkthrough, narrated as it happened: the three filters that isolate the signal, then the two densest sessions read event by event.

    Every flagged click was a reader selecting text. On the enterprise pricing page, one visitor accounts for all 17 dead clicks — four and a half minutes on the page, highlighting as they read. On the team-plan usage-limits page, 13 of the 22 dead clicks land inside the Direct Answer box at the top of the article: people selecting the summary to copy it out. Nobody clicked a broken button. Nobody clicked a price that wouldn’t respond. The one honest exception is a bold line inside a call-to-action block that got clicked like a button, four times — the only element on either page we’d even consider changing.

    If we’d worked from the dashboard alone, we’d have “fixed” pages that are doing their jobs — and probably broken the format that makes them get cited in the first place.

    This is the part of analytics nobody sells you: the number is a question, not an answer. The recording is the answer — if somebody actually watches it.

  • Receipts: One Week, 6,753 Bot Visits, Three Kinds of Bots

    Receipts: One Week, 6,753 Bot Visits, Three Kinds of Bots

    “AI traffic” sounds like one thing. On the dashboard it is three different things, doing three different jobs, and they are not interchangeable.

    Healthcare Facility Hub, last 7 days: 6,753 AI-bot requests. The operators alone are a crowd — Microsoft 1,250, Meta 1,046, Google 646, OpenAI 580, Amazon 564, Anthropic 505, Perplexity 444, Huawei 401, ByteDance behind them, and a tail that runs down to a single visit each from names most site owners have never heard of.

    Clarity sorts them by what they came to do. AI Crawlers made 5,139 of the visits, 76.10% — the index builders, reading everything so the models know it exists. AI Search made 1,031, 15.27% — bots fetching a page because somebody just asked a question: PerplexityBot 444 of them, plus Lyrenth and Parallel. AI Assistants made 583, 8.63% — browsing on behalf of a person mid-conversation: OpenAI 320, Anthropic 94, DuckDuckGo 17, Cohere exactly 1.

    The distinction matters because each kind wants something different from a page. A crawler wants it complete and clean. A search bot wants the answer findable in seconds. An assistant wants the page to make sense lifted out of context. One page, three readers, three jobs.

    And for all 6,753 visits, the scrape-to-referral ratio is 535:1. One referral came back all week. The most-wanted page on the site, by the way, is not the homepage — it is a field sheet, /email-my-field-sheet/, with 885 requests, 13.11% of everything the bots did.

    Ask for receipts.

  • Receipts: ChatGPT Read 375 Pages of One Site. It Sent Back 1 Visitor.

    Receipts: ChatGPT Read 375 Pages of One Site. It Sent Back 1 Visitor.

    People say you can’t tell which AI models are reading your site, or what they do when they get there. This is Microsoft Clarity on one of ours. It names the operator, the bot, and the activity — no guessing.

    Continuity Hub, last 30 days: ChatGPT-User made 375 requests. The homepage 83 times. Then the guides, one by one — supply-chain resilience, financial-services continuity rules, OSHA evacuation plans — down to pages that got a single read each. The bot didn’t skim the site. It walked the whole catalog.

    The scrape-to-referral ratio is 494:1. For every 494 pages the model read, it sent back one visitor. One referral, total, from chatgpt.com.

    That ratio is the part nobody selling AI visibility talks about. Being read by the models and being sent customers by the models are two different numbers, and the first one is enormous while the second one is nearly zero. We’ve measured the same shape across our sites — 408:1 on one, 837:1 across the fleet in September. The reading is real. The referring barely exists.

    So when you interview whoever handles your SEO and AEO, ask them to pull up this screen for your site, live, with the dates in frame. If they can’t show you the receipts, they’re reading from somebody else’s book.

  • WSU Is Building an Aquaculture Center in Puyallup. Builders Have Until November 10 to Get in Line.

    WSU Is Building an Aquaculture Center in Puyallup. Builders Have Until November 10 to Get in Line.

    Washington State University is hiring a design-build team for new aquaculture facilities at its Puyallup Research and Extension Center, and the first door closes fast: statements of qualifications are due Tuesday, November 10, 2026, before 3:00 p.m. The contract covers both the Puyallup center and the Pullman campus, and its guaranteed maximum price is $25.6 million — design, construction, contingencies, and fees included, with Washington sales tax excluded.

    What gets built in Puyallup

    The Puyallup half of the project starts with a building that already stands. The center’s Salmon Lab, 4,542 net square feet, will be renovated across roughly 3,000 square feet of it. Alongside it, new construction adds approximately 8,000 to 12,000 square feet — space for fish rearing, quarantine and examination rooms, wet and dry laboratories, and cold storage — plus about 2,000 square feet of secured outdoor area for large fish tanks.

    The Pullman half of the same contract renovates aquaculture space in four buildings, including the Carver Farm Fish Vivaria, and adds 7,000 to 10,000 square feet of new construction near Carver Farm. One team takes both campuses: WSU is procuring a single progressive design-build contract, and responding teams are limited to the builder and the prime designer.

    The money is federal, and it has rules

    The project rides on a National Institute of Standards and Technology grant — award 60NANB26D275 — for what the funding proposal called a Scientific Research Center. At a Puyallup city council meeting in September, university representatives described the planned Puyallup aquaculture center as supported by a $50 million federal appropriation. The $25.6 million in the solicitation is a different and narrower number: the guaranteed maximum price for this design-build contract itself.

    Federal money brings federal conditions with it. The Build America, Buy America requirements sit inside the request-for-qualifications package, and the finished buildings must meet Washington’s Clean Buildings Performance Standard. A team that wins this job is signing up for both.

    A two-page audition

    For a $25.6 million contract, the first audition is strikingly small. The statement of qualifications is capped at two pages — 11-by-17, nothing under 10-point type — plus a single third page for the team’s resumes. WSU states plainly that pages beyond the three will not be reviewed. Shortlisted teams move to a proposal round due December 15; WSU expects to announce the selected team on Friday, December 18, 2026, and execute the agreement by December 29.

    The calendar

    • Optional Puyallup site walk: Thursday, October 29, 2026, 2:30–4:30 p.m., Allmendinger Building, 2606 W. Pioneer, Puyallup
    • Statements of qualifications due: Tuesday, November 10, 2026, before 3:00 p.m., by email in PDF to contracts@wsu.edu, cc carbour@wsu.edu
    • Proposals from shortlisted teams: December 15, 2026
    • Selected team announced: December 18, 2026
    • The long arc after selection: project confirmation in May 2027, detailed design in October 2027, construction documents in January 2028, and substantial completion in March 2029

    Questions go to the project manager, Cyndi Arbour, at carbour@wsu.edu or (509) 335-7010. The full solicitation, including the RFQ document itself, is posted on WSU Facilities Services’ alternative public works page, and the state’s Office of Minority and Women’s Business Enterprises carries the advertisement.

    What it adds to the town

    The Research and Extension Center has been becoming a water campus for years. Its master plan names the direction outright — a leader in water research — and its Salmon Ecology Toxicology Lab already works on the fish this region’s rivers are known for. The city marked the relationship in September, proclaiming September 21–26 as WSU Puyallup Research & Extension Center Appreciation Week, with center director Todd Murray addressing the council.

    An aquaculture build of this size makes that identity physical: renovated lab space, up to 12,000 new square feet, outdoor tank yards, and a construction run on West Pioneer that stretches into 2029. It lands in the same season the town’s Opportunity Zone nomination went to Treasury — different money, same direction. Puyallup’s research footprint is compounding, and universities build the kind of institutions that stay for decades.

    We will name the selected team here when WSU announces it on December 18.

  • What an IICRC Card Is Worth, Measured

    What an IICRC Card Is Worth, Measured

    Data collected October 24, 2026. Every dollar figure below is in the dataset linked at the end of this article, or is arithmetic on that file. The rejects log — every lead that did not survive a page read, and why — is linked there too.

    The design this collection was judged against was written first, before any page was opened. Every dollar below is in the dataset or is arithmetic on that file. Annual bands are turned into hourly at 2,080 hours (40 × 52) only in the model. The dataset keeps the unit the page printed.

    The question nobody had answered

    An earlier research pass looked for an authoritative dollar value on an IICRC certification and did not find one. No study. No table. One proposed pay model, Ken Larsen’s, written up in Restoration & Remediation in April 2022. The measurement here is the other way: read real postings, price the credential the way labor economics prices a credential, and publish the method with the number.

    The number, from this pass, is a wide interval around zero. That is a result. It is not a slogan.

    The method

    Two borrowed tools, named on purpose.

    Jacob Mincer’s earnings equation puts the wage in logs and holds schooling and experience. Sherwin Rosen’s hedonic price reads a wage as the sum of the attributes bundled into the job. The certificate is one attribute. The posting also buys a role, a city, and a tenure screen. The certificate’s price is whatever gap is left after those are held still.

    The pay figure is the midpoint of the band on the page. A single figure is a band with the same low and high. Preferred is its own status. It is not folded into required, and it is not treated as silence.

    Two comparisons were specified before any page was opened.

    1. Inside a role × metro cell, the median midpoint of postings that require the named cert, against the median of postings that do not mention it. A cell with fewer than 4 postings on either side does not produce a result. It produces an inventory line.
    2. Across the file: log of the hourly midpoint on required-cert indicators, role, metro, a coarse experience band, and franchise status. A cert with fewer than 8 required postings does not get a price. The coefficient can still be shown, with the N, so a reader can see that the interval is too wide to use.

    “Associated with” is the verb wherever the card cannot be separated from the rest of the posting. One clean dollar per cert was the failure mode this design was written to avoid.

    The dataset

    48 rows. 47 URLs. One Spyder Construction page in Littleton stated two bands, technician and lead, and is two rows. Five of these rows were added after a browser pass over Indeed, and only after this run fetched a page that itself stated the pay. The other names from that pass had no posting URL, or the page did not return a current band. They are in the rejects log.

    Read on 2026-10-24, except four pages that printed their own posted date: Right-Now Restoration of Seattle (2026-08-25), Kustom US in San Diego (2026-03-11), A1 Restoration of San Diego (2026-07-15), A1 Restoration of Dallas (2026-03-20). Those four were still up when read. A March posting read in October can be stale. It is in the file because the page still stated the pay.

    Metro Rows
    Seattle–Tacoma, WA 9
    Phoenix, AZ (Buckeye and Chandler included) 7
    Denver, CO (Littleton, Englewood, and Lakewood included) 9
    Chicago, IL (Schaumburg, Niles, New Lenox included) 5
    San Diego, CA (San Marcos included) 4
    Dallas, TX (Fort Worth included) 4
    Tampa, FL (Thonotosassa included) 4
    Atlanta, GA (Woodstock, Norcross, Alpharetta included) 3
    Boise, ID (Nampa, Meridian included) 2
    Spokane, WA 1

    Roles: 22 water/mitigation technicians, 18 lead technicians or crew chiefs, 8 project managers, 0 mold remediation technicians. Mold work is inside the water and lead ads. It never arrived as its own paid posting.

    Employers: 34 franchise, 14 independent, 0 carrier-program. Franchise pages (CareerPlug for SERVPRO, Paul Davis, ServiceMaster, PuroClean, Restoration 1, Rytech, AdvantaClean, Voda) were the pages that actually opened. Indeed returned HTTP 401. ZipRecruiter returned HTTP 403.

    The target was 120. The file stops at 48 because the rest of the leads did not survive a page read. The rejects are in the linked rejects log. The sample was not padded.

    Posted hourly midpoints, before any cert split: technicians median $22.50 (N=22, range $16.50–$29.50), leads median $27.00 (N=18, range $22.50–$33.65), project managers median $34.50 an hour (N=8, range $25.00–$42.50). The project-manager median includes two hourly postings: SERVPRO of Morton Grove / East Niles at $22–$28, and Greenwood Heating in Everett at $40–$45. The other six PM bands are annual. Their median midpoint is $71,750.

    Per-cert findings

    Status counts across all 48 rows:

    Cert Required Preferred One of a list Not mentioned
    WRT 8 14 1 25
    ASD 1 12 0 35
    AMRT 2 6 0 40
    FSRT 4 9 1 34
    OCT 0 1 1 46
    HST 0 0 0 48

    Four more rows require an IICRC card without making one named cert mandatory. Restoration 1 of North Fort Worth, MVP Restoration, and SERVPRO of Morton Grove / East Niles name no cert. All Pro in Denver requires at least one of WRT, OCT, CCT, or FSRT. Eleven rows prefer an IICRC card and do not name it. One, a SERVPRO of Aurora Central technician posting, tells the hire to go get the card after starting. Those unnamed cards are not assigned to WRT.

    The regression below is log(hourly midpoint) on a required-cert indicator for each of the four named certs, plus lead, project manager, metro, experience (none / some / two-years-or-more), and franchise. Reference row: technician, Seattle–Tacoma, experience not required, independent. N=48. R²=0.80. The fit is high because role and metro explain the wage. The cert intervals are the part that does not.

    WRT

    WRT is the only named cert that reaches the pre-registered floor of 8 required postings. The adjusted association is about −3.9%, and the 95% interval runs from −18.4% to +13.1%. That interval is the headline range. It covers a raise, a cut, and zero. It is not a price. Adding the five verified pages from the browser pass moved the point estimate down from the first-pass figure, because the new high bands do not require WRT. The interval still covers zero.

    The eight required rows are not eight clean WRT screens.

    • Paul Davis of Tacoma, lead, $28–$32, 2 years, WRT only (row 6).
    • Paul Davis of Greater Phoenix, lead, $26–$32, 2 years, WRT required, ASD and FSRT preferred (row 10).
    • SERVPRO of Buckeye, crew supervisor, $24–$26, 2 years, WRT only (row 15).
    • Bill Howe, San Diego, lead, $25–$30, 5 years, WRT only (row 17).
    • ServiceMaster by Weibye, Boise, lead, $20–$25, 3 years, WRT and FSRT. The sentence says required, and it sits under the heading “Preferred Qualifications” (row 42).
    • A1 Restoration of Seattle, technician, $27–$31, prior experience, WRT + FSRT + AMRT together (row 2).
    • Spyder Construction, Littleton, lead, $24–$30, 2 years supervising, WRT + FSRT + AMRT together (row 26).
    • ServiceMaster of Seattle, project manager, $72,000, 2 years, page spells them WTR, ASD, and FRST (row 7).

    Every ASD, AMRT, or FSRT requirement in this file sits inside a WRT requirement. No posting asked for the advanced card by itself. The separate coefficients later in this draft are splits of that stack. They are not four prices.

    Inside a single role and metro, the WRT contrasts that exist are one posting against one posting. All of them fail the size rule.

    • Denver leads: Spyder required, midpoint $27.00, against three leads that do not mention WRT (All Dry $27.00, SERVPRO of Aurora Central $24.00, BMS CAT $24.00). The not-mentioned median is $24.00. Delta $3.00 an hour, about 12%. Two of those three prefer an unnamed IICRC card. N=1 and 3. Still under 4 on the required side.
    • San Diego leads: Bill Howe required, midpoint $27.50, against Paul Davis of North County, WRT not named, midpoint $24.00. Delta $3.50 an hour, about 15%. Bill Howe also asks for 5 years. N=1 and 1.
    • Seattle–Tacoma leads: Paul Davis of Tacoma required, midpoint $30.00, against Paul Davis of Greater Seattle, which pays for the class instead of requiring the card, midpoint $27.50. Delta $2.50 an hour, about 9%. The Tacoma ad also asks for 2 years in restoration. The Lynnwood ad asks for 1 year in a trade. N=1 and 1.

    Held inside the lead title and pooled across metros, the six WRT-required leads have a median midpoint of $27.25. The seven leads that do not mention WRT have a median midpoint of $25.75. Delta $1.50 an hour, about 5.8%. Several of those seven prefer an unnamed IICRC card. Set those aside and the three fully silent leads — Paul Davis Lynnwood at $27.50, All Dry Denver at $27.00, PuroClean Woodstock at $26.00 — have a median of $27.00. Delta $0.25 an hour. Same job family, card required or not, the posted midpoint barely moves.

    The tempting technician gap is one row. The only technician posting that requires WRT is A1 of Seattle at a $29.00 midpoint, and it also requires FSRT and AMRT. The median technician posting that does not mention WRT is $21.00 (N=12). Delta $8.00 an hour, about 38%. That is the ad, not the cert. The adjusted model, which can see that this row is a stack in a high-wage metro, does not turn it into a WRT price.

    Fourteen other postings prefer WRT and will hire without it, or will pay for the class. Preference is common. A hard WRT screen is not.

    ASD

    ASD is required on one posting: the ServiceMaster of Seattle project manager, stacked with WRT and FSRT (the page’s FRST). N=1. The fitted coefficient is about +8.5%, and the interval runs from −28% to +64%. That interval is what a single stacked row does to a regression. It is not a range anyone should quote as the value of ASD. Twelve postings prefer ASD. Thirty-five do not mention it. No role × metro cell has an ASD contrast with both groups large enough to use.

    AMRT

    AMRT is required on two postings, both stacks: A1 of Seattle (with WRT and FSRT) and the Spyder lead (with WRT and FSRT). N=2. The fitted coefficient is about +40%, interval −4% to +105%. Too thin to conclude. The Denver lead contrast is Spyder at $27.00 against four leads that do not mention AMRT, median $25.50, delta $1.50 an hour, about 6%. N=1 on the required side. Six postings prefer AMRT. Forty do not mention it.

    FSRT

    FSRT is required on four postings: the two stacks above, the ServiceMaster of Seattle project manager, and the Boise ServiceMaster lead whose “required” sentence sits under a preferred heading. N=4, under the floor of 8. The fitted coefficient is about −23%, interval −46% to +10%. The sign flips relative to AMRT because the model is pulling one stack apart. That is collinearity, not a finding that FSRT pays less. Inside Seattle–Tacoma project managers the only contrast is ServiceMaster at a $34.62 midpoint, which requires FSRT, against Greenwood Heating at $42.50, which does not mention FSRT. Delta about −$7.88 an hour. N=1 and 1. Greenwood is a department supervisor at a home-services company, not the same job as the ServiceMaster posting, and the cell is too small to use. Nine postings prefer FSRT. One, All Pro in Denver, will accept FSRT as one of several cards. Thirty-four do not mention it.

    The same All Pro posting is the only OCT appearance that treats the card as a way in the door: at least one of WRT, OCT, CCT, or FSRT, preferably two, pay $21–$26. PuroClean of North Seattle prefers OCT and does not require it. HST is absent from all 48 pages.

    A coarser indicator — any of the four named certs required — has the same eight rows, because the advanced cards never appear without WRT. Its adjusted association is about −5.1%, interval −16.2% to +7.4%. Drop the six template-cluster rows (four A1-boilerplate ads, two near-duplicate “you are IICRC certified” ads in Fort Worth) and the association on the remaining 42 is about −10.3%, interval −22.6% to +3.9%. Both intervals cover zero.

    What the regression can see is the job, not the card. Project manager, relative to technician, is about +51% (interval about +34% to +71%) in the full model. That coefficient has eight postings behind it, including an hourly band at $22–$28 and a department-supervisor band at $40–$45, so it is a sample fact, not a national PM premium. It is large enough to show why a cert study that ignores title will call a promotion a certificate.

    The employer side

    This is eligibility, not a percent.

    On Accuserve’s own contractor page (https://www.accuserve.com/contractor, read 2026-10-24), water-mitigation membership requires an IICRC WRT technician on site for every visit. ASD is preferred and should be held by someone in the company. Mold remediation requires AMRT, plus whatever the state or locality requires. The same page also requires insurance limits, background checks, a weighted extractor, and two kinds of moisture meter. The card is one gate in a list. The page does not attach a wage to it.

    A second Accuserve page, the re-inspection protocol posted May 9, 2024, asks the inspector on a disputed water loss for WRT and ASD, and for AMRT when the issue is mold. That is a credential for a specific assignment, stricter on ASD than the join-page preference. Both are on Accuserve’s site. They are not the same rule, and neither is a pay scale.

    Contractor Connection’s requirements URLs, fetched the same day, returned a homeowner matching page. The certification matrix was not on the page. Alacrity’s join URL returned HTTP 404. Sedgwick, Lionsbridge, and BrightServ were not opened on a program-owner page that named a cert. Trade blogs that say every program requires WRT were not used. One verified program gate is the finding. A percentage of programs is not.

    The two anchors

    Larsen’s model, as printed in Lorne McIntyre’s April 20, 2022 Restoration & Remediation article “Building a Sustainable Restoration Workforce” (https://www.randrmagonline.com/articles/90069-building-a-sustainable-restoration-workforce), adds a percent of the project manager’s base, at a tenure stage, for each card earned.

    • Technician assistant, months 3–9, is at 37% of PM base. WRT adds 4 points of PM base. FSRT adds 4.
    • Technician apprentice, months 9–18, is at 45% of PM base. ASD adds 5.
    • Restoration technician, months 18–36, is at 55% of PM base. AMRT adds 5. OCT adds 3. HST adds 3.

    Four points of the PM’s base is not a 4% raise on the technician’s check. At the assistant stage, 4 / 37 is about 11% of that stage’s pay. ASD’s 5 points on a 45% stage is about 11% of that stage’s pay. AMRT’s 5 points on a 55% stage is about 9% of that stage’s pay. The article is explicit that this is one restorer’s recommendation, tied to a career path, not a measured market wage.

    Applied to the one single-figure PM base in this file, ServiceMaster of Seattle at $72,000, Larsen’s WRT step is 4% × $72,000 = $2,880 a year, or $1.38 an hour at 2,080 hours. The ASD or AMRT step is 5% × $72,000 = $3,600 a year, or $1.73 an hour. Applied to the median of the six annual PM midpoints in this file ($71,750), the same steps are $2,870 and $3,587.50 a year. Those are illustrations of Larsen’s rule on observed PM bases. They are not posting premia.

    Agreement: several franchise ads in this file say the band moves with certifications (Paul Davis of Tacoma, SERVPRO of Buckeye, PuroClean of Boise, ServiceMaster of Seattle’s spelling variants). They do not print the step. Larsen’s direction — the card is a reason to move someone up a ladder — matches that language.

    Disagreement, stated as far as the postings can carry it: no page read here publishes a 4% or 5% step, and the adjusted association of a WRT requirement with the posted midpoint is an interval from −18% to +13% that includes zero. The lead-title comparison, the closest thing to holding the job still, is $0.25 to $1.50 an hour depending on how strictly “not mentioned” is drawn. That is smaller than an 11% step on a $27 lead midpoint (11% of $27 is about $3 an hour), and the sample is too small to rule Larsen’s step out. The postings do not confirm it. They also describe a different object: a hiring screen on a band, not a raise after someone already on the crew earns the card.

    Franchise ladder: HOLD. No corporate pay ladder was read on SERVPRO, Paul Davis, ServiceMaster, PuroClean, or 911 Restoration’s own site. A WayUp copy of a 911 Restoration schedule in Appleton, Wisconsin, was outside the sample and was not the employer’s page. It is not an anchor.

    What this study cannot say

    The card is bundled with the rest of the ask. The eight WRT-required ads are leads, a project manager, or a technician who must also hold FSRT and AMRT. Experience rides along: 2 years, 3 years, 5 years. A regression with 48 rows and a stack of dummies does not unbundle that. The interval around zero is the honest summary of the unbundling this file can support.

    Silence is not zero. “Not mentioned” means the posting did not use the named cert as a screen. The hired person may already hold it. Preferred, which is where WRT actually lives in this file (11 ads), is a third state and was kept out of the contrast on purpose.

    A posting is not a paycheck. Bands are recruiting statements. Rytech of Seattle prints $20–$37. SERVPRO of Oldsmar / Westchase prints $50,000–$85,000. The midpoint treats those as one wage. All Pro’s $55,000–$65,000 and DRYCOR’s $62,000 are bonus illustrations on the page, and they were not used as the band. Overtime, on-call bonuses, and production pay are outside the midpoint.

    Metro price levels differ. The model includes metro indicators for that reason. A national dollar gap would have mixed Seattle with Tampa. The technician median in this file is $22.50, and one Atlanta technician ad prints $16–$17 with a blank in the body and $16.00–$17.00 in the footer. That row is kept because it is what the page printed. It pulls Atlanta down. It is one row.

    Pay-transparency laws are not the whole selection story. Washington, California, Colorado, and Illinois account for 27 of 48 rows. Phoenix, with no statewide mandate in view here, still contributed 7, because franchise career pages stated pay anyway. Spokane, inside a disclosure state, contributed 1. The binding limit was which pages opened, not only which states require a number.

    Four A1-family ads share a boilerplate paragraph and are flagged a1-boilerplate in the CSV. Two Fort Worth ads share the sentence “You are IICRC certified” and are flagged you-are-iicrc-certified. They are real pages with different pay. They are not six independent wage policies. The sensitivity that drops them still covers zero.

    ServiceMaster of Seattle spells the cards WTR and FRST. ServiceMaster Phoenix spells the water card WTR. Those were coded as WRT and FSRT, and the page spelling is in the notes. Paul Davis of NW Chicago lists ORT among preferred extras. ORT was not coded as OCT. Restoration 1 of Chicago Southland lists MRST. MRST was not coded as AMRT. Paul Davis of Greater Seattle offers paid training in “IICRC FRST” and was not coded as requiring FSRT.

    No cell in this file can support the sentence “the cert is worth this much.” The sentence the file supports: a named IICRC requirement, as these employers wrote it in October 2026, is associated with a posted-wage gap that this sample cannot distinguish from zero, once role, metro, and a coarse experience control are in the equation. The place the card shows up cleanly is on the employer’s side of the market, as a gate Accuserve publishes for who may take the work.

    The full table

    R = required on the page. P = preferred, including “or willingness to obtain.” 1of = accepted as one of a list, not required by itself. A dash means the named cert is not mentioned. Unnamed IICRC language is in the CSV column generic_iicrc and is not in this grid. Experience bands: none, y1, y2, y3, y5, or stated without a year count. URLs and notes are in the CSV. Row 25 and row 26 are one Spyder URL.

    ID Metro Employer Role Posted pay WRT ASD AMRT FSRT OCT Exp
    1 Seattle-Tacoma Paul Davis Restoration of Greater Seattle Lead $25–$30/hr — — — — — y1
    2 Seattle-Tacoma A1 Restoration of Seattle LLC Tech $27–$31/hr R — R R — stated
    3 Seattle-Tacoma Right-Now Restoration of Seattle LLC Tech $20–$26/hr P — P P — none
    4 Seattle-Tacoma Rytech of Seattle Tech $20–$37/hr P P — — — none
    5 Seattle-Tacoma PuroClean of North Seattle Lead $26–$30/hr P P P P P y2
    6 Seattle-Tacoma Paul Davis Restoration of Tacoma Lead $28–$32/hr R — — — — y2
    7 Seattle-Tacoma ServiceMaster of Seattle PM $72,000/yr R R — R — y2
    8 Seattle-Tacoma Paul Davis Restoration of Greater Seattle Tech $20–$25/hr P P P P — none
    9 Phoenix SERVPRO of Buckeye Tech $19–$22/hr — — — — — none
    10 Phoenix Paul Davis Restoration of Greater Phoenix Lead $26–$32/hr R P — P — y2
    11 Phoenix ServiceMaster Restore 10262 – Phoenix Tech $19–$21/hr P P — — — none
    12 Phoenix Paul Davis Restoration of Greater Phoenix Tech $20–$24/hr — — — — — none
    13 Phoenix Voda Cleaning & Restoration of Phoenix Tech $20–$25/hr P — — — — y1
    14 Phoenix Restoration 1 of Phoenix Tech $20–$28/hr — — — — — none
    15 Phoenix SERVPRO of Buckeye Lead $24–$26/hr R — — — — y2
    16 San Diego Kustom US Inc Tech $25–$34/hr — — — — — y1
    17 San Diego Bill Howe Plumbing, Heating & Air, Restoration & Flood Lead $25–$30/hr R — — — — y5
    18 San Diego A1 Restoration of San Diego LLC Tech $20–$25/hr P P P P — none
    19 San Diego Paul Davis Restoration of North County San Diego Lead $20–$28/hr — — — — — stated
    20 Dallas A1 Restoration of Dallas LLC PM $65,000–$78,000/yr — — — — — stated
    21 Dallas Restoration 1 of North Fort Worth Tech $20–$25/hr — — — — — stated
    22 Dallas MVP Restoration, LLC Tech $19–$24/hr — — — — — stated
    23 Dallas ServiceMaster Restore by Restoration Specialists Tech $18–$25/hr P P — P — none
    24 Denver All Dry Water Damage Experts Lead $26–$28/hr — — — — — y2
    25 Denver Spyder Construction Tech $22–$26/hr — — — — — stated
    26 Denver Spyder Construction Lead $24–$30/hr R — R R — y2
    27 Denver All Pro Restoration DBA Rinco, Inc. Tech $21–$26/hr 1of — — 1of 1of stated
    28 Denver SERVPRO of Aurora Central Tech $18–$23/hr — — — — — none
    29 Chicago Paul Davis of NW Chicago Lead $24–$30/hr P P P P — y2
    30 Chicago SERVPRO of Central Schaumburg/West Bloomingdale Lead $24–$27.50/hr — — — — — y2
    31 Chicago SERVPRO of Morton Grove and East Niles PM $22–$28/hr — — — — — y2
    32 Chicago Restoration 1 of Chicago Southland Lead $25–$28/hr P P — P — y2
    33 Chicago Restoration 1 of Chicago Southland Tech $18–$20/hr — — — — — none
    34 Atlanta AdvantaClean of Norcross and Buford PM $70,000–$85,000/yr — — — — — y3
    35 Atlanta PuroClean of North Metro Atlanta Lead $26/hr — — — — — y2
    36 Atlanta SERVPRO of North Fulton Tech $16–$17/hr — — — — — none
    37 Tampa Paul Davis Restoration of Tampa PM $60,000–$75,000/yr — — — — — stated
    38 Tampa SERVPRO of Oldsmar / Westchase PM $50,000–$85,000/yr — — — — — y3
    39 Tampa DRYCOR RESTORE Tech $17.50–$22/hr — — — — — y3
    40 Tampa PuroClean of Tampa Palms Tech $17–$24/hr — — — — — none
    41 Spokane Paul Davis Emergency Services of Spokane Valley PM $70,000–$100,000/yr — — — — — stated
    42 Boise ServiceMaster Quality Cleaning by Weibye Lead $20–$25/hr R P — R — y3
    43 Boise PuroClean of Boise Lead $26–$30/hr P P P P — stated
    44 Seattle-Tacoma Greenwood Heating and Home Services PM $40–$45/hr P P — — — none
    45 Denver SERVPRO of Aurora Central Lead $22–$26/hr — — — — — y1
    46 Denver SERVPRO of Denver Southeast Tech $22–$25/hr P — — — — none
    47 Denver BMS CAT Lead $22–$26/hr — — — — — stated
    48 Denver Rytech of Denver Lead $60,000–$80,000/yr P — — — — y2

    Rows 9, 14, 16, 19, 21, 22, 25, 28, 30, 31, 33, 36, 38, 45, and 47 carry unnamed IICRC language (preferred, required, or “seek it after hire”) that this grid does not show. Read generic_iicrc and notes in the CSV before treating a dash as “this employer does not care about a card.”

    Friction log and debrief

    Blocked sources. Indeed (HTTP 401), ZipRecruiter (HTTP 403), LinkedIn (not opened). Those three were supposed to carry the sample. Franchise career pages and a handful of Paylocity, Rippling, and JobTarget pages were what actually returned a job body with a dollar figure. Career.com timed out on the one CRC Seattle URL that looked usable. Glassdoor was outside the source list and was not used, even where an index showed an employer-provided band.

    Shell pages. A recurring CareerPlug failure: the URL resolved, and the body was the franchise welcome page, with no job and no pay. Search indexes of several of those URLs contained a pay figure. Those figures stayed out. The rejects log names each URL. This is the same failure mode as an earlier snippet pass, caught at the fetch.

    Thin cells. Every within-cell cert contrast is 1 against 1. Mold is empty in all 10 metros. Spokane has a project manager only. Boise has two leads and nothing else. Dallas has no lead. Denver, Phoenix, and San Diego have no project manager with a readable band in the opened set. Atlanta’s technician cell is one ad at $16–$17. No cell clears 4 on each side of a cert contrast. The pre-registered rule was to say so and not borrow a gap from another city. That rule bound.

    What a second pass fixes. A browser session that can pass Indeed and ZipRecruiter, or a data pull the boards license, is the difference between 48 and 120. The Seattle-through-Denver browser pass still could not supply Indeed URLs for 19 of the 20 ads it named. Those ads stayed out. The Chicago-through-Boise browser pass stopped before it returned a single posting, so those five metros were not added to. Pay-transparency states will still over-contribute if the pull is public postings, and that should stay as a reported bias rather than a weight invented after the fact. The second pass should also open the current Contractor Connection, Alacrity, and Sedgwick contractor manuals on the program owner’s domain. Those three were holds, not findings. A franchise corporate compensation guide, if one exists on the franchisor’s own site, is the missing ladder next to Larsen. Calling ten employers and asking what they added to the check when a tech passed WRT would measure the object Larsen wrote down. This file measures the object the postings contain, which is a hiring screen on a band.

    What this pass should not be asked to do. It should not be rounded into one dollar per card. The publishable unit from these 48 pages is the WRT interval, −18% to +13%, N=8, with ASD, AMRT, and FSRT left unpriced because they never appear except on top of WRT and their counts are 1, 2, and 4.

    The homework, in files

    The full dataset — all 48 postings, with employer, metro, role, the band as printed, each cert’s status on the page, experience requirement, and the source URL — is published with this article: cert-value-dataset.csv. The rejects log — the blocked sources, the shell pages, and every lead that did not survive a page read — is here: cert-value-rejects.txt. The method is the second section of this article; the limitations are stated in “What this study cannot say,” and they are part of the finding.

    Related, on this site: the IICRC certification and restoration training guide this measurement was built to inform.

  • The Agent-Ready Site: What Kin’s WebMCP Launch Means for Every Business Website

    The Agent-Ready Site: What Kin’s WebMCP Launch Means for Every Business Website

    On October 23, 2026, Kin Insurance became the first U.S. home insurer to enable WebMCP in its quoting experience — an open web standard that lets an AI agent work directly with kin.com, so a homeowner can tell ChatGPT "help me shop for home insurance" and get back a real quote. Strip away the insurance details and what remains is a pattern every business website is about to be measured against: is your site built for the agent your customer sends?

    Most businesses are still arguing about whether to let agents in. Kin skipped that argument. The interesting question is what its launch is made of, layer by layer — because three of the four layers are already visible in our own fleet's numbers.

    Layer 1: Decide to welcome the machine

    Agent traffic is not coming; on our own sites it is already the majority — roughly 62% of visits across the fleet we run are bots and agents, not people. The only choice left is whether that traffic meets a door or a wall.

    Kin chose the door, publicly and in advance: it had already announced that AI shopping agents are welcome on kin.com rather than blocked, naming Meta's Muse among them. The opposite choice exists in the same industry — in September, insurance marketplace Insurify blocked Muse from its comparison platforms, arguing an agent could pull a price stripped of the context that makes it meaningful. Both are coherent positions. What is no longer available is having no position: a site that has not decided is a site whose default settings decide for it.

    Layer 2: Structure the content so a machine can carry it accurately

    An agent can only repeat what it can read, so the agent-ready site is built out of answers, not brochures: one real question per page, paragraphs that stand alone as complete ideas, and structured data underneath that states the facts in machine-readable form.

    This is the layer we work in every day, and it is unglamorous, mechanical work. Tonight, on one operator site in our fleet, we finished putting structured FAQ data — drawn from each page's own questions and answers, verbatim — onto 155 of its 166 articles, because agents cite what is structured and skip what is implied. Multiply that instinct across every page a business owns and you have the content layer of agent-readiness: nothing important lives only in an image, a video, or a sales conversation.

    Layer 3: Give the agent a way to act, not just to read

    WebMCP is the layer most sites do not have yet: the site declares the actions an agent may take — get a quote, with these inputs, in this order — so the agent executes a designed path instead of improvising clicks across a human interface.

    Kin's version is a quote flow, and its testing shows why the layer matters: agents reached a finished quote after asking the consumer only a handful of questions, because the path was declared and the carrier's data filled the rest. The equivalent for any business is the moment a visit becomes a transaction — a booking, a quote, an order. Our own commerce thinking already runs on two rails, one built for humans at a checkout and one an agent can complete; Kin just shipped the insurance version of the second rail, first.

    Layer 4: Measure what the machines do

    Agent-readiness you cannot measure is a vibe. Kin will know whether agents quote it, because the protocol makes agent sessions countable; the rest of us measure the read layer — which pages agents cite, which questions they bring, how the share moves.

    On tygartmedia.com, we track AI citations from our own search-engine exports rather than a vendor's estimate: 1,459,726 citations across 922 cited pages in the October 15 export, up from 269,399 across 324 pages in the September 27 export. Those numbers are the scoreboard for layers 1 and 2. The day an agent can transact here, layer 3 gets a scoreboard of its own.

    Where our fleet honestly sits

    Layers 1, 2, and 4 are running here today — welcome posture, structured content, citation measurement. Layer 3, declared agent actions, is what Kin shipped first, and it is the next build. That is a fair summary of most of the web right now: readable by agents, citable by agents, and still requiring a human to show up for the transaction itself.

    The businesses that treat that gap as a roadmap, rather than a surprise, are the ones whose sites will be ready when their customers stop browsing and start sending.

    Frequently asked questions

    What is WebMCP? An open web standard that lets an AI agent interact with a website through a machine-usable path the site itself declares — no plug-in and no screen-scraping. Kin enabled it in its home insurance quoting experience on October 23, 2026, the first U.S. home insurer to do so.

    What makes a website "agent-ready"? Four layers: a deliberate decision to welcome agent traffic instead of blocking it by default; content structured as standalone answers with machine-readable data underneath; a declared path that lets an agent complete an action, such as a quote or booking; and measurement of what agents actually do on the site.

    Do agents really visit business websites that much? On the fleet we operate, roughly 62% of visits are bots and agents. The share varies by site, but the direction does not: the reader a growing share of your pages serve first is a machine deciding what to show its human.


    Source: Kin Insurance announcement via PR Newswire, October 23, 2026. Fleet figures are Tygart Media's own: bot share from our site analytics; citation counts from our Bing AI Performance exports of September 27 and October 15, 2026.