Buyer data requirements
A static guide for qualified buyers preparing module review context without forms, file upload, backend storage or live client data on the public site.
General data-review boundary
Synthetic-preview reminder
Module-by-module data object table
Use this table to prepare a qualified email. Do not submit data through the website.
| Module | Public status | Required objects | Optional objects | Prohibited/sensitive objects | Validation responsibility | Missing-data behavior | Integration assumptions |
|---|---|---|---|---|---|---|---|
| Project Risk Intelligence | Review-ready source-package offer | Risk register; Cost exposure records; Schedule pressure indicators; Procurement status updates; Issue records | Risk owners and update cadence; Mitigation or action notes; Project-control reporting labels; Cost-code or work-package references | No live client data on the public site.; No personal, payroll, bank, payment, credential or tax records.; No privileged legal material, confidential contract terms or dispute strategy before an appropriate agreement/NDA.; No production system credentials, API secrets, private repository links or source-package material. | Buyer validates risk taxonomy, field meaning, owner names, update cadence and whether synthetic or approved sample structures are acceptable. | Missing cost, schedule, procurement or issue signals narrows the review to available risk-register objects and should be called out before scoping. | Project controls and PMO reporting platforms; Construction ERP project modules; Risk registers and issue logs; Cost exposure and forecasting workflows; Schedule and procurement dashboards |
| Change Order & Claims Intelligence Pro | Review-ready source-package offer | Change events; Notice records; Evidence references; Commercial impact entries; Open actions | Event categories and owners; Document-control references; Approval or review states; Contract workflow labels | No live client data on the public site.; No personal, payroll, bank, payment, credential or tax records.; No privileged legal material, confidential contract terms or dispute strategy before an appropriate agreement/NDA.; No production system credentials, API secrets, private repository links or source-package material. | Buyer validates event status, notice fields, evidence-reference permissions and commercial-impact definitions. | Missing evidence, notices or impact fields limits review to workflow structure and open-action handling without claim-readiness depth. | Contract management platforms; Defects and issues management platforms; Construction ERP commercial modules; Document control and evidence registers; Project controls and commercial reporting workflows; Integrator delivery environments |
| Subcontractor Cost Control & Margin Leakage | Review-ready source-package offer | Subcontract package records; Commitments; Variation and claim indicators; Margin exposure records; Package status | Budget and award values; Payment or certification status; Allowance movement notes; Cost-code or package-owner references | No live client data on the public site.; No personal, payroll, bank, payment, credential or tax records.; No privileged legal material, confidential contract terms or dispute strategy before an appropriate agreement/NDA.; No production system credentials, API secrets, private repository links or source-package material. | Buyer validates package identity, commitment fields, variation labels, exposure definitions and permitted commercial-control context. | Missing commitments, package status or variation indicators reduces review to package structure and should not be treated as margin-exposure validation. | Construction ERP commercial modules; Cost management platforms; Subcontract administration workflows; Payment and certification review processes; Commercial reporting dashboards |
| BOQ / Cost Intelligence | Available under proposal | BOQ lines; Quantity units; Cost categories; Estimate references; Budget and ERP handoff fields | Cost-code mapping notes; ERP handoff assumptions; Estimate review states; Buyer-specific unit conventions | No live client data on the public site.; No personal, payroll, bank, payment, credential or tax records.; No privileged legal material, confidential contract terms or dispute strategy before an appropriate agreement/NDA.; No production system credentials, API secrets, private repository links or source-package material. | Buyer validates BOQ structure, units, category assumptions and whether scoping can proceed without confidential pricing material. | Missing BOQ structure, unit conventions or ERP handoff assumptions keeps the route at proposal-stage scoping only. | Construction ERP cost-code structures; Estimating and quantity surveying systems; Cost management platforms; Budget review workflows; Integrator delivery environments |
| Tender Comparison & Award | Available under proposal | Bidder submissions; Package scope; Clarification notes; Commercial scores; Approval and audit trail references | Clarification workflow labels; Commercial scoring support assumptions; Governance or approval-stage references; Procurement audit-trail expectations | No live client data on the public site.; No personal, payroll, bank, payment, credential or tax records.; No privileged legal material, confidential contract terms or dispute strategy before an appropriate agreement/NDA.; No production system credentials, API secrets, private repository links or source-package material. | Buyer validates bidder data permissions, package scope, scoring governance and procurement-review boundaries. | Missing bidder submissions, package scope or governance assumptions keeps the route at proposal-stage scoping only. | Procurement software platforms; Construction PM systems; ERP procurement modules; Commercial scoring workflows; Document control and clarification registers |
ML-readiness data table
Use this table to assess whether a module has enough buyer-approved data for ML-assisted candidate review. It does not create an upload path or validated ML claim.
| Module | Maturity | Required labels by module | Optional labels by module | Sensitive/prohibited data notes | Buyer validation responsibility |
|---|---|---|---|---|---|
| Project Risk Intelligence | Review-ready module. ML/data readiness can be reviewed for deterministic risk scoring, signals and candidate anomaly or forecasting support. | Risk state or severity labels.; Overrun, delay, claim or quality outcome labels when buyer wants evaluated ML-assisted review.; Snapshot date and time horizon labels. | Mitigation status.; Escalation or owner response.; Procurement delay category.; Schedule pressure band. | No live client data collection through the public site.; Use synthetic or buyer-approved sample structures until qualification, agreement and NDA where appropriate.; Do not send personal, payroll, bank, payment, credential, tax or privileged legal material through the public site.; Do not send production credentials, API secrets, private repository links or source-package material. | Buyer validates project snapshots, signal definitions, target outcome labels, time horizon, sampling design and false-positive/false-negative tolerance. |
| Change Order & Claims Intelligence Pro | Claims Pro AI evaluation path. ML/data readiness can be reviewed for contract clause extraction, change event narrative structuring, analogous case semantic search, methodology validation and service-mode evaluation scope without legal advice or production validation claims. | Clause type labels for extraction evaluation.; Citation verification labels against source documents.; Change-event category labels.; Evidence completeness or missing-evidence labels.; Accepted, rejected or partially accepted outcome labels when buyer wants evaluated ML-assisted review. | Disputed event flag.; Notice timeliness label.; Evidence type label.; Analogous case relevance judgment for Recall@K review; buyer-side validation required.; Narrative parsing agreement label; buyer-side validation required.; Recovery amount band if buyer is willing to evaluate it. | No live client data collection through the public site.; Use synthetic or buyer-approved sample structures until qualification, agreement and NDA where appropriate.; Do not send personal, payroll, bank, payment, credential, tax or privileged legal material through the public site.; Do not send production credentials, API secrets, private repository links or source-package material.; Do not send privileged legal material, dispute strategy or confidential settlement material through the public site. | Buyer validates extracted clauses against source documents, citation references, golden cases, agreed evaluation cases, evidence permissions, claim outcome semantics, accepted/rejected labels, disputed-event handling, service-mode evaluation scope and any optional recovery amount evaluation. |
| Subcontractor Cost Control & Margin Leakage | Review-ready module. ML/data readiness can be reviewed for package history, margin exposure signals and candidate anomaly or similarity support. | Package status labels.; Final margin outcome labels when buyer wants evaluated ML-assisted review.; Cost event or variation category labels. | Unapproved extras materialized label.; Payment delay label.; Progress or certification stage.; Commercial-control escalation label. | No live client data collection through the public site.; Use synthetic or buyer-approved sample structures until qualification, agreement and NDA where appropriate.; Do not send personal, payroll, bank, payment, credential, tax or privileged legal material through the public site.; Do not send production credentials, API secrets, private repository links or source-package material. | Buyer validates package identity, commitment history, cost event definitions, progress/certification/payment snapshots and final margin outcome labels. |
| BOQ / Cost Intelligence | Proposal-stage only. ML/data readiness is limited to item normalization and item similarity scoping. | Item category or normalization labels for proposal-stage scoping.; Unit convention labels.; Buyer-approved cost category mapping labels. | Item similarity examples.; ERP handoff category.; Estimate review state.; Price anomaly review flag if buyer permits pricing context. | No live client data collection through the public site.; Use synthetic or buyer-approved sample structures until qualification, agreement and NDA where appropriate.; Do not send personal, payroll, bank, payment, credential, tax or privileged legal material through the public site.; Do not send production credentials, API secrets, private repository links or source-package material.; Confidential pricing material should remain excluded before NDA unless the buyer explicitly approves scoped review. | Buyer validates BOQ structure, item normalization labels, unit conventions, pricing sensitivity and proposal-stage scope before deeper discussion. |
| Tender Comparison & Award | Proposal-stage only. ML/data readiness is limited to offer normalization and offer comparison scoping. | Offer normalization labels for proposal-stage scoping.; Exclusion or qualification labels.; Package scope and comparability labels. | Clarification status.; Commercial scoring support category.; Approval stage.; Audit-trail review state. | No live client data collection through the public site.; Use synthetic or buyer-approved sample structures until qualification, agreement and NDA where appropriate.; Do not send personal, payroll, bank, payment, credential, tax or privileged legal material through the public site.; Do not send production credentials, API secrets, private repository links or source-package material.; Bidder-identifying or commercially sensitive tender material should remain excluded before NDA unless the buyer explicitly approves scoped review. | Buyer validates bidder permissions, offer comparison labels, exclusion/qualification semantics, procurement governance and proposal-stage scope before deeper discussion. |
Claims Pro AI data
Change Order & Claims Intelligence Pro has an evidence-gated Claims Pro AI evaluation path. Public pages do not collect files, contract data, keys or live client data.
Claims Pro AI block
Review-ready data preparation
The required objects below come from the existing public module routes and buyer questionnaire prompts.
BOQ / Tender
BOQ and Tender data objects help scope buyer assumptions; they do not make either module review-ready.
Proposal-stage boundary
Proposal-stage scoping only.
Scoping objects
BOQ lines; Quantity units; Cost categories; Estimate references; Budget and ERP handoff fields
Missing-data behavior
Missing BOQ structure, unit conventions or ERP handoff assumptions keeps the route at proposal-stage scoping only.
Proposal-stage scoping only.
Scoping objects
Bidder submissions; Package scope; Clarification notes; Commercial scores; Approval and audit trail references
Missing-data behavior
Missing bidder submissions, package scope or governance assumptions keeps the route at proposal-stage scoping only.
Module ML/data label readiness
Review-ready modules can discuss buyer-approved historical labels. BOQ and Tender remain proposal-stage only for normalization and comparison scoping.
Review-ready module. ML/data readiness can be reviewed for deterministic risk scoring, signals and candidate anomaly or forecasting support.
Required labels
Risk state or severity labels.; Overrun, delay, claim or quality outcome labels when buyer wants evaluated ML-assisted review.; Snapshot date and time horizon labels.
Optional labels
Mitigation status.; Escalation or owner response.; Procurement delay category.; Schedule pressure band.
Buyer validation responsibility
Buyer validates project snapshots, signal definitions, target outcome labels, time horizon, sampling design and false-positive/false-negative tolerance.
Claims Pro AI evaluation path. ML/data readiness can be reviewed for contract clause extraction, change event narrative structuring, analogous case semantic search, methodology validation and service-mode evaluation scope without legal advice or production validation claims.
Required labels
Clause type labels for extraction evaluation.; Citation verification labels against source documents.; Change-event category labels.; Evidence completeness or missing-evidence labels.; Accepted, rejected or partially accepted outcome labels when buyer wants evaluated ML-assisted review.
Optional labels
Disputed event flag.; Notice timeliness label.; Evidence type label.; Analogous case relevance judgment for Recall@K review; buyer-side validation required.; Narrative parsing agreement label; buyer-side validation required.; Recovery amount band if buyer is willing to evaluate it.
Buyer validation responsibility
Buyer validates extracted clauses against source documents, citation references, golden cases, agreed evaluation cases, evidence permissions, claim outcome semantics, accepted/rejected labels, disputed-event handling, service-mode evaluation scope and any optional recovery amount evaluation.
Review-ready module. ML/data readiness can be reviewed for package history, margin exposure signals and candidate anomaly or similarity support.
Required labels
Package status labels.; Final margin outcome labels when buyer wants evaluated ML-assisted review.; Cost event or variation category labels.
Optional labels
Unapproved extras materialized label.; Payment delay label.; Progress or certification stage.; Commercial-control escalation label.
Buyer validation responsibility
Buyer validates package identity, commitment history, cost event definitions, progress/certification/payment snapshots and final margin outcome labels.
Proposal-stage only. ML/data readiness is limited to item normalization and item similarity scoping.
Required labels
Item category or normalization labels for proposal-stage scoping.; Unit convention labels.; Buyer-approved cost category mapping labels.
Optional labels
Item similarity examples.; ERP handoff category.; Estimate review state.; Price anomaly review flag if buyer permits pricing context.
Buyer validation responsibility
Buyer validates BOQ structure, item normalization labels, unit conventions, pricing sensitivity and proposal-stage scope before deeper discussion.
Proposal-stage only. ML/data readiness is limited to offer normalization and offer comparison scoping.
Required labels
Offer normalization labels for proposal-stage scoping.; Exclusion or qualification labels.; Package scope and comparability labels.
Optional labels
Clarification status.; Commercial scoring support category.; Approval stage.; Audit-trail review state.
Buyer validation responsibility
Buyer validates bidder permissions, offer comparison labels, exclusion/qualification semantics, procurement governance and proposal-stage scope before deeper discussion.
Validation responsibility
Integration assumptions
Intelligence data readiness
Use the Intelligence Layer and ML readiness pages when data objects may support anomaly detection, similarity search, classification, ranking or retrieval-assisted review.
ML-ready boundary
Next step
Share module interest, available objects, missing objects, sensitive-data boundaries, validation owner and integration assumptions before requesting deeper review.
Direct line
labs@nivorqa.comUse email for review-pack requests, module fit questions, licensing conversations and pilot scoping.