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: 07 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 Section 1.2 – Project

Objectives, Pages 5–6;

Section 5.2 – Specifications: Design and User Experience, Does PCC anticipate using primarily existing photography, video, and other creative assets for the redesigned site, or should vendors include production of new photography, video, illustration, or other visual assets within their proposed scope?

Yes, PCC will provide existing assets, while the selected vendor will be responsible for developing the website's visual design concepts and creative direction, including the overall look, feel and application of the College's brand across the website.

2 Section 1.2 – Project Objectives, Pages 5–6;

Section 5.2 – Specifications, Pages 15–17

Does PCC maintain a system of record or structured data source for academic programs, courses, credentials, and related information that the new website should integrate with, or should vendors assume this information will be managed directly within the website CMS?

Academic program and course information is maintained through Modern Campus. Continuing-education and workforce development program information is maintained through FundFive.

PCC would like to explore opportunities to integrate with these systems rather than managing duplicate information directly within the website CMS.

3 Section 1.3 – Contract Term, Page 6; Section

5.3 – Tasks/Deliverables, PCC identifies a tentative contract award date of September 28, 2026 and states that implementation shall not exceed 12 months. Can PCC provide a preferred launch window or academic-calendar blackout periods vendors should account for in the project schedule?

PCC does not have a preferred or required go-live date. Major launches, migrations, and other significant project activities should avoid peak registration, enrollment, and financial-aid periods when possible. The selected Vendor will work with PCC to refine the timeline and identify any scheduling considerations during the project.

4 Section 5.1 – General, Page 14; Section 5.2 – Specifications, Pages 15–17

Are there significant custom content types, plugins, applications, databases, forms, or legacy functionality in the existing environment that PCC expects the selected vendor to migrate, replace, recreate, or preserve as part of the redesign?

Major plugins include Elementor, Gravity Forms, Employee Directory, TablePress, WP Mail Logging, SearchWP, and Events. PCC expects key functionality such as search, employee directory, forms, events, and chatbot functionality to be maintained or replaced with equivalent functionality in the redesigned website.

5 Section 5.1 – General, Page 14; Section 5.2 – Specifications, Pages 15–17

Can PCC provide additional detail regarding the employee-facing intranet/internal content solution, including the existing platform(s), approximate content volume, number of users, primary use cases, and functionality that should be retained, replaced, or enhanced? PCC expressly includes an employee-facing intranet/internal content solution in the scope.

PCC’s current intranet platform is Sharepoint. PCC anticipates approximately 1200 employees and 45,000+ student users. 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.

6 Section 5.2 – Specifications: Design and User Experience, Does PCC have existing brand guidelines (color palette, typography, logo usage rules) that the redesign must adhere to, or is there an opportunity to evolve the visual identity as part of this engagement?

Yes, PCC will provide existing logos, fonts, color palette and photography/video assets. The selected vendor will be responsible for developing the website's visual design concepts and creative direction, including the overall look, feel and application of the College's brand across the website.

7 Section 5.2 – Specifications: Design

The RFP identifies eight distinct audience groups. Has PCC done

PCC has not conducted a formal user research study of the current and User Experience, any prior user research (surveys, interviews, analytics segmentation) that indicates which audiences are highest priority, or which current navigation patterns are causing the most friction?

website. The selected Vendor will be expected to conduct user research and usability testing as part of the Discovery phase. PCC has identified challenges related to content organization, website performance, visual design, program discovery, and on-site search.

8 Section 5.2 – Specifications: Design and User Experience, For program pages specifically, are there existing page structures or information hierarchies PCC considers successful that the new design should build on, or is a full reconception expected?

PCC has not established specific program-page structures or information hierarchies that must be retained. Vendors should evaluate existing content and recommend an approach that improves program discovery and user experience while meeting project objectives.

9 Section 5.2 – Specifications: ADA Compliance, Pages 15–16

Should vendors assume that remediation of existing PDFs and other downloadable documents for accessibility is included within the project scope? If so, can PCC provide an approximate quantity and identify which party will be responsible for remediation?

Yes. Vendors should include accessibility review and remediation of existing documents as part of their proposed scope and pricing. PCC has approximately 120 PDF files requiring accessibility review. PCC would like to reduce the number of downloadable documents where possible by transitioning information to accessible web content. Any remaining downloadable documents should be made accessible in accordance with applicable accessibility requirements.

10 Section 5.2 – Specifications:

Platform and Technology, Page 16

Does PCC have a preferred or required hosting environment or managed WordPress platform?

PCC expects the selected Vendor to provide and manage the hosting environment. PCC does not have a preferred hosting provider or managed WordPress platform.

Hosting must be US based.

11 Section 5.2 – Specifications:

Content Management and Best Practices, Can PCC clarify the anticipated division of responsibility between PCC and the selected vendor for content inventory, auditing, rewriting/editing, consolidation, creation of new content, entry, migration, and final quality assurance?

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

12 Section 5.2 – Specifications:

Platform and Technology / Security, Pages 16–17

Does PCC currently use Microsoft 365, SharePoint, Teams, or another internal platform, and what authentication/SSO solution does PCC currently use? Should vendors anticipate integration with these systems and SSO for the employee-facing solution?

PCC currently uses Microsoft 365, SharePoint, and Teams. The employee-facing intranet must integrate with Microsoft Entra ID for Single Sign-On (SSO). PCC is open to Vendor recommendations regarding integration.

13 Section 5.2 – Specifications:

Functionality and Performance, Pages 16–17

Can PCC identify the primary third-party systems, applications, APIs, or data sources the redesigned website and intranet must integrate with, particularly systems supporting admissions/applications, CRM/inquiry management, academic programs/catalog, registration, directories, events, forms, emergency communications, and Foundation/giving?

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.

14 Section 5.2 – Specifications:

Suggested Sites, Page

The reference sites span a range of visual styles. Are there specific qualities from those sites PCC wants to avoid, or are they all equally valid as inspiration? For example, Beaufort CC is noted for motion and interactive elements

— is that level of visual dynamism something PCC is open to, or does conservatism around performance and accessibility take precedence?

The suggested sites are intended as examples of features, functionality, and design approaches PCC finds noteworthy. Vendors should propose a design approach that balances user experience, accessibility, performance, and project objectives.

15 Attachment A: Pricing, Does PCC have an established budget or anticipated funding range for the initial website redesign and implementation?

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

16 Section 5.3 – Tasks/Deliverables, Page 18; Attachment A: Pricing, Page 22

The RFP identifies migration of up to 500 combined pages. Can PCC provide an approximate inventory of the current public website and internal-facing content, including web pages, PDFs/documents, forms, media, and other significant content types, and clarify what PCC intends to count toward the 500-page migration allowance?

The current PCC website contains approximately 2,477 core content URLs, including 1,362 static pages and 1,115 news posts. The media library contains approximately 5,321 items. The 500-page migration limit applies only to public-facing website pages and does not include intranet content, documents, forms, media assets, program records, news/events, or faculty/staff profiles.

17 Section 4.2 – Financial Stability, Page 12;

Attachment F – Certification of Financial Condition, Section 4.2 references Attachment G for the Certification of Financial Condition, while the RFP's attachment list identifies the Certification of Financial Condition as Attachment F. Can PCC confirm the correct attachment designation and form vendors are required to complete and return?

The Certification of Financial Condition is located on Page 24 of the RFP as ATTACHMENT F.

18 Section 1.2, Page 5;

Section 5.1, Page 14

Intranet Architecture: Is the employee-facing intranet expected to be hosted on the same WordPress environment (e.g., as a WordPress Multisite or sub-directory/sub-domain) as the public website, or does the College require a completely separate and secure installation?

PCC does not require the employee-facing intranet to be hosted on the same WordPress environment as the public website.

Vendors should recommend the architecture they believe best meets PCC’s security, accessibility, usability, and maintenance requirements.

19 Section 5.1, page 14 Could PCC provide additional context regarding the current state and mandatory requirements for the employee-facing intranet/internal content solution, including approximate user population, current traffic, existing internal-content environment, authentication/SSO requirements, required integrations, and approximate content volume to be transitioned?

PCC currently uses SharePoint as its employee intranet and anticipates approximately 1,200 employee users. The intranet must integrate with Microsoft Entra ID for Single Sign-On (SSO). PCC’s goal is to replace the existing intranet with a separate, secure, and user-friendly solution for employee communications, resources, forms, policies, and related employee information. Specific content volumes have not been established.

20 Section 5.2, Pages 15-

Intranet Authentication & Single Sign-On (SSO): Does the College require Single Sign-On (SSO) integration for employee access to the intranet? If so, which Identity Provider (IdP) is currently utilized by PCC (e.g., Microsoft Azure AD / Entra ID, Okta, Shibboleth, SAML/OAuth)?

Yes, PCC requires Single Sign-On (SSO) for the employee intranet using Microsoft Azure AD / Entra

ID.

21 Section 5.2, Page 17 Third-Party Technical Integrations:

Could the College provide a detailed list of the specific third-party systems, CRMs, and LMS platforms (e.g., Canvas, Moodle) currently in use that must

PCC’s current systems and platforms include Colleague (SIS and faculty/staff information), Element451 (CRM, forms, events, and chatbot functionality), CFNC (admissions and applications), Modern Campus (academic catalog integrate or exchange data with the new public website?

and program data), FundFive (continuing education and workforce enrollment), SharePoint/Microsoft Entra ID (employee intranet and SSO), and Moodle (soon to be Canvas). Most systems are currently linked to rather than directly integrated with the website. PCC is particularly interested in exploring deeper integration with Modern Campus and FundFive to reduce duplication and improve consistency of information. The existing Colleague directory connection and Element451 functionality should also be considered. Vendors should recommend appropriate integration approaches and include associated costs in their proposals

22 Section 4.7, Page 13 Cyber Liability Insurance Requirements: The RFP checked the box for a contract value up to $1,000,000.00 requiring Cyber Liability coverage. Could PCC clarify if there is a specific minimum policy limit required (e.g., $1,000,000 or $2,000,000 per occurrence/aggregate) for this insurance?

PCC requires a minimum of $1,000,000 in Cyber Liability Insurance coverage. Therefore, vendors must provide evidence of cyber liability coverage meeting or exceeding this limit and addressing the coverage areas identified in Section 4.7.

Coverage that is merely 'commercially reasonable' but below the $1,000,000 minimum would not satisfy the requirement.

23 Section 5.3, page 18 For the migration of up to 500 combined pages, could PCC clarify what content is included in this count and the approximate distribution between public website content and intranet/internal content? Are documents, forms, and other digital assets included within this limit?

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.

24 Section 5.3, page 18 Content Migration Scope: The RFP specifies the migration of "up to 500 combined pages". Could the College please clarify the current total volume of pages, PDFs/documents, and web forms

PCC’s current website contains approximately 900 public pages in addition to other content types.

The Vendor will be responsible for migrating up to 500 pages. PCC staff will be responsible for on the active website? If the total exceeds 500, will the Vendor be responsible only for migrating a prioritized selection of 500 pages (with PCC staff migrating the rest), or is the Vendor expected to migrate all active content?

migrating the remaining pages and content identified for inclusion in the new website. The Vendor should include a content migration strategy that addresses all existing content and pages, including how content will be reviewed, prioritized, and transitioned.

25 Section 5.2, page 16 Within the up-to-500-page migration scope, should Vendors assume that all migrated content may require rewriting/editing, or should the Vendor propose a prioritization approach for rewriting selected high-value content while PCC retains responsibility for other content?

Vendors should propose a prioritization approach for content requiring rewriting or editing. PCC expects the Vendor to assist with high-value content within the up-to-500-page migration scope, while PCC staff will retain responsibility for other content as appropriate.

26 Section 3.4, page 10 Does the accessibility remediation scope include existing or legacy documents, PDFs, multimedia, forms, and other downloadable assets being migrated, or should Vendors assume accessibility remediation primarily for the new templates, components, and prioritized web content?

Yes. The accessibility remediation scope includes existing and legacy documents, PDFs, multimedia, forms, and other downloadable assets being migrated, as well as new templates, components, and web content.

27 Section 5.3, page 18 Phase 6 is estimated at one month but references 30/60/90-day optimization recommendations.

Should Vendors interpret this as a 30/60/90-day optimization roadmap delivered during Phase 6, or as actual post-launch monitoring and optimization activities extending through 90 days after launch?

The 30/60/90-day optimization activities should be interpreted as actual post-launch monitoring, review, and optimization activities extending beyond launch.

28 Section 5.1, page 14 Will PCC support the recruitment and scheduling of stakeholders and end users for discovery and usability testing, and are there any audience groups for which participant access is expected to be limited?

Yes. PCC will assist with the recruitment and scheduling of stakeholders and end users for discovery and usability testing, as appropriate. PCC does not anticipate any specific audience groups for which access will be limited.

29 Section 5.1, page 14 / Section 5.2, page 16

Could PCC describe the current technical environment for the public website, including hosting infrastructure, WordPress version, development/staging/production environments, and any technical

PCC’s current website is hosted on SiteGround and uses WordPress version 7.1. The site utilizes a single WordPress installation. PCC has not identified technical constraints that must be preserved and is open to constraints the Vendor must preserve?

Vendor recommendations regarding architecture and infrastructure. Hosting must be US based.

30 Section 5.1, page 14 Should Vendors assume responsibility for provisioning and operating the hosting infrastructure, including monitoring, patching, backups, and recovery, or will these responsibilities remain with PCC?

Yes. The selected Vendor will be responsible for provisioning and operating the hosting infrastructure, including monitoring, patching, backups, and recovery. Hosting must be US based.

31 Section 5.2, page 16 For the advanced search requirement, what content and data sources should be searchable, and does PCC have an existing or preferred search technology that Vendors should retain or integrate with?

PCC expects the advanced search to support the public website’s content, including pages, documents, programs, services, and other relevant content. PCC does not have a required search technology that Vendors must retain or integrate with.

32 Section 5.2, page 16 Should Vendors assume responsibility for accessing and migrating data from the current website, or will PCC provide the necessary access and data for migration? If so, how will PCC provide access and data?

PCC will provide the selected Vendor with the necessary access to the current website and data required for migration. The specific access and data transfer methods will be coordinated with the Vendor during the project.

33 Section 5.2, page 17 Could PCC identify the public-facing systems that require integration with the new website and indicate which integrations are mandatory for launch? Will APIs, documentation, test environments, and technical support be available for those systems?

PCC’s current public-facing systems include Colleague, Element451, CFNC, Modern Campus, FundFive, SharePoint/Microsoft Entra ID, and Moodle (soon to be Canvas). Most are currently linked to rather than directly integrated with the website. PCC expects to retain the existing Colleague directory connection and Microsoft Entra ID SSO for the intranet and is particularly interested in exploring deeper integrations with Modern Campus and FundFive. API access, documentation, test environments, and technical support will be coordinated as needed during the project.

34 Section 5.2, page 17 Does PCC have defined availability and disaster-recovery requirements, including uptime targets, backup retention, RTO, and RPO, or should Vendors recommend appropriate targets?

Vendors should recommend appropriate targets.

35 Section 5.2, page 17 Should the redirect and broken-link remediation scope cover all existing PCC URLs, including pages that will not be migrated, or only the URLs associated with migrated content?

The selected Vendor’s redirect and broken-link remediation strategy should address all existing PCC URLs, including pages that will not be migrated, in order to minimize broken links and preserve the user experience.

36 Section 5.3, page 18 The estimated durations for Phases 2 through 6 total 13 months, while the RFP states that the project shall not exceed 12 months. Should Vendors assume that certain phases are expected to overlap?

The phase durations listed in the RFP are estimates and may overlap as appropriate. Vendors may propose a schedule that fits within the 12-month maximum.

37 Section 5.2, pages 16–

Does PCC have defined technical acceptance criteria for performance, Core Web Vitals, browser/device compatibility, security, and other non-functional requirements, or should Vendors propose those targets?

PCC does not have specific technical acceptance criteria beyond the requirements outlined in the RFP. Vendors should recommend appropriate targets based on industry-based practices.

38 Attachment A, Page

Recurring Cost Allocations: Since WordPress is the default platform, should the "CMS Maintenance Costs" line be utilized for general WordPress plugin/license renewals, or should those be itemized under "Other Recurring Costs"? Who is expected to hold and pay for the ongoing licenses of third-party plugins selected for the build?

The CMS Maintenance Costs category should be used for proprietary CMS costs only.

Vendors should itemize all recurring costs associated with their proposed solution under the appropriate recurring cost categories. Vendors are expected to include the cost of ongoing licenses required for their proposed solution.

39 Section 6.2, page 19 What are the applicable payment terms? Please specify the payment timeframe (e.g., Net 30, Net 45, Net 60) from the date of invoice or acceptance of the goods or services.

As stated in ATTACHMENT C:

NORTH CAROLINA GENERAL TERMS

& CONDITIONS (9), Payment terms are net not later than 30 days after receipt of a correct invoice or acceptance of goods, whichever is later.

40 Section 5.1, Page 14 Please describe the intended scope of the employee-facing intranet or internal content solution. Does PCC expect the selected vendor to replace, redesign, integrate with, or supplement the existing myPittCC SharePoint environment?

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.

41 Sections 5.1 and 5.2, Pages 14–17

Will the intranet require integration with Microsoft 365, SharePoint, Entra ID, Active Directory, or another identity provider for authentication or single sign-on?

Yes. The employee-facing intranet will require integration with Microsoft Entra ID for Single Sign- On (SSO).

42 Section 5.2, Page 17 Please identify the current and anticipated third-party systems requiring an API, data feed, iframe, single sign-on, form handoff, or other integration with the public website or intranet.

PCC’s current and anticipated systems include Colleague, Modern Campus, Element451, Paradigm, SharePoint/Microsoft Entra ID, FundFive, and Moodle (soon to be Canvas). PCC anticipates integrations with Colleague for directory information, Modern Campus for academic program and course information, Paradigm for online diploma verification, FundFive for continuing education courses, and Microsoft Entra ID for employee SSO. Vendors should identify any additional integration methods they recommend based on project needs.

43 Section 5.3, Page 18 The estimated implementation phases total approximately 13 months, while the RFP states that the project may not exceed 12 months. Should vendors assume that certain phases will overlap?

The phase durations listed in the RFP are estimates and may overlap as appropriate. Vendors may propose a schedule that fits within the 12-month maximum.

44 Section 5.3, Page 18 Please clarify how PCC will define and count the migration allowance of up to 500 combined pages. Will individual program records, news posts, events, PDFs, forms, and intranet documents count toward this total?

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.

45 Section 5.2, Page 16 What level of content editing or rewriting should vendors include

PCC expects a combination of both approaches. The selected Vendor in their proposals? Will PCC provide approved final content, or should the selected vendor provide substantive rewriting of existing pages?

should provide content strategy, information architecture, templates, editorial guidance, governance recommendations, and migration support, while also performing substantive editing and rewriting of content within 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.

46 Sections 5.2 and 5.3, Pages 16–18

Approximately how many PDFs, forms, videos, images, and other media assets will need to be reviewed, remediated, or migrated? Should document accessibility remediation be included in the base proposal?

PCC currently has approximately 5,321 media items in its media library. Document accessibility remediation should be included in the base proposal.

47 Section 3.5, Page 11 Are there restrictions on project personnel located outside the United States accessing development, staging, production, source-code, or PCC data environments?

PCC does not prohibit vendors from utilizing project personnel located outside the United States. Vendors proposing personnel located outside the United States 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.

48 Section 4.7, Page 13 What minimum coverage limit is required for Cyber Liability Insurance?

The minimum coverage limit for Cyber Liability Insurance is $1,000,000.

49 Section 5.1, Page 14 Does PCC intend to provide the hosting environment, require the selected vendor to provide managed WordPress hosting, or consider either approach?

PCC expects the selected vendor to provide and manage the hosting environment. Hosting must be US based.

50 Section 5.2, Page 16 Does PCC currently use a WordPress editorial workflow or approval system? Are there specific publishing, approval, page-review, or content-expiration workflows that must be preserved or implemented?

PCC currently uses WordPress’s built-in content statuses and user roles/permissions to manage content workflow. No specific editorial workflow or approval plugin is currently used.

51 Section 4.4, Page 12 Please confirm that the Customer Reference Form is Attachment D, The Customer Reference Form is located on Page 24 of the RFP as

ATTACHMENT D.

despite the reference to Attachment E in Section 4.4.

52 Section 4.2, Page 12 Please confirm that the Certification of Financial Condition is Attachment F, despite the reference to Attachment G in Section 4.2.

The Certification of Financial Condition is located on Page 24 of the RFP as ATTACHMENT F.

53 Section 2.7, Page 8 Please clarify what vendors are expected to complete and return for Attachments B and C, which appear to be incorporated reference documents rather than fillable forms.

ATTACHMENTS B and C contain the State’s terms and conditions. These documents do not need to be returned; however, the Vendor should enter their company name in the designated blank at the top of each page.

54 Section 5.1, Page 14 Will PCC provide the selected vendor with access to existing analytics, Google Search Console, accessibility reports, hosting information, WordPress plugin inventory, content exports, and other available documentation during discovery?

Yes. PCC will provide the selected Vendor with available documentation and access to relevant systems and information during the Discovery phase.

55 Attachment A: Pricing, Pages 22–23

Has PCC established a budget or anticipated funding range for the initial implementation and the recurring services requested under this RFP?

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

Execute Addendum:

BIDDER: ____________________________________________________________________

ADDRESS (CITY & STATE): _____________________________________________________

AUTHORIZED SIGNATURE: __________________________________ DATE: ____________

NAME and TITLE (Print): ________________________________________________________