# Pascal Automation Studio

Source: https://www.trypascal.io/platform/automation-studio

Turn past work into automation.

Build agents and workflows from the cases your team already handles. Test them on unseen work, choose a limited scope, and expand as results justify it.

## Capabilities

### Reuse what your team knows

Bring past cases and decisions. Keep the evidence, missing history, and exceptions that make the work more than a checklist.

### Build with an agent

Give the builder an outcome and development examples. Review the resulting Agent and Workflow releases before putting them to work.

### Keep the test unseen

Use a separate set of unfamiliar cases. Failed and missing trials stay in the results, alongside completions and correct handoffs.

### Start with a small scope

Choose which work can enter and how much to expose. Keep the required approvals, pause new work, or restore a previous configuration.

### Give exceptions a human path

Send disputed contracts, missing identity, and privileged requests to a person with the reason for the handoff and access to the original case.

### Follow the outcome

See what completed, what reopened, and what still needs evidence. Track human participation separately from automated completion.

## Connected context

Use Work Episodes for case history, Tasks for the build, and Evaluation for testing. Run reviewed Agent and Workflow releases with records from Ontology, evidence from Documents, and actions from Integrations.

- A work model defining the outcome, source evidence, and decisions reserved for people
- Historical work examples, separate development and protected case sets, and exact releases
- Assessment results, operating scope, human review requests, and observed outcomes

## Controls and permissions

Your team sets the outcome, operating scope, and decisions reserved for people. Tests show how a candidate performed in the test environment. Live actions still require current permissions, and business results need later evidence from the systems involved.

## Example

A support team wants to resolve standard entitlement requests. It brings historical tickets, reviews the identity and contract checks, and reserves disputed requests for a specialist. The builder uses development examples; a separate protected set tests the released workflow. The team starts with a limited, supervised scope. In operation, disputed entitlement stays in the human queue, and a resolved ticket remains a pending outcome until the seven-day reopen window is observed.

## Workflow

### Understand the work

- Show how a case starts, what a good outcome looks like, and where your team needs to step in.

### Build the automation

- Work with an agent using development examples. Review the proposed process and select the exact release you want to test.

### Test on unseen cases

- Hold back examples the builder has never seen. Look at completions, correct handoffs, and failures together.

### Choose the operating scope

- Choose the eligible work and how much to expose. Check the trigger, approvals, and human fallback before enabling new work.

### Operate and improve

- Resolve exceptions and watch what happens after a run finishes. Send improvements through another build and test cycle.

## Next steps

Bring a recurring case type, examples of good decisions, and the exceptions people should keep handling. Define how to test the automation before expanding its scope.

- [Contact sales](https://www.trypascal.io/contact)
- [People and agents working together](https://www.trypascal.io/solutions/pascal-work)