Municipal bid postings: keep deadlines and addenda together
Help vendors find current bid documents, addenda and deadlines on your community's website. A practical publishing guide for local government staff.
On this page
Municipal bid postings are the website pages that help vendors find a local government's purchasing opportunities and instructions. Give each opportunity one stable page with its current deadline, documents and addenda. When the purchasing office approves a change, update the page and notify vendors through the established process.
For staff, that means having one link to share when someone asks for the latest information. The approved bid package still supplies the requirements. The website helps people reach it, recognize changes and use the correct submission route.
What should municipal bid postings show first?
Put the project name, bid number, current status and closing date near the top of the page. Show the due time and confirmed time zone beside the date. Then link to the approved documents and explain where vendors submit their response. Someone should be able to find those basics without opening several attachments.
Use the purchasing office's approved wording. If a document gives conflicting dates or an unclear time zone, send it back for confirmation before copying either version onto the page. The website editor should not have to interpret procurement instructions.
Keep distinct deadlines separate:
| Information | What to show on the website |
|---|---|
| Questions | The question deadline and approved route for sending them. |
| Pre-bid meeting or site visit | Date, location and whether attendance is required, as stated in the solicitation. |
| Submission | Closing date, time, time zone and delivery instructions. |
| Bid opening | Its own date and location or meeting link, when supplied for publication. |
Bloomington, Minnesota (opens in a new tab), tells vendors to check question deadlines and directs questions and most submissions through its purchasing platform. The useful lesson for a municipal website is to label each action clearly. A general contact email should not look like the place to submit a bid when the instructions require another route.
What changes when an addendum is posted?
Attach the approved addendum to the same opportunity and check every displayed detail it changes. An addendum can revise the deadline or instructions as well as the project documents. Check the visible deadline before marking the update complete.
In its March 27, 2026 addendum for a water and sewer rate study (opens in a new tab), Meridian Township extended the submission deadline to April 16, 2026 and revised the proposal contents. It also required a signed addendum with the proposal. Those changes affect what a vendor must see and do before submitting.
When an addendum arrives, use this publishing sequence:
- Confirm the approved file, addendum number and release instructions with the purchasing office.
- Add it to the opportunity's document list with a descriptive label and issue date. Keep earlier addenda identifiable.
- Update the displayed deadline or other affected fields to match the approved change. Check the open-bids list and any connected calendar entry too.
- Add a short update note that names the change and links to the full addendum. Have the responsible office confirm that summary.
- Send the required notifications through the established process, then open the public page and attachments to check the result.
Keep a record of what was published and when under the community's procedures. Follow any required notice or distribution steps separately; a website edit alone should not be treated as completing them.
How should vendors get updates?
Give vendors a visible way to follow the opportunity, and keep every published addendum available on its page. The page lets a late subscriber catch up. Notifications help people return to the current information without asking staff to resend each file.
Muniway's Bids & RFPs tool keeps bid documents, addenda, due dates and results together. Vendors can subscribe to an individual bid and receive addenda as staff post them. That gives staff a way to publish an update without maintaining a separate email list by hand.
Be precise about what a subscription does. It does not submit a proposal, prove that the recipient read an addendum or satisfy an acknowledgment requirement. Those actions need their own instructions. If the solicitation requires a signature or another acknowledgment, make that instruction easy to find beside the addendum.
Before relying on a subscription feature, test it with a clearly labeled sample opportunity in a preview environment. Have a colleague subscribe, publish a sample update and check that the message links to the correct page. Verify what happens when someone subscribes after an addendum has already been posted. Avoid sending practice notices to real bidders.
What if the official documents live in another portal?
Use the municipal website as a clear starting point and direct vendors to the maintained opportunity in the purchasing portal. Explain where to get documents, ask questions and submit. Keep those links together so a vendor does not mistake a general inquiry form for the official submission process.
Joliet, Illinois (opens in a new tab), directs vendors to its procurement portal for solicitations, addenda and electronic submissions. Its municipal page also explains that vendors can enable alerts and should check the portal for updates. Keep the portal link beside the submission instructions so vendors can act from the same page.
Avoid maintaining a second attachment collection unless someone is responsible for keeping both copies consistent. If your community's website repeats deadlines from another system, assign an owner for that summary. A link to the official posting is easier to maintain than a copied package that staff forget to update.
Use descriptive link text with the project name and number. The guide to municipal website PDF search explains how document titles and searchable text help people find the right attachment. Keep accessibility checks in the publishing process as well; a readable project summary does not fix the attached files.
What should happen after the deadline?
Move the opportunity out of the open-bids list while keeping its page's status clear. Ask the purchasing office what can be posted next and how it should be labeled. A list of bids received, a bid tabulation and an award notice describe different stages.
Joliet's purchasing page (opens in a new tab) explicitly distinguishes results read at opening from a contract award. Follow that distinction in the website labels. Publish an award status only after the responsible office confirms it.
Keep the existing address useful for people following an older email or bookmark. Where the community's procedures allow, retain the documents and add the approved results on that page. If an opportunity is canceled or replaced, show the confirmed status and link to the replacement when one exists. The guide to expired municipal website notices covers separating current listings from historical information.
Start with one active opportunity. Compare its website deadline and document list with the purchasing office's current package, then follow the submission link from a phone while signed out. Fix any mismatch before the next addendum arrives. That gives staff a concrete check they can repeat each time they publish an update.
Frequently asked questions
Can we keep using an outside purchasing portal?
Yes. Keep a clear entry point on your community's website and identify where vendors get the official documents, submit questions and send their response. Link to the specific opportunity when possible. If staff repeat a deadline on the municipal website, include that field in the update check whenever the purchasing office issues a change.
Does subscribing to bid updates mean a vendor has submitted a bid?
No. A subscription requests updates about an opportunity. Submission is a separate step governed by that solicitation's instructions. Label the two actions clearly, and explain any required registration or addendum acknowledgment separately. A notification also does not establish that the recipient read the document or completed a required acknowledgment.
Should the website show the question deadline as well as the bid deadline?
Yes, when the approved solicitation includes one. Give each deadline its own label and include the time and time zone as confirmed by the purchasing office. Bloomington's purchasing instructions (opens in a new tab) specifically tell vendors to check question deadlines. If an addendum changes the closing date, confirm whether the question deadline changes too.
Should staff replace the original file when a correction arrives?
Follow the purchasing office's release instructions. Keep the approved change identifiable, with its number, date and relationship to earlier documents. If a replacement file is authorized, label it clearly and handle the earlier version under the community's records procedures. Reusing an old filename without explaining the change makes it harder for a returning vendor to recognize what changed.
Keep each bid and its updates in one place.
See how Muniway's Bids & RFPs tool brings together documents, addenda, due dates and vendor subscriptions.