A website procurement can ask for a redesign while leaving the final page-template inventory to discovery. That is different from a brief that already specifies every template. The historical ICAT website RFP offers a concrete example. For proposal comparison, the useful question is how an offer addresses the documented discovery task and its assumptions. This article does not report the project’s outcome or audit the current ICAT website.

The buyer locates the inventory in a workshop

The UNOPS ICAT RFP/2024/53978 log, checked on 14 October 2026, says the number of UX pages or templates would come from the initial workshop. The notice lists Germany as beneficiary and a November 2024 deadline. We read the public answer, not the full terms of reference, final inventory or successful proposal.

Name the discovery output

An illustrative scope note should identify what the proposed workshop will produce: for example, a documented inventory and unresolved decisions for the real buyer to review. These are proposed record labels, not claims about this project’s actual deliverables. The applicable solicitation determines the required format, responsibilities and acceptance conditions.

A hypothetical proposal that simply asserts a fixed set of templates without explaining its assumption can look easier to price than a more careful offer. Yet the two may be addressing different tasks. Make the assumed inventory visible rather than treating it as a fact established by the buyer’s public notice.

Separate discovery effort from later implementation assumptions

When reading an actual offer, identify how its discovery work relates to the design and implementation described later. Record whether the later scope is fixed, provisional or dependent on a documented decision. Do not resolve missing scope by inventing page counts, functionality or integrations. A clear question to the buyer is more useful than a confidently filled blank.

A comparison record can preserve the offered scope, the assumption supporting it and the evidence location. If providers use different assumptions, report that difference before comparing headline totals. This article supplies no price model, change fee or universal contractual mechanism.

Check whether the inventory can be reviewed

A useful proposed inventory distinguishes a reusable template from an individual content page. The actual project may define these differently, so keep those definitions attached to the working file. That makes it easier to see whether a provider’s proposal addresses structure or simply counts existing URLs. No current ICAT URL inventory was collected in this research.

The buyer and responsible project team must confirm the applicable scope before a real commitment. Any contractual consequence of changing that scope needs the actual documents and human review. A public clarification alone cannot establish what a provider owes under a signed agreement.

A bounded procurement conclusion

Our editorial recommendation is to make discovery-dependent scope explicit and compare offers on their documented assumptions. The historical case supports that preparation task. It does not prove current site quality, supplier capability, cost completeness or future SEO results. Read current documents before applying this historical example to a new project. No website was changed, no provider contacted and no actual commercial offer evaluated for this article.