Managed service plan: Managed Contract Inclusion Matrix

Every row is a verbatim sentence read from the named source's own page through our fetch service on the date shown, hash-pinned to the stored read (the sha of the page's visible text; the raw page is mirrored to R2).

2 of the 3 named sources that could be read published a usable figure; 1 published none and are recorded as not published, never filled in; 1 could not be read (blocked, dead or unreachable) and count nowhere.

The headline figures (median, minimum, maximum, quartiles) are over ONE figure per source in USD (a source's median where its page yielded several accepted sentences), so N counts sources, never sentences; 17 candidate sentence(s) were refused by a reviewer with the reason recorded.

The fuller derivation this dataset is chartered to grow into (not yet what the figures above are; they are each source's own published figure as read): Each provider's own plan and service pages are read for a fixed list of twenty inclusions (help desk hours, after-hours cover, patching, monitoring, backup, backup testing, endpoint security, email security, onsite visits, vCIO time, procurement, licences, projects, onboarding, offboarding, documentation, reporting, compliance work, hardware, response SLA).

Per inclusion we derive how many providers put it in the base contract, how many bill it extra, and how many do not say.

The last of the three is the number this market never publishes and the one a buyer needs most, so it is carried in every rendering rather than dropped as missing data.

17 candidate sentences on these pages were refused by a reviewer; each refusal and its reason is recorded in the review ledger.