article-time-estimate-icon

3 minute read

Who’s doing what across my matters and how’s it going?

Matt Pollins

Matt Pollins

table
In this article

    In the process of building our initial beta release, we’ve spent a lot of time listening to lawyers and industry professionals around the world. General counsel. Legal counsel. Legal ops. Partners. Associates. In fact, we didn’t put down a single line of code for the platform until we’d spent many months in listening mode.

    We learned a lot from those conversations. So, in the first of a series of posts, we wanted to share some of what we learned, and how we factored that into Lupl.

    The situational awareness challenge

    “I don’t manage situational awareness of my matters very effectively. At all. I mean, who’s doing what? And where? And how’s it going? These are the things I need to know when I’m picking up my phone first thing in the morning. But there’s no real-time way to get that stuff.”

    “For us, even looking at each type of matter has become overly complicated with the things that people ask for and then what they actually need to do the job. I don’t know what the right balance is, honestly. But the things that you need are, whose hands is it in? Where is it? What’s the ETA? Are there blockers? Where do I need you? Where do you need me?”

    “It’s what I call the ‘subway platform mentality’. When I’m standing on a subway platform, waiting for a train, I’m pretty relaxed as long as the information board is there showing me what’s happening and when my train is coming. But if that board is broken, I freak out, because I have no idea where things stand, or how long I’ll be waiting.”

    These are extracts from the notes of some of the earliest conversations we had with lawyers and legal ops folks about Lupl. We could share a lot more because this was a consistent thread throughout all of our conversations. It’s about the need to manage situational awareness of legal matters, to get that real-time, 360-degree view of what is happening right now.

    So if everyone wants that, why is it proving so difficult to get it?

    Why it’s harder than it should be

    Here are some of the reasons we heard…

    1. Workloads increasing and resources are stretched.

    This is the most obvious reason. The international business environment is more complex than ever. There’s GDPR. There’s Brexit. There’s the US/China trade war. There’s COVID-19. The demands on lawyers are growing – there’s just a lot going on, and it’s tough to stay on top of all of that.

    2. Too many tools and systems.

    There’s a general feeling that there are too many places to look to find what you need. If you have to check across your email, your Slack, your Teams, your intranet, your law firm portals, and your messages, it’s no wonder that everything feels spread all over the place. “Did I send it to you, or did you to send it to me? Or did Jeff send it?”

    3. An allergic reaction to anything that looks like “busy work”.

    One GC put it like this:
    “So this is the impossible wish. Every time we’ve asked this question around our network of lawyers, they just say literally ‘they want to know exactly what’s going on everywhere, instantaneously’. The flip side of that is…nobody’s prepared to contribute.”
    There’s a feeling that getting visibility is great. But spending a ton of time pulling together status reports? No thanks, not worth the effort. They’re out of date almost as soon as they are written.

    4. An increasingly distributed team.

    When we first started working on Lupl, we heard from a lot of users about a shift towards more mobile working and distributed teams:


    “I think the way of the world is that more people will be working remote. And potentially in different offices. The days of the whole team sitting in the same office, or building, or even the same city, seem to be increasingly behind us. Being able to pop over to someone’s desk and ask how that Term Sheet negotiation is going starts to get a little bit harder.”


    And clearly the COVID-19 crisis has accelerated this shift far quicker than anyone could ever have imagined.

    So what does this all mean for Lupl?

    We spent a long time thinking about situational awareness of matters. After a couple of weeks, a lot of coffee, and several conversations with our Advisory Board, we came up with a couple of ideas for things that might help.

    “Matter Synchronisation”

    The first is what we call “matter synchronization”. What does that mean? It means bringing everything for a legal matter together in one place, rather than all over the place. By bringing together all of those moving parts – the people, the conversations, the documents, the systems – our hope is that situational awareness becomes easier.


    It’s important of course that Lupl doesn’t become “yet another channel” that you need to check to figure out what’s happening. That’s why Lupl is a totally open industry platform – bridging multiple solutions to enable users to plug in their systems and get everything they need in one place. This open approach is the core of what we’re trying to do with Lupl and we’ll be sharing more about it in the coming months.

    “Matter Pulse”

    The second feature is something we call “Matter Pulse”. The initial inspiration for this came from a discussion with a startup GC and Head of Legal Ops in San Francisco – and it grew from there as we bounced it off other parts of our community. The goal with Matter Pulse is to enable users to easily capture and track where a matter is at and how it is going.

    What’s next?

    We hope these things go some way towards making situational awareness around matters easier. But we’re under no illusion that this is perfect or solves everything. We’re always on the lookout for more ideas. One of the things we’re thinking about is automating some of matter status visibility. If you have some suggestions about how to make this easier, drop us an email at hello@loopl.net. We’re all ears!

    In this article

      More legal tech insights we think you'll love

      The cost of over-dependence on AI

      AI saves us time, boosts productivity, and lets us do...

      # Lupl Workstream Design Principles: A Practical Guide to Legal Project Management for Lawyers Legal project management works when your setup is simple, ownership is clear, and statuses are unambiguous. This guide shows how to turn existing processes and checklists into a lean, reliable Workstream. Lupl is the legal project management platform for law firms, making it easy and intuitive to apply these principles. It also supports moving your work from Excel, Word tables, or if you are transitioning from Microsoft Planner, Smartsheet, or Monday. You will learn what belongs in a Workstream, a Task, or a Step, and which columns to use. If you want practical project management for lawyers, start here. **Excerpt:** Legal project management works when ownership, dates, and statuses are clear. This guide shows lawyers how to turn checklists into Lupl Workstreams with the right columns, Tasks, and Steps. Use it to standardize project management for lawyers, reduce follow ups, and move matters to done. --- ## How to organize your work with Workstreams, Tasks, and Steps Workstreams, Tasks, and Steps are three different types of objects in Lupl. They form a simple hierarchy. Workstreams contain Tasks. Tasks may contain optional Steps. This hierarchy aligns with standard project management. In project management, you break work into projects, deliverables, and subtasks. Lupl adapts this for lawyers by using Workstreams, Tasks, and Steps. This makes it easier to map legal processes to a structure that teams can track and manage. * **Workstream.** Use when you have many similar or related items to track over time. Think of the Workstream as the table. * Examples: closing checklist, court deadlines, pretrial preparation, regulatory obligations, due diligence, local counsel management. * **Task.** A high level unit of legal work. A key deliverable with an owner and a due date. Tasks are the rows. * Examples: File motion. Prepare Shareholder Agreement. Submit Q3 report. * **Step.** An optional short checklist inside a single Task. Steps roll up to the parent Task. * Examples: Draft. QC. Partner review. E file. Serve. ### Quick test * If it can be overdue by itself, make it a Task. * If it only helps complete a Task, make it a Step. * If you need different columns or owners, create a separate Workstream. --- ## Do you need to track everything in Lupl Not every detail needs to be tracked in a project management system. The principle is to capture what drives accountability and progress. In Lupl, that means focusing on deliverables, not every micro action. * Use the level of detail you would bring to a weekly team meeting agenda. * Position Tasks as key deliverables. Treat Steps as optional micro tasks to show progress. * Example: You need client instructions. Do not add a Task for "Email client to request a call." Just make the call. If the client approves a key deliverable on the call, mark that item Approved in Lupl so the team has visibility. --- ## Start with the Core 5 columns Columns are the backbone of a Workstream. They define what information is tracked for each Task. In project management terms, these are your core metadata fields. They keep everyone aligned without overcomplicating the table. Keep the table narrow. You can add later. These five work across most legal project management use cases. 1. **Title.** Start with a verb. Example: File answer to complaint. 2. **Status.** Five to seven clear choices. Example: Not started, In progress, For review, For approval, Done. 3. **Assignee.** One named owner per row. If you add multiple assignees for collaboration, still name a primary owner. 4. **Due date.** One date per row. 5. **Type or Category.** Show different kinds of work in one table. Example: Filing, Discovery, Signature, Approval. **Priority.** Add only if you actively triage by priority each week. If added, keep it simple: High, Medium, Low. --- ## Add up to three Helper columns Lupl includes a set of pre made columns you can use out of the box. These allow you to customize Workstreams around different phases or stages of a matter. They also let you map how you already track transactional work, litigation, or other processes. Helper columns are optional fields that add context. In task management, these are similar to tags or attributes you use to sort and filter work. The key is to only add what you will update and use. Pick only what you will use. Stop when you reach three. * Party or Counterparty * Jurisdiction or Court * Phase * Approver * Approval, status or yes or no * Signature status * Risk, RAG * Amount or Number * External ID or Client ID * Document or Link * Docket number * Client entity **Guidance** * For Task Workstreams, prefer Approver, Approval, Risk. The rest are more common in Custom Workstreams. * Aim for eight columns or fewer in your main table. Put detail in the Task description, attachments, or Steps. --- ## Simple rules that keep your table clean Consistency is critical in project management. A cluttered or inconsistent table slows teams down. These rules ensure your Workstream remains usable and clear. * Only add a column people will update during the matter. If it never changes, set a default at the Workstream level or set a default value in the column. * Only add a column you will sort or filter on. If you will not use it to find or group work, leave it out. * If a value changes inside one Task, use Steps. Steps show progress without widening the table. * Keep columns short and structured. Use Description for brief context or instructions. Use Task comments for discussion and decisions. Link to work product in your DMS as the source of truth. * One accountable owner per Task and one due date. You can add collaborators, but always name a primary owner who moves the Task. If different people or dates apply to different parts, split into separate Tasks or capture the handoff as Steps. * Add automations after you lock the design. Finalize columns and status definitions first. Then add simple reminders and escalations that read those fields. --- ## Status hygiene that everyone understands Status is the single most important column in project management. It tells the team where the work stands. Too many options cause confusion. Too few cause misalignment. In Lupl, keep it simple and consistent. * Five to seven statuses are enough. * Use one review gate, For review or For approval. Use both only if your process needs two gates. * One terminal status, Done. This is the end state of the Task. Use Archived only if you report on it or need it for retention workflows. --- ## When to split into multiple Workstreams In project management, it is best practice to separate workstreams when workflows, owners, or audiences diverge. Lupl makes this easy by letting you create multiple Workstreams for one matter. Create a new Workstream if any of the following are true. * You need a different set of columns for a chunk of work. * Ownership or cadence is different, for example daily docketing vs monthly reporting. * The audience or confidentiality needs are different. **Signal** * If half your rows leave several columns blank, you are mixing processes. Split the table. --- ## Decision tree, three quick questions Use this quick framework to decide where an item belongs. This is the same principle used in task management software, adapted for legal workflows. 1. Is this a list of similar items over time, or a discrete phase of the matter * Yes. Create a Workstream. 2. Can it be overdue by itself, and does it need an owner * Yes. Create a Task. 3. Is it a step to finish a Task and not tracked on its own * Yes. Create a Step. --- ## Common mistakes to avoid Many project management failures come from overdesigning or misusing the structure. Avoid these mistakes to keep your Workstreams lean and effective. * Wide tables with many optional columns. Keep it to eight or fewer. * Two columns for the same idea, for example Status and Phase that overlap. Merge or define clearly. * More than one approval gate when one would do. It slows work and confuses owners. * Mixing unrelated processes in one table, for example signatures and invoice approvals. --- ## Build your first Workstream Building a Workstream is like setting up a project board. Keep it light, pilot it, then refine. Lupl is designed to let you do this quickly without heavy admin work. 1. Write the Workstream purpose in one sentence. 2. Add the Core 5 columns. 3. Add at most three Helpers you will use. 4. Define clear Status meanings in plain words. 5. Set defaults for any value that repeats on most rows, for example Jurisdiction. 6. Add two light automations, a due soon reminder and an overdue nudge. 7. Pilot for one week and adjust. --- ## Where this fits in legal project management Use these principles to standardize project management for lawyers across matters. Keep structures consistent. Reuse column sets and status definitions. Your team will find work faster, reduce follow ups, and close loops on time. --- ### On page SEO helpers * Suggested title tag. Lupl Workstream Design Principles, Practical Legal Project Management for Lawyers * Suggested meta description. Learn how to design lean Lupl Workstreams for legal project management. Get clear rules for Tasks, Steps, statuses, and columns to run matters with confidence. * Suggested URL slug. legal-project-management-for-lawyers-workstream-design

      Lupl Workstream Design Principles: A Practical Guide to Legal Project Management for Lawyers

      Learn why large‑firm lawyers are ditching Excel checklists for dynamic,...

      Do AI Agents Have An Identity? Notes from InfoSec Discussions

      Agentic AI is in its early phases but advancing fast....