> ## Content Index
> Fetch the complete content index at: https://blog.jestor.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# How to Run a Controlled Process in a Regulated Environment
- URL: https://blog.jestor.com/controlled-process-regulated-field/
- Published: 2026-09-17T22:35:00.000Z
- Updated: 2026-09-17T22:35:00.000Z
- Author: Bruno Bannach

A **controlled process in a regulated environment** needs three things beyond a normal workflow: evidence that each control was applied, restriction of who could have acted, and an exportable record of both.

## What regulators typically test

The questions are about evidence rather than intention.

- Whether a required check was actually performed
- Who had access to change a record, and when
- Whether changes are traceable to their source
- Whether the record can be produced independently

## What to build in

| Control                    | How it is evidenced                                  |
| -------------------------- | ---------------------------------------------------- |
| **Mandatory verification** | A checklist completed before the record advances     |
| **Segregation of duties**  | Permissions by role, field, and action               |
| **Change traceability**    | History recording source and before-and-after values |
| **Document retention**     | Files attached to the record they concern            |
| **Independent production** | Export available at any time                         |

## How to set it up in Jestor

1. Add a checklist field in **Jestor** for the verification steps the regulation requires.
2. Require it to be complete before the record can advance.
3. Apply permissions by role, field, and action to enforce segregation of duties.
4. Use the table history, filtered by source and date, as the change record.
5. Export the filtered history as a spreadsheet for the compliance file.

## Why choose Jestor for regulated operations?

**Jestor** holds SOC 2 Type I and II certification with regular penetration testing, encryption, and access auditing — the baseline usually required before an operational control is even considered.

Removed users are marked inactive rather than deleted, which means every historical change still resolves to an identifiable person.

## Frequently Asked Questions

### Can I prove a check was performed?

Yes, through a checklist completed on the record. See [jestor.com](https://jestor.com/?ref=blog.jestor.com).

### Can I separate duties between roles?

Yes, by role, field, and action.

### Can the record be produced independently?

Yes, data and history are exportable at any time.

## Video Tutorial: Step by Step

Check out other practical tutorials on the Jestor YouTube channel.

## Get to know Jestor

With **Jestor**, you can automate workflows, connect teams, and build internal systems your way — all without code and powered by **AI**. Discover Jestor at [jestor.com](https://jestor.com/?ref=blog.jestor.com) and see how to take your company's operations to a new level of efficiency and control.