Docs Process Blueprints

Process Blueprints

A blueprint is the reusable definition of a process. Build it once; launch it as a Run any time.

Anatomy of a blueprint

  • Stages — ordered phases of the process.
  • Tasks — within each stage, with:
    • Assignment rule — route to a user, role, or department (department routes to its head), or mark it Ask on run so the starter picks who's responsible each time.
    • Proof requirements — checklist items, file uploads, signatures, approvals, etc.
    • Dependencies — tasks that must finish first, with a policy (warn / block / require override).
    • SLA — an optional deadline in hours.
    • Related SOP — surface the right procedure on the task.

Build it with AI

Instead of building by hand, you can upload a document (e.g. a transition checklist) or describe the process in AI Studio. AI drafts the stages and tasks, detects who owns each step, and decides whether the process is a reusable template (owners asked at run time via Ask on run) or uses the same fixed people every time. See AI Studio.

Starting a run with assignments

When you launch a run from a blueprint that has Ask on run steps, PilotBPM prompts you to fill in who's assigned (and optional due dates) before the run starts — pre-filled with AI's suggestions, with a bulk "fill empty with…" option so it never gets tedious on long processes.

Automations

  • On completion (run level) — when a run finishes, automatically launch follow-on blueprints.
  • On completion (step level) — a single task can launch a sub-workflow when it's done. The sub-workflow's tasks auto-route to the people it assigns, creating a clean handoff (e.g. contract request → data collection → DocuSign → regional approval).

How to configure

  1. Create a blueprint and add stages.
  2. Add tasks; set assignment, proof, dependencies, SLA, and (optionally) a sub-workflow to launch on completion.
  3. Optionally attach an intake form and oversight roles.
  4. Publish the blueprint so it can be launched and quick-launched from the Sandbox.

Roles

Managers and above (or holders of blueprint.manage) can build and publish blueprints.