Answers for common SubdiviCore questions.
A quick reference for teams evaluating the platform, rollout scope, onboarding needs, and daily operating workflows.
What most communities ask first.
These answers keep the brochure clear before a deeper walkthrough.
Is SubdiviCore only for large subdivisions?
No. The platform can start with core admin, resident, and request workflows, then expand into billing, facilities, security, patrol, and work-order operations as the community grows.
What parts of subdivision operations does SubdiviCore cover?
SubdiviCore connects HOA/admin records, resident self-service, billing visibility, announcements, documents, service requests, work orders, facility bookings, gate access, visitor activity, incidents, patrols, guard handovers, and service execution across one platform.
Can residents, guards, service teams, and admins use different apps?
Yes. Admin teams use the web dashboard, residents use the Resident Mobile App, guards use the Security Mobile App, and maintenance staff or service providers use the Service Mobile App. Each surface is shaped around the records, actions, and access boundaries for that role.
Can each subdivision keep its own records separate?
Yes. SubdiviCore is designed around subdivision-scoped records and role-based access so residents, households, guards, service users, and admin teams only work within the community data assigned to them.
Can residents submit service requests?
Yes. Residents can raise requests or concerns from the mobile app, while admins can review details, decide whether work-order execution is needed, and keep the request history organized.
Can maintenance staff or service providers update work orders?
Yes. The service mobile app is designed for assigned work orders. Service users can update execution details such as progress, staff notes, materials, costs, and close-out notes while assignment and final administrative control stay with the admin team.
Does SubdiviCore support billing and payment proof tracking?
Yes. The platform supports dues and fee visibility, payment proof submission, receipt-related workflows, and admin follow-through for subdivision collections.
Can residents book subdivision facilities?
Yes. Facility booking workflows can show available amenities, booking details, and admin-managed approval or coordination steps based on the subdivision's process.
Does the system help with gate access and visitors?
Yes. Resident QR access, visitor-related records, gate activity, and guard-side verification workflows are part of the security and resident experience.
Can guards record incidents and patrol activity?
Yes. The security app supports field workflows for incident records, patrol routes, checkpoints, gate logs, visitor checks, and shift handover context.
Can admins publish announcements and documents?
Yes. Admin teams can manage community notices, operational updates, and important documents so residents and teams have clearer access to shared information.
Does SubdiviCore replace the subdivision office team?
No. It gives the office, guards, service teams, and residents a clearer operating system, but approvals, policies, collections, and community decisions still follow the subdivision's own process.
How does onboarding usually work?
Onboarding starts by identifying the community's records, roles, priority workflows, and launch scope. From there, setup focuses on the modules that matter most before expanding into deeper operations.
How long does a typical rollout take?
Timeline depends on the number of homes, data readiness, active modules, and training scope. A focused launch can start with core records and priority workflows, then add deeper billing, facility, and security operations in phases.
How is SubdiviCore pricing calculated?
Pricing is based on the selected package, the number of homes in the subdivision, one-time setup work, and the monthly subscription tier. Optional services such as AI, email notifications, and SMS notifications are quoted separately when needed.
Can we start with one package and upgrade later?
Yes. A subdivision can start with the package that matches its current operating needs, then move into resident, security, service, or add-on workflows as adoption grows and the community is ready for a wider rollout.
Can existing resident and property records be migrated?
Yes. Existing resident, property, household, vehicle, and billing-related records can be reviewed during onboarding so the launch plan accounts for cleanup, formatting, and import needs.
Will our office team and guards need training?
Yes. SubdiviCore rollout should include orientation for admin users, finance or operations staff, guards, and any service teams so each group understands the workflows, access boundaries, and records they are responsible for.
How do residents, guards, and service users get app access?
Access is prepared around the subdivision's records and approved users. Residents, household users, guards, maintenance staff, and service providers should only receive the app experience and data scope assigned to their role.
What is the difference between the Resident, Security, and Service mobile apps?
The Resident Mobile App is for household self-service, notices, billing visibility, bookings, requests, and access workflows. The Security Mobile App is for guard operations such as gate activity, visitor checks, incidents, patrols, and handovers. The Service Mobile App is for assigned maintenance or provider work orders, progress updates, materials, costs, and close-out notes.
Is the Service Mobile App for in-house staff or outside providers?
It can support both, depending on the rollout scope. A subdivision can use it for internal maintenance teams, approved service providers, or assigned contractors while keeping work orders and execution updates tied to the proper service accounts.
Are email and SMS notifications included?
Email Notifications and SMS Notifications are optional add-ons per subdivision. They can support billing reminders, account verification, visitor updates, facility booking messages, service request updates, emergency alerts, and other notification-heavy workflows when the community needs them.
Does SubdiviCore process online payments?
SubdiviCore supports billing visibility, dues records, payment proof submission, receipts, and admin follow-through. Direct online payment collection, payment gateway setup, or bank-specific integration should be confirmed separately during rollout scoping.
Can package scope change per subdivision?
Yes. The four packages provide a clear starting point, and pricing is organized around homes per subdivision. Final scope can still account for subdivision size, onboarding work, historical data migration, launch priorities, optional add-ons, and support needs.
Can the platform be customized for a subdivision's rules?
Yes. Rollout scope can be adjusted around the subdivision's policies, active modules, staff roles, approval steps, and the records that need to be migrated or maintained.
What support is included after launch?
Support can include launch assistance, workflow guidance, user orientation, issue follow-up, and scope-based adjustments after real residents, guards, service users, and admin teams start using the platform.