Process Street workflow and approval setup help

SureClaw helps scope Process Street procedures with clear tasks, required evidence and a named reviewer.

Start with one repeatable procedure, decide what counts as complete and check how missing evidence or rejected work is handled.

Discuss your workflow
Person in a high-visibility vest holding an inspection checklist and pen.
Stock photo: RDNE Stock project / Pexels

Make the procedure reviewable

A procedure needs more than a list of boxes to tick. SureClaw can help scope a Process Street workflow with a clear run owner, the evidence needed at each stage and a reviewer who decides whether the work can proceed.

We start with one real procedure and the points where work is commonly incomplete. Native tasks and Process Street approvals should be assessed before adding an external automation. An approval configured as a stop task can prevent progress until approved, but assignees, permissions and notifications need to be configured for the actual workflow.

The aim is a procedure people can operate and review. An AI step or another system connection should only be added when its purpose and permitted actions are clear.

An inspection handover example

This is an illustrative procedure design, not a customer case study or a tested Process Street configuration. The sample run has an inspection owner, a required photo and a reviewer who accepts the handover.

  1. The owner submits inspection I104, but the photo is unreadable.
  2. The named reviewer rejects the evidence with the reason “replace the unreadable photo”. The handover remains held at the configured approval.
  3. The owner replaces the attachment and resubmits the affected work for review.
  4. The reviewer checks the replacement and approves it before the run proceeds.

The configuration map needs three separate decisions: which evidence is required, who reviews it and where progress must stop pending approval. A required attachment checks that a file exists; the reviewer still needs to decide whether that file is usable.

We would test no attachment, an unreadable attachment, an unassigned approver and a reviewer who cannot open the evidence. Acceptance requires the correct reviewer to inspect the material, a clear next action after rejection and no progress beyond the configured approval until it is approved.

Creating an external business record from an approved run is a separate integration decision. It needs a stable run identifier, a duplicate rule and a check that retrying does not create the record twice.

Check the people and connection settings

We establish who may edit the workflow, start a run, complete tasks and approve work. We also check how the reviewer is assigned and notified. A workflow that waits for an unassigned approver is not ready for handover even if its task structure looks complete.

Any connector needs its own authentication and action checks. We do not assume that every Process Street function is available through every connector, or that completing a task proves an external update succeeded. Failures need a named owner and a route to inspect the affected run.

Scope and acceptance

Bring one procedure, a few safe examples of complete and incomplete work, and the person who accepts the outcome. An assessment returns a task-and-approval map naming the run owner, required evidence, reviewer, stop point and rejection route, plus an acceptance checklist. If setup is included, that map is checked against a real sample run in your account before handover. Wider procedure standardisation follows what the first workflow teaches.

The business software integration checklist covers connected-record ownership. monday.com help suits board status and cross-team records; Notion help covers knowledge and working documentation where those are the main need.

Email SureClaw about Process Street. SureClaw is an independent consultancy, separate from Process Street.