Find the work hidden between the screens

A portal estimate can account for every visible page and still omit the effort needed to make the service operable. Look at what must happen before, between and after the screens.

Content preparation can become the critical path

A fictional consultancy may have ten service pages but forty PDF versions, each with uncertain approval. Importing those files does not resolve which remain valid. Inventory, review and retirement decisions need owners, even if the new content system is straightforward.

Language work also extends beyond page bodies. Errors, document names, confirmations and support instructions may be needed to complete the journey. Establish the actual coverage and review arrangement rather than treating translation as a percentage added after design.

Integrations have operating costs

Provider accounts, interface access, testing arrangements and future changes can affect the scope. Ask what staff will do with rejected or uncertain operations. A connection that transfers successful examples but provides no reconciliation can move labour into a more difficult exception process.

Transition and recovery need time

Moving records may require matching, cleaning, comparison and a period when two systems coexist. Decide which system receives changes during that period. Account ownership, operator training and recovery rehearsal are deliverables when the business depends on them.

Compare proposals by these responsibilities and acceptance evidence, not by page count alone. The scope guide provides the commercial questions; the dependency worksheet helps identify which answer must arrive before the estimate can become firm.