Skip to main content

Processes

A process is the blueprint for how work should happen.

In Nawfe, a process defines:

  • how work starts
  • what information is collected
  • what decisions or approvals happen
  • which automations or integrations run
  • how work moves between people, teams, tables, and external systems
  • what a finished execution should look like

Use a process when the work happens more than once, changes ownership across people or systems, requires approvals, needs traceability, or becomes expensive when steps are missed.

Draft versus published​

This distinction matters.

  • Draft is where you design and change a process.
  • Published is what live executions use.

Editing a draft does not change executions that are already running against a published version. Publish only when the start path, required data, assignees, approvals, and automation dependencies are ready for live use.

Process references​

These process topics have their own pages:

What makes a strong process​

A strong process is:

  • clear about who does what
  • simple enough to maintain
  • strict where compliance matters
  • flexible where human judgment matters
  • measurable after it launches