Manpower Clauses That Don't Fit AI Projects

A state mission copied last decade's system-integrator RFP and changed the title to Agentic AI. Clause 14 still said the bidder shall deploy eight graduate engineers onsite for the contract period, with attendance on Aadhaar-based biometric, substitution only with equivalent CVs, and a penalty per absentee day. The winning platform needed two people who understood retrieval and policy, a remote on-call, and a quarterly eval. It did not need eight chairs. The chairs arrived. The eval did not. When the agent began citing a repealed circular, the eight engineers opened a ticket on a product they could not change. Attendance was 98 percent. The noting quality was not.

This is a teardown of manpower clauses that fitted staff-augmentation and large custom builds, and that misfit agent platforms. The opinion is not that people do not matter. The opinion is that counting people is a poor proxy for a system that is supposed to draft, retrieve and wait for a human gate. Specify the outcomes, the on-call, and the skills. Let the vendor decide how many chairs to buy.

Not legal advice. Some organisations have genuine onsite-security reasons to want named people in a room. Write those reasons. Do not inherit a number from a 2016 TCS-shaped annexure.

Why the clause existed — and why the object changed

Manpower minima were a way to stop a bidder from winning on price and then vanishing. They were also a way to pretend a body-shop bid was a product. Attendance machines made the proxy auditable. For a three-year MIS customisation with daily change requests, the proxy was crude but not insane.

An agent platform is closer to a product plus a thin professional-services wrapper. The work that matters is eval design, tool allow-lists, prompt and policy change control, isolation drills, and sitting with the section that owns the file. That work is lumpy. It is not eight people filling timesheets because a clause said so.

If you force the eight people, you will pay for them. You will also select for firms that are good at supplying chairs, not firms that are good at keeping an agent inside a purpose tag.

Replace the left column. The right column is still auditable. It just audits the thing you wanted.

Inherited manpower sentence	What it was trying to buy	Write this instead
8 engineers onsite, biometric attendance	Someone is here if it breaks	On-call roster, response and restore times, named severity
CVs with 5 years Java	Skill, badly approximated	Named skills: retrieval, policy, isolation, Indic eval, DPA operations
No substitution without equivalent CV	Continuity	A runbook, a second pair, and a 10-day handover pack on file
Onsite project manager + weekly MOM	A throat to choke	A named vendor accountable manager and a department product owner
Training for 40 officers, 2 days	Adoption	Role-based training plus a measured error rate on the eval set after 30 days

When onsite is real, write the reason

Air-gapped rooms sometimes forbid remote support. Classified networks sometimes require an escort. A collectorate that has no reliable remote path may want a human in the NIC room during go-live week. Those are reasons. They produce a time-boxed onsite clause: go-live window, incident surge, quarterly drill — not a three-year occupation of a bench.

If the reason is 'we do not trust the vendor unless we can see them', you have a trust problem that eight junior engineers will not solve. Trust is logs, isolation, and a contract you can exit. Chairs are a comfort object.

Skills, not degrees

Ask for people who have shipped an isolated runtime, built a held-out Indic set, written a tool allow-list, or sat a deletion drill. Ask how they will staff nights and holidays. Do not ask for GATE scores, MCA percentages, or a blanket 'AI certification' from a three-day course.

If you must see CVs, see two: the accountable engineer and the accountable manager. A binder of eight interchangeable juniors is a staffing company's compliance pack, not a delivery plan.

• Outcome SLAs: eval floor, time-to-draft, override rate, incident restore.
• On-call: hours, escalation, language of the roster, air-gap support path.
• Skills matrix: five named capabilities, not a headcount.
• Time-boxed onsite only where the room requires a body.

Penalties that hit the wrong thing

A per-absentee-day penalty trains the vendor to keep chairs warm. A penalty on missed eval floors, missed restore times, or undeclared egress trains the vendor to keep the agent honest. You will get the behaviour you price.

Do not combine a heavy manpower penalty with a weak outcome SLA. You have told the vendor which document you will actually read.

Objections you will hear — and what to do with them

These are the lines that stall the file. Answer them in the room, then put the answer in the note. A spoken answer without paper will be forgotten by the next officer.

If we do not specify headcount, the vendor will under-staff.

Then specify restore times, eval cadence and a named accountable pair, with liquidated damages that hurt. Under-staffing that misses those is visible. Under-staffing hidden behind eight quiet juniors is not.

Finance will not pass a contract without a manpower schedule.

Give finance a skills-and-outcomes schedule with a price. If their template has a manpower table, fill it with the on-call roster and the time-boxed onsite windows, and say so in the note. Templates can be annotated. They should not silently redesign the buy.

Onsite staff are how we transfer knowledge.

Knowledge transfer is a pack, a joint run of the eval, and a department owner who can change a policy without the vendor. Shadowing eight people who cannot change the product is not transfer. It is company.

CVC likes to see named resources.

CVC likes to see a fair, non-restrictive specification and a file that matches the buy. Named accountable people are fine. A headcount that only one staffing-heavy bidder can meet is a restrictive specification. Write the reason for every named body.

What an on-call clause looks like when it is real

Name the window: for example, 8 a.m. to 8 p.m. on working days, and a named festival roster. Name the first response time and the restore time by severity. Name the air-gap path — jump host you own, dual control, recorded — or say support is on-site during the window because the room forbids remote. Name the language the roster can work in if your officers will raise tickets in a regional language. Name the two humans who are accountable, not eight CVs.

Then name what happens when they miss. A per-hour credit on restore, a right to step-in assistance, a right to exit if restore is missed three times in a quarter. That is still a commercial clause. It is just a commercial clause about the system, not about chairs. If finance needs a table, put the roster in the table and write above it: this is not a headcount deliverable.

Rewrite clause 14 in five working days

Take the inherited manpower annexure and run this red-pen. Do it before the estimate is locked, or the chairs will be in the sanction.

1. Day 1: list what you were afraid would happen if the vendor vanished. Those fears become SLAs and exit packs, not chairs.
2. Day 2: write on-call hours, air-gap support path, and two named roles.
3. Day 3: write the outcome measures and the first-year eval calendar.
4. Day 4: add time-boxed onsite only where the room or the go-live truly needs a body.
5. Day 5: delete biometric attendance for vendor staff unless you have a written security reason that survives the air-gap note.

How this shows up in the file

The note says: this is not a staff-augmentation programme. Headcount is not the deliverable. The deliverable is a system that meets the eval, the isolation drill and the restore times, with a named on-call. Any onsite presence is time-boxed and justified.

If a bidder still offers eight free engineers, do not score the gift. Score the eval.

This article is informational field guidance for Indian public institutions, not legal, procurement, security-accreditation or engineering advice. Confirm against the current Gazette, GFR, GeM term, CVC instruction, CERT-In direction, DPDP text, departmental manual and your counsel before you file it.

How to put this in the RFP, not the preamble

A P2 Procurement who searches “manpower clause IT tender” is usually drafting or scoring a bid. “Manpower Clauses That Don't Fit AI Projects” belongs in eligibility, the evaluation matrix, or a numbered annexure. If it only lives in the covering note, L1 will ignore it.

Eight engineers onsite for three years is how you staff a custom SI programme. An agent platform needs outcomes, an on-call roster, and named skills. Headcount theatre hides the missing SLA. QCBS weights are a choice you must publish before opening. Accuracy is a task plus a dataset, not a slogan. SLAs for agents must name tool-calls, human gates and log export — uptime alone is a hosting metric.

Do not let a vendor write the specification and then bid on it. Record unsolicited proposals. Pay for pilots that touch personal data. Write exit before you write go-live.

1. Move the control from the preamble into a scored or eligibility row.
2. Attach a one-page definition (accuracy, SLA, language, data handling).
3. Require an artefact in the technical bid, not a slide.
4. Extend the bid date if a corrigendum is material.
5. Minute the demo on your data, offline if you claimed air-gap.

Close this loop before the next CAB

Put “Manpower Clauses That Don't Fit AI Projects” on the next change-advisory or bid-opening agenda as a single line item with an owner. If it cannot earn a line item, it will not earn a control. The owner should be a P2 Procurement, not “the vendor.”

Revisit the item when the model, the GeM term, the region, or the SI changes. “manpower clause IT tender” is not a one-time workshop. It is a watch item. Date the last check. Unsigned watch items are souvenirs.