The AI rule builder

Writing a good rule means noticing a pattern, knowing which of twenty rule types fits it, and translating one into the other. Blecon Track AI does the noticing and the translating for you, two ways:

Suggest rules reads your workspace's own data (where assets go, how often they come back, which journeys they make) and drafts the rules that data supports.
Describe it instead turns one sentence, written your way, into a rule draft: "tell me if a forklift is still out after 6pm".

Either way, the result is a draft in the normal rule editor. Nothing is created until you review it and click Add Rule. The AI never switches a rule on by itself.

Suggest rules from your data

On the Rules page, click ✨ Suggest rules. Blecon Track AI profiles your workspace (zones and their traffic, visit rhythms, journeys, assets that have gone quiet) and proposes up to five rules, each with the numbers that justify it:

38 of 42 cages return to Depot North within 3 days. 4 have not been back for over 9 days.

Each suggestion offers two actions:

Review opens the rule editor with the draft filled in: the zone, the threshold, the name. Adjust anything, then click Add Rule to create it like any hand-written rule.
Dismiss removes it, and it stays dismissed: asking for suggestions again proposes new ideas, never the ones you said no to.

Suggestions only ever reference zones, asset keywords and rule types your workspace actually has. A workspace with too little data to read simply gets no suggestions.

Describe the rule instead

At the top of the + Add Rule dialog, the Describe it instead box takes one sentence and turns it into a draft. Write it the way you would say it:

"Tell me if a truck has not come back to Barcelona Port within 5 hours"
"Let me know about any driving between midnight and 5am"
"Alert me when a delivery van arrives at the Atlanta warehouse"

Click Draft it. The draft lands on the configure step with everything filled in, and a Read as line above the form restates, in plain words, what Blecon Track AI understood:

Read as: Alerts when a truck has not come back to Barcelona Port within 5 hours.

Check that line first. If the reading is wrong, the form below it will be too. Edit the form, or go back and rephrase. Numbers in your sentence become the parameters exactly: "more than 2 hours" is 2 hours, "by 6pm" is 18:00.

Journey-shaped requests (arrivals, departures, routes, journeys that run long, assets vanishing mid-route) draft as trip rules where your workspace has trips, because a trip rule follows the journey rather than a zone boundary and false-alarms less.

Your sentence is kept on the created rule and shown on its detail page, so the whole team can see what the rule is for, in the words it was asked for.

When it cannot draft

Sometimes the answer is "could not draft that": the sentence names a place that matches no zone, asks for something no rule type can express, or duplicates a rule you already have. There is no guessing: a rule bound to the wrong zone would be worse than no draft. Rephrase with a zone name and a condition, or pick a rule type by hand; the picker is on the same screen.

When a rule fires too often

If a rule keeps producing alerts your team marks as False alarm, Blecon Track AI notices and drafts a fix. The rule's detail page shows the advice under "This rule looks too sensitive", with the evidence and the change in plain words:

9 of 11 alerts were marked false alarm and lasted under 5 minutes; requiring 5 minutes inside the zone stops them without hiding real entries.

Review change opens the rule editor with the revised parameters filled in - same rule, same places, only the thresholds change - and nothing is applied until you click Update Rule. Dismiss clears the advice.

Limits and trust

Drafting uses a daily allowance per workspace, shared between suggestions and described rules. It resets each day and is sized so normal use never meets it.
The AI reads only your own workspace's data: your zones, your assets, your rules, your journeys.
A draft is advice. The rule that gets created is always the one you can see in the editor at the moment you click Add Rule.