Skip to content
Start free
Feature

Standing meetings, monthly admin, weekly retainer time — handled once.

A freelance week has more rhythm than a salaried one. The Tuesday standup, the Friday invoicing block, the monthly review. Define each once and Ensar schedules it forward, respecting your work hours.

Start freeAll features
The problem

Where this usually breaks.

Recurring work is the most-underestimated time sink in freelance life. Each instance feels small. The aggregate eats whole days — a freelancer with 3 weekly calls and 1 monthly admin day spends ~48 hours per quarter on standing time, before a single deliverable lands.

Most calendar apps treat each recurring block as identical. In reality, the “30-minute call” that runs 50 minutes does that *every* week. Treating it as a fixed 30 gives you an artificially optimistic week, every week.

Today view shows recurring blocks like any other — same color, same money chip, same first-action.

How Ensaria handles it

Define a recurrence pattern (weekly Tuesday 10am, every weekday morning 9am, last Friday of the month). Ensar materialises the instances forward through your declared work hours. Edit one — choose “this only,” “this and future,” or “all instances.” Same pattern as every calendar app worth using.

Each recurring block accrues its own reference-class history. If your nominal “30-minute weekly call” has averaged 47 minutes across the last 12 instances, Ensar uses 47 in capacity calculations. The plan respects what actually happens, not what the calendar pretends.

Recurring + retainers

Recurring blocks can be tagged with the retainer they belong to. The retainer's hours-included bucket tracks the cumulative time automatically. Recurring work that overflows the bucket surfaces in the Sunday Review — quietly, in mono, the first month it starts.

In the product

Where this shows up.

A few other surfaces in Ensaria where the same idea lives — none of these are settings you opt into; they're how the product behaves by default.

Each instance is a regular block on the calendar — same first-action, same money chip if billable.

Retainer projects show hours-used vs hours-included; recurring blocks count toward the bucket automatically.

Sunday Review flags retainer overage from recurring drift the first month it happens — not nine months later.

Today highlights recurring vs ad-hoc so you can see at a glance what's standing time vs new work.

Common questions

What about an instance I want to skip without affecting future ones?

Open the instance and pick "Skip this only." The recurrence rule continues; just this one occurrence is dropped. The Sunday Review notes it as a skipped block, not as missed work.

Can I attach a different first action to one instance?

Yes. Editing the first action in a single instance only changes that instance — Ensar doesn't propagate first-action changes. Useful for that one week where the standup needs to start with a specific topic.

How does Ensar handle holidays / vacation days?

Mark days off in Settings → Work hours. Recurring instances scheduled on those days move forward to the next available work day or skip entirely, depending on the recurrence's 'on holiday' setting.

Related

Read further.

Recurring work term

Why standing work is the silent driver of where your week went.

Retainer term

The pricing shape that creates most recurring work.

Work hours

The boundary recurring work respects.

For retainer-first freelancers

How retainer-heavy freelancers use this surface.

Free for one active project. No card.

Pro unlocks unlimited everything. Cancel anytime.

Create account
EU-hosted · Export anytime · Delete anytime