IMPORTANT BID ADDENDUM

August 26, 2026

FAILURE TO RETURN THIS BID ADDENDUM IN ACCORDANCE WITH INSTRUCTIONS

MAY SUBJECT YOUR BID TO REJECTION ON THE AFFECTED ITEM(S):

BID Number: RFP 115-6181 COMMODITY: Website Redesign ADDENDUM Number: 04 USING AGENCY: Pitt Community College PURCHASER: Jane Alligood OPENING DATE/TIME: September 2, 2026 @ 2:00 PM ET

INSTRUCTIONS:

Please make the following change(s) in the bid referenced above:

Reference Vendor Question PCC Response

1 5.1 – General Who is the incumbent vendor currently providing similar services?

AndiSites, Inc. is the current incumbent vendor providing website services to PCC.

2 5.1 – General Is the incumbent vendor allowed to participate in this

RFP?

Yes. The incumbent vendor is eligible to participate in this RFP.

3 5.2 – Platform & Technology, 16

PCC states that the proposed solution should integrate with the current WordPress platform.

Could PCC clarify whether the selected vendor is expected to retain the existing WordPress installation and hosting environment, or whether the vendor should establish a new WordPress environment and migrate the existing site?

The approach to the existing WordPress installation will be determined based on the vendor’s assessment and recommendations.

PCC is open to building upon the current configuration if appropriate.

The vendor will be responsible for providing and managing the hosting environment. Hosting must be US based.

4 5.1 General,15 Could PCC provide additional details regarding the employee-facing intranet/internal content solution, including the expected functionality, number of users, user roles, authentication

PCC anticipates approximately 1,200 employees and 45,000+ student users. Roles, departments, and approval workflows are unknown at this time. PCC’s goal is to establish a separate, secure, and user-friendly intranet for faculty and staff that is requirements, content types, search requirements, and other capabilities expected at launch?

distinct from the College’s public-facing website. The intranet would serve as a centralized location for internal communications, resources, documents, forms, policies, announcements, and other employee information. PCC currently uses SharePoint for its employee intranet and intends for the new solution to replace the existing intranet. The intranet will require Single Sign-On (SSO) through Microsoft Entra ID.

PCC is open to the Vendor’s recommendations regarding the best platform or approach, including third-party solutions such as Interact. The proposed solution should provide appropriate security, authentication, permissions, search, and integration with PCC’s existing technology environment while remaining easy for employees to use and College staff to manage.

5 5.2 – Content Management and Best Practices, 16

Does PCC expect the public website and employee-facing intranet to operate within the same WordPress installation, separate WordPress installations, or another architecture recommended by the vendor?

PCC does not have a predetermined requirement for the public website and employee-facing intranet to operate within the same or separate installations. Vendors should recommend the architecture they believe best meets PCC’s needs and provide a rationale for their recommendation.

6 5.2 – Content Management and Best Practice, 16

For the configurable permissions and approval levels referenced for contributors, editors, approvers, administrators, and intranet users, could PCC clarify the expected number of users and required permission levels/workflows?

PCC anticipates approximately 1,200 employees and 45,000+ student users for the intranet and approximately five users for the website. Roles and approval workflows are unknown at this time.

7 5.2 – Content Management and Best Practice, 16

Could PCC provide the approximate breakdown of the 500 combined pages between public-facing website content and internal/intranet content?

The 500-page migration limit applies to public-facing website pages only. It does not include intranet content, PDFs/documents, forms, media assets, program records, news/events, or faculty/staff profiles.

8 5.2 – Content Management and Best Practice, 16

Please clarify whether the "up to 500 combined pages" migration requirement includes only public-facing HTML pages or also includes program pages, news, events, faculty/staff profiles, documents, forms, and other content types.

The 500-page migration limit applies to public-facing website pages only. It does not include intranet content, PDFs/documents, forms, media assets, program records, news/events, or faculty/staff profiles.

9 5.2 – Content Management and Best Practice, 16

Could PCC clarify the expected division of responsibility between PCC and the selected vendor for content rewriting, editing, cleanup, metadata creation, accessibility remediation, approval, and final migration validation?

The selected Vendor will be primarily responsible for content inventory, rewriting, editing, cleanup, metadata creation, accessibility remediation, migration, redirects, and quality assurance for the approved 500-page migration scope. PCC staff will participate in content review and provide final approval. PCC staff will be responsible for migrating the remaining content identified for inclusion in the new website.

10 5.2 – Functionality and Performance, 17

Could PCC provide a list of the existing systems/applications that must integrate with the website and/or intranet, including enrollment, student services, marketing, workforce, Foundation, communications, and other internal systems?

PCC’s current systems and platforms include Colleague, Element451, Modern Campus, FundFive, SharePoint/Microsoft Entra ID, and Moodle (soon to be Canvas). Most of these major systems are linked to rather than directly integrated.

Vendors should identify any recommended integrations and include associated costs in their proposals.

11 5.2 – Functionality and Performance, 17

Could PCC identify the current web analytics platforms and configurations in use and clarify whether the selected vendor is expected to migrate existing tracking, events, goals, dashboards, and historical reporting configurations?

PCC currently uses Google Analytics, Siteimprove, and Google Search Console for website analytics, monitoring, and search performance.

Vendors should include migration or recreation of existing tracking configurations and integrations as appropriate to maintain continuity of reporting and data collection.

12 5.3 Tasks/Deliverables, 18

Could PCC clarify whether the four-month Development, Integrations & Content Migration phase is expected to include all integrations, search, analytics, forms, redirects, Yes. Vendors should assume the Development, Integrations & Content Migration phase includes implementation of approved integrations, search functionality, analytics configuration, forms, redirects, migration of up to 500 public-facing website pages, and migration of up to 500 pages, and internal-content transition?

transition activities necessary to support launch. The exact approach and sequencing may be refined during project planning and may overlap with other project phases.

13 4.1 Pricing / Attachment A, 12 & 22

Should vendors include hosting, third-party plugins, software licenses, subscriptions, security services, analytics tools, and support/maintenance as part of the recurring Year 2–5 costs, or will PCC procure/manage any of these separately?

Vendors should include all anticipated hosting, third-party plugins, software licenses, subscriptions, security services, analytics tools, and support/maintenance costs in their proposals. PCC may elect to procure or manage certain services separately based on cost and project needs.

Hosting must be US based.

14 5.1 – General Who will be responsible for hosting?

The selected vendor will be responsible for providing and managing the hosting environment.

Hosting must be US based.

15 5.1 – General What is the hosting preference – Cloud vs On-prem?

PCC’s preference is cloud hosting.

Hosting must be US based.

16 5.1 – General What is your preferred hosting service provider (AWS or Azure)?

PCC does not have a preferred hosting service provider. Hosting must be US based.

17 5.1 – General Do you expect the vendor to perform any tasks on-site, or can all work be performed remotely?

PCC does not require onsite work.

Vendors may propose a remote or hybrid work arrangement as appropriate for the project.

18 5.1 – General Do you accept offshore resources?

Yes. PCC is open to proposals that utilize offshore resources. Vendors must disclose worker locations through Attachment E: Location of Workers Utilized by Vendor. PCC may consider proposed performance outside the United States as part of its evaluation of the proposal.

19 Section 5.3 – Project Cost Has PCC established an approved budget or anticipated budget range for the initial implementation of the public website and employee-facing intranet/internal content solution?

PCC has established a budget for the project; however, the College will not disclose the specific amount.

20 Section 5.1 - Current Website and Environment

Please provide information regarding the primary pain points and limitations PCC is currently experiencing with the existing website, including usability, accessibility, content management, search, performance, integrations, analytics, and security.

PCC’s primary challenges with the current website include content organization, website performance, visual design, accessibility, program discovery, and on-site search.

Students, faculty, and staff often have difficulty finding the information they need. PCC is seeking a modern website solution that improves overall user experience and better supports the College’s current and future needs.

21 Attachment A – Scope of Work

Does PCC currently operate an employee intranet or internal content platform? If so, please identify the platform and describe its primary functionality and known limitations.

The current platform is built with SharePoint online as the foundation and customizations using ShortPoint.

The product does not meet modern development standards and has to be managed soley by the IT staff. It would be ideal to have a solution that is low code/no code and managed by areas outside of IT. Also, having the solution integrate with other applications and is mobile responsive.

22 Attachment A – Scope of Work

Please clarify whether the intranet is expected to include employee directories, internal search, policies, HR resources, forms, calendars, announcements, departmental content, document repositories, workflows, notifications, or personalized content.

The intranet would serve as a centralized location for internal communications, search, departmental content, resources, documents, forms, policies, announcements, calendars and other employee information. The final scope and functionality may be refined based on project needs.

23 Attachment A – Scope of Work

Please provide an approximate volume of existing internal pages, documents, forms, and other content expected to be migrated to the new intranet.

The current PCC website contains approximately 2,477 core content URLs, including 1,362 static pages and 1,115 news posts. The media library currently contains approximately 5,321 items. The RFP includes migration of up to 500 pages by the Vendor, with PCC staff responsible for migrating the remaining pages identified for inclusion in the new website.

24 Attachment A – Scope of Work

Please clarify whether the intranet is expected to integrate with Microsoft 365, SharePoint, The intranet will require integration with Microsoft Entra ID for Single Sign-On (SSO). PCC currently uses SharePoint for its employee intranet

Teams, HR systems, calendars, identity-management systems, or other existing PCC platforms.

and is open to vendor recommendations regarding integration with Microsoft 365, SharePoint, Teams, and other existing PCC platforms based on project needs.

25 Attachment A – Scope of Work

Please clarify whether PCC will permit the employee-facing intranet/internal content solution to be developed using Microsoft SharePoint, including integration with PCC's existing Microsoft 365 environment, if applicable.

Our goal is to establish a separate, secure and user-friendly intranet for faculty and staff, distinct from the college’s public-facing website. The intranet would serve as a centralized location for internal communications, resources, documents, forms, policies, announcements and other employee information. We are open to the vendor’s recommendations regarding the best platform or approach to achieve this goal, including third-party solutions such as Interact. We would like the proposed solution to be easy for both employees to use and for college staff to manage, while providing appropriate security, authentication, permissions and integration with our existing technology environment.

26 Attachment A – Scope of Work

Please provide an approximate inventory of the content expected to be migrated, including pages, documents, forms, images, videos, events, profiles, and other digital assets.

The current PCC website contains approximately 2,477 core content URLs, including 1,362 static pages and 1,115 news posts. The media library currently contains approximately 5,321 items. The RFP includes migration of up to 500 pages by the Vendor, with PCC staff responsible for migrating the remaining pages identified for inclusion in the new website.

27 Attachment A – Scope of Work

Please clarify whether PCC expects the new website and intranet to be hosted within PCC's existing infrastructure, by a third-party hosting provider, or by the selected Vendor.

The selected vendor will be responsible for hosting. Hosting must be US based.

28 Attachment A – Scope of Work

If PCC will provide the hosting environment, please identify the infrastructure, cloud platform, database, network, security, backup, monitoring, and system-

The selected vendor will be responsible for hosting. Hosting must be US based.

administration responsibilities that will remain with PCC.

29 5.1 – Current Website / Hosting

Please clarify the current hosting environment for the PCC website, including the hosting provider/platform and whether hosting is managed by PCC, the incumbent Vendor, or a third-party provider.

PCC’s current website is hosted on SiteGround and managed by the incumbent vendor. Hosting must be US based.

30 Attachment A – Scope of Work

Please clarify the expected scope and duration of post-launch support and maintenance.

PCC expects the selected Vendor to provide post-launch support and maintenance as part of the proposed solution. Following launch, the Vendor should support the website through the 30/60/90-day optimization period and provide recommendations for ongoing improvements. For Years 2–5, Vendors should propose the ongoing support, maintenance, hosting, security updates, software updates, technical support, and related services they recommend. PCC has not established specific post-launch service levels or support requirements and encourages Vendors to describe their recommended approach and associated costs.

31 5.3 – Timeline Is there a required or target launch date associated with the project?

PCC does not have a required launch date.

32 General / Vendor Requirements

Please clarify whether registration with the North Carolina Secretary of State is required at the time of proposal submission or may be completed after contract award and prior to contract execution.

Vendors must be a North Carolina registered Vendor in good standing prior to the Certification of Award.

33 Section 5.2 Is PCC open to replacing WordPress with a higher education CMS?

Yes. As stated in Section 5.2, PCC is open to considering an alternative CMS if the vendor clearly identifies and justifies the alternative approach.

34 Section 5.2 How will PCC evaluate a justified alternative CMS against a WordPress-based proposal?

PCC will evaluate alternative CMS proposals using the same requirements and evaluation criteria outlined in the RFP.

35 Section 5.1 What are the required intranet capabilities?

The intranet would serve as a centralized location for internal communications, search, departmental content, resources, documents, forms, policies, announcements, calendars and other employee information. The final scope and functionality may be refined based on project needs.

36 Section 5.3 What is the true migration scope behind the “up to 500 combined pages” requirement?

The 500-page migration limit applies to public-facing website pages only. It does not include intranet content, PDFs/documents, forms, media assets, program records, news/events, or faculty/staff profiles.

37 Section 5.3 What Systems do you have that you would like integration with?

Is there a priority of system integrations? What specifically would you like to integrate within these systems.

PCC’s primary systems requiring integration include Colleague, Modern Campus, Element451, and potentially Paradigm (online diploma services). PCC currently pulls employee directory information from Colleague, would like to pull academic program and course information from Modern Campus, and anticipates the need to validate the authenticity of online diplomas through Paradigm.

Execute Addendum:

BIDDER: ____________________________________________________________________

ADDRESS (CITY & STATE): _____________________________________________________

AUTHORIZED SIGNATURE: __________________________________ DATE: ____________

NAME and TITLE (Print): ________________________________________________________