Disclosure Assist Help Centre

How the planned customer journey works

A task-by-task guide to starting and completing a future Disclosure Assist project.

The current public website provides information, an estimator and a non-sensitive initial-review form prototype. Production payment, portal, upload and automated-assistant systems are not live yet.

When production services are authorised, the intended journey is:

1. Start Here and complete the public estimator without sending evidence.
2. Select only the service modules you need.
3. Request an Initial Review using non-sensitive scope information.
4. Review the proposed modules, estimate, constraints and intake route.
5. Confirm the versioned initial scope.
6. Complete payment when an authorised production payment route is available.
7. Receive a CaseID and case-specific portal activation.
8. Follow the onboarding and authorised intake instructions.
9. Provide evidence using the agreed online or encrypted physical-media method.
10. Monitor the customer-friendly case status.
11. Complete Decisions & Approvals when customer input is required.
12. Review invoice and payment information.
13. Complete any final authorised payment where applicable.
14. Receive the agreed final handover.

Using the estimator

Understand what shapes the range and what happens after it.

The estimator considers data or document volume, source complexity, selected service modules and urgency where applicable. It produces an indicative workload and cost range, not a fixed quote or final invoice.

Professional work is scoped and priced after reviewing your evidence workload. If the estimated high range exceeds 40 hours, automatic pricing stops and an operator scope review is required. Internal provisional module coefficients are not public pricing promises.

• Do not paste evidence or sensitive case facts
• Check the selected-scope summary
• Request an Initial Review to confirm scope and capacity

Portal overview

What each planned customer section is intended to do.

The future portal is intended to provide authorised case-specific access. The current portal shown on this website is a non-production demonstration only.

• Dashboard — see a concise case summary and actions required
• Cases / Projects — review the authorised project record
• Your Service Scope — see selected and unselected modules
• Upload New Files — follow the authorised evidence-intake route
• Decisions & Approvals — provide attributable customer input
• Invoices & Payments — distinguish estimate, scope, invoices and payment state
• Case Status — understand the current customer-facing stage
• Delivery / Tracking — review handover progress where applicable
• Ask Disclosure Assist AI — obtain automated service and process help
• Account — review authorised account information
• Report a Technical Issue — report access, display, intake or delivery problems

Dashboard and CaseID

Read the planned dashboard and use your case reference safely.

A future Dashboard may show the CaseID, selected service scope, current status, actions required, outstanding Decisions & Approvals, invoice/payment status and delivery status where applicable.

A CaseID identifies a case or project; it is not evidence. You may be asked to quote it when reporting a technical or delivery issue. A synthetic example is DA-DEMO-001. Do not share another customer's CaseID, and portal access remains limited to authorised users.

Providing email or PST evidence

A structured mailbox is usually more useful than thousands of separate exports.

PST and mailbox collections are structured evidence sources. Where appropriate, preserve the original PST or mailbox source instead of unnecessarily exporting thousands of separate emails.

The service may inventory email and attachment relationships, extract supported sender, recipient and date information, and analyse duplicate or version relationships. Large or source-sensitive collections may use the authorised encrypted physical-media route. This is technical document support, not forensic expert work.

Responding to a decision request

Clarify administrative facts without asking the service to decide legal issues.

A request may ask you to clarify a document description, confirm supplied information, resolve an administrative ambiguity, approve additional scope or respond to conflicting source information. Factual conflicts are preserved neutrally; the system does not resolve legal disputes.

Commercial/scope approval is different from a case/document decision. “Would you like to add chronology preparation?” changes commercial scope. “Which description should be used for this item?” records case/document input. Neither allows Disclosure Assist to make legal decisions for you.

Estimate, scope and invoice

Understand the planned billing information without assuming a live provider.

An ESTIMATE is an indicative workload and cost range. CONFIRMED SCOPE records the authorised modules and constraints. An INVOICE requests payment for authorised work under the agreed model, and PAYMENT STATUS records the future transaction state.

ADDITIONAL AUTHORISED WORK requires an approved scope change. FINAL PAYMENT may apply before the agreed handover. The estimator result is not a final invoice, and no production payment provider has been selected.

Final handover methods

The method depends on the agreed project arrangements.

Possible future methods include secure digital handover where authorised, encrypted USB and tracked physical delivery. Where encrypted USB is used, the device is encrypted, delivery is tracked where applicable, and password or access information is supplied separately.

Sensitive operational details are not published on the public website.

Lost, damaged or undelivered media

Use the controlled delivery-issue process and quote your CaseID.

If final media appears lost, damaged or undelivered, use Report a Technical Issue / delivery issue and quote your CaseID. Do not post passwords or security credentials publicly or include them in an insecure message.

Replacement or access reissue remains controlled and is not automatic.

When to report a technical issue

Describe the problem and quote the CaseID when one exists.

Use Report a Technical Issue for a portal-access problem, upload problem, corrupt-file warning, incorrect status display, invoice display problem, delivery/tracking issue or account-access problem. Do not use it to request legal advice.

The future support model is Help Centre + Disclosure Assist AI + Report a Technical Issue, with a formal complaint route to be approved later. No instant or live human response is promised.

Technical issue or formal complaint?

Use the correct route for the kind of concern.

A technical issue is a system or process problem. A formal complaint concerns the service itself. The final formal complaint procedure is not yet published because it remains subject to operator and legal/compliance approval.