Routine checks
Use a defined rule when the answer can be checked directly, such as whether a required field is present.
Product documentation
Define the work.
Know what happens next.
A practical reference for defining a first ActorLattice process: responsibilities, information, approvals and a result you can check.
Start with a result you can check.
Example: a client file is complete and ready for a named reviewer.
Write down what starts the work, the information it needs and the conditions that make it complete. For a client file, that could mean each required document has arrived, the relevant checks are finished and the next person has accepted the handoff. A vague goal such as handle onboarding does not define a completion condition.
Give each Actor a clear responsibility.
Actors are digital workers in the process being designed. Receiving a task does not mean every step needs an AI model.
Interpretation
Use AI where the task needs interpretation, with the limits and review agreed for the process.
Human judgment
Give unclear questions and consequential decisions to the responsible person.
Separate reading, preparing and acting.
Define who may read each kind of information, who may prepare an action and who may approve or carry it out. An Actor allowed to draft a reminder should not be assumed to have permission to send it. Record where the work must pause for a person. Confirm the controls available in the release used for your pilot.
Keep attempts and results separate.
These terms describe the worked example. Confirm the exact states and supported actions for your process.
| Record | What to check |
|---|---|
| Received | The file arrived; it may still need review. |
| Prepared | The proposed action is ready, but has not necessarily been approved or executed. |
| Approved | The required person permitted the action. |
| Confirmed | The intended destination reported the agreed result. |
Connect outside tools only when needed.
A process can be scoped around ActorLattice screens, records and tasks. If it needs an outside service, name the product, account, permitted action and expected result. A provider logo is not a promise that every action is available. Agree which records stay in the current practice-management system, and confirm availability for the pilot.
Check proposed integrationsDecide what can continue and what must wait.
Define the routine tasks intended to continue outside office hours, the decisions that wait for people and who handles a failed or unclear result. Agree support hours, deployment responsibilities and access before the pilot. Cloud and self-hosted options do not remove those responsibilities.
Review deployment questions