Technology Advisory & Systems Engineering
Owner's Technical Representative
Independent oversight of vendor implementations on the agency’s behalf.
What this covers
When an agency implements a major system, the vendor's project manager works for the vendor. An owner's technical representative works for the agency: reviewing deliverables, tracking risk, and making sure the implementation matches the contract.
Typical activities
- Review of vendor plans, designs, and deliverables against contract requirements
- Risk and issue tracking with escalation to agency leadership
- Change request analysis and negotiation support
- Test planning and acceptance oversight
- Data migration validation
- Go-live readiness assessment and post-implementation review
What you receive
Regular status reporting, deliverable review records, a risk register, and readiness and acceptance recommendations.
Why it matters
Large implementations fail quietly through scope drift, skipped testing, and unverified migration. Independent oversight catches those problems while they are still fixable.
Signals that the agency can no longer verify what the vendor reports
The test is not whether the project is late. It is whether anyone on the agency side can independently confirm what the vendor says is done.
- Status reporting originates only with the vendor's project manager, and no one on staff can confirm that a task marked complete is complete.
- Design documents and configuration workbooks are approved by staff who had no time to read them, or approved by default when a review window expires.
- Change requests are justified as out of scope for items that appear in the solicitation or in the vendor's own proposal, and nobody is reading those documents against the request.
- Schedule slips are absorbed by the testing window rather than the build window.
- Data conversion is scheduled late and has no reconciliation method defined beyond record counts.
Any one of these can be handled in-house. Several at once usually means the agency cannot hold the vendor to the contract it signed.
What to require in the solicitation and the contract
An owner's technical representative has only the standing and access the contract gives it, and that is easy to narrow later:
- An organizational conflict of interest provision barring the representative from reselling or implementing the product under oversight, or holding a partner or referral relationship with its publisher, with a continuing duty to disclose during the term.
- A reporting line to the project sponsor or steering committee rather than through the implementation vendor or the staff whose contract is being reviewed.
- Named key personnel, with substitutions subject to agency consent, since the work depends on the judgment of specific reviewers.
- Access rights written into the implementation contract as well as the oversight contract: attendance at design and test sessions, access to the vendor's defect tracker, test evidence, and non-production environments, and draft deliverables issued early enough to be read.
- Review turnaround commitments in both directions, so oversight never becomes the reason a deliverable is late.
- A statement that the representative advises the agency and does not direct the vendor.
- A pricing structure that survives a slip, such as time and materials with a not-to-exceed ceiling, or fixed price by phase with a stated rate for extensions. Oversight that ends on the original go-live date leaves the highest-risk weeks uncovered.
Scope that reaches past the implementation vendor's contract
The vendor's contract covers the vendor's product. Much of the unmanaged risk sits at the boundaries: interfaces to finance, identity, GIS, records, and payment systems owned by other departments or vendors, conversion from legacy sources nobody examines in detail until late, and components delivered by a subcontractor the agency never evaluated. Scope the representative to read the subcontracting arrangements and to press interface and conversion work earlier in the schedule, because no single vendor can sequence that work alone.
Check the requirements attached to the money before scoping. For some federally funded state systems, including certain health and human services programs, an independent verification and validation function may be expected as a condition of funding approval, and many states run central review of large technology projects through the state CIO or an equivalent department of technology. Those rules decide whether this role can be combined with that function in one contract or bought separately.
How to tell whether the oversight is working
Review comments carry a recorded disposition of accepted, rejected, or deferred with the reason attached, rather than delivered verbally in a meeting. Acceptance recommendations rest on traceability from requirement to test case to executed result rather than on a demonstration. Findings reach the vendor before they reach the steering committee, so the vendor's response travels with them. The representative also says when the vendor is right and the agency is the source of delay.
The failure modes are as visible. Oversight that restates the vendor's status deck, records no written disagreement across an entire project, or begins directing vendor staff has stopped doing the job, and a representative who has not read the deliverable definitions in the contract was never doing it.
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
What is the difference between an owner's technical representative and independent verification and validation?
An owner's technical representative works alongside the implementation as it proceeds, reviewing what the vendor produces and advising the agency's sponsor as decisions come up. Independent verification and validation is usually a formal assessment against a defined method or standard, produced on a set cadence and often written for an oversight body or a funding agency as well as for the project. Some agencies buy both, and some cover both functions in one contract. Settle in the scope who receives findings, how often, and in what form.
Do we need an owner's technical representative if we already have a project manager?
They cover different gaps. A project manager runs the agency's side of the work: staffing, decisions, communications, and schedule. A technical representative judges whether the vendor's designs, configurations, test results, and converted data actually satisfy the contract, which takes experience with the kind of system being implemented. If only one can be funded, decide whether the real exposure is coordination or technical verification.
Can the firm that helped write our RFP also serve as the owner's technical representative?
Often yes, and knowing how the requirements were written is an advantage, provided that firm is not bidding on the implementation and has no relationship with the winning vendor. The disqualifying problem is a financial tie to the product under oversight, such as reselling it, implementing it as a partner, or receiving referral fees. Agencies normally handle this with an organizational conflict of interest clause and a written disclosure that stays in effect for the term. Some states and funding programs add their own restrictions, so confirm those before the solicitation is issued.
Can we add an owner's technical representative after the implementation has already started?
Yes, and it commonly happens after a missed milestone, a disputed change order, or a failed test cycle. The first phase looks different: read the contract and the deliverable definitions, find out what has already been formally accepted, and baseline the current state before starting forward-looking reviews. Because earlier decisions are already locked in, the value concentrates in testing, data conversion, interfaces, and go-live readiness.
Does an owner's technical representative have authority to direct the vendor or stop work?
No. The representative advises the agency, and direction to the vendor comes only from the agency through its contract administrator or project sponsor. That line matters legally as well as organizationally, because direction from someone outside the contracting authority can support a vendor claim that the agency changed the work, often called a constructive change. State the limit in the contract so nobody has to infer it mid-project.