Daily help desk editorial capacity: a work-in-progress protocol — September 14 protocol

Methodology and findings

Research question: How does the number of simultaneous article drafts relate to review delay, returned work, and unowned carryover?

Methodology, scope, population, and observation window: Set an observation period and a consistent definition of active editorial work. For every item, record entry time, work type, risk class, source status, owner, reviewer, approval wait, return reason, completion, rejection, and carryover. Compare bands of concurrent work without changing the limit during measurement. This is a proposed operational study for OutsourcedHelpdeskServices.com. It reports no observed customer, ticket, or employee result.

Evidence basis and references: NIST CSF 2.0 and NIST SP 800-53 support accountable, reviewable controls. ICO guidance supports necessary and proportionate personal-data handling. GOV.UK guidance connects measures to user needs. CISA supports secure defaults and named security ownership. These primary sources shape the protocol but provide no local measurements.

Finding to test: The protocol tests an association between work in progress and editorial completion quality. It does not prescribe one universal daily limit.

Operational use: Set a local queue limit from observed review capacity, then include maintenance and retirement work when testing the revised routine. Record observations separately from reviewer judgments and later inferences.

Inference and causal boundaries, with limitations: Work items differ in difficulty, staffing and interruptions can confound the relationship, local results may not transfer, and an association cannot show that draft volume caused delay or defects. Any result would apply only to the declared sample, period, definitions, systems, and available records. It could not establish causality, a universal benchmark, customer satisfaction, legal compliance, or performance outside the sample.

Publication note: Published September 14, 2026. A result report must disclose sample size, exclusions, missing data, denominators, reviewer agreement, protocol changes, and the access date for every reference.

Sources

1. NIST Cybersecurity Framework 2.0 — Primary NIST framework for governing and measuring cybersecurity risk.
2. NIST SP 800-53 Rev. 5 — Primary NIST control catalog covering access, audit records, configuration, and information handling.
3. ICO guidance on data minimisation — Regulator guidance on limiting personal data to what is adequate, relevant, and necessary.
4. GOV.UK Service Manual: measuring the success of your service — Government service guidance connecting performance measures with usability research and user outcomes.
5. CISA Secure by Design — Primary CISA guidance on secure defaults and accountable product security.