Workflows Directory
Workflow templates for business systems and integrations or IT and systems
Results
13 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
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
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
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 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
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
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
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
Pilot acceptance-test preparation
Go into every AI pilot with the test already written: the cases that matter, what good looks like for each and the rule your owner will use to decide.
- Starts it
- Pilot owner
- Brings
- notes, document
- 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
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
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