Skip to main content
web-development

Website Tender Notices: A Business Publishing Brief

Plan tender notice references, document versions, amendments, closing information and submission boundaries for an organisation website.

Mocky Digital
16 November 2026
7 min read

A website tender notices brief defines how an organisation publishes procurement opportunities, distributes the correct documents and explains changes before a submission closes. The website needs to support the organisation's approved process without presenting an obsolete attachment as current or suggesting that downloading a file completes an application.

For an organisation planning website development in Kenya, this is a practical content and workflow worksheet. It does not prescribe procurement law, evaluation rules or mandatory notice periods. Those requirements belong to the organisation's authorised procurement team and any appropriate advisers. All scenarios below are illustrative planning examples.

Identify the website's role in the process

Decide whether the website publishes information only, links to an existing procurement portal or receives submissions itself. These are substantially different scopes. A page with a download button does not include an auditable submission system, reviewer permissions or a complete evaluation workflow.

Write the visitor journey in ordinary language. Someone finds an open opportunity, identifies the relevant reference, obtains the current documents and follows the approved submission instructions. If the actual submission happens elsewhere, the website should explain that boundary clearly rather than collect an unrelated general enquiry.

Keep supplier registration separate from responding to a particular notice. A supplier may already be registered but still need to complete the opportunity-specific process. The organisation should approve the wording of both routes so readers do not mistake one for the other.

Prepare a controlled notice record

Give each opportunity a stable reference and a descriptive public title. Record the responsible department, approved summary, publication status, submission route and closing information. Include a named content owner who can confirm facts and authorise corrections when the web team has a question.

Separate the public record from internal discussion. Draft estimates, reviewer comments and unapproved attachments should not sit in the same release folder as final documents. A file being present in a shared drive is not evidence that it is ready for public distribution.

Specify who approves the initial notice and any later change. A website editor may be authorised to publish approved material without being authorised to change the submission conditions. Make that distinction explicit so an urgent correction does not depend on staff guessing the limits of their role.

Organise information for a reader on a phone

Lead with the opportunity title, reference, current status and the practical next step. A visitor should not have to download several large documents to discover that the notice has closed or that submissions use a separate portal. Keep the summary faithful to the authoritative documents.

Use descriptive headings for documents, submission instructions, clarifications and closing information. W3C's headings guidance explains that headings communicate content organisation and can support navigation. Ask the developer to implement a meaningful hierarchy rather than make ordinary paragraphs look like headings only through font size.

Check long references and titles at a narrow screen width. Avoid a layout that cuts off the distinguishing part of an opportunity's name. Where several notices have similar wording, the reference and status should remain visible enough for a reader to select the correct one.

Connect documents to the correct version

Prepare a document register for each notice. Include a stable document label, version, approval status and public description. If the notice has several files, explain the purpose of each rather than calling them all attachment. Readers need to distinguish instructions, schedules and clarification material.

The website download library brief covers the wider file publication process. Add opportunity references and version relationships here so an editor cannot accidentally attach a document belonging to another notice with a similar filename.

Decide how superseded versions are handled. A replacement should not leave the page pointing to an old file while the new one exists elsewhere. If earlier material remains available for context, clearly identify its status. The business owner must approve the explanation rather than quietly assuming that every reader has the latest copy.

Define clarification and amendment handling

Choose the approved route for questions and identify who can publish an answer. A question received through a general website form should not automatically become a public clarification. The procurement owner should review the content and decide which response belongs in the notice record.

Describe how amendments relate to the original instructions. A visitor arriving from an old link needs to find current information and recognise that something changed. The page should not require them to compare two documents line by line simply to discover an approved extension or correction.

Use a change record with the notice reference, affected material, approved explanation and publication owner. Include every relevant placement, such as a listing summary and detail page. The website news publishing brief can support the editorial approval process, while procurement-specific decisions remain with the authorised team.

Give closing information an operational meaning

Specify the closing date, time and time zone using the organisation's approved rules. Decide which system controls submission availability and what happens if the website and external portal disagree. A date printed on a page should not be presented as proof that another service will accept a submission until that moment.

Agree the states required for the public website, such as forthcoming, open, paused and closed. Explain what the visitor can do in each state. A closed notice should not retain an apparently active submit button unless it leads to an accurately labelled record or other approved destination.

Do not invent extension policies or outage remedies. The organisation should decide how a technical disruption is reported and who approves any change. The web team's role is to show the approved decision consistently and retain appropriate publication evidence, not to create procurement terms while fixing a page.

Keep publication separate from submission receipt

If a portal receives responses, confirm the exact destination for each opportunity. Test that the link carries the correct context and that the receiving service identifies the same reference. A working general portal homepage link may still leave suppliers unable to locate the intended notice.

If submissions are in scope for the website itself, prepare a separate specification for access, attachments, acknowledgements and reviewer permissions. Define what establishes an accepted submission. A successful file upload or outgoing email is not automatically proof that the complete response reached its authorised destination.

Use controlled records and isolated destinations for acceptance tests. Do not submit fictional procurement responses into a live process. Review the website form acceptance guide for safe testing principles, then add the specific receipt evidence required by the organisation's actual workflow.

Hand over a maintainable notice archive

Decide how readers find current opportunities and distinguish them from historical notices. An archive can be useful, but old submission instructions should not look like a live invitation. Agree the labels and any document availability rules with the responsible owner.

Test an open notice, a closed notice, a replaced attachment, a corrected deadline and an unavailable external destination. Ask a reviewer to explain which documents they would use and where they would submit. If their interpretation differs from the approved process, revise the page before accepting the build.

Include the notice register, publication permissions, update route and archive decisions in handover. Request a website project quotation with those requirements and the actual receiving platform. That gives the development team a concrete scope for reliable information delivery without pretending that a content page alone is a complete procurement system.

Frequently asked questions

Does a notice page need to accept submissions?

No. It can publish approved information and direct readers to an existing authorised process. Make that boundary clear.

Can an editor extend the deadline?

Only through the organisation's approved authority. Website editing access should not imply permission to change procurement conditions.

Should replaced documents remain public?

Agree the rule with the responsible team. If earlier files remain available, label their status and point readers to current instructions.

Does downloading the documents count as applying?

No. The page should explain the actual submission route and the evidence that confirms receipt through that route.

Share this article

Ready to Start Your Project?

Tell us what you need designed, built, or printed. We will reply with a clear price and timeline.

Book a Call

Preparing your booking calendar…

Having trouble? Open the booking calendar directly.

Mocky Digital

Let’s talk about your project

Choose a service and leave your details. We’ll follow up with you.

By submitting, I agree that Mocky Digital may save my details on its website and in Cal CRM and email me relevant service tips and offers. I can unsubscribe at any time.

Your details are used to respond to your enquiry. Privacy policy.