The portal should distinguish requested, received and reviewed documents by customer and period; professional analysis remains the firm's responsibility.
Index
Marking a document submitted does not mean it is usable; incomplete files return to customers and create an invisible queue.
The rule that changes the scope
The portal should distinguish requested, received and reviewed documents by customer and period; professional analysis remains the firm's responsibility.
A shared folder supports uploads; custom software organizes period-specific outstanding items and returns with clear reasons.
The outstanding list should reflect what was requested for that period rather than a standard folder for every customer. One file may answer several requests, but reviewing one should not close others by inference. Define customer-specific access before submission and replacement after review. The portal organizes document exchange; it must not promise to eliminate the firm's technical assessment or professional obligations merely because every requested file was uploaded.
Specify operational deliverables
- Associate each request with its reporting period and the document expected by its owner.
- Separate a received file from a file accepted after the firm's review.
- Keep replacements and comments without mixing documents from different periods.
Test the exception before acceptance
In a hypothetical scenario, a customer uploads a previous-period file; the portal must keep the request open and explain what needs correcting.
Reference for assessing scope
NN/g: writing task scenarios for usability testing
Prepare your project with Quantum9
Bring an outstanding-document list and a submission that had to return to the customer.