article-time-estimate-icon

3 minute read

Why Lupl Chose to Pursue SOC 2 Compliance in its First Year

Matt Pollins

Matt Pollins

lupl to persue SOC2
In this article

    We are excited to announce that Lupl recently completed its SOC 2 Type I audit – just a few months after its commercial launch. SOC 2 is an international gold standard for security and requires a significant cost and time commitment to obtain, so it’s no surprise that few early-stage startups prioritize in such a certification so early in their journey. So why did we choose to subject ourselves to third-party scrutiny at a time of rapid growth and change?

    One word: Trust.

    Get a free demo or try Lupl for free.

    Trust is a Core Value for Lupl

    If you’re not among the thousands of legal professionals using Lupl today, you might wonder why trust is so important to our company. Lupl is a secure legal collaboration platform that makes it easy for everyone to work together on legal matters within and between organizations. It combines powerful native communication, collaboration, and legal project management functionality with the ability to plug and play with your own tools and systems. Among our clients are some of the largest law firms and corporations who manage their clients’ and customers’ most sensitive and personal information, making platforms that support legal prime attack vectors. In fact, according to the American Bar Association, about 80% of the largest law firms have experienced some sort of cybersecurity violation.

    So frequently, we’re told we must trade innovation, utility, and convenience in the pursuit of information security. We just don’t believe that’s true. That’s why we built Lupl with Privacy by Design principles at its core, which says that, “When embedding privacy into a given technology, process, or system, it should be done in such a way that full functionality is not impaired, and to the greatest extent possible, that all requirements are optimized.” We believe it’s not only possible, but also our obligation,

    to deliver a platform with the full functionality you need without sacrificing privacy and security.

    This is precisely why we’ve committed so much time and budget to privacy and security. We’ve baked security into our software deployment process and regularly subject our systems to third-party penetration testing. Our corporate IT environment is more aligned to a large corporation than a startup, and we’ve recently employed a Security Operations Center that ensures we have people and technology detecting and responding to threats 24 hours a day, every day.

    Security is Never ‘Done’

    At Lupl, security is never done. Before turning our efforts to our SOC 2 Type 1 examination, we completed the Level 1 self-attestation via Cloud Security Alliance’s Security, Trust, Assurance, and Risk (STAR) Registry, to make it easy for current and potential customers to evaluate our security and compliance posture. You can access our self-assessment in the publicly available STAR registry here.

    So, what’s next for Lupl’s Security team? We’ve already entered the audit period for our SOC 2 Type 2 examination, which will review how we deliver upon SOC 2’s trust principles over the course of the next six months. We also asked our auditors to map our policies and procedures to HIPAA standards as a part of their SOC 2 Type 1 audit and are happy to report that our path to compliance is clear. Later this year, we’ll seek the ISO/IEC 27001 certification for information technology security techniques governed by the International Organization for Standardization. And, in 2023, we’ll focus on attaining the Cloud Security Alliance’s STAR Level 2 certification, which builds on other industry certifications and standards to make them specific for the cloud.

    About SOC 2 Compliance

    SOC 2 is the second of three Service Organization Control (SOC) reports standardized by the American Institute of Certified Public Accountants in 2010. Its purpose is simple – to ensure a service provider’s systems are set up to ensure the security, availability, processing integrity, confidentiality, and privacy of customer data. Companies seeking SOC 2 compliance subject themselves, their policies, and practices to third-party review. Independent auditors have full access to any and all detail about the organization undergoing review – everything from Board membership to hiring practices to how access to data is managed and controlled. SOC 2 Type 1 examination evaluates an organization’s security controls at a single point in time, whereas SOC 2 Type 2 examines how well a company’s controls perform over a period of time. The process often takes six to 12 months and requires tens of thousands of dollars of investment.

    If you’d like to learn more about privacy and security at Lupl, get in touch today.

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