Workflows Directory
Find your team’s next superpower.
- Function: Project and delivery
- Industry: E-commerce and retail
- Industry: Education
- Industry: Energy
- Industry: Real estate
- Clear all filters
Results
10 workflow templates
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
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
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
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
Program outcome map
Before an evaluation, the program and evaluation leads get one map linking each activity to the outcome it is meant to serve, with proposed measures, data sources, assumptions and the questions the evidence cannot yet answer. It claims no impact.
- Starts it
- Program lead
- Brings
- export, notes
- Gets
- 8 outputs
Property diligence index
The transaction lead gets a diligence room in order: every document indexed by workstream, every checklist item and request tracked, and every open finding tied to the report or request that raised it. Specialists judge the findings; nothing is valued or sent.
- Starts it
- Transaction coordinator
- Brings
- export, notes
- Gets
- 5 outputs
Punch list consolidation
The site manager gets the punch list for the next closeout walk as one list grouped by location and trade, with repeated entries merged, photographs attached and a proposed follow-up date for each open item. Nothing is assigned, closed or accepted.
- Starts it
- Site manager
- Brings
- export, notes
- Gets
- 7 outputs
Service visit work packet
Before a planned visit to a turbine, inverter or terminal asset, the maintenance supervisor gets one packet built from the logs and approved scope supplied: reported symptoms, previous visits, open parts requests and access questions. It judges no condition and sends nothing.
- Starts it
- Maintenance supervisor
- Brings
- export, notes
- Gets
- 7 outputs
Submittal register review
The project engineer gets one register of every required submittal: what has arrived, the review status as recorded, the documents still missing and the long-lead items at risk against the date each order must be placed. Nothing is routed, accepted or ordered.
- Starts it
- Project engineer
- Brings
- export, notes
- Gets
- 6 outputs
Three-week look-ahead constraint review
Before the coordination meeting, the superintendent gets a brief that sets each planned activity of the next three weeks beside what could hold it up: trades sharing an area, unfinished predecessors, open approvals, late deliveries and unanswered RFIs. The superintendent confirms the sequence and assigns the follow-up.
- Starts it
- Project engineer
- Brings
- export, notes
- Gets
- 7 outputs