Workflows Directory
Find your team’s next superpower.
- Function: Business systems and integrations
- Function: Information security
- Function: Recruiting and hiring
- Clear all filters
Results
20 workflow templates
App data requirements
When the requirements for an internal app leave fields or actions unclear, the business systems analyst gets one data specification: entities, fields, who reads and writes each, and every unresolved name as a question. Nothing is built or changed.
- Starts it
- Business systems analyst
- Brings
- export, notes, document
- Gets
- 9 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
Candidate outreach drafting
For each person a recruiter or founder has already chosen to approach about an approved role: a first message and two follow-ups, each personal line traced to a public work source the recruiter supplied, do-not-contact names and opt-outs honoured, and a reply log. The recruiter sends every message.
- Starts it
- Recruiter
- Brings
- export, document
- Gets
- 5 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
Employee onboarding plan
Every new colleague starts with a first week and a first 90 days planned to the standard of your best manager: what to read, who to meet, what to practice and what productive means at day 30, 60 and 90.
- Starts it
- Hiring manager
- Brings
- notes, document
- Gets
- 6 outputs
Hiring pipeline status report
Each week your people lead or founder sees every open role on one page: applications at each stage, days open against the target, roles running late, pass-through between stages, which sources lead to interviews, and every blocker with its owner. It counts; it never assesses a candidate.
- Starts it
- People lead
- Brings
- export, notes, document
- Gets
- 6 outputs
Household record differences
When the CRM and the custodian's account export disagree about a household, the operations owner gets one comparison: accounts with no household, possible duplicates and field-by-field differences, each with its source row and a proposed correction left as a question. No record is changed.
- Starts it
- Operations owner
- Brings
- export, notes
- Gets
- 6 outputs
Interview plan and scorecard
Before the first interview, the hiring manager and every interviewer share one plan: the criteria the role needs, the same questions in the same order for every candidate, and a blank scorecard each person fills in alone. It rates no one. People make every decision about a candidate.
- Starts it
- Hiring manager
- Brings
- notes, document
- Gets
- 7 outputs
Interview process review after a hiring round
After a hiring round closes, the recruiting lead gets a review of the interview process: questions that gave no usable evidence, competencies nobody covered, inconsistent rubric use, and revisions to approve before the next search. It reviews the process only; no candidate is assessed.
- Starts it
- Recruiting lead
- Brings
- export, notes
- 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
Job description
A hiring manager’s rough notes become a job description the right people want to answer: why the role exists, the work itself, and only the must-haves that are real. Your approved pay and employer wording go in untouched, and nothing is posted until the hiring manager and the people lead approve it.
- Starts it
- Hiring manager
- Brings
- notes, document
- Gets
- 2 outputs
Job posting and sourcing plan
For one approved role, the hiring manager gets a plan for where to post and where to look: every channel on the company's own list ordered by the signal it should give for that kind of role, a week-by-week schedule inside the budget, and what to count on each channel. Nothing is posted or paid until a person approves.
- Starts it
- Hiring manager
- Brings
- export, notes, document
- Gets
- 4 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
Notification channel plan
When a business event needs to notify people, the integration owner gets one channel plan from the event definitions: trigger, urgency, who is told by which channel, what needs confirmation, fallbacks and reply handling. Consent and message rules stay as questions. Nothing is sent.
- Starts it
- Integration owner
- Brings
- export, notes
- Gets
- 1 output
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
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
Service inbox routing plan
When a new service inbox is being set up, the service owner gets a routing plan: each approved address, the queue it should reach and who owns it, checks to run before it goes live, and the wrong-address risks, loop risks and unconfirmed queue owners still open. Nothing is configured.
- Starts it
- Service owner
- Brings
- export, notes
- Gets
- 5 outputs
Teaching tool vendor data questions
Before a school or college adopts a teaching tool that would handle student or staff information, the privacy or procurement lead gets a scoped question pack on data flows, access, retention and subprocessors, with each supplied vendor document mapped to the questions and the gaps listed.
- Starts it
- Privacy lead
- Brings
- export, notes, document
- Gets
- 5 outputs
Work sample exercise brief
For one approved role, the hiring manager gets a practical exercise: a bounded task from the role's real work, instructions for the candidate with a time limit and adjustments, and the evidence the panel will look for. The panel judges the work; nothing is rated here.
- Starts it
- Hiring manager
- Brings
- export, notes, document
- Gets
- 5 outputs
Workflow inventory
When the ownership and status of your automated workflows come up for review, the platform owner gets one inventory built from the exports supplied: environments, enabled states, last run, queued runs and owner gaps. Quiet workflows become questions, not removal lists.
- Starts it
- Platform owner
- Brings
- export, notes
- Gets
- 7 outputs