# Standing orders for a scheduled Grok Bot (free sample)

> The card we use for every scheduled Grok Bot job, a cron table in local time, and two reporting rules (quiet by default, end of day) that cut most of the noise.

- URL: https://paperchasewebb.ai/bots/marketplace/items/standing-orders-for-a-scheduled-grok-bot-free-sample/
- Type: Prompt pack
- Category: Solo business
- By: PaperChaseWebb
- Works with: Grok Bot (named in the listing); Plain .md
- Price: Free USD
- Difficulty: Beginner
- Setup time: 5 min
- Time to result: Five minutes per routine
- Format: Markdown (.md) file, standing-orders-for-a-scheduled-grok-bot-free-sample.md
- Version: 1.0, updated 2026-10-26
- License: Personal and commercial use.

## What you end up with

Your scheduled bot runs in the right time zone, stops when its job ends and messages you only when something needs you.

## What you get

- The standing order card
- A cron table in local time
- Quiet-by-default and end-of-day reporting rules

## Who it is for

Anyone whose scheduled bot messages at odd hours, reports too often or keeps running after its job is over.

## Tools needed

- Grok Bot: runs the scheduled routine
- You need: A Grok Bot that can run scheduled routines

Cost to run: Free.

## Sample prompt: Turn a habit into a standing order (Grok Bot)

```
Every [day / week] I [manual task]. Write a standing order card: cron line in [zone], exact or flexible, run and report windows, end date, steps, done-when check and a REPORT ONLY IF rule.
```

The REPORT ONLY IF line does most of the work.

## Free preview of standing-orders-for-a-scheduled-grok-bot-free-sample.md

````markdown
# Standing orders for a scheduled Grok Bot (free sample)

A free sample from Grok Bot Templates: personas, standing orders and handoffs, by PaperChaseWebb. Written for Grok Bot.

A bot that runs on a schedule is only as good as the order it reads at the start of each run. Loose orders give you messages at odd hours, reports nobody reads and watches that never stop. This sample gives you the card we use for every scheduled job, a cron cheat sheet in local time, and the two reporting rules that cut most of the noise.

## The standing order card

Paste this into the bot's instructions or a file it reads at the start of every run.

```text
STANDING ORDER: [short name]
OWNER: [bot name]
SCHEDULE: [cron line] in [time zone], [exact or flexible within N minutes]
WINDOW: run [any time / hours]; report [weekdays 07:00 to 19:00 local]
EXPIRES: [date, or the condition that ends it]
JOB: [one sentence]
STEPS: 1. [...] 2. [...] 3. [...]
DONE WHEN: [the check that proves the run worked]
REPORT: [every run / end of day / only if] to [who]
REPORT ONLY IF: [conditions worth a message]
NEVER: send, post, spend, trade, deploy or delete without my yes for that one action.
```

## Cron in local time

| You want | Cron line |
|---|---|
| Weekdays at 7:30 AM | `30 7 * * 1-5` |
| Hourly, 7 AM to 7 PM, weekdays | `0 7-19 * * 1-5` |
| Every 30 minutes, working hours | `*/30 7-18 * * 1-5` |
| Mondays at 9 AM | `0 9 * * 1` |

Write the zone next to the line ("America/Chicago", not "my time"). If the pla
````

## Worth knowing

- Check whether your setup runs schedules in local time or UTC before you trust the first run.

## Questions

**What is in the full pack?** 8 ready-to-paste personas, event routine recipes, multi-bot handoffs with a decision log and four approval gates, memory hygiene rules, a 20-point check with 10 test scenarios, and 12 prompts.

## How to get it

Free sample. Download it directly at https://paperchasewebb.ai/bots/marketplace/items/standing-orders-for-a-scheduled-grok-bot-free-sample/, no signup.

Seller: PaperChaseWebb Inc., mgmt@paperchasewebb.com