Football matches rarely change on a single event alone. More often, goals are preceded by sustained periods of pressure, territorial dominance, and repeated attacking actions. Recognizing these phases early is the whole idea behind Smart Alerts — but building a multi-condition alert from a blank screen means deciding on event types, thresholds, and time windows all at once, and it's easy to end up with something too narrow to ever fire or too broad to mean anything.
What Templates Actually Are
When you create a new Smart Alert, Goal Guru shows a row of templates above the option to build one from scratch, with the prompt "Choose a template to get started quickly, or create from scratch." Each template is a pre-filled set of conditions built around a recognizable match pattern — sustained pressure without a goal, a fast start from the side expected to win, cards piling up in a tense match, that kind of thing. Pick one and every setting is already populated with sensible values; you're not starting from zero, you're starting from something that's already a reasonable alert.
Templates only appear when you're creating a new alert, not when editing one you already have — once you've picked a starting point (template or blank), you're editing a normal Smart Alert from there with no special restrictions.
The Conditions Behind the Patterns
There's no hidden scoring formula behind a template — it's built from the same condition types available to you when configuring an alert manually. Two layers matter most for recognizing a developing pattern rather than a single moment:
Event counts over a time window: shots, corners, cards, and other raw events, counted within a rolling window you define — for example, 5+ shots in the last 15 minutes.
Situation duration: how long a team has spent in an attacking or dangerous position, as opposed to a safe, uncontested one. A team that's spent 10+ minutes of the last 15 in a dangerous situation is a materially different signal than one that's had a single shot from distance — the duration condition captures sustained control that a raw event count alone can miss.
A template that's watching for building pressure typically combines both: an event-count condition (shots, corners) alongside a situation-duration condition, so the alert only fires when activity and sustained territorial control show up together — closer to how you'd actually judge momentum by eye than either signal alone.
Customizing What You Start With
A template is a starting point, not a fixed package. After selecting one, every condition is fully editable — swap the target team, tighten or loosen the thresholds, add a league filter, or combine it with an additional condition type entirely. If a template's default of "5+ shots in 15 minutes" is triggering more often than you'd like, narrow it to 7. If you only care about this pattern for your favorite team, restrict the target. Nothing about starting from a template locks you into someone else's exact configuration.
Test Before You Trust It
Whether you started from a template or built an alert from scratch, the same rule applies before you rely on it during a live match: backtest it against recent games first. A template gets you to a working alert faster, but it doesn't guarantee the thresholds are right for the leagues or teams you actually follow — a 30-day backtest tells you how often it would have fired and what tended to happen afterward, which is the difference between an alert you trust and one you're just hoping works.
Templates exist to remove the blank-page problem, not to replace understanding what your Smart Alert is actually watching for. Start from one, read through what it's checking, and adjust it until it's watching for the specific pattern you care about.