Customer context and review rules
Customer-approved context increases relevance while review states preserve authority.
Reference version 1.1 · Updated September 4, 2026
Configured context
- Product and application libraries: SKUs, approved products, technical data, use cases, and competitor context.
- Engineering references and methods: approved calculations, guidance, limits, and reference documents.
- Discovery and qualification: Query Architect strategies, markets, project filters, pursue/review/reject rules, and exclusions.
- Operating governance: roles, permissions, quantity accuracy profiles, approval gates, and downstream handoffs.
Change control
Treat changes to product data, review methods, qualification rules, accuracy profiles, and permissions as controlled configuration. Record the version used for a material report so later reviewers can reconstruct the result.
Detail: four configuration pillars
- Product and application knowledge: SKUs, approved products, technical data sheets, competitor matrices, applications, and approved-equal context.
- Engineering and takeoff rules: scale, geometry, waste, overlap, conversion, structural, hydraulic, soil, material and discipline-specific review methods.
- Opportunity strategy: direct specifications, competitors, alternate language, design conditions, exclusions and scoring thresholds.
- Ways of working: accuracy profile, named reviewers, permissions, report expectations, approval gates and integration destinations.
Need help applying this page to an evaluation?Ask a product question

