Skip to main content

Case study · Workforce Partners Management Group

Connecting workforce learning, case management, and operational systems across a long-term partnership.

For more than ten years, PageUP has worked with WPMG across public websites, consulting, custom applications, workforce learning, practical AI, and privacy-sensitive operational systems. The technology changes with the program, but the responsibility remains consistent: understand how the work operates, build the right structure around it, and support the people accountable for the result.

A long-term PageUP–WPMG relationship spanning websites, private applications, practical AI, reporting, communications, and continuing system development.

Websites · Business Systems · Practical AI · Case Management · Reporting · Ongoing Consulting

  1. Completed

    Housing-assistance case management

    Operating responsibility
    Case records, payments, reporting, and communication
    Evidence boundary
    Privacy-safe lifecycle; protected records stay private.
  2. Public presentation

    Quick Bites workforce learning and AI coaching

    Operating responsibility
    Practice and preparation within agency-defined programs
    Evidence boundary
    Public presentation and demo-request path.
  3. Current development

    Childcare-provider portal

    Operating responsibility
    Related records, permissions, documents, and staff review
    Evidence boundary
    Architecture and responsibilities; no protected screens.

The operating context

Different programs create different responsibilities for people, records, evidence, and follow-through.

WPMG's public history spans workforce consulting, transition assistance, job readiness, training, employment support, self-sufficiency programs, and related services. Those programs are not interchangeable. Each one brings its own participants, staff responsibilities, information, decisions, reporting needs, and boundaries.

PageUP's role across the relationship has been to understand those differences before choosing the interface or technology. Sometimes the result is a public website. Sometimes it is a private case-management application, an AI-supported learning experience, or a portal that connects records, documents, permissions, and review.

The common thread is not one software package. It is an operating model translated into a system people can use.

One partnership · distinct systems

The work changed as WPMG's programs and opportunities changed.

  1. Completed system

    Waco Housing Authority engagement

    A private online case-management application connected applicant intake, assistance awards, payments, receipts, remaining-budget tracking, reporting, permissions, and client and staff communication. The engagement concluded in late September 2025.

  2. Current public proof

    Quick Bites

    An agency-customizable workforce learning and AI coaching experience supports interview practice, résumé and job-search work, and related guidance. The public presentation introduces the concept and provides a path to request a private demonstration.

  3. Current development

    Childcare-provider portal

    A separate portal is organizing enrollment, related parent contacts, documents, PDFs, signatures, corrections, permissions, staff review, migration, and rollout around the needs of childcare-provider operations.

These are separate engagements with different users, records, risks, and stages of completion. They are presented together only to explain the long-term relationship and the architectural judgment carried from one operating problem to the next.

Responsibility before technology

PageUP's role extended from discovery and architecture through implementation, verification, and continuing support.

Understand the operation
Identify the people, records, decisions, exceptions, evidence, and outcomes the system must support.
Model the information
Define relationships among applicants, cases, parent contacts, facilities, payments, documents, statuses, and other records without flattening unlike information into one form.
Design access and responsibility
Give participants, staff, reviewers, case managers, providers, and administrators the views and actions appropriate to their roles.
Build the working application
Use WordPress, Divi 5, Gravity Forms, GravityView, custom PHP, and supporting services where they fit the operating requirements.
Connect communication and evidence
Tie email, text messages, PDFs, receipts, signatures, reports, and status changes to the underlying record and workflow.
Migrate, test, document, and improve
Move existing information carefully, verify ordinary and exception paths, document the system, support rollout, and continue refining active work.

The platform matters. The larger responsibility is making sure the platform reflects how the work actually operates.

Completed operational system

Connect the case from applicant intake through payment records, reporting, and communication.

For WPMG's Waco Housing Authority engagement, PageUP built an online case-management system around the full working record rather than a collection of unrelated forms and spreadsheets.

  1. Record

    Applicant intake

    Information entered through the website created the starting case record.

  2. Responsibility

    Case administration

    Authorized staff reviewed and managed assistance activity within role-aware views.

  3. Record

    Awards and payment categories

    The application recorded assistance awards and tracked remaining funds by payment category.

  4. Evidence

    Payments and receipts

    Client-payment records and supporting receipts remained attached to the case.

  5. Evidence

    Reporting

    Structured reports supported state reimbursement submission and management review.

  6. Communication

    Communication

    Email and text status updates kept clients and staff informed at defined points in the process.

  7. Oversight

    Oversight

    Reporting supported review of case-manager activity and program administration.

Granular permissions, custom roles, Gravity Forms, GravityView, and extensive PHP customization supported requirements that went beyond a standard website workflow.

The engagement concluded in late September 2025. The public case study describes the system's responsibilities without exposing its records or protected interfaces.

Practical AI for workforce learning

Use AI to support practice and reflection within a defined learning experience.

Quick Bites combines workforce-development content with AI coaching for areas such as interview practice, résumé work, job-search support, and related preparation. It is not presented as an autonomous employment adviser or decision-maker. The AI supports a defined learning purpose while the agency determines the program requirements and the people responsible for delivery.

Agency-customization areas may include

  • program priorities and participant needs;
  • approved learning content and terminology;
  • coaching scenarios and practice activities;
  • agency-specific resources and next steps;
  • boundaries, escalation, and staff responsibility;
  • presentation, access, administration, and reporting requirements.

Quick Bites is currently being previewed to prospective agencies. Its public page provides an audio presentation and a demo-request path; the AI experience itself is shown privately rather than offered as an unrestricted public demonstration.

Current application development

Model related people, records, documents, and permissions without exposing the families behind them.

The new childcare-provider portal is a separate WPMG project. Its architecture organizes child enrollment, related parent contacts, facility-aware access, documents, PDFs, signatures, corrections, staff review, status, migration, and rollout support around the actual relationships in the work.

The portal is described through its data relationships and workflow. Personal records, signed documents, and protected interfaces remain private.

Related records
Parent contacts can be associated with the appropriate child records without repeating or fragmenting the relationship.
Role-aware access
Providers and staff receive access appropriate to their facility and responsibility.
Documents and signatures
PDFs, uploaded evidence, signatures, corrections, and review remain connected to the right workflow.
State and communication
Status controls what happens next and supports timely notices to the people involved.
Migration and safeguards
Existing information is matched and moved with dry runs, exception review, verification, and recovery planning.

The systems-minded pattern

Different interfaces can still share the same discipline.

  • People and roles

    Identify who participates, what each person is responsible for, and where access must differ.

  • Records and relationships

    Define what must remain connected and what must stay separate.

  • States and exceptions

    Model not only the ordinary path but also corrections, incomplete information, reassignment, and review.

  • Evidence and communication

    Keep documents, receipts, signatures, reports, messages, and history attached to the work they explain.

  • Oversight and recovery

    Support verification, reporting, migration review, and correction without treating the system as infallible.

  • Continuing responsibility

    Maintain documentation, support active systems, and adapt the implementation when the operation changes.

The reusable asset is not a generic template. It is the discipline required to understand the operation before building around it.

Start with the operating responsibility

Start with the process people need to carry through.

Describe the people involved, the records and evidence they rely on, where the work changes state, and what a dependable result must make possible. PageUP can help determine whether the answer is a focused workflow, a private portal, an integration, a practical AI experience, or a larger application.