Estimate the publication work that the project actually includes

A page count is useful, but it does not describe a multilingual publication project on its own. Ten pages may use one repeatable, approved structure. Another ten may require different edition relationships, institutional review, file preparation and a connection to a system controlled by someone else.

We discuss the evidence and responsibilities before estimating the work. The scope should explain what the agreed price covers and what would require a further decision.

Content structure and preparation

Count the types of material as well as individual records. An organisation page, a programme, a publication issue and a directory entry each need different facts. Identify which content is already approved, which needs editing and which has not yet been supplied.

Language scope also needs more detail than the number of languages. Record the full editions, summaries, interface labels and attachments included. Review of specialist terminology or a partner's official name may involve people outside the development team. Their availability affects the delivery plan even when the technical template is ready.

Existing systems and public routes

A rebuild may involve moving files, retaining cited URLs, mapping historical records and checking how existing connections work. These tasks depend on the condition of the source material and the access available. A sample migration is often more informative than an estimate based on an assumed clean export.

For a repair, the first scope may be a bounded investigation. Its output should identify the observed failure, supporting evidence and practical options. It should not promise a complete rebuild or a particular diagnosis before the system has been inspected.

Tools, accounts and ongoing costs

Hosting, domain renewal, provider subscriptions, document storage and external services need named owners. Record the costs of preparing and maintaining material as well as the software bill. A project can be technically small while depending on work that the organisation has not yet assigned.

A partner workspace may require a paid capability that a public website does not. A connection may need an authorised account or a supported API. We check the intended provider and account arrangement rather than infer availability from another customer's setup. The cost-planning guide examines how to expose an overlooked dependency.

Review and acceptance

The scope should specify the representative records, roles, language editions and tasks used for review. It should distinguish website work from PDF remediation, content translation, professional advice or independent security assessment when those are separate services.

Changes discovered during review can have different consequences. Correcting an implementation that fails an agreed task is not the same as adding a new publication type or another language edition. Recording the original acceptance conditions makes that conversation easier.

A manageable starting engagement

You may need an investigation, a first publication type or a targeted repair before committing to a larger programme. The decision should leave a useful result: an understood problem, a working task or a content structure that the organisation can maintain.

Bring the material and constraints described in project planning. We can then discuss a scope with explicit dependencies, a review process and a clear route for changes. Prices, dates and continuing support are agreed for the work itself; this page does not set a standard package or response promise.