Workflows Directory

Find your team’s next superpower.

Results

20 workflow templates

  • App data requirements

    When the requirements for an internal app leave fields or actions unclear, the business systems analyst gets one data specification: entities, fields, who reads and writes each, and every unresolved name as a question. Nothing is built or changed.

    Starts it
    Business systems analyst
    Brings
    export, notes, document
    Gets
    9 outputs
  • CRM field ownership map

    Before a CRM sync or field mapping changes, the systems owner gets a field map from the supplied exports and sample records: each field's source, match keys and conflict rule, with unclear keys, consent fields and duplicates left as questions for each field's owner.

    Starts it
    Systems owner
    Brings
    export, notes
    Gets
    7 outputs
  • Culture health check

    A founder or people lead sees whether the company's stated values show up in daily work: each value written as behaviours you could watch for, read against the team's own evidence, with where practice matches, where it drifts, and two or three rituals to try. Reported by team and theme, never about a person.

    Starts it
    Founder
    Brings
    export, notes, document
    Gets
    7 outputs
  • Employee health plan comparison

    For an owner or people lead at renewal: the broker's health plan options next to each other, with premiums split between company and employee, deductibles, out-of-pocket limits, network notes, the cost to the company and to a typical employee at low, middle and high use, and questions for the broker.

    Starts it
    People lead
    Brings
    export, notes, pasted text
    Gets
    6 outputs
    • People and HR (filtered by)
    • Growth & scaling (filtered by)
    • Construction
  • Employee onboarding plan

    Every new colleague starts with a first week and a first 90 days planned to the standard of your best manager: what to read, who to meet, what to practice and what productive means at day 30, 60 and 90.

    Starts it
    Hiring manager
    Brings
    notes, document
    Gets
    6 outputs
  • Headcount plan

    For a founder, people lead or finance lead preparing next year: every role and its cost by team, the new roles and backfills with their months, the fully loaded cost month by month against the budget, and what changes if revenue lands lower or higher. It plans roles and money, never decisions about named people.

    Starts it
    Finance lead
    Brings
    export, notes
    Gets
    5 outputs
  • Hiring pipeline status report

    Each week your people lead or founder sees every open role on one page: applications at each stage, days open against the target, roles running late, pass-through between stages, which sources lead to interviews, and every blocker with its owner. It counts; it never assesses a candidate.

    Starts it
    People lead
    Brings
    export, notes, document
    Gets
    6 outputs
  • Household record differences

    When the CRM and the custodian's account export disagree about a household, the operations owner gets one comparison: accounts with no household, possible duplicates and field-by-field differences, each with its source row and a proposed correction left as a question. No record is changed.

    Starts it
    Operations owner
    Brings
    export, notes
    Gets
    6 outputs
  • Internal change announcement

    One decided change, announced well: managers briefed first, a message for each group in the right order, talking points, and the questions people will ask, answered only from the decision or marked open. Every message is a draft that a person approves and sends.

    Starts it
    Internal communications lead
    Brings
    export, notes
    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
  • 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
  • Manager feedback preparation

    Every manager walks into a feedback conversation prepared like your best one: specific dated observations, the questions worth asking, a clear ask and the support on offer.

    Starts it
    Team manager
    Brings
    notes, document
    Gets
    7 outputs
  • Matter coverage plan for absences

    When leave or a staffing change takes someone away from active matters, the practice manager gets a draft coverage plan: a proposed cover for each matter, the attorney-confirmed dates in the absence, the access each cover needs and every handoff that is blocked. The practice lead and responsible attorneys decide.

    Starts it
    Practice manager
    Brings
    export, notes, document
    Gets
    8 outputs

    Prepares work for a lawyer. Not legal advice.

  • Notification channel plan

    When a business event needs to notify people, the integration owner gets one channel plan from the event definitions: trigger, urgency, who is told by which channel, what needs confirmation, fallbacks and reply handling. Consent and message rules stay as questions. Nothing is sent.

    Starts it
    Integration owner
    Brings
    export, notes
    Gets
    1 output
  • 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
  • Site safety induction pack

    For one named site, the site, facilities or people lead gets an induction built from that site's own emergency arrangements, rules and hazards, with a short check of understanding, a sign-off record for each person and refresher dates by role. A competent person approves it and delivers it.

    Starts it
    Site manager
    Brings
    export, notes, document
    Gets
    6 outputs
    • People and HR (filtered by)
    • Growth & scaling (filtered by)
    • Construction
  • Staff newsletter and FAQ roundup

    Each month the office manager turns what teams send in into one staff newsletter, with answers to the questions people keep asking, each quoted from an approved source and its owner named. Nothing about one person's pay, health or performance goes in, and a person approves the issue before it goes.

    Starts it
    Office manager
    Brings
    export, notes, document
    Gets
    2 outputs
  • Training needs analysis

    For one team, the HR lead or team manager gets what each role must be able to do, how many people can do it now, where the team falls short, and the training to arrange first, with who arranges it and by when. Counted by role, never a rating of a named person.

    Starts it
    Team manager
    Brings
    export, notes
    Gets
    5 outputs
    • People and HR (filtered by)
    • Growth & scaling (filtered by)
    • Hospitality
  • Volunteer shift options

    A volunteer lead gets draft shift options once an event's availability replies are in: each role's needs set against who volunteered, the requirements on record and the shifts already confirmed, with every uncovered position shown. The lead checks and confirms; nothing is assigned or sent.

    Starts it
    Volunteer lead
    Brings
    export, notes
    Gets
    4 outputs
    • People and HR (filtered by)
    • Growth & scaling (filtered by)
    • Education
  • Workflow inventory

    When the ownership and status of your automated workflows come up for review, the platform owner gets one inventory built from the exports supplied: environments, enabled states, last run, queued runs and owner gaps. Quiet workflows become questions, not removal lists.

    Starts it
    Platform owner
    Brings
    export, notes
    Gets
    7 outputs