Book a fit call

Workflows Directory

Find your team’s next superpower.

Results

215 workflow templates, showing 49 to 72

  • Cost of poor quality worksheet

    An owner or operations lead who senses that rework, scrap and returns are costly gets one worksheet: the failure costs already on record, sorted by category, with estimates, gaps and unresolved allocations listed. The owner decides what to fix first.

    Starts it
    Owner
    Brings
    export, notes
    Gets
    6 outputs

  • Course catalog quality check

    The registrar's office gets one comparison of a department's course updates against the current catalog export: codes, titles, credits, descriptions and linked components, row by row, with every conflict set out as a question for academic review. No catalog record is changed.

    Starts it
    Catalog coordinator
    Brings
    export, document
    Gets
    5 outputs

  • Course sequence and workload review

    A course lead revising an outline for the next cohort gets a module map: learning goals, prerequisites, activities and the instructor's own time estimates, with crowded weeks and coverage gaps marked and every gap written as a question. The course lead decides what changes.

    Starts it
    Course lead
    Brings
    export, notes
    Gets
    4 outputs
    • People and HR
    • Education (filtered by)
    • Professional services (filtered by)

  • Court-order deadline notice preparation

    When a court order arrives, the legal assistant has a draft notice ready for the attorney: every directive in the court’s own words, every date copied from the order or proposed under the firm’s own written rule file, and a list for the attorney to confirm. Nothing is calendared or sent until the attorney confirms.

    Starts it
    Legal assistant
    Brings
    document, pasted text
    Gets
    7 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

  • Current experience baseline

    Before a redesign, the design lead gets a baseline built from the captures and page list they supply: each page read with its content and design observations, the patterns that recur, and the pages outside the evidence. The lead confirms the baseline and sets the scope.

    Starts it
    Design lead
    Brings
    export, notes, document
    Gets
    6 outputs

  • Customer case study

    With a customer who has agreed to help, prepare the interview, then turn their words and the figures they supply into a case study in a short and a long version. Every quotation and number is listed for the customer to approve in writing, and nothing is published or named before they do.

    Starts it
    Marketer
    Brings
    export, notes, document, pasted text
    Gets
    5 outputs

  • Customer interview synthesis

    Turn a stack of customer call notes into the answer to one question, in your customers’ own words. Every quotation is cited to the note it came from, every theme shows its confidence and the evidence against it, and nothing is claimed that the notes do not say.

    Starts it
    Founder
    Brings
    notes
    Gets
    5 outputs

  • Customer onboarding plan

    For every new customer, your customer success lead gets one plan for the first weeks: the result the customer must reach, the fewest milestones that get them there with an owner on each side, the promises both sides made, and each message as a draft. Nothing is sent until a person approves it.

    Starts it
    Customer success lead
    Brings
    notes, document
    Gets
    6 outputs

  • Customer reply drafting

    Every customer gets the reply your best person would write. Hand over the customer's message, your tone guide and your approved answers, and get back a draft in your voice where every statement and every promise traces to something you approved. A person on your team reads it, edits it and sends it.

    Starts it
    Support agent
    Brings
    notes, document, pasted text
    Gets
    3 outputs

  • Customer satisfaction detractor follow-up

    Every week your support lead gets each low satisfaction or recommendation score with the ticket behind it: the customer's own words, what went wrong as far as the ticket shows, a suggested owner and a draft message, plus the trend and a warning wherever the numbers are too thin to read. A person sends every message.

    Starts it
    Support lead
    Brings
    export, notes, pasted text
    Gets
    7 outputs

  • Dashboard brief

    Before anyone builds the dashboard, the requester gets one brief that settles the work: the decisions it serves, what is shown, each metric's definition, the filters, notes on every source and who refreshes it. The requester approves what is shown and the definitions.

    Starts it
    Analyst
    Brings
    export, notes
    Gets
    4 outputs

  • Dataset profile

    Before anyone joins or relies on a new export, the analyst gets one profile of it: what one row stands for, where keys repeat, what is missing, which values look odd, and a numbered list of questions for the data owner. No data is changed and no verdict is given.

    Starts it
    Analyst
    Brings
    export, notes
    Gets
    4 outputs

  • Deal close plan

    Your account executive holds one late-stage deal on two pages: the buyer's case for buying now, counted from the buyer's own figures, and a dated plan of every step to signature with its owner on each side. The seller decides what the buyer sees; nothing reaches the sales system without approval.

    Starts it
    Account executive
    Brings
    export, notes, document
    Gets
    4 outputs

  • Decision log

    Your chief of staff keeps one register of what the leadership actually approved, across every meeting and message: each decision with who approved it, each action with one owner and a date, what is overdue, and a flag wherever a new decision clashes with an earlier one or revives a rejected idea.

    Starts it
    Chief of staff
    Brings
    export, notes, pasted text
    Gets
    5 outputs

  • Delegation brief and follow-up

    Every task a manager hands over goes with a clear brief: what to deliver, in what form, by what date and time, why it matters, who will use it, what the person may decide alone and when the manager will check in. Each week, one list shows what is open, what is late and the next note to send.

    Starts it
    Manager
    Brings
    export, notes, document, pasted text
    Gets
    5 outputs

  • Deliverable issue completeness check

    As a calculation, report or drawing package nears issue, the quality reviewer or document controller gets a checklist: missing review records, revisions that disagree between the index, the register and the title block, and citations of out-of-date calculations. Issue stays with the engineers.

    Starts it
    Quality reviewer
    Brings
    export, notes
    Gets
    5 outputs

  • Departing-employee knowledge capture

    When someone is leaving or changing role, their manager gets an interview guide aimed at what only that person knows, then a handover document the successor can work from, every point traced to the conversations and marked with how sure it is. Nothing is shared until the manager approves.

    Starts it
    Manager
    Brings
    export, notes, pasted text
    Gets
    2 outputs

  • Deposition transcript summary

    Before the next deposition, a motion or trial, the attorney has a draft page-line summary of the transcript, arranged by the topics they named: every point cited, every exhibit and objection logged, and every place the testimony differs flagged without a label. The attorney decides what it means.

    Starts it
    Paralegal
    Brings
    notes, document
    Gets
    8 outputs

    Prepares work for a lawyer. Not legal advice.

  • Design assumption change register

    When client criteria or design assumptions change, the project engineer gets one sourced register: what changed, which recorded requirements it touches, how firm each source is, and what still needs confirmation. No design basis is altered.

    Starts it
    Project engineer
    Brings
    export, notes
    Gets
    6 outputs

  • Design handoff record

    Before engineering starts, the design owner gets one record built from the approved design: every state, token, breakpoint and content rule either covered or flagged, with each unstated behaviour written as a question. The engineer confirms the questions are resolved.

    Starts it
    Design owner
    Brings
    export, notes
    Gets
    6 outputs

  • Discipline interface issue register

    After a coordination meeting exposes conflicts between disciplines, the design coordinator gets one register: each conflict from the minutes, linked to the clash-export rows and model revisions involved, with the lead who owns each system and the decision still needed. Nothing is resolved.

    Starts it
    Design coordinator
    Brings
    export, notes, document
    Gets
    5 outputs

  • Discount request review

    Before a price below list goes to a customer, whoever approves it gets one page: the discount and what it costs in margin, every clause of your own written policy met or missed, who approves and in what order, and what the customer gives in return. A person decides; nothing is sent.

    Starts it
    Sales lead
    Brings
    export, notes, document
    Gets
    7 outputs