People and locations
Who performs the work, where access occurs, and who remains accountable
Trust and cross-border operations
Clear boundaries before access begins.
Every engagement starts with written rules for systems, permitted data, access, authority, and escalation. Sensitive operational data enters scope only through an agreed channel.
Workflow boundaryDefined before access
Work locationNamed precisely
Permitted accessScoped by system and role
Client authorityRetained explicitly
EvidenceOwner · source · review date
Scope before access
What every workflow scope defines.
The exact answer depends on the systems, data, authority, and operating risk involved in the work.
Data boundary
Permitted and prohibited data, approved systems, and the channel used for access
Identity and access
Named users, least-privilege roles, authentication, access changes, and offboarding
Devices and network
The device, workspace, and network requirements appropriate to the workflow
Operating quality
Documented procedures, human review, exception handling, and escalation practices
Retention and deletion
How long working information is needed and what happens when the work ends
Incident response
Who receives a report, how it is escalated, and how both teams coordinate
Continuity
How absence and surge coverage work through one accountable interface
First-contact boundary
Start with the workflow—not sensitive records.
The first call is for business context: the trigger, volume, current systems, and decisions your team retains. Customer records, identity documents, banking data, and confidential operational files stay out until an approved channel is in place.
See how to startBefore sensitive work enters scope
- Confirm the contract, DPA, purpose, and permitted processing location.
- Define least-privilege access, MFA, logging, retention, and deletion.
- Name client approvals and keep regulated or final decisions client-side.
- Agree on incident handling and service-provider oversight.
Continuity model
Continuity should stay inside the managed service.
The written scope defines the absence and surge route, access handoff, client dependencies, and notification path. The client continues through one named interface instead of coordinating backup staffing directly.
Start with one workflow
Put the access boundary in writing before work begins.
Use the fit call to name systems, permitted data, retained authority, and operating requirements.