{"schema_version":1,"experiment_id":"eoa_inverse_innovation_exp09_archetype_breadth150_20260804","cell_id":"load_leveling_or_demand_smoothing__accounting_auditing","arm":"BREADTH_PROBE_ONE_SHOT","candidate_id":"load_leveling_or_demand_smoothing__accounting_auditing__P1","proposal_index":1,"version":0,"title":"Capacity-Profiled Audit Evidence Release Calendar","problem":"During a period-end external audit, multiple audit workstreams can release prepared-by-client evidence requests to the same accounting personnel in a narrow post-close interval. Some requests are date-locked or urgent, but recurring control documentation, standing data extracts, roll-forward preparation, and other dependency-light work may have wider feasible windows. The temporal concentration can exceed owner and reviewer capacity even when the aggregate workload could fit within the full audit window.","actors":["External-audit engagement manager, who coordinates workstream requests","Audit workstream leads and specialists, who define evidence needs and dependencies","Client controller, who authorizes accounting-team commitments","Client accounting and control owners, who prepare and approve evidence","Audit reviewers, who inspect submissions and issue follow-up requests"],"observable_state":"Request-system timestamps and dependency records show a large share of estimated preparation and approval effort released during the same few close-period days; several requests converge on the same owners; owner queues and audit-review queues peak together or in succession; some earlier or later capacity bands remain uncommitted; and every deferred request can be traced to an explicit future service window rather than an untracked backlog.","consequence":"Concentrated requests can create long owner queues, rushed evidence preparation, delayed audit review, and a compressed interval for resolving exceptions before the reporting deadline.","affected_objective":"Complete sufficient, appropriately reviewed audit evidence within reporting constraints while preserving evidence quality, owner capacity limits, urgent-work responsiveness, and an auditable chain of responsibility.","intervention":"Before the close-period surge, create one dependency-tagged inventory of anticipated evidence requests. Jointly classify each item as date-locked, urgent-bypass, or shiftable within a documented earliest-release and latest-completion window. The engagement manager and controller then apply a capacity-profiled workload intake calendar: shiftable requests receive staggered release dates and reserved owner/reviewer service slots in lower-load intervals, while date-locked and urgent requests retain protected capacity. Every shifted item keeps a named owner, scheduled service path, and latest permissible completion date. At a fixed daily cadence during close, queue depth, uncompleted shifted work, owner concentration, and secondary peaks are reviewed; only unstarted shiftable items may be re-slotted. Smoothing stops when backlog, deadline risk, or protected-work delay crosses a pre-agreed threshold.","structural_mapping":[{"archetype_element":"Bursty or synchronized demand","domain_realization":"Several audit workstreams release evidence requests to shared accounting owners around the same close milestones."},{"archetype_element":"Time-varying constrained capacity","domain_realization":"Accounting owners and audit reviewers have finite preparation, approval, and review capacity that varies across the close and reporting calendar."},{"archetype_element":"Temporally shiftable fraction","domain_realization":"Dependency-light recurring documentation, standing extracts, and preparatory roll-forward work can be assigned within bounded windows; date-locked balances and urgent exceptions cannot."},{"archetype_element":"Temporal distribution policy","domain_realization":"A jointly approved intake calendar assigns staggered release dates and reserved fulfillment and review slots according to owner capacity bands."},{"archetype_element":"Protected urgent or nonshiftable work","domain_realization":"Deadline-critical evidence, suspected misconduct, control failures requiring prompt attention, and genuinely date-locked items bypass smoothing and retain capacity."},{"archetype_element":"Defined path for shifted demand","domain_realization":"Each shifted request retains an owner, release date, service slot, latest completion date, and visible status."},{"archetype_element":"Feedback and peak-migration control","domain_realization":"Daily review of owner queues, reviewer queues, deferred-work completion, and time-band concentration permits bounded re-slotting before a secondary peak forms."}],"mechanism_mapping":[{"mechanism_slug":"workload_intake_calendars","role":"Controls when shiftable audit requests enter active client preparation rather than merely recording a common final due date.","counterfactual_removal":"Without the intake calendar, workstreams can release requests independently, recreating the synchronized demand peak."},{"mechanism_slug":"staggered_start_or_release_times","role":"Moves eligible requests from overloaded intervals into feasible lower-load intervals while retaining the same evidence obligation.","counterfactual_removal":"Without staggered release, reserved capacity may exist but requests still become actionable simultaneously."},{"mechanism_slug":"service_slot_allocation","role":"Reserves paired preparation and audit-review capacity so shifted work has a credible completion path rather than becoming hidden backlog.","counterfactual_removal":"Without paired slots, deferral can relocate requests without ensuring that owners or reviewers will serve them."},{"mechanism_slug":"urgent_work_bypass_rule","role":"Exempts nonshiftable, deadline-critical, or risk-significant work from temporal redistribution.","counterfactual_removal":"Without the bypass rule, smoothing could delay matters whose audit, legal, or reporting consequences make delay unacceptable."}],"causal_chain":["Workstream-level request planning makes anticipated demand, dependencies, owners, and feasible timing windows visible.","Joint classification separates genuinely nonshiftable or urgent requests from work with safe temporal flexibility.","Capacity bands and paired owner-reviewer slots expose lower-pressure intervals capable of absorbing shiftable work.","Staggered release moves eligible demand out of the predicted peak without deleting evidence requirements.","Protected capacity allows urgent and date-locked work to proceed during the close-period peak.","Named slots and latest-completion dates keep shifted requests visible and prevent indefinite deferral.","Daily queue and concentration feedback detects backlog growth, starvation, or peak migration and triggers bounded re-slotting or suspension.","If the problem is temporal concentration rather than aggregate insufficiency, the peak load should decline while completion, evidence standards, and reporting constraints remain preserved."],"baseline":"Each audit workstream maintains its own request list, releases items when its testing becomes ready, and assigns conventional due dates. The client controller expedites conflicts after queues form, while urgent items compete with routine items through reminders and manual escalation. A shared portal may display the backlog, but it does not deliberately redistribute release timing according to capacity.","nearest_rivals":["A centralized evidence-request portal: improves visibility and reconciliation but does not necessarily change when requests enter active preparation.","Priority triage: advances high-risk items within a peak but may leave the peak and total owner overload intact.","Temporary staffing or overtime: expands short-term capacity rather than redistributing shiftable demand over time.","Rolling or interim audit procedures: may move substantive audit work earlier, but the proposed intervention specifically levels request release using item-level feasibility windows and paired capacity slots.","Due-date extension or simple deferral: delays work without allocating it to a capacity-supported service path and can conceal backlog.","Audit scope reduction: removes evidence demand, whereas this intervention retains required requests and changes their timing."],"remaining_contrastive_claim":"The candidate is specifically a temporal load-redistribution policy: it changes when eligible evidence requests become actionable and reserves later preparation and review capacity, while preserving total evidence obligations and bypassing urgent work. A portal, priority queue, release cap, or due-date change alone lacks that combination.","authority_safety":{"decision_authority":"The external-audit engagement partner retains authority over audit scope, evidence sufficiency, risk response, and the reporting timetable; the client controller retains authority over client staff commitments. The engagement manager may operate the calendar only within timing windows jointly approved by those authorities and the responsible workstream leads.","authorized_first_step":"Conduct a read-only retrospective replay of one completed engagement using existing request timestamps, dependencies, owner assignments, and estimated effort; no live request, deadline, scope, staffing assignment, or audit judgment may be changed.","excluded_actions":["Changing audit scope, evidence thresholds, sampling decisions, or professional judgments","Delaying suspected misconduct, urgent control failures, or other risk-significant matters","Moving a request outside its dependency-valid or reporting-compatible window","Committing client personnel or audit specialists without their authorized manager","Suppressing, deleting, or closing requests to improve the apparent peak","Using protected characteristics or organizational power as slot-allocation criteria","Automatically changing live calendars based on the retrospective replay"],"halt_rollback":"For any later pilot, halt new re-slotting and revert unstarted items to their previously approved timing when urgent-work delay appears, any item lacks a feasible completion slot, backlog exceeds the agreed limit, a secondary peak is projected, an evidence dependency proves invalid, or either decision authority withdraws approval. Preserve the full change log and escalate aggregate-capacity shortfalls rather than continuing to smooth them."},"negative_tests":{"strongest_counterevidence":"After separating request effort by owner, dependency, and evidence-availability date, the apparent peak consists predominantly of genuinely date-locked work, or owner capacity is fully occupied across the entire permissible audit window. That would indicate a capacity or process-design problem rather than a shiftable timing problem.","problem_falsifier":"The inferred problem is falsified if timestamped workload reconstruction shows no material temporal concentration relative to owner and reviewer capacity, no underused feasible intervals, or no safely shiftable request fraction.","intervention_falsifier":"The intervention is falsified if a dependency-valid retrospective replay cannot reduce maximum owner-and-reviewer load without increasing missed latest-completion dates, protected-work delay, unresolved shifted backlog, evidence-quality exceptions, or a comparable secondary peak.","risks":["Misclassifying date-locked or urgent evidence as shiftable","Moving preparation earlier than the underlying evidence can validly exist","Hidden backlog behind a smoother release chart","Starvation of deferred requests","Peak migration to another close-period interval or from preparation to audit review","Repeatedly assigning inconvenient slots to less influential client teams","Workstream gaming of urgency labels to obtain preferred capacity","False confidence from aggregate capacity while a specialist owner remains overloaded","Extra planning and estimation work exceeding the operational value of smoothing","Reduced responsiveness when unexpected audit findings require rapid replanning","Perceived auditor interference with client management responsibilities","Exposure of sensitive request metadata through an overly broad shared calendar"]},"next_evidence_step":"Using one completed engagement and only already-authorized records, reconstruct daily request effort by owner and reviewer for a bounded interval spanning the close and reporting period. Have the engagement manager, controller, and relevant workstream leads label each request's earliest valid release, latest acceptable completion, dependencies, urgency status, and uncertainty without changing historical judgments. Replay the proposed staggered-release and paired-slot rules, then compare maximum daily owner load, maximum review load, shifted-item completion, urgent-item timing, secondary peaks, deadline feasibility, and concentration of inconvenient slots across owner groups. Record unclassifiable items and planning effort. This step tests structural fit and operational feasibility only; it does not estimate a live effect size.","prior_art_status":"UNSEARCHED","diversity_from_prior_proposals":"Not assessed against other proposals because runtime isolation forbids inspecting them; this candidate is derived solely from the supplied load-leveling archetype and accounting-and-auditing domain card.","revision_record":{"parent_version":null,"progress_targets_addressed":[],"conceptual_changes":[],"operational_changes":[],"evidence_changes":[],"claim_changes":[]}}