
Client: PricewaterhouseCoopers
Industry: Professional Services / Accounting & Consulting
Project: Human Capital Resource Management & Resource Enablement
Technology: Quickbase, ServiceNow, Zycus, Workflow Automation, Role-Based Access Controls
Use Case: Human Capital Resource Management, Workforce Request Management, Recruiting Operations, Employee & Contractor Onboarding, Approval Automation & Resource Lifecycle Management
PwC is a global professional services organization whose operations depend on the ability to coordinate people, skills, approvals, and resources across a complex enterprise environment.
At that scale, workforce management extends far beyond maintaining employee records:
PwC uses Quickbase as a Resource Enablement platform designed to connect those activities within a centralized operational environment.
The application supports requesting, fulfilling, recruiting, onboarding, offboarding, and tracking activity over time for both FTE and third-party labor resources, while role-based security determines which functionality and information different users can access.
Rather than treating resource requests, recruiting, approvals, onboarding, and workforce administration as separate activities, the platform creates a more structured path from: Resource Need → Request → Review → Approval → Recruiting/Fulfillment → Onboarding → Active Resource → Offboarding
The result is a stronger operational foundation for managing workforce activity across multiple teams, roles, and stages of the employee and contractor lifecycle.
Human capital resource management becomes considerably more complex when every request must move through multiple business functions.
A hiring manager may initiate the need, but fulfilling that request can require participation from Human Capital, Resource Operations, recruiting, finance, leadership, project teams, and other approvers.
PwC's application was expected to serve a broad internal user population while controlling access to specific functions and artifacts according to security roles.
The documented roles include:
That creates a fundamental process challenge: How do you coordinate a workforce request across many stakeholders without losing visibility, accountability, or control?
The process also spans different worker populations and source systems.
Zycus data was initially planned for manual import, while ServiceNow was identified as an integration; therefor, PwC needed more than a database of employees, it needed an operational system capable of answering:
Without a connected workflow, those questions require teams to reconstruct information across systems, stakeholders, and process stages.
Quandary Consulting Group supported the development of a Quickbase application designed to bring the workforce resource lifecycle into a more structured operational model.
The engagement used a Rapid Application Development approach, focused on creating an MVP that could accelerate time to value while establishing a platform PwC could continue owning and evolving internally.
The resulting architecture centers workforce activity around a shared resource lifecycle rather than disconnected transactions.
One of the most important elements of the application is its ability to support both full-time employees and third-party labor.
This creates a common operational structure for resource demand.
Hiring managers can initiate resource needs within a standardized environment rather than allowing requests to originate through inconsistent channels.
From there, requests can move through the appropriate fulfillment, recruiting, approval, onboarding, and administrative processes.
This gives PwC a clearer system of record for understanding what resources have been requested, why they are needed, and where each request stands.
Not every participant in a resource process needs the same information or capabilities.
PwC's documented application model includes numerous operational and approval roles, ranging from hiring managers and recruiters to Finance, Resource Operations, Human Capital, Chiefs of Staff, and leadership.
Quickbase allows the workflow to reflect those organizational responsibilities. Users can interact with the information and actions relevant to their role while sensitive functionality and artifacts remain restricted.
The application becomes a coordination layer between teams rather than simply a repository of records.
Resource requests can require decisions from multiple parts of the organization.
The roles include specific approval responsibilities for ITSCo, Resource Operations, Finance, and CAO leadership, demonstrating the need for structured governance around resource decisions.
Centralizing these approvals in a workflow can establish a consistent path for each request. Which meant that instead of relying on employees to determine who should review something next, workflow logic can help route requests according to defined business requirements.
This creates clearer accountability and a stronger record of how workforce decisions move through the organization.
ServiceNow was identified as a required integration for launch, with employee and contractor data expected to enter the Resource Enablement environment through that connection.
That integration is important because workforce applications become less reliable when employees must repeatedly recreate information that already exists elsewhere.
Connecting ServiceNow with Quickbase creates the opportunity for PwC to establish a more consistent flow of workforce information: ServiceNow → Employee/Contractor Data → Quickbase Resource Workflow → Operational Action
Quickbase can then focus on orchestrating the resource management process around that information rather than becoming another disconnected source of duplicate workforce data.
Third-party labor introduces another data requirement: Contractor company information.
PwC identified Zycus as the source for contractor company data, with an initial model based on manual imports and the possibility of periodic imports thereafter.
Bringing this information into the same resource environment helps connect third-party workers with the companies and resource requests surrounding them.
That creates greater consistency between resource demand, contractor organizations, workforce records, and operational activity.
The Resource Enablement application is designed to support more than hiring.
Its scope extends across: Requesting → Fulfilling → Recruiting → Onboarding → Resource Activity → Offboarding
That lifecycle approach is strategically important, because many workforce systems concentrate on one stage of the process. Recruiting systems manage candidates. HR systems maintain employee records. Procurement systems manage vendors.
Operational teams, however, need to understand how those stages connect.
Quickbase provides an orchestration layer around the lifecycle so PwC can maintain continuity from the original resource need through the eventual transition or offboarding of the worker.
The application was also intended to track resource activity over time, giving PwC a historical view of how workforce records and requests evolve.
That historical context creates a stronger foundation for operational analysis. Which means that, instead of seeing only the current state of a request or resource, teams can better understand the lifecycle surrounding it.
This can support process improvement, workforce planning, governance, and future analysis of how resource demand moves through the organization.
PwC identified reporting as an important component of the Resource Enablement environment.
The organization wanted reporting comparable to existing ServiceNow dashboards, including monthly, quarterly, and annual views; position totals by country and company; outstanding requests; and request statuses.
This transforms the application from a workflow tool into an operational intelligence platform. Leadership and operational teams can begin evaluating questions such as:
The value is not simply having more reports, it is to create a shared dataset from which those reports can be generated consistently.
The use case as included, Beeline and Randstad, as potential later-phase integrations, while PwC's proprietary system was considered as another possible data source.
This gives the Quickbase environment room to evolve. The immediate architecture can solve current resource management requirements while creating a foundation for a broader connected workforce ecosystem over time.
Conceptually, that architecture can progress toward: Enterprise Workforce Systems → Quickbase Resource Enablement → Workflow & Approvals → Recruiting & Fulfillment → Workforce Reporting
Rather than rebuilding the application every time another system becomes relevant, PwC can extend the operating model as requirements mature.
By centralizing resource requests, recruiting coordination, approvals, onboarding, offboarding, employee and contractor information, and operational reporting, PwC can create a more structured approach to managing workforce demand across the organization.
The impact extends across the resource lifecycle:
The result was a more connected workforce management model in which PwC can coordinate people, processes, approvals, and workforce data through a shared operational platform.
Standardized resource requests, structured workflow routing, centralized status information, and role-specific responsibilities reduced the administrative work required to move workforce requests from initiation through fulfillment.
Bringing hiring managers, Human Capital, Resource Operations, recruiters, and approvers into a shared workflow reduced reliance on manual coordination between teams. Which meant that PwC employees no longer needed to repeatedly asking where a request stands, the status became part of the operational record.
Structured approval workflows reduced delays caused by manually routing workforce requests between Resource Operations, Finance, ITSCo, leadership, and other stakeholders.
ServiceNow integration provided an opportunity to bring existing employee and contractor information into Quickbase rather than requiring users to recreate the same information manually.
A centralized workflow made approved resource demand visible to the teams responsible for recruiting and fulfillment without requiring separate handoffs.
Connecting workforce requests with downstream onboarding activities gave Human Capital and Resource Operations greater visibility into what must happen before a resource became operational.
Centralized request and resource data significantly reduced the effort required to assemble recurring workforce reports.
Centralized status visibility and clearly assigned responsibilities made it easier to identify requests that are waiting for action.
Standardized request structures, required information, role-based workflows, and integrated source data improve the completeness of resource records.
The larger value of the PwC Resource Enablement environment is not simply digitizing a hiring form.
It is creating a connected operating model around how workforce demand becomes workforce capacity. A hiring manager identifies a need
And the information generated throughout that process becomes available for operational reporting; this created a much more valuable progression: Workforce Demand → Resource Request → Governance → Approval → Recruiting/Fulfillment → Onboarding → Active Resource → Lifecycle Management → Workforce Intelligence
Instead of workforce information existing only as records inside individual systems, Quickbase creates an operational layer connecting the people and processes responsible for acting on that information.
By combining Quickbase rapid application development with workflow automation, role-based access, ServiceNow integration, contractor data, and enterprise workforce reporting, PwC establishes a scalable foundation for managing resource demand across both employees and third-party labor.
Services
Industries




© 2026 Quandary Consulting Group 2026. All Rights Reserved.
Privacy Policy