Frequently asked questions
Clear answers before your chapter makes a website decision.
Learn how projects, migration, integrations, monthly plans, maintenance, ownership, accessibility, security, and board transitions work with Chapter Partner.
Getting startedProjectsPlatformsPricingSupportTrust
Plain-language answersLimitations stated honestlyFinal terms documented in writing
01
GETTING STARTED
Working with Chapter Partner
Chapter Partner designs, develops, redesigns, migrates, integrates, maintains, and supports websites for local chapters and membership organizations. PMI chapters are our primary specialization, with services also available to ISC2 chapters and other professional associations.
No. Start with the chapter’s goals, current problems, workflows, constraints, and existing tools. We can recommend a practical service and technical direction after discovery.
Bring the current website URL, primary concerns, desired timing, relevant parent-association requirements, known platforms or integrations, approximate chapter size, and the board roles involved in making a decision. Do not send passwords or confidential member data.
Yes. A focused review of representative public pages can identify important issues involving member journeys, mobile usability, accessibility, performance, trust, search readiness, and maintainability. Request a chapter website review.
02
WEBSITE PROJECTS
Design, migration, content, and launch
Timing depends on scope, content readiness, migration volume, integrations, design depth, stakeholder availability, and approval speed. A realistic schedule is provided after discovery rather than promising one duration for every chapter.
The proposal defines responsibilities. The chapter always owns factual accuracy and final approval. Chapter Partner can organize, edit, migrate, or create covered content when that work is included in scope.
Often, yes. We first review the source platform, access, export capabilities, content quality, files, event archives, URLs, integrations, and any proprietary limitations. Migration commitments are made only after feasibility is understood.
Usually. The new site is commonly prepared in a separate staging environment while the current public site remains available until the approved launch window.
Yes, in most cases. The chapter should retain clear ownership and administrative control of its domain. We can coordinate approved DNS changes with the authorized domain contact during launch.
The chapter appoints a responsive project lead and final approver. Stakeholders review the appropriate milestones, and the project lead submits one consolidated feedback set so conflicting comments are resolved before work continues.
03
PLATFORMS & INTEGRATIONS
Technology, ownership, and connected tools
The recommendation depends on content, integrations, budget, hosting, internal skills, security expectations, portability, and long-term support needs. We begin with requirements rather than forcing every chapter into one predetermined tool.
Ownership and licensing are stated in the proposal and agreement. We favor clear chapter ownership or control of its domain, approved content, supplied assets, primary accounts, and portable data, subject to third-party licenses and applicable payment terms.
Yes, when the selected platform and engagement include administrative access. Permissions can be limited by role, and applicable training or documentation is provided. Chapters may also choose to have Chapter Partner handle covered updates.
No provider can guarantee every connection. Feasibility depends on supported APIs, exports, embeds, permissions, licensing, security, documentation, and vendor cooperation. We verify access before promising an integration.
Integrated mobile-app options can be discussed for chapter content, events, member-facing features, and push-notification workflows. The supported functionality, platform requirements, store responsibilities, fees, and ongoing support are confirmed in the proposal.
Usually not. Automation can reduce repetitive steps, but chapters still need accurate source information, approvals, ownership, exception handling, and quality checks.
04
PRICING & AGREEMENTS
Monthly plans, projects, and third-party costs
Current plans are based on chapter size: Essential is $130/month for up to 150 members; Growth is $160/month for up to 300; Advanced is $215/month for up to 600; Pro is $270/month for up to 1,200; and Ultimate is $330/month for more than 1,200. Final inclusions and terms are confirmed in the service agreement. View pricing details.
Only when explicitly stated in the proposal or service agreement. Initial design, setup, migration, custom development, or prerequisite repairs may be scoped and priced separately.
Not unless explicitly stated. Hosting, domains, premium extensions, event systems, payment fees, email platforms, apps, vendor subscriptions, taxes, and usage charges may be separate.
We explain the effect on price, timing, dependencies, and completed work. Material additions or changes proceed only after the chapter approves the revised scope or separate estimate.
The applicable term, renewal, notice, cancellation, payment, and transition provisions are stated in the proposal and service agreement. General website copy does not replace those written terms.
05
MAINTENANCE & SUPPORT
Keeping the website current and dependable
Often, yes. We first review the platform, hosting, access, software, extensions, integrations, documentation, and current technical condition. Prerequisite repairs or unsupported technology are identified before coverage begins.
It can. Applicable plans may include covered updates for pages, events, news, leadership, sponsors, forms, documents, and other agreed content alongside technical care.
Where offered, “unlimited” applies to covered support requests under the documented fair-use terms, authorized contacts, channels, hours, priorities, and exclusions. Projects, redesigns, custom development, third-party costs, and out-of-scope work are separate.
Response and completion depend on the selected plan, priority, complexity, approvals, access, and third-party involvement. Applicable response targets and support hours are stated in the service agreement.
Ongoing plans can include transition support: confirming authorized contacts, reviewing access, documenting active work, and orienting incoming leaders to the website-support process.
06
ACCESSIBILITY, SECURITY & PRIVACY
Responsible quality and risk statements
No responsible provider should promise permanent or absolute accessibility. Websites, content, standards, and third-party tools change. We can assess against an agreed target, remediate covered barriers, document limitations, and establish better ongoing practices.
An overlay is not a substitute for accessible design, semantic code, usable content, keyboard testing, and remediation of underlying barriers.
No. Security work can reduce common risks and improve preparedness but cannot eliminate every vulnerability, outage, human error, account compromise, or third-party incident.
No. We can implement agreed technical and content measures, but the chapter should obtain advice from qualified professionals regarding privacy, cookies, accessibility obligations, trademarks, terms, and other legal requirements.
Do not send passwords, payment information, confidential records, or member data through ordinary forms or email. Access and sensitive-data handling require an approved authorized method appropriate to the engagement.
07
ASSOCIATIONS & INDEPENDENCE
PMI, ISC2, and other chapter communities
No. PMI chapters are our primary specialization, but we can also serve ISC2, ISACA, IIBA, ASIS, other professional-association chapters, regional associations, trade groups, and similar membership organizations.
No affiliation, endorsement, or sponsorship is implied unless a formal relationship is explicitly stated. Association names identify the chapter communities we serve. All third-party names and marks belong to their respective owners.
Yes, when the chapter supplies current authorized guidance and assets. The chapter remains responsible for confirming its rights, approvals, and obligations with the parent association.
Only where the chapter has appropriate authorization and the parent association or platform provides a supported, permitted technical method. Access and feasibility are verified before inclusion in scope.
The short version
Start with the chapter’s needs. Document everything that matters.
The best engagement is clear about goals, scope, ownership, third-party dependencies, pricing, approvals, limitations, launch, and ongoing responsibilities before work begins.
- ✓ Requirements before platform
- ✓ Authorization before integration
- ✓ Written scope before work
- ✓ Testing before launch
- ✓ Continuity after handover
Still have a question?
Tell us what your chapter is trying to solve.
We’ll answer what we can, identify what needs discovery, and explain the most practical next step.