A clear path from buyer request to reviewed response package.
One request at a time, with honest review capacity and a separate verifiable package for every buyer.
- Check the current request and review volume
Submit the buyer request type, due date, business email, active-review count, and record inventory. The Platform confirms whether the current request fits the fixed evidence and timing boundaries, then recommends one, two, three, or five review slots based on the volume you report.
- Choose review capacity and pay
One review is US$5,950. Volume packs cover two reviews for US$10,950, three for US$15,950, or five for US$24,950, excluding applicable taxes. Capacity packs are one-time volume purchases, not subscriptions or faster-processing tiers. Card payment activates after completed payment; invoice/PO orders activate after cleared payment.
- Open Buyer Console and identify the request
Confirm your organization, buyer organization, request type, buyer due date, and a stable request reference. A separate buyer request uses a new reference and one capacity slot. Reuse the same reference only when regenerating the same request.
- Upload buyer questions and authorized evidence separately
Use the buyer-request slot for the questionnaire, RFP, spreadsheet, or portal-exported questions. Use the source-records slot for authorized policies, procedures, diagrams, registers, reports, or approved trust materials. Accepted formats include PDF, DOCX, XLSX, PNG, JPG, CSV, JSON, and TXT, with up to 40 source files and 100 MB total per run.
- Generate a separate package for each request
The Platform maps requirements to the uploaded evidence, creates positive statements only where records support them, separates customer-confirmation items from gaps, and produces a request-specific ZIP. A successful new request consumes one slot. A failed generation does not consume a slot.
- Review, verify, and send
Your team reviews the summary, requirement matrix, source-linked statements, evidence binder, gap and confirmation report, forwarding note, manifest, signed receipt, verification instructions, checksums, and downloadable evidence. Your team decides what to send to the buyer. Each included review permits up to two same-request re-runs during the 30-day order window.
Every positive response statement must have a source.
The Platform creates a supported response statement only when an authorized submitted record satisfies a versioned rule in the selected request profile. Each statement identifies the source record and location used by the Platform. When no supplied record supports the requirement, it is marked Not supported by submitted records. When an authorized business owner must confirm a fact that the records do not fully prove, it is marked Customer confirmation required.
Buyer questions, evidence, and generated packages stay separate.
Buyer questionnaires, README files, upload instructions, Fit Check files, and internal-only material are never used as supporting evidence. Authorized evidence marked downloadable is included in that request's ZIP under evidence/downloadable. View-only evidence is referenced without redistributing raw bytes. Each buyer request receives a distinct package identifier, manifest, signed receipt, checksums, due date, and evidence set.
Source records are used for the run, then deleted.
Source uploads are retained for up to 24 hours after the Platform reaches a terminal result for the run. The Platform retains order metadata, request history, manifests, receipts, and generated packages during the 30-day order window. For a same-request re-run, upload revised or additional records; the Platform does not retain the original source uploads for automatic re-use.