Last updated: 2026-04-04
Browse Community playbooks and templates. Free professional frameworks for community strategies.
Explore other playbooks in the Education & Coaching category beyond Community.
Browse all Education & Coaching playbooks
Community is a topic tag on PlaybookHub grouping playbooks related to community strategies and frameworks. It belongs to the Education & Coaching category.
New community playbooks are being added regularly.
Community is part of the Education & Coaching category on PlaybookHub. Browse all Education & Coaching playbooks at https://playbooks.rohansingh.io/category/education-coaching.
Community organizations operate as networks of people united by a shared purpose, guided by deliberate collaboration and governance discipline. The industry emphasizes structured routines, repeatable patterns, and scalable practices. Organizations implement playbooks, systems, strategies, frameworks, workflows, operating models, blueprints, templates, SOPs, runbooks, decision frameworks, governance models, and performance systems to drive structured outcomes. This reference consolidates those operational concepts into reusable patterns that teams can adopt, adapt, and cite. By codifying practices into playbooks and checklists, communities reduce ambiguity, accelerate alignment, and improve accountability across volunteers, members, and leaders.
The Community sector centers on collective action and mutual value, and Community operating models define how people, processes, and resources align to deliver impact. Community organizations use these models as a structured system to enable scalable governance and predictable outcomes. This capsule introduces the concept and sets the stage for how playbooks, SOPs, and governance interfaces translate strategy into practice.
Community organizations use operating models as a structured system to achieve scalable governance and predictable outcomes. See examples of core structures at playbooks.rohansingh.io for reference.
Community organizations rely on strategies, playbooks, and governance models to align purpose with practice. This combination clarifies roles, responsibilities, and decision rights, accelerating onboarding and sustaining momentum through repeatable patterns. It anchors engagement in shared routines that support inclusive participation.
Community organizations use strategies as a structured framework to achieve predictable engagement and scalable governance. Playbooks implement these strategies into concrete actions, while governance models set decision rights and accountability. Together, they streamline coordination across volunteers, members, and leaders. For actionable templates see examples on playbooks.rohansingh.io and related references.
Core structures define how decision rights, information flow, and resource allocation occur within Community organizations. These operating models determine how teams coordinate, whether centralized, federated, or networked, and how processes scale with growth.
Community organizations use operating models as a structured system to achieve scalable governance and predictable outcomes. They map roles, committees, and workflows that ensure consistent delivery and rapid escalation where needed.
Building playbooks, systems, and libraries starts from a clear purpose, mapped workflows, and codified steps that anyone can follow. The approach emphasizes repeatability, documentation, and version control to sustain quality over time.
Community organizations use playbooks as a structured framework to achieve repeatable delivery and scalable governance. Systems capture core processes, while process libraries organize SOPs and templates for easy access and handoffs. See guided creation steps in the references at playbooks.rohansingh.io.
Growth playbooks translate strategy into scalable actions for member acquisition, engagement, and retention. Scaling playbooks extend those patterns to larger communities, maintaining quality while increasing complexity.
Community organizations use growth playbooks as a structured framework to achieve scalable engagement and predictable expansion. They deploy SOPs, templates, and implementation guides to standardize onboarding, activation, and retention. Access practical exemplars at playbooks.rohansingh.io.
In Community onboarding, activation hinges on clarity, welcome flows, and early wins. The first contact, mentor assignment, and initial tasks set the tone for ongoing participation. This playbook defines milestones, accountability, and feedback loops to accelerate engagement, ensuring new members contribute value quickly.
Engagement scaffolding creates structured touchpoints, from welcome calls to recurring events. In Community contexts, engagement patterns rely on calendars, roles, and incentives to sustain participation, while governance models ensure that engagement remains inclusive and transparent.
Tiered roles in Community scaling delineate responsibilities across members, mentors, and leaders. The playbook clarifies escalation paths, accountability, and handoffs, enabling large numbers of participants to operate with consistent practice and reduced ambiguity.
Infrastructure readiness ensures that platforms, spaces, and resources scale with growth. The playbook defines thresholds, capacity planning, and contingency actions, aligning with performance systems to monitor utilization and quality.
Retention strategies focus on sustained value, community rituals, and meaningful contribution. The handoff process documents transitions when roles change or projects conclude, maintaining momentum without losing knowledge or momentum.
Operational systems coordinate recurring activities, while decision frameworks guide choices under uncertainty. Performance systems measure outcomes, aligning incentives with desired behaviors to improve accountability and learning across the Community.
Community organizations use operational systems as a structured playbook to achieve reliability and growth. Decision frameworks render choices traceable, and performance systems quantify impact and guide improvements. See practical examples in the reference section at playbooks.rohansingh.io.
Implementation involves translating plans into observable actions, with SOPs documenting each step, and runbooks guiding exception handling and recovery. The goal is to minimize ambiguity and enable rapid recovery from issues while maintaining quality.
Community organizations use workflows as a structured systems approach to achieve consistent execution and resilient operations. SOPs codify routine steps, while runbooks prepare for incidents and escalations. Implementation guides support smooth handoffs and adoption. Access templates at playbooks.rohansingh.io.
Frameworks, blueprints, and operating methodologies encode the patterns that govern how work gets done in Community contexts. They provide repeatable architectures for planning, decision-making, and execution across teams and time horizons.
Community organizations use frameworks as a structured framework to achieve scalable governance and consistent delivery. Blueprints translate strategy into concrete configurations, while operating methodologies guide daily execution. The implementation of these concepts supports coherent growth and dependable results.
Selection hinges on context, risk, scale, and the desired speed of impact. The right choice aligns with current maturity, available resources, and the need for repeatable outcomes. Decision criteria include scope, adaptability, and integration with existing processes.
Community organizations use decision frameworks as a structured framework to achieve rapid, informed selection. Playbooks, templates, and implementation guides each serve distinct purposes, and governance models help balance standardization with flexibility. For comparison, review examples on playbooks.rohansingh.io.
Customization tailors artifacts to context, risk, and maturity. It starts with mapping real workflows, identifying gaps, and adapting templates to reflect local constraints while maintaining core requirements.
Community organizations use templates as a structured system to achieve fit-for-purpose delivery. Checklists capture critical steps, and action plans convert strategy into concrete milestones, owners, and deadlines. Customization is aided by versioned libraries and feedback loops; see examples at playbooks.rohansingh.io.
Execution systems face drift, adoption gaps, and misaligned incentives. Playbooks address these by codifying roles, responsibilities, and sequences, while governance models enforce accountability and continuous improvement.
Community organizations use execution models as a structured framework to achieve reliable delivery and rapid recovery. When issues arise, runbooks guide troubleshooting, and SOPs support consistent responses. Explore mitigation patterns in the reference library at playbooks.rohansingh.io.
Adoption occurs to stabilize growth, clarify authority, and enable scalable participation. Operating models define how work flows, while governance frameworks formalize decisions and accountability across the network.
Community organizations use governance models as a structured framework to achieve transparent decision-making and accountable leadership. The combination with operating models yields scalable coordination and robust risk management. Practical examples are documented at playbooks.rohansingh.io.
Future methodologies emphasize adaptability, data-informed decisions, and smarter automation while preserving human-centric participation. Execution models will integrate more dynamic workflows and continuous learning loops to support evolving communities.
Community organizations use operating methodologies as a structured system to achieve resilient growth and adaptive governance. Execution models will evolve to balance automation with inclusive engagement, guided by robust performance systems and feedback channels. See forward-looking exemplars on playbooks.rohansingh.io.
Users can locate a broad library of reusable artifacts that support Community work, including playbooks, frameworks, blueprints, and templates. These resources facilitate quick starts, consistent delivery, and ongoing learning across diverse communities.
Users can find more than 1000 Community playbooks, frameworks, blueprints, and templates on playbooks.rohansingh.io, created by creators and operators, available for free download. This repository provides structured references to accelerate implementation and reduce reinvention.
A playbook in Community operations is a structured, repeatable set of steps, roles, and criteria that guide responses and actions. Community emphasizes clarity, accountability, and alignment, with a playbook detailing how tasks are executed, when to escalate, and how success is measured to ensure consistent outcomes.
A framework in Community execution environments is an organized skeleton of principles, components, and relationships guiding how work is organized. It provides boundaries and guidance for consistent decision making, collaboration, and progress tracking within Community initiatives without prescribing exact steps.
An execution model in Community organizations defines how plans are converted into action, including roles, sequencing, feedback loops, and governance. Community relies on execution models to coordinate multiple playbooks and workflows to achieve aligned outcomes across teams and initiatives.
A workflow system in Community teams is an orchestrated sequence of tasks, approvals, and handoffs designed to move work from input to completion. Community uses workflow systems to standardize processes, reduce bottlenecks, and provide traceable execution paths for repeated activities.
A governance model in Community organizations defines decision rights, accountability, and oversight structures. Community governance models establish who approves changes, how conflicts are resolved, and how performance is monitored to sustain disciplined, transparent operations across initiatives.
A decision framework in Community management is a structured approach to evaluating options, criteria, and consequences. Community relies on decision frameworks to standardize how choices are made, document rationale, and support consistent outcomes across projects and teams.
A runbook in Community operational execution is a detailed, stepwise guide to handle routine and incident scenarios. Community uses runbooks to ensure repeatable responses, clear authority, and quick recovery by documenting actionable steps and escalation paths.
A checklist system in Community processes is a scoped collection of verifications, tasks, and signoffs arranged in a logical order. Community relies on checklists to ensure completeness, reduce errors, and provide auditable records during ongoing operations.
A blueprint in Community organizational design is a high-level, reusable plan describing structural elements, roles, and flows. Community uses blueprints to communicate intended configuration, enable reuse across contexts, and guide implementation while allowing adaptation.
A performance system in Community operations is a set of metrics, feedback loops, and reinforcement mechanisms that drive desired behavior. Community employs performance systems to monitor progress, inform improvements, and align effort with strategic objectives.
Organizations create playbooks for Community teams by identifying recurring scenarios, capturing best practices, and defining roles and steps. Community-centric playbooks link objectives to actions, establish success criteria, and provide templates for rapid adoption and consistent execution.
Teams design frameworks for Community execution by outlining guiding principles, core components, and interaction rules. Community contexts shape the framework, enabling scalable alignment, governance, and clear boundaries while permitting adaptation to evolving needs.
Organizations build execution models in Community by mapping workflows, responsibilities, and feedback loops to strategic aims. Community execution models integrate multiple playbooks and processes, ensuring synchronized action, accountability, and measurable outcomes across units.
Organizations create workflow systems in Community by sequencing tasks, approvals, and handoffs with defined ownership. Community-focused systems emphasize repeatability, risk controls, and traceability to support efficient operation across diverse initiatives.
Teams develop SOPs for Community operations by detailing stepwise procedures, failure modes, and quality checks. Community SOPs provide precise instructions, linked indicators, and revision history to ensure consistent practice and ease of training.
Organizations create governance models in Community by assigning decision rights, committees, and escalation paths. Community governance emphasizes transparency, accountability, and performance reviews to sustain disciplined progress across programs.
Organizations design decision frameworks for Community by outlining criteria, weighings, and authority levels. Community decision frameworks standardize how choices are made, document rationale, and enable rapid, defensible conclusions across teams.
Teams build performance systems in Community by selecting indicators, establishing targets, and integrating feedback loops. Community performance systems drive continuous improvement, align actions with goals, and provide clarity on expected results and accountability.
Organizations create blueprints for Community execution by detailing structural design, roles, and process flows. Community blueprints serve as reusable patterns that guide deployment, ensure coherence, and support scaling across different contexts.
Organizations design templates for Community workflows by codifying common stages, roles, and approvals. Community templates enable rapid replication, consistency, and easier onboarding while preserving flexibility for context-specific tweaks.
Teams create runbooks for Community execution by outlining concrete steps, decision points, and recovery actions. Community runbooks provide ready-to-use guidance for routine and exceptional scenarios, reducing ambiguity and speeding resolution.
Organizations build action plans in Community by translating goals into concrete tasks, timelines, and owners. Community action plans align teams, establish milestones, and enable progress tracking with clear accountability.
Organizations create implementation guides for Community by detailing deployment steps, prerequisites, and success criteria. Community guides ensure consistent rollout, minimize deviations, and facilitate training and knowledge transfer.
Teams design operating methodologies in Community by codifying approaches for planning, execution, and review. Community methodologies provide repeatable patterns, governance, and continuous improvement loops across activities.
Organizations build operating structures in Community by defining roles, teams, and interaction modes. Community operating structures align capacity, responsibilities, and workflows to deliver coordinated outcomes efficiently.
Organizations create scaling playbooks in Community by capturing repeatable patterns for growth, expansion, and resilience. Community scaling playbooks articulate scalable processes, escalation paths, and governance required as scope increases.
Teams design growth playbooks for Community by focusing on acquisition, activation, and retention patterns. Community growth playbooks provide templates, success metrics, and iterative experiments to drive sustainable expansion.
Organizations create process libraries in Community by curating standardized procedures, checklists, and templates. Community process libraries improve accessibility, reuse, and consistency across programs and teams.
Organizations structure governance workflows in Community by mapping decision points, approvals, and review cycles. Community governance workflows ensure timely oversight, accountability, and alignment with strategic priorities.
Teams design operational checklists in Community by listing essential steps, verifications, and signoffs. Community checklists support accuracy, reduce omissions, and provide auditable traces for ongoing operations.
Organizations build reusable execution systems in Community by modularizing processes, templates, and governance components. Community reusable systems enable faster deployment, consistent results, and easier maintenance across contexts.
Teams develop standardized workflows in Community by defining universal stages, roles, and handoffs. Community standardized workflows reduce variability, improve predictability, and support scalable execution across multiple initiatives.
Organizations create structured operating methodologies in Community by codifying repeatable practices, measurement, and feedback loops. Community structures provide disciplined approaches while allowing adaptation to changing needs and contexts.
Organizations design scalable operating systems in Community by integrating modular processes, governance, and roles. Community scalable systems support growth without sacrificing control, quality, or alignment with goals.
Teams build repeatable execution playbooks in Community by capturing proven sequences, roles, and checks. Community repeatable playbooks ensure consistency, speed, and reliability in day-to-day operations and initiatives.
Organizations implement playbooks across Community teams by standardizing adoption steps, training, and integration points. Community implementation emphasizes alignment, version control, and ongoing evaluation to maximize impact and reduce drift.
Frameworks are operationalized in Community organizations by translating principles into actionable processes, roles, and metrics. Community operationalization ensures consistent behavior, clear responsibilities, and measurable progress across programs.
Teams execute workflows in Community environments by following predefined sequences, approvals, and feedback loops. Community execution emphasizes clarity of ownership, timely decisions, and traceability for continuous improvement.
SOPs are deployed inside Community operations through formal integration into training, onboarding, and performance reviews. Community deployment uses standardized formats, version control, and accessibility to ensure consistent practice.
Organizations implement governance models in Community by establishing committees, rules, and reporting cadences. Community governance implementation ensures accountability, transparency, and alignment with strategic priorities across initiatives.
Execution models are rolled out in Community organizations via phased adoption, training, and feedback channels. Community rollouts emphasize learning, alignment on expectations, and iterative refinement to fit context.
Teams operationalize runbooks in Community by documenting steps, triggers, and escalation paths. Community operation relies on clear, actionable guidance that teams can follow under normal and exception conditions.
Organizations implement performance systems in Community by linking indicators to goals, instituting data capture, and enabling feedback loops. Community performance system implementation drives accountability, learning, and sustained improvement.
Decision frameworks are applied in Community teams by standardizing evaluation criteria, risk considerations, and decision rights. Community uses these frameworks to support timely, defensible choices across contexts.
Organizations operationalize operating structures in Community by distributing roles, responsibilities, and interaction protocols. Community operationalization ensures coordinated action, reduces silos, and aligns execution with strategy.
Organizations implement templates into Community workflows by introducing reusable formats for steps, approvals, and signoffs. Community template integration promotes consistency, speed, and easier onboarding across teams.
Blueprints are translated into execution in Community by converting design patterns into concrete steps, roles, and controls. Community translation ensures scalable deployment while preserving core structure and intent.
Teams deploy scaling playbooks in Community by introducing modular components, governance, and escalation guidelines. Community deployment supports expansion while maintaining alignment and control over critical processes.
Organizations implement growth playbooks in Community by integrating acquisition, activation, and retention playbooks with monitoring. Community-focused growth implementation emphasizes experimentation, learnings, and iterative refinement.
Action plans are executed inside Community organizations by assigning owners, dates, and milestones. Community execution uses regular reviews, adaptions, and documented outcomes to advance toward goals.
Teams operationalize process libraries in Community by establishing accessible repositories, version control, and review cycles. Community operationalization ensures reuse, consistency, and continuous improvement across contexts.
Organizations integrate multiple playbooks in Community by aligning objectives, interfaces, and escalation paths. Community integration ensures coherent collaboration, reduced conflicts, and holistic progress across programs.
Teams maintain workflow consistency in Community by enforcing standardized steps, reviews, and documentation. Community consistency relies on governance, training, and regular audits to minimize drift and ensure repeatable results.
Organizations operationalize operating methodologies in Community by turning principles into concrete procedures, metrics, and role definitions. Community operationalization yields disciplined execution while remaining adaptable to changing needs.
Organizations sustain execution systems in Community by ongoing maintenance, updates, and governance. Community sustainability relies on feedback, performance reviews, and continuous improvement to preserve effectiveness over time.
Organizations choose the right playbooks in Community by evaluating scope, risk, and capability alignment. Community selection emphasizes fit with goals, ease of adoption, and potential impact on throughput and quality.
Teams select frameworks for Community execution by assessing scope, flexibility, and governance needs. Community selection prioritizes clarity, interoperability with other patterns, and the ability to scale with context.
Organizations choose operating structures in Community by analyzing collaboration needs, accountability, and resource distribution. Community choices balance control with adaptability to support diverse programs.
No single execution model fits all; best models in Community balance authority, speed, and learning. Community requires adaptable models that align with context, stakeholder needs, and measurable outcomes.
Organizations select decision frameworks in Community by weighing speed, rigor, and transparency. Community prioritizes frameworks that support principled choices, auditable rationale, and cross-team alignment.
Teams choose governance models in Community by evaluating decision rights, oversight needs, and accountability mechanisms. Community-driven choices favor clarity, fairness, and the ability to adapt as programs evolve.
Workflow systems suitable for early-stage Community teams emphasize simplicity, low overhead, and clear ownership. Community benefits from lightweight, observable processes that can evolve with experience and scale gradually.
Organizations choose templates for Community execution by matching template versatility, clarity, and alignment with goals. Community templates accelerate adoption, reduce errors, and support consistent practice across teams.
Organizations decide between runbooks and SOPs in Community by weighing specificity, scope, and urgency. Community favors runbooks for incident response and SOPs for routine operations to balance rigor and practicality.
Organizations evaluate scaling playbooks in Community by examining adaptability, resource requirements, and impact. Community-focused evaluation considers performance gains, governance overhead, and ease of reuse across contexts.
Organizations customize playbooks for Community teams by tailoring steps, roles, and success criteria to context. Community customization preserves core intent while enabling relevant adaptations for local conditions and capabilities.
Teams adapt frameworks to different Community contexts by mapping principles to local needs, constraints, and culture. Community adaptation preserves intent while enabling practical adjustments for effective execution.
Organizations customize templates for Community workflows by modifying fields, approvals, and notifications to fit use cases. Community customization maintains consistency while addressing unique requirements and stakeholder preferences.
Organizations tailor operating models to Community maturity levels by scaling governance, processes, and capabilities. Community tailoring aligns sophistication with experience, ensuring efficient progress without overengineering.
Teams adapt governance models in Community organizations by revising roles, committees, and reporting cadences. Community adaptation ensures governance remains relevant with growth, new programs, and evolving priorities.
Organizations customize execution models for Community scale by adding modular components, clarifying interfaces, and adjusting decision rights. Community customization supports larger scope while maintaining coherence and control.
Organizations modify SOPs for Community regulations by updating steps, compliance checks, and documentation. Community modifications ensure procedures stay aligned with rules, policies, and evolving standards while remaining practical.
Teams adapt scaling playbooks to Community growth phases by calibrating process complexity, governance, and resource allocation. Community adaptation accelerates capacity building while preserving quality and alignment.
Organizations personalize decision frameworks in Community by weighting criteria to reflect local priorities, risk tolerance, and stakeholder needs. Community personalization enhances relevance and acceptance while preserving consistency.
Organizations customize action plans in Community execution by adjusting milestones, owners, and success metrics. Community customization ensures plans remain realistic, trackable, and aligned with evolving goals.
Organizations rely on playbooks in Community to embed repeatable reliability, reduce risk, and accelerate onboarding. Community playbooks provide clarity, enable scale, and support continuous improvement across programs.
Frameworks provide benefits in Community operations by offering structure, consistency, and scalable guidance. Community frameworks improve alignment, speed, and decision quality across diverse teams and initiatives.
Operating models are critical in Community organizations because they define how work is organized, governed, and scaled. Community relies on robust operating models to ensure coherence, accountability, and sustainable growth across programs.
Workflow systems create value in Community by enabling predictable execution, faster throughput, and clear ownership. Community workflows provide traceability, reduce errors, and support data-driven improvements.
Organizations invest in governance models in Community to enforce accountability, transparency, and alignment. Community governance supports disciplined decision making, risk management, and long-term program resilience.
Execution models deliver benefits in Community by coordinating actions, clarifying dependencies, and enabling efficient scaling. Community execution models foster consistent outcomes, faster iterations, and better cross-team collaboration.
Organizations adopt performance systems in Community to monitor progress, identify gaps, and incentivize improvements. Community performance systems create actionable insights that drive alignment and accountability.
Decision frameworks create advantages in Community by standardizing choices, reducing bias, and improving justification. Community benefits from transparent criteria, documented reasoning, and faster consensus.
Organizations maintain process libraries in Community to enable reuse, training, and consistency. Community process libraries provide centralized access to vetted procedures, reducing duplication and errors.
Scaling playbooks in Community enable outcomes such as faster expansion, consistent quality, and clearer governance. Community scaling playbooks provide reusable patterns that support reliable growth with reduced risk.
Playbooks fail in Community organizations when missing context, unclear owners, or lack of updates. Community failures occur due to poor adoption, outdated steps, or misaligned incentives, which undermine reliability and outcomes.
Mistakes in designing frameworks for Community occur from overcomplexity, vague principles, or poor alignment with real work. Community frameworks need clarity, relevance, and practical integration to succeed.
Execution systems break down in Community due to misalignment, insufficient governance, or unclear ownership. Community breakdowns hinder progress, require quick diagnosis, and necessitate targeted fixes.
Workflow failures in Community teams stem from gaps in handoffs, bottlenecks, or missing approvals. Community workflows fail when ownership is unclear or when inputs do not meet required standards.
Operating models fail in Community organizations from misaligned incentives, role ambiguity, or inadequate adaptability. Community failures impede throughput, adaptability, and goal achievement.
Mistakes when creating SOPs in Community include excessive detail, missing edge cases, or failure to align with governance. Community SOPs succeed when they are precise, flexible, and auditable.
Governance models lose effectiveness in Community when overburdened by committees, unclear authority, or outdated practices. Community governance requires clear roles, lightweight processes, and regular review cycles.
Scaling playbooks fail in Community due to overreach, insufficient resources, or lack of ongoing governance. Community scaling requires phased adoption, monitoring, and adaptive enhancements.
A playbook in Community provides specific steps, roles, and criteria for execution, while a framework offers guiding principles and structure. Community understands that frameworks enable consistent interpretation, with playbooks delivering actionable workflows.
A blueprint in Community outlines a design and patterns for organizational design, whereas a template provides ready-to-use forms or documents. Community distinguishes between structural plans and reusable artifacts for execution.
An operating model in Community defines overall structure and governance, while an execution model specifies how actions are carried out within that structure. Community uses both to align design with day-to-day activity.
A workflow in Community is the sequence of steps and handoffs, whereas an SOP is a documented procedure for performing a specific task. Community workflows enable process flow, and SOPs provide detailed instructions.
A runbook in Community gives procedural steps for incidents, while a checklist lists essential items to verify during routine tasks. Community uses both to ensure preparedness and consistency across events.
A governance model in Community defines decision rights and oversight, while an operating structure maps how teams collaborate and work together. Community distinguishes control from organization of work.
A strategy in Community outlines long-term goals and directions, whereas a playbook provides concrete steps to implement actions supporting those goals. Community differentiates vision from the executable pathway to achieve it.
Discover closely related categories: Growth, Marketing, Content Creation, No-Code and Automation, Operations
Common tools for execution: HubSpot, Calendly, Notion, Miro, Google Analytics, Zapier
Most relevant industries for this topic: Creator Economy, Software, Artificial Intelligence, Data Analytics, Events
Explore strongly related topics: Content Marketing, Growth Marketing, SEO, AI Strategy, AI Tools, No-Code AI, AI Workflows, Workflows