Trial and prepaid processing
Understand review credits, processing limits, and purchase status.
Trial allowance
An eligible new workspace receives a trial limited to 30 days, 10 completed packet reviews, and $50 of processing, whichever is reached first. The clock starts with the first admitted processing operation, which can include file preprocessing before a report. A trial belongs to the workspace and its original creator; transferring ownership, creating another key, or deleting files does not replenish it.
One trial packet review can run at a time. The trial also admits at most 120 source-file versions totaling 1,200 MiB. Per-file and packet limits still apply: up to 30 MiB per file, 12 files and 120 MiB per batch, and 250 pages per PDF. An archive container and each expanded source entry count toward the allowances. Resuming the same accepted entry does not count it again; deleting it does not restore the allowance. The service-wide trial processing limit can temporarily prevent new work even when your own allowance remains.
An allowance applies only to formats supported by your workspace. If it is limited to PDF review, use standalone PDFs: images, ZIP archives, and native CAD files are refused, including when reusing saved sources. The archive allowance described above does not grant permission to process an archive. A PDF-only review does not waive the utility's required evidence. See supported uploads.
How reviews count
A logical packet review reserves one credit before processing and consumes it when a usable report is saved. Its preprocessing, document checks, platform retries, and automatic follow-up checks share that review operation for the same source files, project inputs, and requirement version. A new deliberate review or a changed review snapshot can use another credit. Saving a new usable report still consumes a credit when cached evidence avoids new provider work; reading an existing report does not. Utility screening uses the reviewing utility workspace's allowance and the exact submitted package, independently of the developer's private review.
A platform failure without a usable report releases the review credit, while processing already performed still counts. If a provider's result is uncertain, the reserved processing allowance stays held until it can be reconciled. Repeatedly restarting or uploading the same file does not resolve that uncertainty. Contact support if work remains blocked.
New processing stops when an allowance expires or is exhausted. Existing authorized reads and exports remain available, and expiry does not delete your files. Unsupported processing paths are unavailable in this rollout, including native DWG processing, unrestricted assistant chat, generic jobs, and legacy digitization. Use supported packet intake and review. Purchasing capacity does not change file support or utility coverage.
Prepaid packs
When purchases are enabled, a workspace Owner or Admin opens Billing on the website. Select your organization, review the offered pack and its limits, then choose Continue to secure checkout. Current pack quantities and prices appear there. There is no subscription or automatic refill. Purchases are a website workflow.
Returning from checkout does not confirm payment. Payment pending means verification is still underway; Credits added confirms that processing capacity was recorded. Recent organization purchases appear in the same page. Billing shows packs and purchase receipts; a combined trial/prepaid balance display is not yet available. If purchases are unavailable, no checkout starts.
A refund, dispute, or inconsistent payment record can place the remaining capacity on hold for review. Usage already consumed remains in the history. A changed dispute or refund status does not automatically replenish or release capacity. Contact support for reconciliation.