Workflows Directory

Find your team’s next superpower.

Results

34 workflow templates, showing 1 to 24

  • Ad to page check

    When a campaign's landing page is ready for a prelaunch check, the acquisition owner gets a findings list that sets each ad beside the captured page: message, offer details, form and next step, on mobile and desktop. Page states nobody captured are marked unknown.

    Starts it
    Acquisition owner
    Brings
    export, notes
    Gets
    4 outputs
  • Board meeting pack

    Before each board meeting, the CEO gets a pre-read built on the one decision the board is asked to make, with every figure from the company's own reports, an agenda kept mostly for discussion and the questions directors are likely to ask. Afterwards, a record of what was decided. The CEO sends it all.

    Starts it
    Chief executive
    Brings
    export, notes, document
    Gets
    5 outputs
  • Board minutes draft

    After a board meeting, the secretary gets draft minutes built only from what they supply: notes, agenda, motion text and vote record. Attendance, motions, votes, documents and actions are laid out, and every gap is marked for the secretary to settle.

    Starts it
    Board secretary
    Brings
    export, notes
    Gets
    7 outputs
  • Business continuity plan

    For an owner or operations manager: the activities the business cannot stop for long, how long each can be down and how much data it can lose, what each depends on, the fallback for each, and named owners, deputies, contacts and a test date, ready for a competent reviewer and the owner's approval.

    Starts it
    Owner
    Brings
    export, notes
    Gets
    7 outputs
  • Business trip plan

    The assistant hands the traveller one plan for one business trip: dates and nights fixed from the brief, travel and hotel options with prices and the day each was checked, a day-by-day timetable around the meetings, the cost against travel policy and the bookings still to make. Nothing is booked or paid.

    Starts it
    Executive assistant
    Brings
    notes, document, pasted text
    Gets
    5 outputs
  • Cloud spend variance bridge

    When cloud or tooling costs move away from budget, the finance lead and the engineering manager get a bridge from budget to actual by service and cost owner, with usage beside each large move, the unallocated and shared costs, and the questions each side must answer.

    Starts it
    Finance lead
    Brings
    export, notes
    Gets
    6 outputs
  • Component inventory audit

    When patterns come up for review, the design-system owner gets an inventory built from the library export and its documentation: every component with its naming, token and state gaps, and the pairs that may overlap. Nothing is merged on appearance; the owner decides.

    Starts it
    Design-system owner
    Brings
    export, notes
    Gets
    4 outputs
  • Component specification

    When an approved reusable component needs documenting, the design-system owner gets one specification of its variants, states, usage rules and accessibility notes, set beside the existing patterns, with every gap or clash written as a choice for the owner.

    Starts it
    Design-system owner
    Brings
    export, notes
    Gets
    6 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
  • 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
  • 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
  • Emergency drill brief

    Before a fire, evacuation or other drill, the site or office manager gets one brief: the scenario the responsible person has approved, who does what, what each observer records, and the questions for the debrief. It writes no emergency plan.

    Starts it
    Site manager
    Brings
    export, notes
    Gets
    4 outputs
  • Employee offboarding and handover checklist

    When someone leaves, your HR lead and their manager share one checklist: every piece of their work handed to a named colleague before the last day, every system on your access register removed by its owner at a set time, and every item of equipment back. Nothing is removed or sent without a person.

    Starts it
    People lead
    Brings
    export, notes
    Gets
    7 outputs
  • Executive situation brief

    Before a conversation that matters, with a key partner, a major customer or a co-founder, the executive gets one brief from the records they approve: the short version in a sentence, what is already decided and promised, what each side has said, the question to settle and the choices open. The executive decides.

    Starts it
    Executive
    Brings
    export, notes, document
    Gets
    9 outputs
  • Executive week-ahead calendar review

    Before the week starts, the executive assistant hands the executive one brief: every clash, every journey or run of meetings with too little time, every meeting with no stated purpose or no preparation time, and proposed time for the week's priorities. Nothing is accepted, declined, moved or sent.

    Starts it
    Executive assistant
    Brings
    export, notes
    Gets
    7 outputs
  • Inbox triage

    The owner, or the assistant who keeps their inbox, starts the day knowing what needs a reply today, what can wait and until when, and what belongs to someone else, with a draft or a forwarding note for each. Nothing is sent, archived, deleted or moved, and no mailbox login is needed.

    Starts it
    Executive assistant
    Brings
    export, notes, pasted text
    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
  • Journey accessibility findings

    When a user journey is ready for accessibility review, the reviewer gets a finding list: each finding with its task impact and evidence, the manual checks still required and the limits of the review. The reviewer verifies every finding and agrees fixes with the design owner.

    Starts it
    Accessibility reviewer
    Brings
    export, notes
    Gets
    5 outputs
  • Lead form field review

    When a client questions a long inquiry form or abandoned submissions, the conversion lead gets a field-by-field review: what each field is used for downstream, where people leave, and proposed labels, error messages and test questions. The lead and the client's data owner decide every change.

    Starts it
    Conversion lead
    Brings
    export, notes, document
    Gets
    6 outputs
  • Leadership meeting rhythm

    Your chief executive gets a proposed calendar of leadership forums and written reports, built from today's meetings and the decisions left waiting: each forum with its purpose, inputs, attendees, frequency and one decision owner, and the hours it gives back. The chief executive chooses; no calendar is changed.

    Starts it
    Chief executive
    Brings
    export, notes
    Gets
    7 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
  • 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
  • Online class setup packet

    The learning-platform administrator receives one complete request for an approved class: course name, section, room, responsible teacher, the people who can be invited and every roster exception, drawn from the approved details and the roster export.

    Starts it
    Academic office assistant
    Brings
    export, notes, document
    Gets
    6 outputs
    • IT and systems (filtered by)
    • Executive and office support (filtered by)
    • Education