Book a fit call

Workflows Directory

Find your team’s next superpower.

Results

59 workflow templates, showing 1 to 24

  • Academic calendar check

    While year, term and session dates are being assembled, your registrar gets a draft calendar with every registration window tied to its term, and every conflicting, missing or out-of-bounds date listed as a question. Nothing is published or changed.

    Starts it
    Registrar
    Brings
    export, notes
    Gets
    3 outputs

  • Acceptance criteria sheet

    Hand a developer or agency a story with its definition of done written down: testable expected behaviours, error cases and edge cases, each traced to a rule or design state, with the unclear terms and open questions listed for the product owner.

    Starts it
    Product owner
    Brings
    notes
    Gets
    5 outputs

  • Assumption map

    For a product owner whose plan rests on beliefs nobody has tested: each belief is written down, set against the evidence you hold, ranked by what it would do to the plan, and given a cheap test to choose from. You decide what to test; no evidence is invented.

    Starts it
    Product owner
    Brings
    export, notes
    Gets
    6 outputs

  • Business model assumptions review

    Before you commit money to a new or revised business model, see it block by block with every claim marked evidenced or assumed, the riskiest assumptions ranked, and the cheapest test for each. You choose what to test; no projection or valuation is made.

    Starts it
    Founder
    Brings
    export, notes
    Gets
    7 outputs

  • Buyer security questionnaire answers

    When a buyer sends a security questionnaire, your sales owner gets a draft answer matrix: each question beside the evidence your security owner supplied, its date, its limits and a named reviewer, with stale, partial and unverifiable answers marked.

    Starts it
    Sales owner
    Brings
    export, notes, pasted text
    Gets
    4 outputs

  • Client document request tracker

    When a client sends its first batch of records, the engagement manager gets the request list brought up to date: each item and period marked received, incomplete, mentioned only or missing, plus a short follow-up draft. The manager judges what is sufficient and approves anything sent.

    Starts it
    Engagement manager
    Brings
    export, notes, pasted text
    Gets
    5 outputs

  • Client findings validation document

    Before research becomes recommendations, the engagement lead sends the client one document: each material finding beside its evidence, the implication proposed and a clear request to confirm, correct or defer it. Nothing is added that the evidence does not show.

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

  • Client-status update preparation

    Every client gets an accurate status update on schedule, drafted from the notes and the task list, with confirmed dates kept apart from estimates and the client’s open decisions in plain view.

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

  • Completed engagement file review

    The quality partner gets a worksheet that tests finished engagement files against the firm's own checklist: each item linked to the engagement letter, workpaper or sign-off that answers it, with any open finding, and the missing evidence listed. The quality partner confirms findings and assigns remediation.

    Starts it
    Quality partner
    Brings
    export, notes
    Gets
    4 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

  • 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

  • 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 feedback themes

    Each month your support lead sees what customers keep telling you: tickets, disputes, reviews and survey comments grouped into themes with counts and quotations, the three issues most worth fixing with a proposed fix and owner, and a note for customers once a fix ships. A person decides every fix.

    Starts it
    Support lead
    Brings
    export, notes, document
    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

  • Daily production report

    When a shoot day wraps, the production coordinator gets a draft daily report from the call sheet, timecards and department reports: hours totaled as written, schedule changes noted, and every missing or overlapping entry listed as a query. The production manager checks it.

    Starts it
    Production coordinator
    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

  • 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

  • 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

  • Engagement margin review

    Midway or at close, the partner and finance lead get one worksheet for an engagement: recorded time, agreed fee, billed to date and supplied costs by workstream, the gaps that limit it, and the questions the team must answer. No cost rate is invented.

    Starts it
    Finance analyst
    Brings
    export, notes
    Gets
    6 outputs

  • Engagement staffing plan

    When several engagements want the same people, the resource lead sees the collision before kickoff: role needs against free days, leave and competing assignments, week by week, with two or three staffing options. The resource lead and partners choose.

    Starts it
    Resource lead
    Brings
    export, notes
    Gets
    6 outputs

  • Feedback follow-through updates

    When a change ships or a decision lands on something customers asked for, your account owner gets the list of who asked, the confirmed status of each request, and an individual draft update for each person in the channel they prefer. No update promises a date or feature the team has not confirmed.

    Starts it
    Account manager
    Brings
    export, notes, document
    Gets
    5 outputs

  • Implementation blocker brief

    When a customer's setup milestone slips, the implementation lead gets one brief: the missing inputs, the unresolved access and data questions and the dependencies behind the delay, each with its source and an owner, plus points to raise with the customer.

    Starts it
    Implementation lead
    Brings
    export, notes
    Gets
    6 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

  • Launch checklist

    Whoever owns a launch date gets one dated checklist for the weeks before, the day itself and the weeks after, with an owner on every line. Each announcement is written out so the approver sees exactly what goes out, to whom and from where before saying go. Nothing is announced by the assistant.

    Starts it
    Owner
    Brings
    export, notes
    Gets
    6 outputs