Skip to main contentSkip to content
Knowledge Hubs

CPC Order XXVII — Suits by or against Government/public officers: Rules, Procedure, Evidence & Practical Guide

Quick answer

Order XXVII contains special procedural rules when Government or a public officer in official capacity is a party. It deals with the named party, authorised signing/verification, service/appearance through Government Pleader, reasonable time for instructions and the court’s duty to assist settlement where possible. It must be read with section 80 CPC where pre-suit notice applies.

Procedure is fact-sensitive. Order XXVII — Suits by or against Government/public officers should be read with the CPC sections, other connected Orders, applicable High Court amendments/rules and the court’s current e-filing/practice directions. A national CPC form does not override a valid local procedural requirement.

What Order XXVII — Suits by or against Government/public officers does in a civil suit

The Order is part of the First Schedule to the Code of Civil Procedure, 1908. Its rules govern a defined procedural problem rather than the substantive cause of action. Lawyers should therefore separate three layers: the substantive right/defence, the general CPC procedural requirements and the special mechanics introduced by this Order.

For government as party, authorised signing/verification, Government Pleader, appearance time and settlement duties, the court record matters more than a generic checklist. Pleadings, affidavits, authority documents, service records, hearing orders and exhibits should each show compliance with the precise rule invoked. High Court amendments can alter forms or local procedure, so the court/state version should be checked before filing.

Rule-control checklist

  • Identify the exact rule within Order XXVII — Suits by or against Government/public officers relied upon in the pleading/application/order.
  • Confirm the person signing, verifying, deposing, accepting service or appearing has the required authority and factual competence.
  • Use current court e-filing, affidavit, notarisation/attestation and pagination requirements.
  • Preserve service proof and every order affecting time, evidence or appearance.
  • Read the Order with sections on notice, evidence, costs, limitation and appeal relevant to the case.

Practical litigation workflow

  1. Frame the procedural issue. State why Order XXVII — Suits by or against Government/public officers is engaged and which rule applies.
  2. Collect authority/evidence. Do not draft from memory; obtain the corporate/government/affidavit record that proves the procedural assertion.
  3. Check local rules. Review the relevant High Court/District Court e-filing and procedural directions.
  4. Draft narrowly. Keep statements within the knowledge/authority required by the rule and distinguish legal submissions from facts.
  5. Serve and docket. Preserve portal filing receipt, process/service evidence and the next limitation/hearing date.
  6. Prepare the witness/officer. If the Order permits or requires attendance/cross-examination, select someone with actual knowledge of the records.

Evidence file

Maintain a single chronology with pleading version, verification/affidavit, board/department authority where relevant, annexure list, service proof, process fee, e-filing acknowledgement and each subsequent order. This makes procedural objections easier to answer and reduces inconsistency between pleadings and oral submissions.

Worked example

A contractor proposes to sue a State department. Before filing, counsel checks section 80 notice requirements, correctly describes the Government party, preserves the contract/claim record and plans service/appearance under Order XXVII rather than treating the department like an ordinary company defendant.

Common mistakes

  • Using a person with formal designation but no factual knowledge to verify/depose.
  • Ignoring State/High Court amendments or local e-filing practice.
  • Assuming compliance with this Order cures a defect under another CPC section/order.
  • Failing to preserve proof of service/authority and then trying to reconstruct it after objection.
  • Turning an affidavit or verification into argumentative legal submissions rather than controlled facts.

Drafting and court-file review for CPC Order XXVII — Suits by or against Government/public officers: Rules, Procedure, Evidence & Practical Guide

CPC Order XXVII — Suits by or against Government/public officers: Rules, Procedure, Evidence & Practical Guide should be tested against the actual forum’s amendments and practice directions before filing. Build a short rule memo identifying the central CPC rule, any applicable High Court amendment, local e-filing requirement and the procedural consequence sought. This prevents counsel from citing the correct central Order but using the wrong local form, affidavit practice or service step.

Run a factual-authority check. The signer/deponent/officer should have both legal authority and access to the facts needed for the statement. Keep board resolutions, government authorisation, delegation, corporate records or source documents as applicable. Where a deponent relies on records rather than personal observation, draft the affidavit/verification consistently with the evidentiary rule and identify the source.

Maintain a defect-and-cure log after filing. If the registry/court raises a procedural objection, record the defect, legal basis, cure, re-filing date and any order extending time. For CPC Order XXVII — Suits by or against Government/public officers: Rules, Procedure, Evidence & Practical Guide, this is especially useful because later appellate arguments often turn on what was actually filed/served and when.

Finally, ensure procedural compliance supports rather than obscures the substantive case. A perfectly formatted affidavit or corporate verification cannot replace proof of the underlying debt, breach, government claim or defence. The trial strategy should connect each procedural document to the relevant issue and exhibit.

Decision matrix, evidence retention and review sign-off

For CPC Order XXVII — Suits by or against Government/public officers: Rules, Procedure, Evidence & Practical Guide, the operational owner should document who decides, who prepares, who independently reviews and who retains the evidence. A useful RACI should cover the litigation counsel, authorised representative, factual witness and court/Tribunal filing owner. The control should specify the event that starts the workflow, legal/source reference, completion deadline, evidence expected and escalation point. This is more reliable than a narrative policy because the reviewer can test whether a real event was captured and completed on time.

The principal failure modes for CPC Order XXVII — Suits by or against Government/public officers: Rules, Procedure, Evidence & Practical Guide are wrong forum/local rule, limitation error, defective authority, weak service evidence and unindexed annexures. Convert these risks into explicit pre-release checks. Each material conclusion should have a source and a factual record; where a number, date, classification or legal status is used, the review file should show how it was derived. If management overrides the normal control, record the reason, approver and compensating check rather than silently changing the result.

Evidence retention should follow the life of the obligation, transaction or dispute. Keep the governing source version, submitted/signed document, supporting schedules, acknowledgement/order and later amendment/correction together. A screenshot can help prove the state of a portal, but it should not replace the underlying legal instrument or signed record. For recurring processes, preserve a period-by-period control log so a future auditor can distinguish current compliance from a document copied forward from the prior year. For CPC Order XXVII — Suits by or against Government/public officers: Rules, Procedure, Evidence & Practical Guide, retain the evidence categories identified on this page with the page-specific filing, approval, review or decision record.

Before the final action on CPC Order XXVII — Suits by or against Government/public officers: Rules, Procedure, Evidence & Practical Guide, verify the current forum rules, limitation and service record before filing or hearing. Record the review date and person responsible. If the applicable law, portal or regulator material changes after the review, reopen the control rather than relying on the earlier sign-off. This currentness discipline is especially important for 2026 pages because several major legal and regulatory frameworks transitioned during the year.

Frequently asked questions

What is the purpose of CPC Order XXVII — Suits by or against Government/public officers?

Order XXVII contains special procedural rules when Government or a public officer in official capacity is a party. It deals with the named party, authorised signing/verification, service/appearance through Government Pleader, reasonable time for instructions and the court’s duty to assist settlement where possible. It must be read with section 80 CPC where pre-suit notice applies.

Does Order XXVII — Suits by or against Government/public officers override High Court rules?

No. Check valid High Court amendments and local procedural/e-filing rules alongside the central CPC.

Is a procedural defect always fatal?

Not necessarily. Consequences depend on the defect, prejudice, curability, timing and court orders. Do not assume automatic dismissal or automatic cure.

What evidence should be retained?

Authority documents, pleading/affidavit, annexures, filing acknowledgement, service proof and relevant court orders.

Where can I verify the current central text?

Use India Code for the Code of Civil Procedure, 1908 and then check the relevant High Court rules/amendments for the forum.

Primary sources

Professional-use note. This page is a practical legal/compliance guide. Before a filing, appeal, regulated action or tax computation, verify the current Gazette/regulator text, live portal requirements, jurisdiction and your facts.

Last reviewed against primary sources: 30 September 2026.