13.2 Interviews, Due Diligence, References & Selection

Interviews, Due Diligence, References, and Selection

Independent OpenExamPrep teaching for published PSP Domain 3 Task 2 knowledge is that selection is a diligence file, not a price sort. Chapter 12.4 published the evaluation factors and the ethics freeze. This section is what you do to the firms: interview the people who will touch the system, test whether the company can survive the job financially, confirm insurance and bonds, call references who will talk about punch lists and as-builts, verify manufacturer certification, screen technicians who will hold keys, and score the result on a weighted scorecard that can reject a rock-bottom installer who cannot program the VMS.

Exam focus: Interview programmers, not only salespeople. Ask references about punch-list behavior and as-builts. Factory letters and named technician certificates are different artifacts. Lowest price is not lowest risk.

Why diligence sits after the package and before the PO

A fair solicitation can still award a firm that will fail commissioning. Diligence is how you learn that before award, when the cost is a lost week of evaluation, not a live pharmacy without a working lock. Public owners still have to follow their statute—diligence is not a secret extra criterion you invent after opening prices. You publish that interviews, references, bonding, and certification will be scored or used as responsibility checks. Private owners have more interview flexibility; they do not have a license to skip the file.

Treat diligence as responsibility (can they perform?) sitting beside responsiveness (did they follow the instructions?). A complete bid form from a firm that cannot obtain a performance bond or a factory credential is a reject, not a bargain.

Interviews that test the work, not the brochure

An interview (or oral presentation, or demonstration) is a structured conversation with key personnel. Independent study for this task treats the salesperson as optional and the programmer, project manager, and lead installer as mandatory when the buy includes a live database, a VMS, or a cutover in an occupied building.

Ask questions the brochure cannot answer:

• Which VMS version is in the proposal, and who on the crew holds the current manufacturer certificate to administer it?
• How will you migrate the existing credential database without a Monday-morning lockout?
• Show the health-check or device-tree view you would leave the owner—not a marketing video.
• Who badges in at 02:00 for the pharmacy anteroom, and what is that person’s backup?
• What did you miss on the last hospital punch list, and how did you close it?

Score the named people, then write those names into the award (Chapter 12.3 already treated key personnel as commitments). A firm that sends a regional vice president and a rented programmer is telling you the night crew does not exist.

Demonstrations belong on this owner’s sample door or a recorded instance that matches the specified software tier. A dark conference-room demo of analytics is not proof Camera 12 will identify at the badge desk.

Worked clinic: two firms look equal on paper. In interview, Firm A’s technician walks the existing can, names the listed release module that will not fit, and describes the larger enclosure already in the unit-price sheet. Firm B’s salesperson says “we always make it work.” The interview is the diligence artifact that 12.4’s matrix cannot see.

Financial due diligence

Financial due diligence asks whether the firm can finish. Security installs are working-capital heavy: they buy cameras and panels weeks or months before the owner’s pay application clears. A thin firm wins low, cannot float the long-lead order, and disappears—or pulls labor off your site to chase a faster check.

Typical file items:

• Bonding capacity versus this contract amount (single-job and aggregate). A surety letter is stronger than a marketing sentence.
• Bank reference or evidence they can purchase long-lead material without owner prepayment—or a stored-materials clause you actually intended.
• Liens, judgments, bankruptcy, and tax liens in the jurisdictions where they will work.
• Backlog. A crew already committed to three hospitals cannot also staff your dock on the promised dates.
• Credit reviews where the owner’s policy requires them. You are not becoming their accountant. You are testing survival.

A low bid that is far below the independent estimate (12.4) is a financial flag as well as a scope flag. Either they missed Door 4’s pathway, or they cannot afford to do it right.

Insurance and bonding

Insurance is not a PDF decoration. Match the risk:

• Commercial general liability for premises and operations.
• Automobile if they drive to sites.
• Workers’ compensation as the jurisdiction requires.
• Installation floater or equivalent for material in transit and on site before acceptance.
• Professional liability if they are providing design-assist or calculations through their engineer.
• Cyber liability if they will join the owner’s network, image workstations, or hold video and credential data.

Ask for additional insured status, waiver of subrogation, and primary/noncontributory language when the owner’s template requires it. Expiry dates that land mid-install need a renewal covenant.

Bonds—bid, performance, and payment—are still the usual public-construction tools. A performance bond is a surety’s promise the work will be completed. A payment bond protects subcontractors and suppliers. Bonding is not a substitute for VMS skill. It is evidence a third party underwrote capacity. A firm that cannot bond a hospital pharmacy ACS is not “agile.” It is under-resourced.

Private owners sometimes waive bonds and rely on retainage and parent guarantees. That is a documented risk acceptance, not a free pass to skip insurance.

Reference checks that ask about punch lists and as-builts

Vendor-supplied references are a starting list, not the investigation. Call owner project managers and facility security leads on similar occupancies. Ask questions that predict Chapter 14 pain:

• Did they close the punch list, or did leftover cameras and unlocks linger past substantial completion?
• Were as-builts usable—device IDs matching the field, passwords documented, license keys in the owner’s name—or a pile of marked-up sales drawings?
• How many change orders were their missed existing conditions versus owner-directed extras?
• Did they train the operators who still work there, or a conference room that turned over?
• Would you let them hold keys again?

A glowing reference that never mentions punch or as-builts is a brochure. A blunt reference that says “they fought every leftover item and the as-built set actually matched the IDs” is gold. Record the call. Do not score a firm on a distributor’s email that says they buy a lot of cameras.

Worked warehouse: the incumbent’s reference admits they never delivered Door 4 as-builts and that the spare-pair note was lost. That is not “tribal knowledge.” That is a diligence fail you can score before you hand them another PO.

Manufacturer certification

Company authorization (the integrator is allowed to buy and warrant a product line) is not the same as named technician certification (a person who can program, update, and health-check that version). Ask for both. Certificates expire. A letter from 2019 for a VMS that has had two major releases is a souvenir.

Certification matters because listings, warranties, and access to factory support often depend on it. It also matters because the lowest-price installer who cannot program the VMS is the classic trap on this task. They can pull cable, mount a dome, and still leave a recorder that never records Camera 12 at the identification plane. On an IFB, treat missing required certification as non-responsible. On an RFP, weight programming skill so a cheap cable crew cannot win on price alone.

Do not accept “our partner will program it” unless that partner is a named subcontractor with the same diligence, insurance, and interview.

Criminal-background screening when technicians hold keys

Technicians who receive owner keys, access badges, pharmacy escort privileges, infant-ward access, or cash-room entry are not anonymous trades. Require criminal-background screening (and any drug screen or badging the occupancy already uses for similar contractors) to the owner’s written standard, before keys are issued. The standard should match what you require of officers and facilities staff who hold the same keys—not a weaker “vendor exception.”

Screening is not a personality test and not a license to demand irrelevant history. It is a control for people who can bypass the system they are installing. Record who was screened, who holds which keys, and how keys return at the end of shift. A firm that refuses screening for a key-holding crew is declining the job, not negotiating a courtesy.

If the work is outdoor camera poles with no key issue, do not invent a theatrical clearance. Match the access.

Conflicts of interest at selection time

Chapter 12.4 already covered gifts, bid-rigging, hidden OEM specifications, and the designer who also bids. This section adds the selection-time conflicts:

• An evaluator who is a former employee or spouse of a bidder.
• An integrator who sits on the evaluation committee while competing.
• Ownership stakes, referral fees, or a side agreement to buy leftover material from the winner.
• A reference who is secretly a subcontractor on the same bid.

Recuse and document. A weighted scorecard filled out by a conflicted scorer is a protest exhibit. Private owners still owe the file a recusal; “we are a family company” is not an ethics defense.

Weighted scorecards

A weighted scorecard turns published criteria into numbers before prices are opened (or, on a public RFP, according to the published order). Typical security weights might include price, similar-occupancy experience, schedule realism, factory-certified programmers, references on closeout behavior, bonding and insurance, and interview performance. The exact weights belong in the solicitation. Changing them after seeing a favorite firm’s number is the Chapter 12 ethics failure with a spreadsheet.

The scorecard is how you reject the lowest-price installer who cannot program the VMS without pretending price did not matter. If programming and certification are twenty-five percent, a cheap mount-and-run crew loses even when their goods line is low. If you needed only price, you needed an IFB on a fully defined commodity—and you still needed a responsibility check for the license to program.

Normalize scores. One evaluator who gives everyone a 10 except the incumbent’s rival is incumbency bias in digits. Average independent scores, then record the narrative: why Firm A’s reference on as-builts beat Firm B’s glossy interview.

Selection is the moment you either buy a programmer or buy a pallet. Section 13.3 is how project management keeps the award from colliding with a 26-week factory queue you never asked about.