article-time-estimate-icon

4 minute read

Where Lupl Matters: Managing an International Regulatory Project

India Preston

India Preston

Lupl helps move legal work forward on International Regulatory Matters
In this article

    What is it?

    Regulatory frameworks are legal mechanisms that exist across most sectors and around the world. They are designed to control and monitor organizations and sectors in order to protect consumers, investors and the environment, among other things. Each jurisdiction has its own set of rules in line with its cultural and constitutional values, and these continuously evolve.

    The implementation of laws such as GDPR carry increasing fines for regulatory non-compliance. For many international companies, it can be very difficult to navigate changes in law across multiple jurisdictions. So organizations regularly seek advice about the regulations that apply to them directly in order to avoid the potential reputational and financial cost of non-compliance. 

    Who are the key legal players?

    International regulatory matters tend to be managed by an Associate in the Regulatory team. Depending on the complexity, they may work with other internal teams such as Litigation, Employment, Commercial and Corporate. Where the Associate’s firm has international presence, they will coordinate with lawyers from their firm in other jurisdictions as needed.

    When a law firm does not have presence internationally and requires local advice, this will involve coordinating with local counsel in each relevant jurisdiction. For example, a client may require advice on distributing an advertising campaign in 30 different countries. This would involve coordinating with local counsel, possibly all from different firms, in each of those 30 jurisdictions.

    New call-to-action

    What is the key deliverable?

    The client needs an answer to their enquiry. This may be embodied in a summary and a table or risk analysis which lays out the advice from each jurisdiction. The challenge is in collating all the inputs from different countries to get to the answer the client is looking for.

    What problems exist with it today?

    What problems exist with it today?

    • Relentless inbox traffic: issuing instructions, Q&A, gathering fee quotes and coordinating several iterations of the advice for each jurisdiction will overwhelm your inbox.

    • Difficulty identifying relevant local counsel: every lawyer has their own ‘little black book’ of local counsel. But with few shared or up-to-date contact books in law firms, it can be very time-consuming to find the best external team for your matter outside of your own network.

    • Manual handling of fee quotes and budget tracking: before the client presses ‘GO’, the Associate must present fee quotes from each jurisdiction for providing their advice. Collecting this information (and tracking progress against it) is a manual, time-consuming process, which often requires chasing.

    • Manual input into Excel progress trackers: very often, the Associate will use Excel to track each step of the journey with each jurisdiction – from ‘Conflicts email sent’ to ‘Final advice received.’ Or perhaps it’s a pen and paper job. This is a high risk process, requiring constant, manual effort to maintain it, with responsibility falling on one person alone.

    • Management of time, tasks and deadlines: with everything in Excel or on paper, it can be difficult to grasp how much still needs to be done, by whom and within what timeframe.

    • Collating advice and creating document templates: as local counsel advice comes in, it must be collated into a table. As comments are exchanged and new iterations of advice are prepared, it’s easy to lose track of the latest updates.

    How can Lupl help?

    Lupl can help you to operationalize your review and to manage your tasks, deadlines and documents more effectively. This reduces your administrative effort and helps to clear the fog!

    • Bring order to your stack of legal memos
      • Lupl can be the central place to store each jurisdiction’s advice (and it syncs with your DMS). Local counsel can upload their advice directly to the matter. Here, you can tag and sort the advice however it makes sense to you. Add new versions as they come in, keeping the latest at the top of the pile. Once you have received all your final versions, this will make collation much more straightforward.
      • Use Lupl’s powerful search tool to search both within and across your documents.

    • Manage your deadlines
      • Keep track of all the many deadlines – for the client, for firms to provide fee quotes and advice, for clarification questions, for Partner review…etc. Use tasks to plan out your timeline for the matter. Set a deadline for each task and Lupl will remind you as they become due. You can group your tasks by jurisdiction.
      • Check tasks off your lists as they are completed. With our iOS and Android apps, you can add, edit and check off tasks on the go.

    • Reduce the noise in your inbox
      • Work with local counsel inside a matter and keep everything together in one place. Link documents and tasks, reducing email traffic and increasing productivity.
      • Send documents in Lupl for comments to local counsel outside of the matter. They can populate the comments thread in the document by email.

    • Share responsibility for driving the matter forward
      • Assign tasks to local counsel and they can update them, reducing the burden on one person to manually update a spreadsheet.
      • Give access to the Matter Manager so they can check in on progress periodically.

    • Standardize your process by creating a matter template
      • Create a matter template in Lupl and begin your next regulatory project right away with pre-populated task lists, template documents (eg fee quote tracker) and pinned resources.
      • You could even start your own ‘little black book’ to add to your template and share with the rest of your organization. Perhaps others will add their contacts in too…

    And stay tuned. We’ve listened to the pinch points of these international regulatory projects and we are turning our minds to further improving this process for you!

    In this article
      Group 185

      Don't have time to read the whole article now?

      Find out how Lupl simplifies legal processes, helps manage information and deadlines for overwhelmed law firms.

      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....