Recurring work is everything on your calendar that happens on a schedule rather than a one-off basis. Weekly standups. Monthly retainer hours. Daily check-ins. Quarterly invoicing days. The standing Friday Slack review.
It's the most under-noticed time sink in freelance life: each instance is small enough to ignore, but the aggregate eats whole days. A freelancer with three weekly client calls and one monthly admin day spends roughly 48 hours a quarter on recurring work before they've done a single deliverable.
Why it's hard to plan for
Calendar apps render recurring work as if each instance is the same — same duration, same start time, same energy cost. In real life:
- the weekly call that "should" be 30 minutes often runs 50,
- the monthly admin day quietly absorbs everything you've been postponing,
- the daily check-in compounds because it requires context-rebuild every morning.
Treating these as cheap, fixed blocks gives you an artificially-optimistic week. Forecasting them honestly is the difference between "I have 30 hours this week" and "I have 21 hours after recurring work, four hours of buffer, and 17 hours of real client time."
How Ensaria relates
Recurring work in Ensaria is a first-class scheduling concept: define a recurrence once (weekly Tuesday 10am, every weekday morning 9am, last Friday of the month), and Ensar materialises the instances forward, respecting your work hours. Edits propagate three ways (this only / this and future / all). Capacity calculations subtract recurring work before showing you "available hours this week," so the number you see is honest.
Each recurring block also accrues its own reference-class history: if your "30 min weekly call" has actually averaged 47 min across the last 12 instances, Ensaria will tell you that's the realistic estimate, not the calendar one.
Related terms
- Retainer — the pricing shape that creates recurring work.
- Capacity — what recurring work eats from.
- Scope creep — what makes each instance bigger than planned.