Stabilize and Grow Our Close-Reporting Workspace

Our internal close workspace now supports 28 users and roughly 1,600 monthly document events, but growth has exposed slow imports, unclear failure messages, and guidance that no longer matches the current workflow. Within two weeks, we want baseline measurements for import latency, failure rate, support volume, and completion time, followed by fixes to the highest-impact bottlenecks. By week four, the target is a 40% reduction in median import time, fewer than 2% unclassified failures, and updated operator guidance for every changed state. We need someone who can support the existing code and evolve it in measured increments after that initial month, including monitoring, small workflow improvements, and concise release notes. The rate is flexible around the 1,700 scope signal; propose an initial improvement package and a sensible support cadence separately.