Q: How current is the data the network surfaces?

Every per-region median on `/wbs/ ` and `/benchmarks/ ` is calibrated against the WBS line's last-submitted timestamp — the network rolls a quote out of the active window once it crosses the stale threshold for that line. Each cost guide on `/guides/ ` carries a `lastUpdatedAt` ISO date stamped on the most recent substantive edit, and the per-card caption on the cost-guide index reads "Last updated " so the freshness signal sits next to the guide title.

Question 1

What does AMP-Score actually do with the quote I submit?

Accepted Answer

A submitted quote lands in the AMP-Score network with your vendor alias, your region, and the unit-cost basis on the WBS line you submitted against. The network uses those three signals to compute the per-region aggregate that publishes once enough distinct vendor aliases cross the gate. The network does not sell, rent, or share individual quotes, and there is no outbound contact list, marketing blast, or third-party data buyer downstream of a submission.

Question 2

What's the reciprocity deal — why would I give you a quote when I'm not buying?

Accepted Answer

Reciprocity is the only way the per-region aggregate unlocks. The aggregate is gated on a minimum number of distinct vendor aliases per code per region; without enough submissions, the aggregate stays hidden. Once the gate clears, every contributor on that code reads the same per-region median — the estimator who submitted for switchgear last quarter reads the same MV-switchgear per-region median that a new estimator reads this quarter. The submitter invests one line so the cohort can price one line better.

Question 3

How current is the data the network surfaces?

Accepted Answer

Every per-region median on `/wbs/` and `/benchmarks/` is calibrated against the WBS line's last-submitted timestamp — the network rolls a quote out of the active window once it crosses the stale threshold for that line. Each cost guide on `/guides/` carries a `lastUpdatedAt` ISO date stamped on the most recent substantive edit, and the per-card caption on the cost-guide index reads "Last updated " so the freshness signal sits next to the guide title.

Question 4

How accurate are the network’s benchmark figures, really?

Accepted Answer

Each benchmark aggregate is hand-authored against three concrete checks: the unit-cost basis on the WBS line it prices against, the regional gate (a minimum threshold of distinct vendor aliases per region), and the outlier policy applied at rollup time. An estimate that lands outside the cohort spread is flagged, never silently rolled in — the per-region median on `/wbs/` and `/benchmarks/` reflects quotes that cleared both gates, and the cost guide covers the bucketing the network calibrates against.

Question 5

Is my vendor identity actually anonymous — and what could re-identify a submission?

Accepted Answer

Vendor identity is anonymized at submit time — the network stores a vendor alias derived from your account, not your company name, your contact, or any submittable ID you could round-trip back to a real-world entity. What can re-identify is structural: a region + WBS line + unit-cost basis combo that nobody else in the cohort has logged is, by definition, identifiable to the cohort. The per-region gate exists precisely to suppress that signal — once a few distinct vendor aliases land on the same line, individual quotes blend into the median.

The estimator objection answers the AMP-Score network gives on every first submission.

Looking for the WBS-level deep-dive instead?