Workflows Directory

Find your team’s next superpower.

Results

54 workflow templates, showing 25 to 48

  • Freight shortage record packet

    When a receiver reports missing or damaged freight, the claims coordinator gets one packet lining up dispatch quantities, warehouse scans, bill of lading, proof of delivery, photos and the customer report, with each unanswered question listed. It assigns no fault and sends nothing.

    Starts it
    Claims coordinator
    Brings
    export, notes
    Gets
    6 outputs
  • Hearing preparation pack

    Before a set hearing, the arguing attorney has one draft pack: the hearing as the notice states it, the docket history, each order's directives quoted, each witness's prior statements with page cites, exhibit and checklist status as the firm records them, and an open-items list. The attorney decides every argument.

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

    Prepares work for a lawyer. Not legal advice.

  • Help article from a resolved issue

    Turn every answer your team works out once into an article the next customer finds on their own. Hand over a resolved ticket and your list of articles; get back a draft in your customers' words, with their details removed and every step traced to the ticket. Your knowledge-base owner decides what goes live.

    Starts it
    Support agent
    Brings
    export, notes, document, pasted text
    Gets
    6 outputs
  • Help centre gap review

    Once a period, your support lead sees what the help centre is missing, read from that period's tickets and search log: questions agents answered by hand, articles that fell short, articles search could not find, and one gap list ranked by the tickets an article could have saved. The lead decides what is written.

    Starts it
    Support lead
    Brings
    export, notes
    Gets
    6 outputs
  • Inbound demand or claim intake record

    When a demand, claim or subpoena arrives, the company's lawyer gets one intake record the same day: who sent it, what it asks, every date it states, the facts and citations it relies on, related matters, where the records are, and a question on keeping them. It rates nothing and recommends nothing.

    Starts it
    Legal operations coordinator
    Brings
    export, notes, document
    Gets
    2 outputs

    Prepares work for a lawyer. Not legal advice.

  • Incoming referral completeness check

    When a referral arrives, the coordinator gets one checklist: what the referring office sent, held against the practice's own referral checklist, what is missing or needs a new copy, and a draft request for exactly those items. A clinician sets urgency; nothing is sent until the coordinator approves it.

    Starts it
    Referral coordinator
    Brings
    export, notes, pasted text
    Gets
    6 outputs
  • 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.

  • Learning system access review

    At term end or after staff change roles, the system owner lays the learning system's user and access exports beside current staff, class assignments and the approved role matrix. Departed users, changed roles and dormant accounts come back as questions for the data owners. Nothing is changed.

    Starts it
    System owner
    Brings
    export, notes
    Gets
    7 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.

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

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

  • Product recall customer contact plan

    Once your business has issued a recall, the customer care lead gets the contact plan: affected customers from the order export, the approved notice word for word, drafts that offer only the remedies you run, and a tracker that counts a customer done only when the item is back or repaired.

    Starts it
    Customer care lead
    Brings
    export, notes, document
    Gets
    6 outputs
  • Public guest review reply

    Answer an online guest review without exposing the guest's stay. Hand over the review and the service actions you have confirmed, and get a short public reply plus separate private notes, each statement tied to its source. The guest relations manager checks and approves.

    Starts it
    Guest relations manager
    Brings
    export, notes, document, pasted text
    Gets
    5 outputs
  • Reader correction request brief

    When a reader disputes a fact or reports a missing credit, the editor gets one internal note: the request, the published passage, the evidence supplied and the questions only an editor can answer. A draft acknowledgement waits for the audience lead's approval.

    Starts it
    Editor's assistant
    Brings
    notes, document, pasted text
    Gets
    3 outputs
  • Record sharing access matrix

    When an approved access policy has to reach the CRM, the system owner lays the current sharing setup beside the proposed one, by record type and by role, internal and external. Every change is a question for its owner; inherited and platform-fixed settings are marked unknown.

    Starts it
    System owner
    Brings
    export, notes
    Gets
    6 outputs
  • Release notes draft

    The product owner gets draft release notes for one shipped release, in words users recognize: what is new, changed, removed and fixed, the steps users must take, and the known limitations. Only what was supplied is described. The owner checks and publishes.

    Starts it
    Product owner
    Brings
    export, notes
    Gets
    8 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.

  • Returned unit review brief

    When a failed-unit report or return request arrives, the service coordinator gets one brief tying the customer's report to each unit's shipment record, serial and recorded configuration, with unmatched serials and missing evidence listed. It names no cause.

    Starts it
    Service coordinator
    Brings
    export, notes, document, pasted text
    Gets
    7 outputs
  • Service inbox routing plan

    When a new service inbox is being set up, the service owner gets a routing plan: each approved address, the queue it should reach and who owns it, checks to run before it goes live, and the wrong-address risks, loop risks and unconfirmed queue owners still open. Nothing is configured.

    Starts it
    Service owner
    Brings
    export, notes
    Gets
    5 outputs
  • Stale ticket sweep

    Once a week the support lead gets one sheet of what the queue is hiding: tickets with no real activity past their limit, tickets left waiting on the customer with the three ways out of each, likely duplicates, and each person's load weighed by size and age. A person makes every move.

    Starts it
    Support lead
    Brings
    export, notes, document
    Gets
    6 outputs
  • Support escalation brief

    When a support case must move to a specialist or manager, the support lead gets one brief: the customer's impact, a dated timeline from the ticket history, the evidence, the fixes tried, the workaround in place and the decision needed. Nothing goes to the customer.

    Starts it
    Support agent
    Brings
    export, notes, document
    Gets
    8 outputs