Workflows Directory

Find your team’s next superpower.

Results

157 workflow templates, showing 121 to 144

  • Reference check question plan

    After the interviews, the recruiter gets short reference calls aimed only at what the panel still could not establish, put to the referees the candidate named and agreed to, with a note sheet for each call that keeps the referee's own words. It gives no view on the candidate.

    Starts it
    Recruiter
    Brings
    export, notes, document
    Gets
    6 outputs
  • Referral source follow-up

    The day after a partner meets someone who sends the firm work, they have a follow-up draft and a list of every promise made at the table, by both sides. The draft uses only approved materials and nothing said in confidence; the partner checks it, chooses the next step and sends it.

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

  • Restricted gift rollforward

    The finance lead gets a working schedule for one named restricted fund: opening balance, recorded gifts, coded expenditure and closing balance, with every unresolved difference listed from the gift agreement summary and the ledger detail. Nothing is posted.

    Starts it
    Bookkeeper
    Brings
    export, notes
    Gets
    6 outputs
  • 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
  • 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
  • RFQ clarification list

    A buyer sending drawings and specifications out for quotation gets one list of missing details, conflicting revisions and ambiguous tolerances, and a record of each supplier's answers. The buyer approves every message; the engineer settles every technical question.

    Starts it
    Buyer
    Brings
    export, notes, pasted text
    Gets
    6 outputs
  • Roadmap tradeoff review

    When a new priority arrives, the product owner sees what the roadmap would have to give up to hold it: the capacity gap by team, the work that could move, the commitments and dependencies that move with it, and the questions still open. The owner decides.

    Starts it
    Product owner
    Brings
    export, notes
    Gets
    8 outputs
  • Sales call preparation brief

    Your salesperson, partner or account manager walks into every meeting with a brief they can read in five minutes: who will be there, what has been said and promised so far, what is still open, and a plan for the call. Every line traces to your own notes or a public page, and anything inferred is labelled.

    Starts it
    Salesperson
    Brings
    notes, pasted text
    Gets
    7 outputs
  • Sales proposal preparation

    Your account executive answers an RFP in minutes, not weeks, with a proposal draft where every claim traces to approved company information and every gap is already a question for the right person.

    Starts it
    Account executive
    Brings
    document
    Gets
    4 outputs
  • Schedule recovery options

    When a committed milestone slips, the project manager brings the sponsor two to four ways back: what each changes, the dates it gives every later milestone and dependency, and the assumptions it rests on. The sponsor chooses; delivery leads confirm the dates.

    Starts it
    Project manager
    Brings
    export, notes
    Gets
    5 outputs
  • Scope change impact review

    When new work turns up in a project plan, the project manager gets one review: every deliverable compared with the agreed baseline, each addition marked approved or not, its estimated effect on effort, cost and the end date, and the decision the sponsor has to make. The sponsor accepts or declines each one.

    Starts it
    Project manager
    Brings
    export, notes, document, pasted text
    Gets
    6 outputs
  • Search exclusion conflict check

    The paid search specialist gets a list of live keywords that a live exclusion may be blocking, each with the level where the exclusion applies and the campaign intent it touches. They are clues from the text; the specialist decides what to change.

    Starts it
    Paid search specialist
    Brings
    export, notes
    Gets
    5 outputs
  • Shared folder filing plan

    The office coordinator gets a plan for tidying a shared folder: a proposed folder structure, every file's move with its owner named, and the duplicates and access questions to settle first. Owners approve their own moves; nothing is moved, renamed or deleted.

    Starts it
    Office manager
    Brings
    export, notes, document
    Gets
    6 outputs
  • Site observation follow-up

    After a site visit, the visiting engineer and the project manager get one observation report: each field note beside its location, source photograph, drawing revision and any earlier register entry, a proposed follow-up owner, and the questions still open. It assesses no condition.

    Starts it
    Visiting engineer
    Brings
    export, notes
    Gets
    5 outputs
  • Slow-moving stock and markdown plan

    Before a seasonal reset, the merchandiser or store owner gets one plan from the sales and stock exports: each item's sell-through and weeks of cover, the cash tied up in dead and slow stock, and a markdown plan in dated steps with the margin each leaves and a date to stop. The owner decides every price.

    Starts it
    Merchandiser
    Brings
    export, notes
    Gets
    5 outputs
  • Smallest useful release scope

    A product owner or founder with more features than capacity gets one page: what is in the first release and what is deferred, all tied to one user outcome, with the reason for each cut. The owner decides the scope; no effort is estimated beyond what is supplied.

    Starts it
    Product owner
    Brings
    export, notes
    Gets
    7 outputs
  • SOP exception capture

    Turn what your most experienced person does with the awkward cases into an exception register for one procedure. Once the owner approves it, every colleague handles those cases the way your best person does.

    Starts it
    Operations lead
    Brings
    notes, document
    Gets
    2 outputs
  • Stalled-deal review

    Your sales lead sees, from the record alone, which open deals have stopped moving, what each one's stage still lacks and whose move it is, and where every recent no ended and why. Nothing in your sales system is changed; corrections are proposed for a person to make.

    Starts it
    Sales lead
    Brings
    export, notes, document, pasted text
    Gets
    7 outputs
  • Stock count reconciliation

    After a physical count, the bookkeeper and the warehouse or store lead get every item counted beside the quantity and value in the books, each difference in units and money, what to check for it, and the items to recount. Nothing is adjusted until a person approves.

    Starts it
    Bookkeeper
    Brings
    export, notes
    Gets
    5 outputs
  • Store facts file

    The person who runs an online store builds the one file every other store workflow template reads first: what the store sells, the facts each product page should state, the statements it stands behind, buyers' questions, policies, roles and access. Nothing on the store is changed.

    Starts it
    Owner
    Brings
    export, notes, document, pasted text
    Gets
    2 outputs
  • Store guide for AI shopping assistants

    The person who runs an online store gets the plain-language guide a shopper's AI assistant reads about the store: what it sells, for whom, which product line suits which need, and where the policies are. Every line traces to the approved store facts file, and a person places it.

    Starts it
    Operator
    Brings
    document, pasted text
    Gets
    6 outputs