Back to DocsCONTROLS DOCS

Enterprise controls delivered through ordinary workflows.

Forge Control does not ask every user to become an ERP operator. Staff complete guided actions; the platform records the control layer around those actions.

Operation tracking

Retail and Property workflows return operation metadata such as operation ID, idempotency key, status, and correlation context. This is how business actions become trackable instead of disappearing into informal work.

Maker-checker review

Sensitive actions can require review or approval. Retail exposes approvals and exceptions; Property exposes Needs Attention and operation review for failed, deferred, or daily-closure-blocking work.

Site scope

Both apps carry an active site or branch context so the user knows where the operation is happening and owners can review activity by location.

Idempotency

Mutating workflows submit with idempotency keys. This protects retries and helps prevent accidental duplicate business actions.

Reconciliation

Retail includes reconciliation workflows that compare expected operational records with actual state. Property connects invoices, payments, tenant ledger, maintenance, and review signals.

Reports and documents

Both products create report jobs and print documents so management views can be repeated, shared, and reviewed.

WORKFLOW CONNECTION

How one action becomes business truth.

This is the core pattern across Forge Control Retail and Forge Control Property. The domain changes; the operating discipline stays consistent.

1

Frontline user completes a business workflow.

2

The app submits the workflow with role, site, and idempotency context.

3

The platform records operation status, approval needs, and business references.

4

Managers review exceptions, approvals, or closure blockers.

5

Reports, reconciliation views, accounting records, and audit trails come from the same workflow history.