Workflows Directory

Workflow templates for legal and contracts or project and delivery

Results

57 workflow templates, showing 25 to 48

  • Invention disclosure brief for patent counsel

    Before the first call with patent counsel, the founder or engineering lead has one factual brief: the invention in the inventor's words, who contributed what and when, every outside demonstration, sale, talk or publication with its date and audience, and the records still missing. Counsel decides.

    Starts it
    Founder
    Brings
    export, notes, document
    Gets
    7 outputs

    Prepares work for a lawyer. Not legal advice.

  • IP ownership and licence question table

    Before an agreement or statement of work is signed, IP counsel gets one table of the ownership, assignment, licence, background-IP and confidentiality clauses, each quoted with its section, set against the company's own IP positions and led by whether the assignment words counsel expects were found.

    Starts it
    Contracts manager
    Brings
    notes, document
    Gets
    6 outputs

    Prepares work for a lawyer. Not legal advice.

  • Launch checklist

    Whoever owns a launch date gets one dated checklist for the weeks before, the day itself and the weeks after, with an owner on every line. Each announcement is written out so the approver sees exactly what goes out, to whom and from where before saying go. Nothing is announced by the assistant.

    Starts it
    Owner
    Brings
    export, notes
    Gets
    6 outputs
  • Legal hold custodian tracker

    Once counsel has issued a legal hold, your legal operations lead keeps one tracker for counsel: every custodian and system in counsel’s scope, who has acknowledged and who is overdue, who has left or changed role, the refresh date counsel set, and reminders copied from counsel’s own text for a person to send.

    Starts it
    Legal operations lead
    Brings
    export, notes, document
    Gets
    3 outputs

    Prepares work for a lawyer. Not legal advice.

  • Matter budget and status summary

    The responsible partner sees one matter whole: scope, phases against their dates, the budget against fees to date and the projected total, a red, amber or green status with the rule behind it, risks and next actions with owners. Built from the time export and the matter plan, never a view on the merits.

    Starts it
    Matter lead
    Brings
    export, notes, document
    Gets
    10 outputs
  • Meeting agenda, notes and follow-ups

    Whoever runs the meeting walks in with an agenda where every topic has an outcome and a time, and walks out with a one-page record: what was decided, who owns each action and by when, and what is still open. Nothing reaches anyone until that person has read it and sends it.

    Starts it
    Team lead
    Brings
    notes
    Gets
    4 outputs
  • Missed milestone client reply

    When a client challenges a delay, a deliverable or an earlier commitment, the account director gets a draft reply and an internal action note that keep confirmed facts apart from proposed recovery steps and the decisions still needed. Nothing is sent.

    Starts it
    Account director
    Brings
    export, notes, document, pasted text
    Gets
    2 outputs
  • NDA check against counsel's approved positions

    Before anyone signs a proposed NDA, counsel gets every clause quoted with its section and set beside the positions counsel has approved: matching, departing or not covered. Any obligation beyond confidentiality sends the whole NDA to counsel. The check never says an NDA is ready to sign.

    Starts it
    Salesperson
    Brings
    notes, document
    Gets
    6 outputs

    Prepares work for a lawyer. Not legal advice.

  • Open-source licence inventory for counsel

    Before a release ships or an acquirer asks, counsel and the engineering lead get every open-source package listed with its licence as found, the file and line where it was read, and the duties your own policy attaches to it. A missing, custom or conflicting licence is marked needs review, never cleared.

    Starts it
    Engineering lead
    Brings
    export, notes, document
    Gets
    5 outputs

    Prepares work for a lawyer. Not legal advice.

  • Outside-counsel invoice questions

    When a law firm’s invoice arrives, legal operations has one worksheet ready: every line set against the agreed rates, the approved matter budget and the company’s own billing guidelines, each difference written as a neutral question for the firm. Nothing is sent, paid or rejected until people decide.

    Starts it
    Legal operations manager
    Brings
    export, document
    Gets
    10 outputs

    Prepares work for a lawyer. Not legal advice.

  • Pilot build readiness brief

    Before a prototype or pilot build, the build lead gets one brief: part shortages, revision conflicts and open actions set against the team’s own build checklist, with allocated parts kept apart from received ones. People confirm; nothing is released.

    Starts it
    Build lead
    Brings
    export, notes, document
    Gets
    7 outputs
  • Premortem before a decision

    Before your team commits to a plan that is hard to undo, such as a move, a launch or a new system, a short workshop pictures it a few months on, already failed. The record ranks the reasons, turns each top risk into a check, a warning sign and an owner, and leaves the go decision with the owner.

    Starts it
    Owner
    Brings
    notes
    Gets
    4 outputs
  • Privilege log entry check

    Before a draft privilege log goes to review counsel, the paralegal gets an entry-by-entry check against counsel’s approved format and role map, and a list of logged documents’ attachments with no entry. It checks metadata only: review counsel makes every privilege call and writes or approves every description.

    Starts it
    Paralegal
    Brings
    export, notes, document
    Gets
    6 outputs

    Prepares work for a lawyer. Not legal advice.

  • Program outcome map

    Before an evaluation, the program and evaluation leads get one map linking each activity to the outcome it is meant to serve, with proposed measures, data sources, assumptions and the questions the evidence cannot yet answer. It claims no impact.

    Starts it
    Program lead
    Brings
    export, notes
    Gets
    8 outputs
  • Project handover readiness check

    When a finished deliverable is ready for the team that will run it, the project manager brings one checklist against that team's own requirements: acceptance evidence, instructions, access, training, support owners and open items. The receiving owner accepts or names the conditions still to meet.

    Starts it
    Project manager
    Brings
    export, notes
    Gets
    6 outputs
  • Project intake and capacity review

    When a new initiative is proposed, the portfolio owner sees it scored on the business's own criteria beside the projects already committed, the delivery days it would use month by month, and what it would crowd out or push later. The owner accepts, defers or rejects it.

    Starts it
    Portfolio owner
    Brings
    export, notes, document
    Gets
    6 outputs
  • Project lessons review

    When a phase or a project ends, the project manager gets one blameless review: whether it achieved what it was for, how scope, schedule and budget moved and why, whether the success measures were the right ones, and practice changes for the team to choose, each with an owner and a follow-up date.

    Starts it
    Project manager
    Brings
    export, notes
    Gets
    8 outputs
  • Project scope baseline

    A project manager turns an approved brief into a draft scope baseline: the deliverables, what is excluded, the acceptance criteria for each deliverable, the constraints and the open questions for the sponsor. Nothing implied counts as scope until the sponsor says so.

    Starts it
    Project manager
    Brings
    export, notes, document
    Gets
    7 outputs
  • Project status report

    The lead of an internal project gets a status report the sponsor can read in two minutes: each workstream red, amber or green with the reason, what moved, who must clear each blocker, the decisions needed and the dates at risk. No milestone is called done without evidence, and the lead confirms every status.

    Starts it
    Project lead
    Brings
    export, notes, pasted text
    Gets
    7 outputs
  • Property diligence index

    The transaction lead gets a diligence room in order: every document indexed by workstream, every checklist item and request tracked, and every open finding tied to the report or request that raised it. Specialists judge the findings; nothing is valued or sent.

    Starts it
    Transaction coordinator
    Brings
    export, notes
    Gets
    5 outputs
  • Punch list consolidation

    The site manager gets the punch list for the next closeout walk as one list grouped by location and trade, with repeated entries merged, photographs attached and a proposed follow-up date for each open item. Nothing is assigned, closed or accepted.

    Starts it
    Site manager
    Brings
    export, notes
    Gets
    7 outputs
  • Research plan for counsel

    Before an associate or paralegal starts on a partner's research question, they hold a one-to-two-page plan: the question split into sub-questions, the stated facts against each, the firm's own notes to read first, where to search and with what terms, and the gaps. Leads, not authorities: nothing is named from memory.

    Starts it
    Associate
    Brings
    export, notes, document
    Gets
    6 outputs

    Prepares work for a lawyer. Not legal advice.

  • Reviewer comments into one resolution list

    The owner of a document that came back from several reviewers gets one checklist: every proposed edit and comment, grouped by section, with clashes between reviewers set side by side. Every item stays open until the owner decides it, and the document itself is never touched.

    Starts it
    Document owner
    Brings
    export, notes, document, pasted text
    Gets
    7 outputs
  • RFI review package

    The project engineer gets one packet for each request for information: the register entry, the question word for word, the drawing revisions and specification extracts it touches, earlier responses, and a numbered list of what is unresolved. No answer is proposed.

    Starts it
    Project engineer
    Brings
    export, notes, pasted text
    Gets
    8 outputs