A controlled moderation workflow, not a black box.

Nardux helps define and support human review for approved content queues, with clear policy authority, escalation, quality checks and reporting around the work.

Define exactly what enters the queue.

ENGAGEMENT MAY COVER

Approved content surfaces

  • Posts, comments and user reports
  • Profiles, usernames and listings
  • Community or marketplace conversations
  • Images or recorded video when readiness is confirmed
  • Spam, scams and abuse patterns under client policy
BEFORE PRODUCTION

Readiness requirements

  • Current policy and enforcement authority
  • Accepted and excluded categories
  • Named policy, safety and emergency owners
  • Approved tools, accounts and data handling
  • Training, calibration and go-live sign-off
NOT ASSUMED

Important limitations

  • No promise of zero harm or zero error
  • No unsupported 24/7 or unlimited-volume coverage
  • No voice, livestream or specialist high-risk work without separate approval
  • No independent legal or emergency action unless expressly authorized
  • No unapproved third-party AI use with client or user data

What we need to design the work responsibly.

Discovery can begin with business context. Production access waits until the operating and data requirements are approved.

Product and user journeyContent formats and channelsPolicy versions and examplesVolume, peaks and backlogCoverage and response needsAction and escalation authorityTooling and access requirementsQuality and reporting goals

Move from sample cases to approved operations.

  1. 01

    Define

    Agree surfaces, categories, volumes, actions, exclusions and owners.

  2. 02

    Prepare

    Turn policy into queue guidance, reasons, escalation and quality rules.

  3. 03

    Calibrate

    Train and test using synthetic or appropriately controlled cases.

  4. 04

    Operate

    Review only within authorized scope and document decisions and exceptions.

  5. 05

    Improve

    Report results, resolve ambiguity and approve changes through a controlled loop.

Evidence your team can use.

The exact set depends on scope; a controlled pilot typically combines decision work with the records needed to evaluate continuation.

01

Approved decisions or recommendations

Policy category, action and rationale fields within delegated authority.

02

Escalation and ambiguity log

Cases that exceeded authority, exposed missing guidance or required client input.

03

Operations and quality report

Defined volumes, outcomes, sample method, findings, limitations and actions.

04

Pilot recommendation

Findings on capacity, process, tooling, policy and readiness for the next stage.

Measure the workflow, not only speed.

A quality plan can combine random, risk-based, new-reviewer, changed-policy, appealed and anomaly-driven samples. Reporting may include reviewed volume, actions, backlog, response performance, sample definitions, critical errors, escalations and corrective actions.

Average handle time is treated as diagnostic context, not a standalone target. Complexity, safety, accuracy and system conditions matter.

Questions before a pilot.

Can Nardux start with one channel or queue?

Yes. A narrow queue, defined channel or limited period is often a better starting point than broad production scope. Volume, coverage and category limits still need to be explicit.

Can automation make moderation decisions?

Automation may assist approved routing, prioritization or repetitive workflow steps after review. Consequential decision authority, monitoring and human oversight must be agreed; automation is not assumed.

How are difficult cases handled?

Cases with insufficient evidence, policy conflict, excluded content or risk beyond reviewer authority are paused and routed to the named escalation path rather than guessed.

Do you guarantee an accuracy percentage?

No. Quality measures require an agreed rubric, sample design, period and context. We do not publish or promise unsupported universal accuracy figures.

Test the workflow before expanding it.

Share business context, expected surfaces, approximate volume and timing. Do not send case evidence through the public form.

Scope a Controlled Pilot