A controlled path from operating question to dependable practice.

Nardux uses defined stages, decision gates and shared responsibilities to turn a Trust & Safety need into a scope both teams can understand and support.

Progress only when the next stage is supportable.

Each stage produces a decision or operating artifact. Open risks remain visible rather than being hidden behind a launch date.

  1. 01

    Discovery

    Understand the product, users, surfaces, objectives, stakeholders and constraints.

  2. 02

    Assessment

    Review policy, risk, workflow, access, capacity, quality and reporting readiness.

  3. 03

    Implementation

    Define decisions, roles, tools, escalation, training, quality and controls.

  4. 04

    Moderation & Automation

    Operate the approved scope; use automation only for agreed bounded assistance.

  5. 05

    Reporting & Improvement

    Review measures, appeals, ambiguities, risks and owned corrective actions.

Standardize the controls. Adapt the operating detail.

A common control structure helps each engagement remain reviewable as the queue, team or tooling changes. The completed records and approvals still belong to the specific client scope.

  1. CONTROL 01

    Scope & service design

    Define accepted queues, content, languages, hours, decisions, exclusions, assumptions and entry or exit criteria.

    Record: approved scope and service measures
  2. CONTROL 02

    Policy & authority

    Connect policy versions to reason codes, actions, exceptions, escalation owners and final decision authority.

    Record: policy and authority map
  3. CONTROL 03

    People & readiness

    Confirm role suitability, training, calibration, access need, content exposure, support and stop conditions.

    Record: readiness and calibration evidence
  4. CONTROL 04

    Access & data

    Approve identities, devices, systems, data flow, least privilege, client separation, retention and incident contacts.

    Record: access and data-handling plan
  5. CONTROL 05

    Quality & reporting

    Define samples, critical errors, appeals, measures, limitations, cadence, action owners and verification.

    Record: quality and reporting specification
  6. CONTROL 06

    Continuity & exit

    Set capacity thresholds, pause and fallback paths, handover, access removal, record return and deletion steps.

    Record: continuity and exit plan

Inspect the structure before an engagement. The downloadable register uses fictional examples and is not a contract, completed readiness assessment, service-level commitment or customer result.

Download fictional control register

Authority stays visible across both teams.

This example responsibility map is refined in the statement of work. It is not a substitute for the signed engagement terms.

Operating areaClient ownsNardux owns within scopeShared decision
PolicyPlatform rules and final approvalUsable guidance and ambiguity recordsInterpretation and version rollout
DecisionsEnforcement authority and exceptionsAuthorized review and rationaleDifficult-case escalation
Access and dataApproved systems and instructionsLeast-use handling and access disciplineData flow, retention and incident response
QualityAccepted rubric and critical errorsSampling, calibration and findingsCorrective action and re-review
ContinuityBusiness and emergency contactsCapacity limits and service fallbackChange, pause and exit decisions

Uncertainty leaves the ordinary queue.

POLICY & QUALITY

Decision ambiguity

  • Conflicting or missing policy guidance
  • Potential critical-quality error
  • Appeal or second-review trigger
  • Repeated disagreement pattern
  • Possible training or tooling gap
OPERATIONS & DATA

Control interruption

  • Queue, tool or access failure
  • Unexpected data or permissions
  • Coverage or capacity exception
  • Unapproved workflow change
  • Privacy or security concern
SPECIALIST / EMERGENCY

Outside ordinary authority

  • Credible imminent-harm signal
  • Potentially unlawful instructions
  • Prohibited or specialist content
  • Legal or law-enforcement request
  • Worker-safety stop condition

Changes are versioned before they become instructions.

A material change records the requester, reason, risk, old and new state, effective time, approvers, affected queues and data, testing, training, rollback and verification owner.

Emergency changes can move faster, but they still require a record and retrospective review. Historical cases are re-reviewed only when the approved change decision requires it.

A professional engagement includes a controlled ending.

Continuity, access and unresolved work are addressed whether the engagement expands, changes provider or stops.

01

Reconcile work

Confirm final intake, remaining cases, appeals, incidents, ambiguities and action owners.

02

Transfer responsibility

Return approved records and open work to named client owners without unnecessary data.

03

Remove access

Revoke accounts, tokens, groups and system permissions according to the agreed process.

04

Close with evidence

Complete approved return/deletion steps, final reporting, commercial closure and lessons learned.

Questions about beginning and changing the work.

Does every engagement use all five stages?

The logic remains, but the depth varies. A well-defined advisory task may move quickly; a production moderation scope requires stronger policy, access, escalation, quality and capacity gates.

Who makes final policy decisions?

The client owns its platform rules, enforcement authority and final policy approval. Nardux can translate approved policy into operating guidance and record questions for client decision.

Can scope change after launch?

Yes, through change control. New content, countries, languages, tools, targets or automation can change risk, cost, training, privacy and capacity requirements and therefore require review.

What happens if a readiness gate fails?

The next stage pauses, narrows or returns to remediation. If the request remains outside approved capability or safe conditions, Nardux may refer or decline it.

Start with the decisions your workflow must support.

Share the product, current process, desired outcome and the people who own policy, escalation and implementation.

Review an Engagement