Skip to content

Scheduling

Scheduling is how Laminar keeps your daily workload manageable. If you’ve read Scheduling Your Work in the Guides section, you already know the basics. This page goes deeper into how the concept works and why it’s designed the way it is.

Scheduling a task means setting a date for when it should appear in your active task list. It’s not a deadline. It’s not a calendar event. It’s the answer to: “When do I want to think about this next?”

The system uses this date to decide what to show you in My Tasks. Tasks scheduled for today (and anything overdue) appear in your Ready view. Tasks scheduled for the future are tucked away in the Future view. Tasks with no date also appear in Ready alongside overdue items.

This sounds simple, and mechanically it is. The impact on how your day feels is where it gets interesting.

Most software shows you all your open items all the time. The assumption is: more visibility equals better. You can see everything, so you won’t miss anything.

In practice, the opposite happens. When you have 300 open tasks across 80 matters, “seeing everything” means seeing nothing. You can’t prioritize a list of 300. You end up scanning the same items repeatedly, building a mental picture of what actually needs attention today, and that mental picture is exhausting to maintain and easy to get wrong.

Scheduling replaces the mental picture with an explicit system. Instead of remembering that you need to follow up on the Smith search results on Wednesday, you schedule the task for Wednesday and stop thinking about it. Your brain is freed up for the work that’s actually in front of you.

The tradeoff is trust. You have to trust that the system will surface things when you’ve told it to. That trust builds quickly once you see it working, but the first few days can feel uncomfortable if you’re used to keeping everything visible.

My Tasks organizes your work into views based on scheduling:

Everything that needs your attention now. This includes tasks where the scheduled date has passed (overdue) and tasks with no date set (unscheduled). Overdue items are highlighted so you can spot them immediately.

A growing number of overdue items is a signal. It might mean you’re over-committed, or that some tasks are blocked and need to be rescheduled rather than ignored.

In a well-maintained schedule, your Ready view represents a realistic picture of what you need to accomplish. If it regularly has 40 items in it, that’s probably too many. Not because you can’t look at 40 things, but because you probably can’t complete 40 things in a day. Better to schedule some for later and keep the list honest.

Tasks scheduled for upcoming dates. These are out of your way until their day arrives, but you can switch to this view anytime to see what’s coming. This is useful for planning: if you can see that Thursday already has 15 tasks scheduled, maybe don’t pile more on.

Tasks you’ve finished. They’re here if you need to look something up, but they’re not cluttering your active views.

An important distinction: the scheduled date is about when you want to see the task, not when the task is “due” in a deadline sense.

If a closing is on Friday and you need to prepare documents, scheduling “Prepare closing documents” for Friday is too late. You’d schedule it for Wednesday, giving yourself time to actually do the work.

Some firms use scheduling as a soft deadline system: “this task should be done by this date.” That works fine too. The point is that whatever date you set determines when the task will appear in your active view.

Laminar doesn’t currently have a separate “due date” field distinct from the schedule date. They’re the same thing. If your team needs to differentiate between “when I plan to work on it” and “when it’s actually due,” a common pattern is to schedule the task for when you plan to start, and use the description or a note to record the actual due date.

Changing a task’s scheduled date is expected and normal. Schedules shift. Priorities change. New urgent work arrives. That’s fine.

When you reschedule a task:

  • It immediately repositions in your My Tasks list based on the new date.
  • The change is logged in the activity timeline.
  • If it was overdue, rescheduling to a future date moves it out of your Ready view.

There’s no penalty or stigma attached to rescheduling. The goal isn’t to hit every date perfectly. The goal is to keep your schedule honest so that what you see in Ready is what you’re actually going to work on.

That said, if you find yourself rescheduling the same task repeatedly, that’s worth noticing. It might mean the task isn’t well-defined, it’s blocked on something else, or it’s just not a priority and should be reconsidered entirely.

The real value of scheduling shows up when you’re managing a large caseload.

Consider a firm handling 200 active matters. Those matters collectively hold maybe 800 open tasks. Nobody can look at 800 things and make good decisions. But with scheduling:

  • 350 of those tasks are scheduled for future dates (they’ll surface when relevant)
  • 200 are unscheduled (need date decisions, but they’re separated out)
  • 150 belong to other team members (not in your view at all)
  • Your Ready list has 20 items on it

Twenty items. That’s a list you can finish. That’s a list where you can see what’s important and make real progress. When you finish it, tomorrow’s 18 items are already queued up.

This is why scheduling isn’t optional or a nice-to-have. At high volume, it’s the mechanism that makes the workload possible.

If you manage a team or assign work to others, scheduling is also a planning tool.

When you create tasks and assign them to team members with specific schedule dates, you’re building their daily plans in advance. A team lead might spend Friday afternoon scheduling next week’s work across their team, so that everyone walks in Monday with a clear list.

Team members can reschedule tasks you’ve assigned them. This is by design. They know their day-to-day capacity better than you do from a planning seat. The schedule is a starting point that creates structure, not a rigid mandate.