Workflows Directory
Find your team’s next superpower.
- Function: Compliance, risk and privacy
- Function: Information security
- Function: Product management
- Clear all filters
Results
33 workflow templates, showing 1 to 24
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
Audit preparation
Before the external auditors arrive, your controller holds one audit pack: every request with its owner, date, document and status, the control evidence they will test, last year's findings and what was done, and draft answers to the questions they will ask. People approve everything before it goes.
- Starts it
- Controller
- Brings
- export, notes, document
- Gets
- 9 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 insurance renewal review
Before the business insurance renews, the owner gets one pack: every policy with insurer, limits, deductibles, premium and dates; renewal terms beside expiring ones, every change marked; what changed in the business; claims; and questions for the broker. The broker and the owner decide all cover.
- Starts it
- Owner
- Brings
- export, notes, document
- Gets
- 8 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
Campaign claim evidence register
An account lead gets a register that pairs each draft campaign claim with the evidence the client supplied, its source date, proposed qualified wording and the approvals still missing. Unsupported or stale claims are blocked; only approved wording is released.
- Starts it
- Account lead
- Brings
- export, notes, document
- Gets
- 5 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
Creator content approval
A brand marketer gets a written go or no-go on a creator's draft before it goes live: every product statement checked against the brand's cleared list, the disclosure against the brand's own rules, and feedback the creator can act on without losing their voice. A person sends it.
- Starts it
- Brand marketer
- Brings
- notes, document, pasted text
- Gets
- 7 outputs
Creator publication tracking
A brand marketer sees, creator by creator, what was agreed against what actually went live: each post checked for its disclosure, code, link and approved version, dated checks that it is still up, and every gap set out as a fix to ask for or a decision to make. A person sends every message.
- Starts it
- Creator programme lead
- Brings
- export, notes
- Gets
- 5 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
Emissions activity data schedule
When the reporting period closes, the environmental reporting owner gets one source-linked schedule of energy, fuel and transport quantities with units and the boundary supplied, estimates kept apart from measured activity, missing factor references and gaps listed. It calculates no emissions figure.
- Starts it
- Environmental reporting owner
- Brings
- export, notes
- Gets
- 5 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
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
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
Product pricing options
A product owner weighing how to price or package a product gets one options brief: what each customer group uses, the willingness-to-pay evidence held with stated kept apart from observed, what each option would bill every account, the uncertainties and the tests. It recommends no price.
- Starts it
- Product owner
- Brings
- export, notes
- Gets
- 6 outputs
Product sample feedback revision list
After each round of samples, your product lead gets one revision list by sample version and feature: the changes people agree on, the feedback that conflicts, and drafted notes for the next supplier brief. The product owner decides.
- Starts it
- Product lead
- Brings
- export, notes, document
- Gets
- 7 outputs
Provider credentialing and re-credentialing tracker
The credentialing coordinator keeps one tracker per clinician: each licence, registration, certification, insurance policy and payer enrolment, where it was verified, when it falls due, the day its renewal should start, and which files are not yet complete. A person contacts every board and payer.
- Starts it
- Credentialing coordinator
- Brings
- export, notes
- Gets
- 4 outputs
Record sharing access matrix
When an approved access policy has to reach the CRM, the system owner lays the current sharing setup beside the proposed one, by record type and by role, internal and external. Every change is a question for its owner; inherited and platform-fixed settings are marked unknown.
- Starts it
- System owner
- Brings
- export, notes
- Gets
- 6 outputs
Records request preparation check
When a request for copies of records arrives, the records officer gets a checklist: what the request asks for, what the supplied authorization documents say, who the copies would go to, each set against the practice's own release procedure, with every gap listed. A person decides what, if anything, is released.
- Starts it
- Records officer
- Brings
- export, notes
- Gets
- 3 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