Start a cleanup request from the main site. We will send the private status link after intake is logged.
Private Request Status
Check where your cleanup batch stands.
Use the private status link from your cleanup confirmation to see whether the batch is received, in review, or ready to deliver.
Open your status link.
Paste it below to load the live batch. Without the token, the page stays in preview mode so you can still see the portal shape.
The sample-delivery page shows the customer-safe output format this portal is designed to lead toward.
Cleanup request
Paste the private token to load the live batch. Until then, this page shows the tracked request view customers receive.
The intake method we are using for this cleanup request.
The clearest next action currently attached to this request.
Turnaround target loads here.
We will show the current delivery-job posture here.
Delivery confirmation steps appear here once the handoff is sent.
- Package-specific intake guidance loads here.
- Job-scoping checkpoints load here.
Secure upload requirements for this batch load here.
- Requested upload slots load here.
Notification settings for request updates, delivery notices, and document reminders load here.
Email
Portal
Customers can choose where request updates, delivery notices, and document reminders are sent.
Related cleanup jobs appear here when this client has more than one tracked batch.
- Related cleanup jobs load here.
We have your request and the intake path is recorded.
The batch is ready for review once the source paperwork is with us.
We are cleaning up, checking, and correcting the records before delivery.
The finished batch is prepared for handoff and closeout.
We will contact you directly if anything is missing for this batch.
We are confirming the safest intake path for this batch and preparing it for cleanup.
If we need anything else from you, we will ask directly by email so the batch can keep moving.
We keep the batch on one thread and one intake path so the handoff stays calm from start to finish.
- We keep your paperwork tied to one cleanup thread.
- We only ask for more when something materially blocks the batch.
- You get a bookkeeping-ready handoff instead of a raw OCR export.
Our finished batches are delivered as a clean bookkeeping handoff, not a rough OCR dump.
The source packet usually starts as a batch that still needs sorting, review, and missing-item follow-through.
- Source-batch context loads here.
The finished batch is returned as a customer-safe packet that reduces bookkeeping work instead of restarting cleanup.
- Customer-safe delivery proof loads here.
Once the packet is delivered, you can confirm receipt, accept the handoff, or request a revision here without opening a separate support loop.
Customer delivery actions appear here after the handoff is sent.
- Delivery evidence appears here once the handoff is sent.
Teammate identities appear here so uploads, comments, and follow-through do not all collapse into one shared contact.
- Client-side teammates load here.
- Customer-visible request history loads here.
Internal operator notes stay out of this thread. Use the comment box above to keep questions attached to the batch.
- Customer comments and reply-thread updates load here.
The handoff arrives with a direct note explaining what was cleaned up and what still needs attention, if anything.
The finished packet is designed to save bookkeeping time, not create another cleanup pass.
If more paperwork is waiting, the delivery thread becomes the easiest place to start the next round cleanly.
We keep intake, updates, and delivery attached to one cleanup thread so the batch does not splinter across random messages or uploads.
When evidence is weak, the handoff tells you that clearly instead of hiding it inside a rough export.
The batch is prepared to shorten the next accounting step, not push another cleanup pass back onto your side.
If dates, file handoff, or delivery needs changed, use the original cleanup email thread so the context stays attached to this batch.