Tag: Restoration Industry

  • Flash Flood Warning: Idaho Falls Area Until 2 AM MDT

    Flash Flood Warning: Idaho Falls Area Until 2 AM MDT

    A Flash Flood Warning is active right now for the Idaho Falls area. The National Weather Service in Pocatello issued it at 10:00 PM MDT on Thursday, September 17, and it runs until 2:00 AM MDT on Friday, September 18. Doppler radar is showing thunderstorms producing heavy rain across north central Bonneville County and south central Jefferson County, and flash flooding is ongoing or expected to begin shortly. These are exactly the storms that produce the interior water-intrusion jobs restoration teams see most — water finding its way into living spaces in the middle of the night. This is a live snapshot as of 12:06 AM MDT on Friday, September 18. Conditions change fast — always verify with the National Weather Service for your specific county or ZIP code.

    Idaho Falls area — Flash Flood Warning

    Issued by: National Weather Service, Pocatello, Idaho — 10:00 PM MDT Thursday, September 17.
    Expires: 2:00 AM MDT Friday, September 18.
    Covers: North central Bonneville County and south central Jefferson County in southeastern Idaho.

    At 10:00 PM MDT, Doppler radar indicated thunderstorms producing heavy rain across the warned area. The National Weather Service says flash flooding is ongoing or expected to begin shortly.

    Hazard: Flash flooding caused by thunderstorms.
    Source: Radar indicated.

    Expected impacts: Flash flooding of small creeks and streams, urban areas, highways, streets and underpasses, as well as other poor-drainage and low-lying areas. In practical terms: the underpasses and low dips around Idaho Falls, ponding on streets in Rigby and the smaller towns, and any creek or drainage running high after this rain.

    Locations in the warning path: Idaho Falls, Rigby, Lorenzo, Ucon, Menan and Lewisville.

    Also active nearby — Big Rock burn scar warning: At 10:25 PM MDT, NWS Pocatello issued a separate Flash Flood Warning for the Big Rock burn scar in southeastern Jefferson County and south central Madison County, running until 2:30 AM MDT. Thunderstorms are producing heavy rain over the burn scar, and the Weather Service warns of life-threatening flash flooding with debris flow — rock, mud, vegetation and other loose materials — moving through the scar. Some locations affected include Heise. Roads and driveways may be washed away in places. If you are anywhere near the burn scar area and encounter flood waters, climb to safety immediately. This one is the more dangerous of the two warnings tonight.

    Stay safe tonight

    Turn around, don’t drown. Most flood deaths occur in vehicles — never drive through flooded roadways, and never try to guess the depth of water over a road at night. The National Weather Service’s rule of thumb: six inches of moving water can knock an adult off their feet, and twelve inches can carry a car.

    If water gets into your home: stay out of standing water anywhere electricity may be present, and stay out of the basement until the water recedes and the power is confirmed off. Photograph everything before you touch anything — documentation matters for insurance. Then call a local restoration contractor. Water left sitting starts a second wave of damage within a day, and the clock on that starts the moment the rain stops, not the moment you discover it.

    What this means for restoration teams

    This is the signature southeastern Idaho night for water work: radar-indicated storms, urban and small-stream flooding, and a warning window that runs past 2:00 AM. Expect the calls to start as water recedes and keep coming for days as people discover what happened overnight. The damage categories to plan for: interior water intrusion through foundations, window wells and door thresholds; saturated drywall and insulation in finished basements; mold risk inside 24 to 48 hours on anything that stays wet; and sewage backup in low-lying areas where storm drains surcharge.

    The play tonight: stage equipment now rather than at first call. Pre-position drying assets — air movers, dehumidifiers, extraction — so the first truck rolls complete. Keep an on-call rotation through the morning, because the discovery curve on overnight flooding peaks after sunrise. On the first call, capture the address, the water source, and every affected area before you quote anything.

    Field discipline, same as always: photo-document before mitigation begins, moisture-map every affected room (not just the visibly wet one — water travels inside wall cavities), and keep the homeowner’s payment responsibility clear in writing before work starts. Night jobs with stressed homeowners are where scope misunderstandings are born.

    Local emergency contacts

    Bonneville County Emergency Management: (208) 529-1220 — bonnevillecountyidaho.gov/county-departments/emergency-management
    Life-threatening emergency: 911
    Bonneville County non-emergency dispatch: (208) 529-1200
    Idaho Office of Emergency Management: ioem.idaho.gov

    FEMA and federal assistance

    If the flooding damages your home and you need help beyond what insurance covers, the FEMA Helpline is 1-800-621-3362, open 7 a.m. to 10 p.m. local time, seven days a week. You can also apply at DisasterAssistance.gov, through the FEMA app, or find a recovery center at fema.gov/drc.

    Basic eligibility: U.S. citizenship or qualified status, identity verification, proof of occupancy or ownership, and unmet needs not covered by insurance. Don’t wait — apply as soon as it’s safe.

    Looking ahead

    The Idaho Falls warning expires at 2:00 AM MDT, and the neighboring burn scar warning at 2:30 AM MDT. When a warning expires, that doesn’t mean the water is gone — small creeks and streams often crest after the rain ends, and saturated ground means any additional round of storms overnight floods faster than the first. Storms can arrive in multiple rounds overnight, so watch the NWS Pocatello page for extensions or new warnings.

    For contractors: the demand window on this kind of event opens within hours of water receding and stays open for days. Homeowners discover basement water in the morning, call around midday, and the serious mitigation decisions land over the weekend. Be reachable, be first with the moisture map, and be the contractor who documented everything.

    Sources and how to verify

    NWS Pocatello office page — warnings, updates and extensions post here first.
    weather.gov — enter your ZIP code for the warnings covering exactly where you are.
    Alert data via the National Weather Service API (api.weather.gov), warnings active as of 12:06 AM MDT Friday, September 18.

    To verify for your own county or ZIP: open weather.gov, enter your ZIP, and read the active alerts banner at the top of the page. If Bonneville or Jefferson County is listed, this warning covers you.

    This post is for informational purposes and is not an official weather warning. Always follow instructions from local authorities and the National Weather Service. Stay weather-aware around flash flooding — turn around, don’t drown.

  • Storm Updates: Arizona + Southeastern Utah Flash Flood Outbreak — Tuesday, September 16, 2026

    This is a live storm update and search-demand pulse for Tuesday, September 16, 2026. A monsoon outbreak produced two flash-flood clusters: eight NWS Flash Flood Warnings across Arizona (issued 10:27–11:51 AM MST) covering Maricopa County (Phoenix metro), Pinal County, Pima County (Tucson area), Gila County, and Coconino County (Labyrinth/Face Canyon watersheds), plus two warnings for southeastern Utah’s San Juan County drainages south of Lake Powell (issued 12:01 and 12:34 PM MDT). Several Arizona warnings were tagged life-threatening, with 0.5–1.5 inches already fallen and rates up to 2 inches per hour.

    Flash flooding in desert washes and slot-canyon country moves fast. Verify local conditions with the National Weather Service before travel. Turn around, don’t drown.

    Cluster 1 — Arizona

    Warnings spanned Phoenix metro through Tucson and north into Coconino watersheds. Heavy monsoon cells dumped short-duration, high-rate rain onto urban pavement and desert soils that shed runoff into washes and underpasses.

    Arizona Search Demand (measured live)

    Google Trends pulls (live browser, no CAPTCHA) show East Valley hire-intent leading the state:

    SignalWindowReading
    water damage restoration mesa az7d+850%
    water damage restoration mesa7d+450%
    Mesa (city topic)7d+400%
    Glendale (city topic)7d+250%
    Cost (topic, seed: flood damage repair)7d+250%
    flood damage restoration30d+170%
    water damage restoration phoenix az7d / 30dBreakout
    flood damage restoration near me / flood restoration near me / flood restoration companies30dBreakout

    Trending Now (Arizona, past 7d): “flood watch” 20K+ searches / +1,000% (active); “flash flood warning” 500+ / +1,000% and 200+ / +800%. Hottest metros: Phoenix AZ 100 · Yuma AZ–El Centro CA 81 · Tucson (Sierra Vista) AZ 67. City-level breakout query language also hit Tempe, Scottsdale, Tucson, and Phoenix AZ.

    Cluster 2 — Southeastern Utah

    Two warnings covered San Juan County drainages south of Lake Powell, including Labyrinth Canyon — life-threatening flash flooding of slot canyons and dry washes.

    Utah Search Demand (measured live)

    SignalWindowReading
    emergency water damage restoration30d+4,350%
    water damage restoration services30d+1,400%
    water damage restoration services near me30d+1,100%
    water damage restoration near me30d+750%
    water damage restoration service near me30dBreakout
    flood damage restoration near me / flood damage restoration7dBreakout
    flood restoration salt lake city30dBreakout
    water mitigation company30dBreakout

    What Homeowners Should Do in the First Hours

    • Stop the source if safe: Do not enter flowing washes or standing water near electrical panels.
    • Document high-water marks before cleanup for insurance.
    • Extract before you dry: Mud and silt first; air movers over wet sediment spread contamination.
    • Vet “near me” companies: Ask for IICRC certification, Category 3 blackwater protocol, and written moisture maps — East Valley and Utah “near me” breakouts show hire-intent, not DIY research.
    • Ask the cost question early: Arizona Cost topic +250% on flood damage repair means carriers and deductibles will dominate the next conversation.

    Sources and Verification

    Official data verified against National Weather Service Flash Flood Warnings for Arizona and southeastern Utah (10 warnings, new to the day’s watermark); Google Trends Arizona and Utah regional datasets (7-day and 30-day windows), measured live via browser with no CAPTCHA blocks.

    Informational brief only — not an official warning broadcast. Monitor NOAA Weather Radio and local county emergency management for evacuation and shelter orders.

  • Storm Updates: Rio Blanco County Colorado Flash Flood Warning — Sunday, September 13, 2026

    This is a live storm update and search demand pulse for Sunday night, September 13, 2026. The National Weather Service in Grand Junction, Colorado, issued a severe Flash Flood Warning for Rio Blanco County at 8:25 PM MDT, valid through 11:30 PM MDT. While localized runoff, wash flooding, and steep-terrain drainage pose immediate hazards across northwest Colorado’s Grand Junction–Montrose designated market area (DMA), search behavior across the wider state indicates a tightening baseline for water mitigation and flood repair demand.

    Flash flooding in high-desert and mountainous terrain moves fast and creates sudden structural washouts. Property owners and municipal managers must verify local conditions with the National Weather Service before traveling. Turn around, don’t drown.

    The Warning: Rio Blanco County, CO

    The Grand Junction weather forecast office issued the severe Flash Flood Warning following heavy rainfall over saturated soils and drainage basins in Rio Blanco County. Flash flooding in this geography typically impacts low-water crossings, county access roads, oil and gas pad infrastructure, and residential basements situated along creekbeds and alluvial fans.

    Official NWS Alert identifier: urn:oid:2.49.0.1.840.0.8acebba0f7c98d0a6a7482a49c065131956af988.001.1. The active warning contour spans uninhabited ranch land as well as municipal corridors, requiring local operators to track specific drainage axes rather than treating the county as a single uniform polygon.

    Colorado Search Demand & Trend Signal

    Search trend monitoring captured live query volume across Colorado within 40 minutes of warning issuance. Because hyper-local search volume for sudden events requires a 24- to 72-hour window to register on 7-day rising metrics, demand analysis looks at the broader 30-day baseline across Colorado to measure the demand basin pulling into regional contractor rosters.

    Breakout search terms across the state show intense user focus on contractor vetting and direct proximity queries:

    Breakout Search Query (Past 30d)Seed TopicDemand Context
    flood restoration companiesflood restorationHigh commercial & residential intent
    flood restoration company near meflood restorationImmediate emergency lookup
    flood damage restoration serviceflood restorationFull-scope service inquiry
    water damage restoration aurorawater damage restorationFront Range demand corridor
    water damage restoration aurora cowater damage restorationGeo-specific contractor intent
    water damage restoration company near mewater damage restorationMobile emergency conversion query
    water mitigation companieswater mitigationEarly-stage carrier / extraction focus

    By growth percentage, high-velocity queries across Colorado include water damage restoration service near me (+70%), restoration water damage company (+70%), and water damage restoration denver (+60%). Subregional activity highlights Denver, Colorado Springs–Pueblo, and Grand Junction–Montrose as the three most active DMAs in the state.

    What This Means for Restoration Teams

    Flash flood events in western Colorado create rapid silt, sediment, and Category 3 blackwater contamination when surface runoff penetrates crawlspaces, basements, and foundation slabs. Even if localized rainfall totals appear moderate, runoff volume through desert washes can breach grade rapidly.

    Key operational takeaways:

    • Immediate Containment: Mud and silt must be extracted before drying equipment is placed; running air movers over sediment aerosolizes particulate and bio-contaminants.
    • Moisture Mapping: Test perimeter subflooring and framing immediately. In dry climates like western Colorado, rapid surface evaporation frequently hides deep structural saturation behind baseboards and insulation.
    • Proximity Positioning: The breakout surge in “near me” search terms demonstrates that consumers call the first local verified provider they can reach. Verified phone lines and dispatch triage are critical.

    Sources and Verification

    Official data verified against: National Weather Service Grand Junction (weather.gov/gjt); NOAA National Weather Service Alerts API; Google Trends Colorado Regional Dataset (Past 7d and Past 30d windows).

    Informational brief only — not an official warning broadcast. Monitor NOAA Weather Radio and local county emergency management for evacuation and shelter orders.

  • The Best Claim Product Flags the Short-Pay Before the Job Closes

    The Best Claim Product Flags the Short-Pay Before the Job Closes

    The best product in claims is not another adjuster dashboard. It is the thing that shows the short-pay before the shop or the homeowner closes the file.

    That is not a slogan. It is how Texas SB 458, new Washington claims-handling rules, and the sudden cheapness of vertical agents rhyme. Three different surfaces. One failure mode. Nobody owns the photo set or the estimate map, so nobody demands the appraisal or the supplement in time.

    What actually changed in 2026

    Texas Senate Bill 458 added Chapter 1813 to the Insurance Code. For personal automobile and residential property policies delivered, issued, or renewed on or after January 1, 2026, the policy must contain a binding appraisal provision for disputes solely over the amount of loss. Either the policyholder or the insurer can demand it unilaterally. The amount determined by appraisal is binding except for fraud, accident, or material mistake. That is not a proposal. It is live statute for 2026 renewals.

    The Texas Department of Insurance has been working the implementing rules. Proposed 28 TAC §§5.9800–5.9806 set hard timelines: demand windows, appraiser naming periods, and outer deadlines for the award. Practitioner write-ups already treat the unilateral right as real for policies that renewed into the new year. Shops cannot file the demand themselves, but they can build the file, coach the customer, and stop leaving money on the table when the carrier will not move.

    Washington followed with clearer minimum claims-handling duties under WAC 284-30-390, effective October 18, 2026. Carriers cannot condition coverage on photo-only evaluation. Shops and policyholders gain process language they can cite when supplements stall or explanations stay thin. Illinois added its own amount-of-loss appraisal path in the same window. The pattern across states is consistent: regulators are tightening the rails around automated or virtual first looks while giving policyholders and shops clearer levers on the dollar amount.

    Florida lawmakers have already floated mandatory human review for claim denials. Oregon has guidance on virtual claim adjustment systems and when mobile apps can be required. The direction of travel is the same. Virtual is allowed. Pure automation of the denial or the lowball without a human gate is getting harder.

    At the same time OpenAI shipped the Agents API. Long-running sessions, tool use, recovery, and context management moved from something you build to something you rent. Greg Isenberg called it the AWS moment for agents. The hard engineering is now a line item. What remains scarce is ownership of one painful vertical workflow and the data that makes the next run better.

    The failure mode is the same as leakage

    In the leakage essay the problem was money that already left and no one owned the file. Here the money has not left yet. The carrier estimate or the initial offer is short. The shop or the homeowner has the photos and the line items, but the map of what is missing lives in no system they control. So the file closes at the low number, or the supplement fight starts late and under-documented.

    Collision shops already live this. Hail and storm work in restoration companies live this. The adjuster arrives with a photo-first or virtual process. The initial scope misses labor hours, OEM procedures, or secondary damage that only shows under proper light. The shop knows the number is low. The customer is tired. The clock on the new appraisal window is running. Without a clean first pass that flags the gap, the leverage created by SB 458 stays theoretical.

    The same pattern appears in residential storm claims. Sparse photo sets become lowball scopes. Dense, angled, scaled sets get paid. The difference is not magic. It is ownership of the evidence map before the carrier’s first number hardens.

    The wedge is a free checker, not a platform

    Do not start with a claims management system. Start with the moment the customer already hates.

    Upload the carrier estimate PDF. Or upload the set of damage photos taken the same day. Thirty seconds later: missing line items, density patterns that usually support higher repair hours, scale problems that virtual adjusters systematically under-count, and a short list of the specific points that justify an appraisal demand or a supplement under the new state rules.

    That is the first action a stranger will take this week. No login required for the free pass. No new system of record. Just the photo or the PDF they already have on their phone.

    The product then keeps the map. Which carriers short-pay which procedures in which ZIP codes. Which photo sets correlate with successful appraisal outcomes. Which missing lines reappear after the human gate. That dataset is the moat. Not another dashboard.

    Models draft. People own the send.

    Appraisal demands, supplements, and formal disputes are irreversible steps. The model can draft the demand letter, the photo index, and the line-item comparison. A named human still owns the send. That is the same gate we already run on money movement and filings. The bot finishes the research. The person signs.

    This is not “AI for claims adjusters.” It is a vertical combination of two primitives that already show up in the idea mills: regulated document and photo review (the home-health paperwork pattern Greg has pushed) plus physical-world claim recovery for the trades. The agent does the first pass against a living checklist of short-pay patterns. The human decides whether to pull the appraisal lever that the 2026 statutes now make real.

    The same logic applies to the spend-control side of agents. Once agents hold virtual cards and budgets, someone has to own the receipt and the exception. Here the “receipt” is the estimate and the photo set. The exception is the short-pay. The human gate stays in place for the irreversible action.

    Why the compounding path is the dataset

    Volume turns the free checker into a labeled corpus. Every upload that later produces a higher settlement or a closed appraisal award becomes training signal. Carriers change their virtual adjustment models; the checker sees the new under-count patterns first. Shops in Texas and Washington start citing the same process language; the product already knows which photo sets and which line-item gaps win under the new rules.

    That is the opposite of a third SaaS dashboard. The dashboard is the easy part. The hard part is the map of what actually moves money under the 2026 statutes, kept current by the same people who have the photos and the closed files.

    Once the map exists, the next products write themselves: automatic coaching for the appraisal demand, carrier-specific supplement templates that cite the exact WAC or Chapter 1813 language, and a quiet feed of which virtual adjustment systems are currently under-counting which damage types. None of that works without the first free checker that strangers will use this week.

    What to build this week

    Pick one surface. Collision or residential storm. Offer the free photo or estimate upload. Return a short, numbered list of flags with the specific statutory or regulatory hook that makes the flag matter. Keep every outcome. After a few hundred files the checklist stops being generic and starts being local.

    Do not sell the platform first. Sell the moment the short-pay is still reversible. The rest follows from the map.

    Will Tygart — Tygart Media

    This is the idea-mill series.

  • Storm Updates: 2.00″ Hail in Michigan, 83 MPH Gusts in Montana, Enhanced Risk — Wednesday, September 2, 2026

    Current Hotspots & Active Risk Zones

    For Wednesday, September 2, 2026, the NOAA Storm Prediction Center (SPC) indicates a peak convective risk level of Enhanced Risk (ENH). Primary convective threats include localized damaging straight-line winds, isolated severe hail cores, and convective storm clusters across active sectors.

    There are currently 35 active severe weather watches and warnings tracked nationwide across the National Weather Service network.

    Recent Impact & Local Storm Reports (Past 12–24 Hours)

    Preliminary Local Storm Reports (LSR) compiled by NOAA/SPC indicate 227 notable severe hail, wind, or tornado events over the preceding 24-hour cycle:

    • Tornado (3 ENE Serenada, TX): UNK — [Landspout] Pictures and videos of a landspout with a weak shower in the vicinity between SH 195 and I-35 to the north of Georgetown. Estimated time based on reports a (EWX)
    • Severe Wind (3 WNW Warren, PA): Damaging Gusts — Corrects previous tstm wnd dmg report from 3 WNW Warren. Multiple trees down around the 1900 block of Follett Run Road. (CTP)
    • Severe Wind (Oakfield, NY): Damaging Gusts — Trees down in Elba. (BUF)
    • Severe Wind (8 NNE Tionesta, PA): Damaging Gusts — Trees and wires down. (PBZ)
    • Severe Wind (Harmonsburg, PA): Damaging Gusts — Tree down on a residence on Kendra Lane. (CLE)
    • Severe Wind (3 SSW Grand Valley, PA): Damaging Gusts — Multiple trees down along Selkirk Road. (CTP)
    • Severe Wind (Ceresco, NE): Damaging Gusts — Multiple tree branches down and on houses in Ceresco. Also some windows blown out of a business. Time estimated from radar. (OAX)
    • Severe Wind (3 WNW Warren, PA): Damaging Gusts — Multiple trees down around the 1900 block of Follett Run Road. (CTP)
    • Severe Wind (Batavia, NY): Damaging Gusts — Several hundred power outages in and around Batavia caused by tree limbs and/or damage to electrical lines. (BUF)
    • Severe Wind (Leicester, NY): Damaging Gusts — Trees down. (BUF)
    • Severe Wind (6 WNW Brockway, PA): Damaging Gusts — Trees down. (PBZ)
    • Severe Wind (Livonia, NY): Damaging Gusts — Trees down. (BUF)
    • Severe Wind (5 E Brandy Camp, PA): Damaging Gusts — Tree down over road at the block of 6100. (CTP)
    • Severe Wind (2 NNE Rockton, PA): Damaging Gusts — Corrects previous tstm wnd dmg report from 2 NNE Rockton. Tree and wires down across roadway at intersection of Winterburn Road and Anderson Creek Road. (CTP)
    • Severe Wind (2 NNW Falls Creek, PA): Damaging Gusts — Trees down. (PBZ)

    24–48 Hour Near-Term Outlook

    The Day 2 convective outlook highlights a peak risk level of Slight Risk (SLGT). Mitigation contractors and commercial property maintenance directors should maintain situational awareness as frontal boundaries advance across central and eastern sectors.

    Restoration Operator Notes & Tactical Recommendations

    • Mitigation Fleet Staging: Ensure industrial LGR dehumidifiers, HEPA air scrubbers, and high-velocity axial air movers are tested and loaded for rapid deployment in active convective sectors.
    • Commercial Moisture Audits: Proactively reach out to commercial property accounts, facility managers, and healthcare operators in zip codes impacted by ≥1.25″ hail or ≥60 mph gusts to evaluate roof membrane integrity and rooftop HVAC condenser coils.
    • Emergency Board-Up & Tarping: Prepare roll stock poly, 2×4 lumber, and sandbags for immediate emergency envelope stabilization following severe wind gusts.
    • Field Safety Protocol: Remind field mitigation crews that flash flood waters are classified as Category 3 (black water) bio-hazard contamination requiring full PPE and specialized containment.

    Official Sources & Attribution

    Data compiled from official public datasets provided by the NOAA Storm Prediction Center (SPC) Convective Outlooks, National Weather Service (NWS) Active Alerts API, and preliminary Local Forecast Office Storm Reports.

    Operational Disclaimer: This is a public-data summary for restoration professionals’ situational awareness only. It is not an official weather forecast. Always verify with the National Weather Service, local NWS forecast offices, and official watches/warnings. Preliminary storm reports are unfiltered and subject to change. Do not make critical life-safety or structural dispatch decisions solely based on this brief.

  • The trucks leave. The record doesn’t.

    The trucks leave. The record doesn’t.

    The trucks leave. The record doesn’t.

    The magazine piece tells the facility manager why the gap exists. This is the shop version. Same week. Different door.

    A water job ends when the last air mover comes off the truck, not when the invoice hits QuickBooks. After that, the only carbon record most shops have is a line item and a memory. The facility manager who hired you will get asked for numbers tied to greenhouse gas reporting—specifically Scope 3 under the GHG Protocol. Two buckets show up again and again in those conversations.

    Category 1 (purchased goods and services) covers what the organization bought and had performed on its behalf: labor, equipment run on site, materials installed, subcontractor work. Your job is part of that spend chain. Category 5 (waste generated in operations) covers waste the organization’s activities create when it operates the building—demolition debris, wet carpet, contents sent to landfill, hauls off the loading dock. Restoration generates both in a compressed window.

    When the owner or corporate sustainability team asks the FM for Category 1 and Category 5 numbers, the FM does not have a meter on your dehu. They call you. If you cannot produce a job-level record with a timestamp from the week of the loss, you are not the vendor who gets the next call. Not because anyone hates paper. Because “we’ll get back to you” reads as “we don’t know what we did on your floor.”

    What has to change is not your craft. It is what leaves with the crew.

    The dozen fields: what to write while the floor is still wet

    Not a sustainability essay. A dozen fields, filled before the truck rolls. If a tech cannot complete it in five minutes, the form is wrong. If it waits for the office on Monday, it will be invented.

    The Restoration Carbon Protocol knowledge base is the open mapping if you do not want to invent the buckets. Use it, rename it, or steal the twelve fields. The standard is not the point. The timestamp is.

    Field Why it matters (carbon math) Capture in under a minute
    1. Equipment runtime (hours) — dehus, air movers, scrubbers, etc.; mark primary or estimated Electric or fuel burned on site drives emissions attributed to purchased services (Category 1). Photo hour meters or write run hours from the panel; note if rounded from crew shift length.
    2. Generator runtime (hours) + fuel type — diesel, gasoline, propane, or grid tie-in; primary or estimated Generator fuel is a direct combustion source; grid power still needs kWh or hours for conversion factors. Generator hour meter or fuel fill log; one line for fuel type; photo of meter.
    3. Crew trips — count and approximate miles (shop to site and return, or per day); primary or estimated Vehicle miles stack into purchased services when your crew travels to perform the work. Crew lead odometer at departure and return, or map estimate; one number per trip day.
    4. Haul trips — count, approximate miles, truck type if mixed; primary or estimated Hauling moves mass; miles and trips feed transport emissions tied to the job. Dump run tally on the clipboard; odometer photo or dispatcher mileage note.
    5. Debris — wet drywall (volume) — bags, yards, or tons as your shop measures; primary or estimated Material mass and disposal path drive Category 5 waste reporting. Count bags or roll-off fraction; photo of loaded trailer or ticket weight if scaled.
    6. Debris — carpet / pad (volume); primary or estimated Same stream: landfill vs recycle changes the waste factor. Square feet removed × layers, or roll-off estimate; note wet vs dry.
    7. Debris — contents (volume or weight); primary or estimated Contents off-site as waste or salvage still count in what left the building. Box count, pod fraction, or invoice from pack-out vendor.
    8. Debris — mixed C&D (volume); primary or estimated Mixed loads need a declared split or honest “mixed” with disposal site. Roll-off size × fill level, or scale ticket photo.
    9. Disposal method + receiving facility / transfer station — landfill, recycle, waste-to-energy, donation, etc. Category 5 is not “garbage” in the abstract; method and location determine factors. Photograph dump ticket; copy facility name and address from ticket.
    10. Materials removed (summary) — what came out; primary or estimated Mass balance: what left the building anchors waste and demo attribution. One line from demo scope: “~800 sf carpet, 200 lf baseboard, 12 sheets drywall.”
    11. Materials installed (summary) — what went back in; primary or estimated Installed goods are purchased goods/services (Category 1) the owner will allocate. Pull from pick ticket or invoice stub; photo of delivery slip.
    12. Job class + duration — water / fire / mold / mechanical (or your codes); start and close dates; primary or estimated Duration scales equipment and trip totals; class tells the FM which protocol line to use. Dates from work auth; class from loss type already on the folder.

    Every number gets a flag: primary (measured — meter, ticket, scale, invoice) or estimated (judgment — “~half a 20-yard,” “assume 40-mile round trip”). Never fake precision. An honest estimate with a date beats a fabricated decimal from accounting six months later.

    Building the capture habit

    Nobody fills a questionnaire after the trucks have gone. They fill what stands between them and getting paid.

    Tie it to the invoice trigger

    Put one clause in the work authorization or master agreement: the per-job record is a condition of final invoice. Same shape as a moisture log. Same habit as photos. Final invoice does not go out until the record is attached to the job file—PDF photo of the clipboard, form in your CRM, whatever your shop already uses for documentation that must exist to get paid.

    That single gate does more than a training deck. The crew lead knows the rule: no record, no release. Office staff stop chasing “sustainability forms” and start enforcing the same checklist they enforce for signed auth and dry standard.

    Who owns it, and when

    Owner: crew lead on site—not the office on Monday. The lead has the hour meters, the dump runs, and the conversation with the FM at the door.

    When: before the truck rolls, while the floor is still wet and the debris stream is visible. Last hour on site, not first hour back at the shop.

    What it looks like: one page. Checkbox for job class. Table for the twelve fields. Two columns for primary vs estimated initials. Signature and date. Lives on the clipboard that already holds the moisture log.

    The discipline matches what you already run on the first day of a water loss: document early, while evidence is in front of you. The first-24-hours water loss operators checklist is the same muscle—capture before memory replaces the floor.

    Pushback you will hear

    “We don’t have time.” Five minutes. Hour-meter photos and a dump ticket fit in the same walk-through where you pick up the last cord.

    “We’ll do it Monday.” Monday produces fiction. Miles blend across jobs. Fuel type becomes “diesel probably.” The FM’s deadline will not wait for fiction.

    “The office can estimate.” The office was not on the roll-off. Estimates are fine when labeled estimated—not when invented without a witness.

    Estimates vs primary data: Mark every field. Primary data comes from meters, tickets, invoices, or counted units on site. Estimates are allowed when measurement was impossible—note the reason in one word (“no scale,” “combined load”). Reporting downstream can treat estimates differently; lying about precision cannot be untangled later.

    Feeding Scope 3 reporting from the job file

    Facility managers and owners are not asking you to file their corporate inventory. They need defensible inputs they can map into Scope 3 workbooks.

    Your twelve fields supply the bridge. Category 1: equipment and generator runtime (especially fuel type and grid vs diesel), materials installed, crew and subcontractor effort represented by trips and job duration, and the job class that tells them this was restoration services—not janitorial, not capital project. Category 5: debris by stream, volumes, disposal method, and receiving facility name—so their waste factor matches what actually left the dock, not a generic “construction waste” line.

    When you hand the FM a completed record dated the week of closeout, you give them primary or honestly labeled estimated data with a chain of custody: ticket photos, meter photos, material slips. Their sustainability consultant can plug factors without calling you twelve times. When you hand them silence, they spread one invoice total across a quarter and hope nobody audits.

    The Restoration Carbon Protocol (RCP) documents how restoration-specific activity maps to those reporting needs—field names, streams, and guidance so shops and FMs speak one language. You do not have to adopt every label. You do have to leave a record that can be mapped.

    Who this is for

    Commercial water, fire, mold, and the one-off mechanical swap. The FM inside the building is the only person who can demand the data at the door. You are the only person who can produce it on the job.

    The sentence that pays: “We capture the job record before we leave. You can hand it to whoever asks.” Only say it if the clipboard is on the truck.

    Frequently asked questions

    What if the job is already done and we captured nothing?

    Document what you can reconstruct from tickets, invoices, and photos—with every number marked estimated and the reconstruction date noted. Send it anyway. Partial honest data beats silence. Change the process for the next job; do not rewrite history as primary.

    Who owns the record — the crew or the office?

    The crew lead captures it on site before departure. The office verifies it is attached before final invoice release. Capture is field work; gatekeeping is office work.

    How precise do the numbers need to be?

    Precise enough to be honest. Primary when you have meters and tickets; estimated when you do not—never unlabeled guesses. Facility reporting uses ranges and factors; they cannot use numbers you pretended were weighed when they were guessed.

    Does this replace our moisture log or invoice documentation?

    No. It sits beside them. Same invoice gate, same job file. Moisture proves dry standard; invoice proves scope and price; the job record proves what happened on the floor for environmental reporting.

    What does the FM actually do with these numbers?

    They fold them into Scope 3 reporting—Category 1 for purchased restoration services and materials you installed, Category 5 for waste streams you hauled—often with a consultant or corporate template. Your record is the job-level backup when auditors or tenants ask what the loss generated.

    Do we have to use the Restoration Carbon Protocol name?

    No. Use the twelve fields, your own form, or RCP’s mapping. The FM needs consistent fields and a date from closeout week, not a brand.

  • Pipe, pile, and two seats — the restoration AI shop floor

    Pipe, pile, and two seats — the restoration AI shop floor

    Agencies keep buying “AI stacks.” Restoration shops keep buying more leads.

    Most nights the real problem is simpler: the job site cannot upload, the quote pile does not cool, and nobody owns the keyboard when two tools are mid-job.

    We already published the three field notes. This is the companion that names the stack.

    Clipboard and tablet on a kitchen counter during an insurance adjuster walkthrough after water loss
    Layer 0 starts at the curb — can the site still talk?

    The pipe

    On a water job, cell bars lie. Fiber is dead. The moisture map still has to leave the truck.

    Starlink on a water job is not a partnership post. It is layer 0: a clear-sky dish, a 65–100 W brick, and a boring SSID so photos, Xactimate, and after-hours voice still move when the street does not.

    No pipe → no honest traffic. Voice agents and CRM cards do not invent bandwidth.

    Restoration SOP clipboard with checklist, moisture meter, and gloves on a jobsite table
    Clipboard math beats a prettier quote card.

    The pile

    Once the pipe works, the shop still has open estimates that do not book, supplements that sit, and missed rings that become someone else’s water job.

    The leftover pile borrows the math that cools a trapped ion. Count n (open quotes), A− (book or honest kill), A+ (new noise). Plot the leftover on Mondays. If it does not fall, follow-up is theater or miss rate is the heat.

    AI that only writes a prettier card is a thermometer. AI that texts back in a minute and closes the row is a kick.

    Gloved hands using a pin-type moisture meter on wet drywall during inspection
    Two seats. One measurement owner.

    The two seats

    Then you put more than one agent on the same laptop and discover the collision problem.

    Cursor checked in on Grok Desktop mid-job is the Cosync rule in the open: seats with jobs, not two models arguing in one thread. One seat keeps the PowerShell. The other reads the board, closes orphan twins, and does not steal the keyboard.

    Human Gate still owns OAuth, live Publish, and paid spend. Seats replace waiting and context loss — not the owner.

    Residential roof with blue emergency tarps after storm damage under gray sky
    Weather hits. The floor still has to run.

    One floor

    Read as three posts, they look like tech, physics, and tooling.

    Run as a week, they are one floor:

    • Pipe — can the site and the after-hours line still talk?
    • Pile — are open quotes shrinking on purpose?
    • Seats — who owns the keyboard, and who only Cosyncs?

    Skip the pipe and your “AI dispatcher” is a voicemail with better grammar. Skip the pile math and your lead gen is blue-detune (more noise, same booked jobs). Skip the seat rule and two tools fight over the same Chrome window while the work order twins drift.

    Steal this without buying our tools

    You do not need our stack names.

    • Write one Owner column and one Done-when line on every live card.
    • Put a truck kit on the hook for dead-fiber jobs (or admit you will not upload tonight).
    • Run the four-week leftover sheet before you buy another map-pack click.
    • Practice the check-in: are they stuck, or are they fine — and do I have a capability they lack? If they are fine, leave the keyboard alone.

    That is restoration + AI ops without a slide deck.

    What this is not

    • Not a Starlink / SpaceX / Tesla / xAI partnership.
    • Not “fully autonomous.” Publish and pay stay human.
    • Not Tacoma / Everett / Mason local news. Field notes stay method-first.
    • Not a new SKU. The front door on Tygart Media is still the kit you can copy and hang yourself.

    Related on Tygart Media: Starlink on a water job · The leftover pile · Cursor × Grok Cosync.

  • Starlink on a water job — open field playbook

    Starlink on a water job — open field playbook

    Open field playbook. No patent. Copy it, rename it, change the nouns to fire / mold / rebuild. If it makes you money, good. If it puts another dish on a wet roof, also good.

    License: do what you want. Attribution nice, not required. Tygart Media is not a Starlink, SpaceX, Tesla, or xAI partner. Links below go straight to them. No tracking parameters. No referral codes.

    Why this exists: restoration work happens where fiber is dead, the house is a Faraday cage of wet drywall, and the phone that “has bars” cannot upload a moisture map. Starlink is a sky-view pipe. More honest job-site pipes → more honest traffic on the constellation → more reason to fly birds. The selfish clause is allowed: a 4G phone in the sticks should still talk to a voice agent when the street is dark.

    Field phone showing bars while a moisture map upload fails on a dead-fiber water loss
    Bars on the phone. Upload still dead. That is the job the dish is for.

    Buy and read from the source. Prices move. The impedance rule does not.

    Official doors (clean)

    Starlink (buy / plans / help)

    SpaceX

    Tesla / xAI (voice rides the pipe; they are not the dish)

    1. Impedance — when this kit matches the job

    Use Starlink when two of these are true:

    • The structure or the street has no working cable/fiber (storm, rural, construction, “the pole is in the river”).
    • You need to upload, not just talk: photos, video walkthrough, Xactimate sketch, moisture log, signed work auth.
    • You will be on site more than an hour and cell is congested or roaming into a dead pocket.
    • The office needs a second path so after-hours voice and dispatch do not die with the cable modem.

    Do not use it as:

    • A replacement for a good office fiber drop.
    • A phone. Voice agents still ride the pipe; the dish is not Jarvis.
    • A “we have Starlink” line on the website. Homeowners hire the truck that showed up.

    Cell first if it works. Starlink is the sink when cell is the bottleneck.

    2. Two kits (steal one)

    Kit A — truck / first-on-site (most shops)

    • Starlink Mini on a Roam plan or, if this is actually a business WAN, start at Business and read the current hardware list. Mini is the backpack dish. In-motion rules live here. The home V5 kit is not the roam toy.
    • Power: Mini wants a USB-PD source rated 65–100 W even though it only drinks ~25–40 W. A 45 W phone brick will lie to you. Truck: 12 V → 30 V / Anderson, or a 500 Wh class station.
    • Plan: numbers on starlink.com move. Roam is written for travel. If the kit is production, read Business vs Enterprise. Mini often does not sit on the Priority SLA. Do not tell a carrier you have enterprise uptime because you paid a business invoice for a Mini.
    • One cheap travel router if Mini Wi-Fi dies inside a metal trailer.
    Starlink Mini powered from a truck USB-PD brick rated 65 to 100 watts before entering a wet house
    Power before the meter. 65–100 W brick. Phone chargers lie.

    Kit B — shop / yard / long dry-down

    • Performance / Priority on Business if you need an SLA and a fixed roof.
    • Permanent mount, open sky, snow-melt if you live where it snows.
    • This is backup for the office phone and the photo server. Not the hero kit on day one of a flood.

    3. First 30 minutes on a wet house

    Flooded residential living room with standing water on hardwood after a water loss
    First 30 minutes on a wet house with Starlink up.
    1. Park where the sky is a rectangle, not a slot between two alders. Confirm in the Starlink app.
    2. Dish on the hood, a pole, or the unshaded side of the trailer — not the basement, not under the soffit.
    3. Power before you walk in with the meter. Boot is a couple of minutes.
    4. One speed check. If download is fine and upload is garbage, you will feel it on Xactimate. Rain cuts throughput; talk first, fat files later.
    5. Name the network something boring (SHOP-JOB).

    If the app says obstructed, move the dish. Do not “optimize” for twenty minutes.

    4. What actually eats the pipe

    Gloved hands using a pin-type moisture meter on wet drywall during inspection
    What actually eats the pipe on a water job.
    ThingRough appetiteRule
    Moisture photos, 50–150 shotssmallFine on a small Roam month
    Adjuster video walk, 10 minmediumOnce, compressed
    Xactimate / cloud estimatesmall–mediumSite needs the upload
    Voice agentsmall per minuteCheap; retries are not
    Netflix in the trailerthe villainAfter the job or not at all
    Group video, four peopleburns a small capOne camera

    Voice is why the pipe matters at 11 p.m. Keep the agent short. Book or kill.

    5. Who pays

    Pick one. Write it in the SOP.

    • Job cost — storm / rural / no street internet. Line it like a generator.
    • Shop overhead — office backup + after-hours voice.
    • Never the tech’s personal weekend.

    Standby the truck kit when it is not a weather week. Idle is cheaper than a second hardware buy because someone borrowed it.

    6. Dispatch and voice

    White restoration work van with ladder rack parked at a suburban jobsite curb
    Dispatch and voice when the site is remote.

    The dish is layer 0. The voice agent is layer 1.

    On a dead-fiber job: photos go up the pipe; the after-hours line stays reachable; the agent writes a new row (address, standing water y/n, next action). It does not edit your website.

    If you already have a process, add one rule: when cell upload fails, kit A comes off the hook.

    7. Failure modes

    Trees and eaves. Rain. 45 W bricks. Consumer Roam sold as production WAN. Twelve intake fields before anyone asks “can we come now?”

    8. The sentence that pays the shop

    “If the street internet is out we still upload your photos and get the adjuster pack off the truck tonight.”

    Only say it if the kit is in the truck.

    This document stays free. Charge for the hour you spend teaching another shop the first 30 minutes if you want. Do not charge Starlink. They already sold you the dish.

    9. What this is not asking

    No meeting. No partnership badge. No official anything.

    Redmond already knows how to stamp birds. The ground should not be a graveyard of unused kits. Order here. Then put the dish where the sky is.

    Related field notes: The leftover pile · Cursor checks on Grok Desktop mid-job

    Related on Tygart Media: The leftover pile · Cursor checks on Grok Desktop mid-job.

  • The leftover pile — what ion-trap cooling has to do with restoration quotes

    The leftover pile — what ion-trap cooling has to do with restoration quotes

    In a Paul trap, a single calcium ion sits in an oscillating electric field—too small to see, easy to lose if you blink at the wrong moment. Cool it anyway. A laser tuned slightly red of the ion’s transition shines on it. When the ion drifts toward the beam, Doppler shift brings the light closer to resonance; it absorbs photons more often. Each absorption kicks a tiny bit of momentum opposite its motion. That is Doppler cooling: velocity stolen photon by photon, direction by direction, until the ion mostly sits still in the trap.

    It never hits absolute zero. Random fluorescence puts heat back in. The best you get is the Doppler limit—a floor, not a fantasy of perfect stillness. Stochastic cooling at CERN pushed antiprotons further with timed kicks instead of photons; same moral: you shrink a hot cloud with deliberate impulses, not with wishes.

    Your shop has the same shape, minus the vacuum chamber. The leftover pile is the ion: quotes written but not booked, supplements submitted but not approved, inbound rings that became someone else’s water job. Cooling kicks are follow-ups that book or honestly kill. Noise is new quotes, missed calls, ghost rows in the CRM. More leads without follow-up is blue-detuned laser work—more energy in, same jobs out, pile hotter. The physics will not save a broken sales process; it only names what you are already doing wrong.

    The four columns on your whiteboard

    Think in rates, not vibes. Four symbols are enough for a Monday conversation:

    • n — open quotes and stalled files you still treat as live.
    • A− — follow-ups that book work or honestly kill the row (closed-lost with a reason, not “maybe later”).
    • A+ — everything that adds pile without a matching close: new estimates, voicemails never logged, supplements you forgot to track, adjuster silence you stopped measuring.
    • Floor — the leftover you will always carry. Speed-of-life, tire-kickers, carriers that pay on geological time. Not shame; physics.
    When A− ≈ A+ → pile stays flat. When A+ > A− → pile runs. When you pretend A+ is zero → you predicted a miracle.

    Most owners stare at n and feel virtuous. n is a thermometer. A− and A+ are the levers. If you only measure n, you are reading temperature while the laser points the wrong way.

    Cooling kicks: quote follow-up that actually moves n

    A quote without a cadence is not cooling; it is fluorescence—pretty light that heats the pile. Use a simple clock. Adjust timing to your market; count your own conversion by touch and fix the script, do not copy someone else’s calendar from a podcast.

    Day 1 — confirm reality

    Within one business day of sending the estimate: call if you have a number, text if that is how the customer reached you. Say what is in the document, what happens next if they say yes, and one clear question (“Do you want us to hold a start window this week, or are you still comparing?”). Log the answer in the row. No answer is data; “still thinking” without a date is A+ wearing a friendly mask.

    Day 3 — remove friction

    Second touch: one concrete obstacle. Deductible confusion, landlord delay, another contractor’s line item they do not understand. Offer a ten-minute walkthrough of scope—not a lecture on your brand. If they are not the decision-maker, ask who is and whether you may include them on the next call. Still no response: note “attempted day 3” and move the clock.

    Day 7 — decision fork

    Third touch: binary. “We can mobilize on X or close this file on our side so you are not getting pings—which do you want?” Polite, not passive-aggressive. Restoration is urgent until it is not; your job is to learn which side of that line this file sits on.

    Day 14 — honest kill

    If nothing after a real fork, close-lost. Reason code: no response, chose competitor, insurance denied, scope withdrawn—pick one that is true. Rotting quotes inflate n and train your team that follow-up is theater. Honest kill is A−. It shrinks the pile you actually work.

    Speed-to-lead is the biggest heat source. The unanswered ring is A+ at industrial scale. Answer live when you can. Call back in minutes, not hours. Text-first when the caller already texted. The first 24 hours on a water loss belong to whoever shows up—not whoever sends the prettiest PDF three days later.

    Estimator craft still matters: vague scopes cool nothing. If line items fight the adjuster on day one, you added noise before the laser turned on. A tight scope language habit—your own cheat sheet, verified against carrier pushback you have actually seen—feeds A− later. See your Xactimate line-item cheat sheet as cooling prep, not as a substitute for picking up the phone.

    Supplements: the unpaid tail nobody plots

    Residential files rarely die on the first packet. Several supplement rounds is normal in many shops that measure; your count will differ by carrier mix and how aggressively you document on site. Treat each open supplement as its own row in the pile—not as “part of the job we already won.”

    Loop: submit → track → escalate → collect. Every open supplement needs an owner name and a next-action date. No date means A+. The unpaid tail—approved on paper, not in the bank—is pure pile growth while everyone celebrates revenue on a spreadsheet.

    Escalation with dates on every step

    1. Adjuster — documented follow-up (email plus call log). Note what you sent and when.
    2. Supervisor — same file, new name, reference prior contact dates.
    3. Carrier escalation — formal, factual, no throat-clearing novellas; timeline of submissions and responses.

    If step three is a fantasy because step one never happened, you do not have an escalation problem—you have a tracking problem. Drywall documentation standards on the truck—what S500 in the van means in practice—feeds supplements that survive first review. That is upstream cooling; downstream is still the calendar on each open dollar.

    Measuring the pile: Monday one-sheet

    Once a week, one page. No dashboard archaeology.

    • Count open quotes (n at start).
    • Count new quotes and missed-call rows added (A+ for the week—be honest about voicemails).
    • Count booked jobs and honest closes from follow-up (A−).
    • Plot leftover at end of week.

    If leftover does not fall over a month while you “follow up,” either follow-up is theater or miss rate is the heat. Voice that texts back in a minute is a kick. Voice that only writes a pretty card is a thermometer.

    Pair the sheet with job memory: what repeated on lost files, what line items got kicked back, what adjuster phrases mean “send photos again.” Turning closed jobs into searchable notes—restoration jobs as a knowledge base—cuts A+ from repeated mistakes. It does not replace the cadence above.

    Field connectivity is pile-adjacent: if the crew cannot upload while the homeowner is still anxious, you slow the proof loop and invite competitor speed. Reliable site internet is boring ops; it is also fewer ghost supplements. Worth reading once if you still fight dead zones: Starlink on a water job.

    Not this

    The metaphor has boundaries. It will not cool your brand. It will not set ad spend. It will not fix hiring. It only describes piles that shrink when kicked and grow when ignored. If your marketing pours leads into a CRM nobody touches, you are not running a trap—you are heating ions on purpose and calling it growth.

    Do not overclaim the physics. You are not hitting the Doppler limit on receivables. You are choosing whether A− happens often enough that n is workable. That is enough math for a contractor who would rather dry a wall than derive one.

    FAQ

    What is the “leftover pile” in plain language?

    It is work you already touched but have not collected or closed: open quotes, stalled supplements, and leads you let slip. It is not evil; it is inventory that costs attention until you book it, kill it, or collect it.

    Why compare follow-up to laser cooling?

    Because each good follow-up removes a little uncertainty the way each absorbed photon removes a little velocity—not all at once, and never to zero. Random noise—new leads, missed calls—puts heat back. The comparison keeps you honest about rates, not miracles.

    How many follow-ups before I close a quote as lost?

    A common working structure is day 1, day 3, day 7, and a day 14 fork with an honest close if there is still no decision. Count your own bookings by touch; shorten or lengthen only when your numbers say so.

    What belongs on a supplement escalation?

    Dates, names, and what was submitted each round. Move adjuster → supervisor → carrier escalation with a logged step at each level. Missing dates mean you are guessing, not escalating.

    What should the Monday one-sheet prove?

    Whether leftover shrank. If new noise and open quotes outrun closes for weeks, your pile is running hot—fix speed-to-lead or cadence before you buy more leads.

    Can this framework fix slow insurance pay?

    It helps you see unpaid approved work as pile growth and assign owners. It does not change carrier calendars. It keeps you from mistaking “approved on email” for collected cash.

  • IICRC Van Pocket Card

    IICRC Van Pocket Card

    Tape this in the van. Category, Class, PPE floor, one photo. Twenty seconds. Then go to work.

    This is a free pocket card, not a certification, and not official IICRC. It does not replace S500/S520.

    What you get

    Five-step van pocket flow: category, class, extract, dry, document
    Protocol answers belong in the van — not back at the office.
    • A Notion page you can duplicate and print
    • A tiny Claude skill with the same tables (upload the zip, or paste SKILL.md into a Project)

    How to get it

    Restoration SOP clipboard with checklist, moisture meter, and gloves on a jobsite table
    How to get it: keep the checklist where the carpet is wet.

    Duplicate the card here: IICRC Van Pocket Card (free Notion account, Duplicate in the top right).

    Want the Claude skill zip too? Join The Signal and reply that you want the van card.

    What this is not

    White restoration work van with ladder rack parked at a suburban jobsite curb
    What this is not: another binder collecting dust.
    • Equipment sizing
    • A drying plan
    • Adjuster language

    Need that? The paid IICRC Protocol Lookup ($19) or the Complete Restoration Operations Kit ($97).

    Related on Tygart Media: Starlink on a water job · S500 in the van · local SEO for restoration.