A kitchen sequencing tracker: when a cabinet date crosses the template.

In typical kitchen practice the countertop fabricator templates only after the base cabinets are set. That makes the template the first date in the job that depends on somebody else's shipment, and the last one the remodeler can still protect by working its own supply chain. So the tracker's central check is simple: compare the supplier's latest written date for every base cabinet with the date the template needs them, and say so the moment one crosses the other.

Everything else here supports that comparison: a purchase-order list, status read from supplier emails, a four-state flag, a template-to-install window for the project manager to approve, and a record about engineered stone that never pretends to check a fabricator's safety. An assistant prepares and flags. The project manager and the owner decide.

The list is an Aevrion pattern held in whatever spreadsheet or job software the company uses. Grok Bot, an AI agent product, can be asked for reviewable results such as a spreadsheet with defined columns, which suits a list the project manager reads every morning. The list, not the Bot's memory, is the record; the documentation says plainly that memory does not replace an authoritative source.

This page gives no cabinet lead times, because they vary by supplier and product line and change during the year. The tracker does not need one. It needs the date each supplier has committed to in writing.

Based on the Grok Bot documentation at docs.x.ai as checked on 15 October 2026. Its statements on Bot rules, Bot-to-Bot messaging, routine triggers, connected apps, approval expiry and payments were rechecked against docs.x.ai and Cursor's help pages on 26 October 2026. The trade examples are Aevrion's illustrations, not documented Grok Bot use cases. Aevrion Ops is an independent consultancy. It is not affiliated with, endorsed by or a partner of xAI, SpaceXSI or Cursor. Grok Bot is named here only to describe it.

Suppliers confirm orders and shipments by email or in a dealer portal. Bringing those emails to the Bot, for instance by routing them from the company mailbox into a folder the morning routine reads, is a custom integration that has to be built and tested for that mailbox. A dealer portal is a custom integration too, or supervised browser use where the vendor permits it, subject to testing; a portal may block automation, and a person takes over the Bot's computer for any login or two-factor code.

A weekday-morning routine does the reading. Grok Bot routines run on a schedule at least five minutes apart, and the documentation advises writing a no-data policy into each one, so this routine has a firm rule: when a source cannot be read, the row is marked as not read today and keeps no borrowed date from last week. The app keeps only the twenty most recent run records per routine, and the documentation describes no automatic retry or failure alert, so the project manager glances at run history each week. The reliable workflows article covers routine design in more depth.

The flag is the assistant's comparison, not its judgment. Each flag carries a one-line reason and a link to the message behind it, so the project manager can overrule it without opening anything else.

• CLEAR

  The supplier's written date falls before the needed-by date, and the message is no older than the owner's freshness limit.

• WATCH

  There is no written date yet, or no new word from the supplier within the owner's freshness limit. A chase email is drafted for a person to send.

• THREAT

  The written date now falls after the needed-by date: the cabinet ETA has crossed the template. This line goes to the top of the morning list, with drafts ready for the options the project manager might choose.

• BROKEN

  The delivery arrived short or damaged. The row links to the delivery check and its photos, and the claim deadline from the supplier's terms sits beside it.

Once the cabinet dates are clear, the tracker drafts the window that follows: the template, fabrication, counter install, backsplash and appliance delivery, laid out in order with the source of every date. The draft adds no gaps of its own. Any waiting time between steps is whatever the fabricator and the installers have stated in writing, entered by the owner, and where nobody has stated one, the line says so rather than guessing.

The project manager approves the window, changes it or sends it back. Only then are the booking drafts prepared: a template confirmation for the fabricator, notes for the other trades and an update for the household, each an editable email a person sends. If sending is set to stop for approval, a request raised by a routine with no one present runs out after roughly ten minutes (Cursor's help pages say thirty) and the email stays unsent; and an approval, once given, does not pull back an email already gone.

The lines of the window draft, and where each date comes from:

• BASE CABINETS SET

  The install lead's schedule, confirmed only when every base cabinet on the list is delivered and inspected.

• TEMPLATE

  The visit the fabricator has offered in writing.

• FABRICATION AND COUNTER INSTALL

  The fabricator's own written turnaround, entered by the owner from the fabricator's terms.

• BACKSPLASH

  The installer's booking, placed after the counter install date.

• APPLIANCE DELIVERY

  The retailer's delivery confirmation, set against the counter and backsplash dates.

• FINAL CONNECTIONS

  The plumber's and electrician's return visits, once sink, cooktop and appliances are in.

Engineered stone brings regulatory attention the remodeler should understand but not try to manage. In the United States, OSHA's enforcement directorate issued a memorandum on 22 September 2023 launching what it calls a focused inspection initiative, aimed at silica exposure in businesses that fabricate and install engineered stone, and prioritizing two industry codes: cut-stone product manufacturing and stone merchant wholesalers. It governs Federal OSHA inspections in Regions 1 through 8, encourages State Plans to adopt its instructions, and gives the silica content of engineered stone as no less than ninety-three percent. OSHA's silica overview says cutting and grinding stone creates respirable silica dust, describes silicosis as incurable, and notes separate standards for construction and for general industry and maritime (both as checked on 15 October 2026).

Meeting those standards is the fabricator's duty as the employer of the people cutting and installing the stone. The remodeler's decision is which fabricator to hire, and questions about its own obligations on a shared site go to the appropriate professional. A Bot never verifies a fabricator's silica compliance, never reviews its exposure controls and never reassures a household about a material. The tracker holds two plain facts for sequencing: whether the counter is engineered stone, and whether the fabricator has said in writing that cut-outs will be made in its shop or on site. OSHA and NIOSH's 2026 hazard alert on countertop work lists doing as much work as possible under controlled shop conditions, instead of at the installation site, among its installation controls, and on-site work changes what the window has to allow for.

Appliances are often ordered early and delivered late in the chain, so a slipped template pushes them back too, and the tracker drafts a request to move the delivery for a person to send. When the appliances arrive, the assistant compares the delivered model numbers with the appliance schedule on the approved drawing version and the specification sheets the owner attached, and lists any mismatch for the designer.

The comparison is clerical. Landing areas and clearances around a cooktop or refrigerator were the designer's call when the kitchen was drawn; the National Kitchen & Bath Association's planning guidelines present them as recommendations, each beside a separate line on code (per the PDF on NKBA's knowledge base, as checked on 15 October 2026). The tracker does not re-check a design against them. If a delivered appliance does not match the drawing, the designer decides what happens.

The owner releases purchase orders through an explicit approval, and payments go through a person. The project manager approves template windows. Fabricator choice and every silica question stay with the owner and the fabricator. Every Bot on the account works on one shared computer with the same browser sign-ins, so a portal session nobody closed can be used by any of them; sign out after use.

Aevrion Ops can set up the purchase-order list, the morning routine and the connections to supplier mailboxes and dealer portals for a kitchen company, so far as each vendor's API or terms permit and once tested. For a company that wants this list running, the readiness assessment is where that work begins.

1. In typical practice the template follows the base cabinet set, so the tracker's alarm is a cabinet date that crosses the template date.
2. Every date on the purchase-order list comes from the supplier in writing, with a link; the tracker never estimates a lead time.
3. A morning routine reads supplier emails and portals, marks unread sources as not read today, and leaves run history for a person to check.
4. The template-to-install window is a draft the project manager approves before any booking email is sent.
5. Engineered stone silica compliance is the fabricator's duty; the tracker records the material and the cut-out plan and verifies nothing.