Book a fit call

Workflows Directory

Find your team’s next superpower.

Results

134 workflow templates, showing 49 to 72

  • Interview plan and scorecard

    Before the first interview, the hiring manager and every interviewer share one plan: the criteria the role needs, the same questions in the same order for every candidate, and a blank scorecard each person fills in alone. It rates no one. People make every decision about a candidate.

    Starts it
    Hiring manager
    Brings
    notes, document
    Gets
    7 outputs

  • Interview process review after a hiring round

    After a hiring round closes, the recruiting lead gets a review of the interview process: questions that gave no usable evidence, competencies nobody covered, inconsistent rubric use, and revisions to approve before the next search. It reviews the process only; no candidate is assessed.

    Starts it
    Recruiting lead
    Brings
    export, notes
    Gets
    6 outputs

  • Interview scheduling and candidate confirmation

    For candidates your team has already chosen to interview, the recruiting coordinator gets one scheduling sheet that lines up each candidate's offered times, in their own time zone, with the interviewers' free time, plus a ready confirmation or availability request for each. A person sends every message and invitation.

    Starts it
    Recruiting coordinator
    Brings
    export, notes, pasted text
    Gets
    5 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.

  • Investor update

    Each month or quarter, the founder gets a drafted update for investors: the headline, key figures against plan and last period, cash and runway, wins, problems told plainly with what is being done, and specific asks. Every figure comes from the company's own reports. The founder approves and sends it.

    Starts it
    Founder
    Brings
    export, notes, pasted text
    Gets
    3 outputs

  • Job description

    A hiring manager’s rough notes become a job description the right people want to answer: why the role exists, the work itself, and only the must-haves that are real. Your approved pay and employer wording go in untouched, and nothing is posted until the hiring manager and the people lead approve it.

    Starts it
    Hiring manager
    Brings
    notes, document
    Gets
    2 outputs

  • Job posting and sourcing plan

    For one approved role, the hiring manager gets a plan for where to post and where to look: every channel on the company's own list ordered by the signal it should give for that kind of role, a week-by-week schedule inside the budget, and what to count on each channel. Nothing is posted or paid until a person approves.

    Starts it
    Hiring manager
    Brings
    export, notes, document
    Gets
    4 outputs

  • Job readiness packet

    Before an order goes to the floor, the production or quality lead gets one packet: each requirement matched to its approved drawing, specification or inspection plan, with conflicting revisions, gaps and material shortfalls listed. The owners decide; nothing is approved or released.

    Starts it
    Production planner
    Brings
    export, notes
    Gets
    5 outputs

  • Kit component availability check

    The stock or online-store lead gets every kit beside the quantity actually sellable, the component that limits it, the stock records that disagree and the listings that promise more than can be built. Nothing is changed until a person decides.

    Starts it
    Stock lead
    Brings
    export, notes
    Gets
    6 outputs

  • 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

  • Matter closing checklist preparation

    When the handling lawyer flags a matter for closure, the firm's closing checklist is filled from the matter record: final billing as recorded, open tasks, unreturned items and the handoffs billing and records must accept.

    Starts it
    Operations assistant
    Brings
    export, notes, document
    Gets
    5 outputs

  • Matter-opening checklist preparation

    Every accepted matter goes into setup and billing with one checklist: the fields each system needs, the terms that drive the first invoice, the documents on file and an owner for every open item.

    Starts it
    Firm administrator
    Brings
    document
    Gets
    4 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

  • Menu input cost change review

    When supplier prices change, the chef and food-and-beverage manager get one worksheet: each price movement tied to the quantities in the supplied recipes, the cost per portion of every affected dish before and after, and questions for the chef. It sets no menu price.

    Starts it
    Chef
    Brings
    export, notes
    Gets
    5 outputs

  • Month-end close checklist

    Before the month ends, your controller holds the whole close on one page: every task with its owner, its date and what it waits on, the chain that sets the close date, and each gap already written as a question. Entries are prepared for approval, never posted.

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

  • Newsletter roundup draft

    The newsletter editor hands over the stories picked for this send and gets a draft digest grouped by beat, with a short summary, source line and link for each approved story. Duplicates, corrected stories and incomplete sources are flagged for the editor, who approves any send.

    Starts it
    Newsletter editor
    Brings
    export, notes, pasted text
    Gets
    2 outputs

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

  • Payroll preparation and timesheet review

    Before each payroll run, the owner gets one sheet built from the timesheet and roster exports: hours by person and type, every missing punch and odd entry raised as a question, and an estimated total. Nothing is keyed in, submitted or paid until a person approves.

    Starts it
    Payroll clerk
    Brings
    export, notes
    Gets
    7 outputs

  • 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

  • Policy answers from the handbook

    Staff questions about leave, hours, expenses and conduct get answers that quote your own handbook, name the section, and say plainly where the handbook is silent. Anything about one person's own entitlement goes to HR, and no reply leaves until a person has read it.

    Starts it
    Office manager
    Brings
    export, notes, document
    Gets
    4 outputs

  • Presentation outline and talk track

    Anyone presenting to a board, a client or a conference gets a storyboard built on one message, then a spoken script for every slide, timed to the slot and true to their own speaker notes. Every fact comes from what the presenter supplied, and the presenter approves the message and the words.

    Starts it
    Presenter
    Brings
    notes, pasted text
    Gets
    4 outputs

  • Press pitch preparation

    An owner or marketer with one story to offer gets the outlets and writers it genuinely fits, each backed by a piece they recently published, and a short pitch draft for each. Every claim in a draft comes from facts you supply. Drafts only: a person decides and sends.

    Starts it
    Owner
    Brings
    notes, pasted text
    Gets
    5 outputs