Project & Program Management Support

What this covers

Agencies often lack enough experienced project managers for the initiatives on their roadmap. HQT provides technical project and program managers who understand both the technology and public-sector governance.

Typical activities

• Project charters, plans, schedules, and budgets
• Governance and steering committee support
• Risk, issue, and change management
• Vendor coordination and contract administration support
• Status reporting for leadership and governing bodies
• Portfolio views across multiple projects

What you receive

Managed projects with documented plans, regular reporting, and organized project records.

Considerations for public agencies

Public projects operate under open meeting and public records rules and often under grant reporting requirements. Project records are kept with that in mind.

Signals that the project needs a dedicated manager

The case for this role is easier to make from specific conditions than from a general sense of being stretched. Common ones:

• The person running your largest initiative also carries a full operational workload, so planning happens after hours and slips first.
• Percent complete is reported with no deliverable, test result, or invoice behind it.
• The schedule has not been re-baselined since kickoff, although scope, staffing, or the vendor's release plan has changed.
• Risks are raised in meetings but never written down, or the register still holds only the entries made at kickoff.
• Decisions are made in conversation and then reopened, because no one recorded who decided and on what basis.
• A grant period or a statutory date is fixed and no one can name the tasks on the critical path to it.
• Several related projects touch the same system and no one holds the dependency view across them.

One of these is a staffing gap. Several at once usually means the project runs on individual effort rather than a method, which is what produces late surprises.

Where this work goes wrong

The failure modes are recognizable, and they are the reason to be specific about how the role is run. The manager drifts into scheduling meetings and taking notes. Status becomes a restatement of the vendor's own report with no independent check, so the project stays green until the month before go-live. The schedule carries only vendor tasks, which leaves agency-side work, data cleanup, policy decisions, subject matter expert time, user acceptance testing, and training, invisible until it is late. The plan lives in a tool only the contractor can open, so the agency cannot maintain it after the engagement. Change orders get signed without a written schedule, cost, and risk impact. Steering committees review slides instead of the baseline, the open decisions, and the risks that have not moved.

How the role sits with your vendor and your oversight process

An implementation vendor normally supplies its own project manager under its contract, and that person is accountable to the vendor for the vendor's scope. The agency-side role manages what the agency owes the project, decisions, data, environments, staff time, and acceptance, and holds the vendor to the deliverables in its contract. Keep assurance work separate as well. Independent verification and validation and owner's technical representative support exist to assess the project, so the person who maintains the schedule should not also be the person grading it. Some states require projects above a size threshold to pass through a central IT approval or independent oversight process, and thresholds and required artifacts vary by state and by funding source, so confirm what applies before the reporting cadence is set. Those submissions are built from the same schedule and risk data the manager maintains.

What to specify when you procure this role

• The role, the seniority level, and expected hours by phase, with a mechanism to adjust hours as demand changes.
• Key personnel terms: resumes and interviews for named individuals, and substitution only with written approval of an equivalently qualified replacement.
• Work products in editable formats, kept in systems the agency already owns, plus a turnover package and a transition period at the end.
• Organizational conflict of interest language stating plainly whether the firm or its affiliates may later bid the implementation this role helps manage or specify.
• A reporting line to the agency's executive sponsor rather than through the implementation vendor.
• Acceptance criteria written for documents and cadence rather than software. A baselined schedule accepted by the sponsor is a workable first milestone.
• Evaluation on a work sample, a real status report and risk register with client details removed, rather than on firm boilerplate.

Working with HQT on this

HQT scopes this kind of work as a fixed-price or time-and-materials engagement with a written statement of work, named staff, and a defined acceptance process. We are candid about what we can take on and prefer a well-run project to an oversized one. Contact us to discuss a requirement, a draft scope, or an upcoming solicitation.

Frequently asked questions