Make the offer clear. Make the work manageable.

A website can look complete while its service descriptions still need approval or its editor cannot maintain important information. A business application can have polished screens while the team has not agreed which record controls a decision. We address the information, interface and operating responsibilities as related parts of the same project.

The first discussion identifies what people need to understand or complete, what material already exists and who can confirm it. We can then plan an appropriate service: a new public presence, a considered improvement, a maintained content system or a tool supporting staff and customers. The proposal names the outputs and distinguishes design, working implementation and continuing care.

Choose one representative service, product or staff task and gather the information it actually needs. Bring the current page or working tool, approved descriptions, available media and a suitably redacted example of the next action. Explain which facts change regularly and who knows when they are wrong.

Invite the person who will make an ordinary update after handover. Their questions can reveal an unclear field, a missing source or an unnecessary copying task before the design is final. The project can then specify useful editing and review controls around real responsibilities. That discussion is also a sensible place to identify support or training that needs its own scope.