Product Owned AI Verticals Pricing Security Guide Customers About Sign in See it live

Chapter 3 · Workflows & tasks

Write the process down once. Every engagement gets its own dated work.

Workflows exist so the routine steps of a program happen on time without someone remembering them. You describe your process once as a template, setting out what happens and how many days after what, and StreamBuild turns it into real, dated tasks every time it is applied.

If you are deciding

The process your funder agreement describes is the process the system runs, and slippage shows up as overdue work rather than a surprise at quarter end.

If you use it daily

Your Monday is a list of dated tasks across every engagement you own, generated from the templates, with the email or document already waiting where a step needs one.

If you are doing diligence

Bound actions that produce content go through the same manifest and ownership gate as any other AI output.

Anchors and offsets

A workflow template is a list of steps. Each step is placed a number of days from an anchor: the engagement being created, an intake period closing, an event starting. “Send the welcome pack, day 0. Confirm eligibility, day 5. Committee review, day 21.” Negative offsets work too, for example “send reminders, 7 days before the event”.

/p/<program>/s/<stream>/workflows/<templateId>
Workflow builder: steps with offsets
FIG. 05 A funding-stream intake template. The step list is on the left, and the selected step shows its due rule, here five days after the engagement is created. Anchors and day offsets.

Subjects

A template is applied to a subject, which is an engagement, a lead or an event. Applying it generates the tasks with real dates, assigned to the right people. If the anchor date moves, the generated dates move with it.

Bound actions

A step can carry an action: send an email, generate a document, create a meeting. When the task comes due, the action has done its preparation. The email is drafted, the document is generated. Then it waits for a person. It does not send or file on its own authority, because it runs under the same governance as everything else.

/tasks
Task list across subjects
FIG. 06 One person’s task list across engagements and events, grouped by due date. Tasks with a bound action show what they have prepared. Generated work, dated.

What this does not do

  • Tasks come from workflows. There is no free-standing project board, and no general to-do list unrelated to a subject.
  • Workflows do not branch on conditions. A step that only applies sometimes is completed or skipped by a person.
  • A bound action never sends, files or publishes without a named person owning it.