Set your iqamah times once. Let the engine keep them right all year.
Prayer (adhan) times shift a little every day as the sun moves. Instead of editing iqamah times for all 365 days, you write a few rules per prayer. The engine reads them and generates your whole calendar — keeping each iqamah on a clean, stable time and nudging it in tidy steps as the season changes.
A rule answers a single question: “Given today’s prayer time, what should the iqamah be?” Define that answer once and it applies every day, forever — until you change it.
Why rules instead of typing every day
Say your masjid prays Fajr iqamah about 20 minutes after adhan, but you like round times and never before 5:00 AM. Typing that for 365 days is painful and error-prone. As a rule, it’s three settings — and the engine handles sunrise creeping earlier in spring and later in winter for you.
- Stable & predictable — times land on clean minutes (e.g. every :00 / :15) and only change in tidy jumps, so your congregation isn’t chasing a new time daily.
- Bounded — you set the earliest and latest an iqamah may ever be, so it never drifts somewhere unreasonable.
- Seasonal — separate rules can kick in for Ramadan or when daylight saving flips, without touching your normal schedule.
The three rule types
Every prayer uses one rule type at a time. Pick the simplest one that matches how your masjid actually decides its iqamah.
A set clock time
The iqamah is always the same time. It never moves with the sun.
Minutes after adhan
A fixed offset after the prayer time. It moves exactly with adhan, every single day.
Smart & rounded
Follows adhan but snaps to clean minutes, stays within your limits, and changes only in steps.
Fixed = type a time. Calculated = type a number of minutes. The rest of this guide focuses on Predictive, because that’s the one worth understanding — and the one most admins get stuck on.
The Predictive rule, field by field
A Predictive rule takes today’s prayer time, shifts it by a minimum gap, rounds it to a clean step, and then clamps it between an earliest and latest bound. Five settings control all of that:
| Field | What it does | Example |
|---|---|---|
From End of Salah |
Measure from the end of the prayer window (sunrise for Fajr, the next prayer for others) instead of its start. When on, the engine rounds down so iqamah stays safely before the window closes. | On for Fajr (before sunrise). Off for most others. |
Min Gap |
The minimum minutes between the prayer time and the iqamah — your buffer so people have time to gather. | 20 minutes after adhan. |
Change By |
The rounding step. Iqamah only ever lands on a multiple of this, and only moves in these increments — this is what keeps the time clean and stable. | 15 → times like 5:15, 5:30, 5:45. |
Min Time |
The earliest the iqamah may ever be. Acts as a floor. | 5:00 AM (never earlier). |
Max Time |
The latest the iqamah may ever be. Acts as a ceiling. | 6:30 AM (never later). |
How the engine computes an iqamah
For a normal Predictive rule (From End of Salah off), the engine runs four steps in order:
# Example: Fajr adhan today is 5:12 AM 1. Start from the prayer time → 5:12 2. Add the Min Gap (20 min) → 5:32 3. Round UP to the Change By step (15) → 5:45 4. Clamp between Min 5:00 and Max 6:30 → 5:45 AM
When From End of Salah is on, it flips: the engine starts from the window’s end, subtracts the gap, and rounds down — so the iqamah sits a safe margin before sunrise or the next prayer.
The engine evaluates a rule across the whole week and uses the week’s edge, so one clean time holds for all seven days and then steps to the next. That’s the “predictive” part — a steady schedule your congregation can memorize, not a number that wobbles daily.
Try it: Predictive rule simulator
This runs the exact rounding logic the engine uses. Change the settings and the adhan time, and watch the iqamah — and the steps behind it — update live.
Presets to try: Fajr · Dhuhr · Isha (loose) · Maghrib (from end)
Seasons & daylight saving: the Applicable setting
Each prayer can hold more than one rule. Applicable decides when a rule is in force, so you can layer a special schedule on top of your normal one:
| Applicable | When it applies | Typical use |
|---|---|---|
Standard / AllYear | Your everyday rule — the default whenever nothing more specific matches. | Normal iqamah schedule. |
DST | Used only while daylight saving time is active. Overrides Standard on those dates. | A shifted summer schedule. |
Date Based | Applies only between a Start Date and End Date you set. | Ramadan / Taraweeh, Eid week. |
The engine picks in this order: an active DST rule wins if daylight saving is on; otherwise your Standard rule; a Date Based rule fills in when today falls inside its window. Start and End dates can even be pinned to the daylight-saving switch using {DSTStartDate} and {DSTEndDate}.
Jumu’ah (Friday) prayers
Jumu’ah is set up on its own, separate from the five daily prayers — because Friday prayer works differently. It’s held at a fixed community time rather than derived from the sun, and many masjids hold more than one session.
Multiple sessions
You can define several Jumu’ah sessions — Jumu’ah‑I, Jumu’ah‑II, and so on — each with its own Azan and Iqamah time. Enable an extra session only if your masjid actually holds one.
| Session | Azan | Iqamah | Applicable |
|---|---|---|---|
| Jumu’ah‑I | 1:15 PM | 1:30 PM | All-Year |
| Jumu’ah‑II | 2:15 PM | 2:30 PM | All-Year |
What’s the same, what’s different
- Same idea, simpler. Each session still has a rule with a
Typeand anApplicablescope — but since Friday prayer is a set time, it’s almost always Fixed (a clock time like 1:30 PM). Predictive and Calculated aren’t the usual choice here. - Scopes are Standard, DST, and All-Year only. Unlike the daily prayers, Jumu’ah has no
Date Basedoption. To change Friday times for a season, edit the session directly. - Per-session selection. The engine resolves each session on its own — so Jumu’ah‑I and Jumu’ah‑II can keep independent times.
Daylight saving
Give a session a DST variant to shift it in summer. While daylight saving is active the engine uses the DST time; otherwise it uses Standard. An All-Year time applies whenever it’s set, regardless of season.
# Jumu’ah-II moves an hour later in summer Jumu’ah-II Applicable: Standard Azan: 1:15 PM Iqamah: 1:30 PM Jumu’ah-II Applicable: DST Azan: 2:15 PM Iqamah: 2:30 PM
Jumu’ah is configured in its own step of Salah Management in the Admin portal — add or enable each session, then set its Azan and Iqamah times.
Recipes you can copy
Fajr — tidy, tracks sunrise, never too early
Type: Predictive From End of Salah: Off Min Gap: 20 Change By: 15 Min Time: 5:00 AM Max Time: 6:30 AM # ~20 min after adhan, rounded to :00/:15/:30/:45, clamped 5:00–6:30
Isha — a simple constant time
Type: Fixed Time: 8:00 PM # Same every night, regardless of adhan.
Dhuhr — a flat offset after adhan
Type: Calculated Minutes After: 10 # Always exactly 10 minutes after the Dhuhr adhan.
Ramadan Isha — a seasonal override
Type: Fixed Applicable: Date Based Time: 9:30 PM Start: 01-Mar End: 31-Mar # Runs only during Ramadan; your Standard Isha resumes after.
Common pitfalls
- Min/Max too tight. If
Min TimeandMax Timeare very close, the iqamah gets pinned to a bound and stops tracking the sun. Give it room unless you truly want a near-fixed time. - Change By of 1. Rounding to 1 minute means the time can move almost daily — the opposite of a stable schedule. Most masjids use 5, 10, or 15.
- Forgetting
From End of Salahfor Fajr. Fajr iqamah must land before sunrise. Turn this on so the engine rounds down toward the window’s end instead of up past it. - A Date Based rule with no Standard rule. Date Based only covers its window. Always keep a Standard rule so the rest of the year is defined.
Tell us how your masjid decides each iqamah and we’ll translate it into rules on a quick call. Reach Masjidi support on WhatsApp — we’re happy to help.