Workflows Directory
Find your team’s next superpower.
- Function: Project and delivery
- Industry: Insurance
- Industry: Logistics and trade
- Industry: Manufacturing
- Industry: Real estate
- Clear all filters
Results
8 workflow templates
Pilot build readiness brief
Before a prototype or pilot build, the build lead gets one brief: part shortages, revision conflicts and open actions set against the team’s own build checklist, with allocated parts kept apart from received ones. People confirm; nothing is released.
- Starts it
- Build lead
- Brings
- export, notes, document
- Gets
- 7 outputs
Premortem before a decision
Before your team commits to a plan that is hard to undo, such as a move, a launch or a new system, a short workshop pictures it a few months on, already failed. The record ranks the reasons, turns each top risk into a check, a warning sign and an owner, and leaves the go decision with the owner.
- Starts it
- Owner
- Brings
- notes
- Gets
- 4 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
Stakeholder and decision rights map
Before kickoff, the project manager holds one map of everyone the project touches: each group placed by influence and interest, every key decision with exactly one accountable owner, the decision makers still missing, and who hears what, when and from whom. The sponsor confirms every decision right.
- Starts it
- Project manager
- Brings
- export, notes, document
- Gets
- 6 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