FREE BUSINESS WORKFLOW · AI AS AN EMPLOYEE

Set project-specific rules for an AI workflow

Assign ownership, limit access, and test approval requirements.

Project controls · No sign-up

When to use it

Before an AI workflow takes ongoing actions or accesses business systems.

What you’ll get

A project control checklist and sandbox test record.

Work through the steps

Before you start

A platform with enforceable project permissions and approval gates, an administrator, a project owner, and sandbox tools. Prompts alone cannot enforce access controls.

Step 01

Define ownership

Draft a project charter for [workflow]. Name [owner], allowed tasks, excluded work, data boundaries, and escalation contact.

Step 02

Scope the project

Have an administrator configure controls.

Recommend project settings for [workflow]: approved model, cost limits, relevant skills, and minimum tool permissions. Flag unsupported controls.

Step 03

Require approvals

Apply policies in platform settings.

Draft policies requiring explicit approval before [sensitive actions]. Identify who may approve, what they must see, and how denial blocks execution.

Step 04

Test the boundary

Use disposable sandbox records.

Test an allowed action, an approval-required action, and a denied action. Verify actual tool execution and logs; record whether controls held.

Step 05 · Review before use

Confirm the owner and saved settings.
Ensure denial prevents tool execution.
Check project isolation with another sandbox project.

If you get stuck: If enforcement fails, disable the affected tool and keep actions manual until controls are fixed.

Inspired by ChatPRD’s project-governance workflow. Prompts above are original Hiatt Co practice material.

Back to free workflows