DocAgent & Back-office Copilot
A design case study from the DocAgent demo: intake, extraction, document reconciliation, exception handling and traceable approval.
DocAgent has an existing demo UI; the role-based workspace/apps and the new assistant are proposed prototypes.
Sample UIs use synthetic data. Existing DocAgent screenshots have record/partner/figure data redacted. No real customer or employee results are used for illustration.
Intake
Attach documents to a file code; record source and version.
Extraction
Normalise fields while keeping links to the original document.
Reconciliation
Cross-check and queue discrepancies.
Verification
The owner checks the basis, adds documents or explains.
Approval
The manager approves within scope; data becomes eligible for the next step.
See where the work gets done.
DocAgent: operations centre
Captured from the existing DocAgent demo. Record and partner data redacted; UI structure and labels kept.
DocAgent: Back-office Copilot
Captured from the existing DocAgent demo. Record and partner data redacted; UI structure and labels kept.
DocAgent: audit trail & permissions
Captured from the existing DocAgent demo. Record and partner data redacted; UI structure and labels kept.
Document Operations workspace
Prototype dashboard with simulated records; states and process follow the solution design.
Open the sample UI ↗
Document Operations assistant
What does not match in the document set? Sourced simulated scenario; no LLM call.
Open the sample UI ↗Every role has a clear workflow.
The apps focus on frequent tasks. In production they share the APIs, file codes, permission policy and history of the business platform.
INTAKE & TRACKINGDocument specialist
- Confirm input documents belong to the right file.
- Mark version and readability as checked.
- Forward discrepancies to the reviewer.
RECONCILE & VERIFYReviewer
- Read data fields and source documents.
- Record the basis for the quantity gap.
- Send the review result to the manager.
APPROVE & TRACEOperations manager
- Read the file and review result before approving.
- Approve or return with a request for additions.
- Track history and accountability.
Module mapping & permission limits
| Role | Module | Scope |
|---|---|---|
| Document specialist | File → Document set → Exceptions | Assigned files only; cannot close discrepancies or transmit declarations. |
| Reviewer | Reconciliation matrix → Exceptions → Review result | Records verified checks; cannot submit official data. |
| Operations manager | Approval queue → Agent permissions → Audit log | Approves within delegated scope. Official signing/submission is a separate step. |
From input to an evidence-based decision.
The first role completes the checklist and submits evidence; the next role records an evidence-based result; the approver confirms or returns with a reason. The sample session logs every step.
No digital signing, no declaration transmission, no changes to external business systems.
Sample state is stored in the same browser, separated per solution. There is no authentication, multi-user backend, cross-device sync, push or LLM connection. Those must be built and accepted before real operation.
Sources to compare, not automatic conclusions.
INV-DEMO v1
Illustrative quantity: 120 units; not a real invoice.
PACK-DEMO v1
Illustrative quantity: 118 units; the owner must reconcile.
RULE-DEMO-01
Quantity gaps need an explanation before approval.
INV-DEMO shows 120 units, PACK-DEMO shows 118: a 2-unit gap. Versions must be compared and explained before approval. The assistant does not pick the correct number or submit official data.
DEMO sources are synthetic data for simulation. Real business documents must be collected with usage rights, versioned and quality-checked.
Pilot & acceptance roadmap
- Pick one document type, an answer key and a baseline.
- Configure extraction, rules and the exception flow.
- Run reconciliation alongside specialists; check permissions and traces.
- Accept on new files, then extend integration.
Conditions to verify
- Quantity gaps are blocked before approval.
- Every field has a source or is flagged as unverified.
- No data leaves automatically; every action has a person and a reason.
- Per-file permissions, versioning and duplicate-submission errors are tested.
Agree scope, baseline, sample size, confirming person and operating responsibility before the pilot. Demos do not replace acceptance results or performance commitments.
Reference direction: CTC Smart Tech internal DocAgent demo. Details are compiled from existing documents and source code; new UIs are clearly marked as proposed designs.