AI chat tools · Claude · All guides
How fence companies use Claude for scheduling
Claude is good at reading a long, messy list and putting it in order. That is most of what a fence schedule is. Here is how to use it without letting it run your board.
Where it actually helps
Scheduling a fence company is a puzzle: crews, augers, skid steers, material drops, locate tickets, inspections, weather, and customers who move their dog run at the last minute. Claude will not know any of that unless you tell it. Once you do, it is quick at sorting, grouping, and spotting conflicts you missed at 6 a.m.
- Grouping jobs by area, soil, and machine so iron is not driving across town twice.
- Catching conflicts: two jobs needing the same skid steer on Tuesday.
- Flagging jobs with no locate ticket number yet.
- Writing the crew text for tomorrow in plain words.
- Re-planning fast when rain kills Wednesday.
Set up the job list once
Keep a simple sheet. One row per job. Claude reads pasted tables fine, and paid plans can take a CSV file.
| Column | Example | Why |
|---|---|---|
| Job # | J-2214 | Keeps names out of the chat |
| Area | North side / Rt 9 | Cuts windshield time |
| Footage + gates | 180 ft, 2 walk, 1 double drive | Sizes the day |
| Soil / dig | Rock likely | Picks the machine |
| Machine | Auger + skid steer | Prevents double booking |
| Material status | On site / ships Thu | No crew without posts |
| Locate ticket | Ticket # or blank | No ticket, no dig |
| Customer limits | No Fridays, dog home | Fewer angry calls |
The prompts
- Give it the rules firstTell it how your shop works before you paste the jobs. It keeps the rules for the whole chat.
- Paste the job listTable or CSV. Job numbers, not names.
- Ask for a draft board, not a final oneMake it show its reasoning in one line per job so you can catch bad calls.
- Fix and lockCorrect what is wrong, then ask for the crew texts.
Prompt · Shop rulesClaude
You are helping schedule installs for a residential fence company. Rules: - 3 crews: Crew A (vinyl + aluminum), Crew B (wood + chain link), Crew C (repairs and gates only). - We own 1 skid steer and 2 tow-behind augers. The skid steer can only be on one job per day. - Never schedule a dig without a locate ticket number in the list. - Never schedule a crew on a job where material status is not "on site" or "arrives before 7am". - Group jobs by area to cut drive time. - Crew day is 7am to 3:30pm. Do not invent footage, prices, or dates. If something is missing, list it under QUESTIONS.
Prompt · Draft the weekClaude
Here is this week's job list (CSV below). Build a Monday-Friday draft board as a table: Day | Crew | Job # | Area | Machine | One-line reason. After the table, list: 1. CONFLICTS (machine double booked, missing locate, material not on site) 2. QUESTIONS for the office 3. Jobs you could not fit and why. [paste CSV]
Prompt · Rain day replanClaude
Wednesday is rained out. Move Wednesday's jobs. Keep the same rules. Do not move any job that already has a customer-confirmed day unless you flag it. Show only what changed and who we need to call.
Prompt · Crew textsClaude
Write tomorrow's text for each crew lead. Plain, short, no emojis. Include: start address area, job #, footage and gates, machine pickup, anything weird (dog, tight side yard, HOA). Under 6 lines per crew.
Where it goes wrong
- It will cheerfully schedule a job with no locate ticket if you forget to give it the rule. Rules first, every time.
- It does not know how long your crews take on rock. Give it your own day sizes.
- It can lose track in a very long chat. Start a fresh chat each week and paste the rules again.
- It does not see your calendar unless you connect one. Treat its board as a draft you copy into your real system.
Shop guardrails
- Never paste full customer card numbers, bank info, SSNs, or gate codes into any chat tool.
- Strip names and addresses when you can. Job number + street name is usually enough context.
- Check the business terms of the plan you pay for. Free consumer tiers and business tiers can treat your data differently.
- A human sends it. Drafts go out only after someone in the office reads them.
- No invented numbers. If the tool gives you a price, lead time, or code rule you did not feed it, throw it out.