Documentation a Government Body Will Accept

A Government Body Asks Whether the File Is in Order Before It Asks Whether the Project Is Good

A private counterparty who receives a strong proposal in an imperfect format reads it anyway. A public authority frequently can't.

Submissions to ministries, state industrial bodies, licensing authorities and subsidy administrators pass a compliance check before reaching anyone whose job is to form a view.

A submission that fails that check is returned without its merits having been considered at all.

The applicant experiences this as a rejection of the project. It wasn't. It was a determination that the file wasn't yet in a state where the project could be assessed.

The reason isn't bureaucratic temperament.

A public official acts under delegated authority, spends public money, and can be asked afterwards to justify what they did and on what basis. By an auditor, a legislature, a court, or a successor in the same chair.

That accountability produces a documentary culture with a specific property. The file must speak for itself, years later, to a reader who wasn't present and can't ask anyone a question.

Every requirement that looks like formality serves that property. A prescribed format ensures the file contains what a later reader needs. An attestation records who is answerable for a figure.

This article sets out what that means for the document: why format compliance is a gate before merit, how a submission is condensed into a file note and what survives, why a figure without a traceable source is worse than no figure, what annexure discipline requires, and why a sanction begins the conditions rather than ending them.

One caution belongs at the front. Public administration differs between jurisdictions, between departments, and between schemes run by the same department. Nothing here states the procedure of any named authority or substitutes for the published rules of the specific scheme.

In Government Documentation, Format Compliance Is a Gate Most Files Fail At

The first person to handle a submission generally isn't assessing it. They're checking it against a list.

Are the prescribed forms present and in the prescribed version? Are annexures numbered and cross-referenced as required? Are attestations signed by persons holding the offices the scheme specifies? Is the applicant eligible on the face of the documents?

That check has a binary outcome, and it happens before anyone forms any view about the project.

Applicants underestimate this stage because it has no analogue in commercial dealing.

An appraiser who likes a proposal asks for the missing document and keeps reading. A scrutiny clerk working to a checklist frequently can't.

The file is incomplete, and an incomplete file returned is the correct disposal under the procedure they're working to.

The judgement being exercised is about the checklist, not the applicant. Appealing to the strength of the project has no purchase at that desk, because the strength of the project isn't what's being determined.

The most expensive version of this is version drift.

Schemes publish forms and revise them. A form downloaded months earlier, or reused from a previous application, may have been superseded.

The content may be identical in substance and the file is still returned, because the officer can't certify the applicant furnished the prescribed form when the prescribed form is a different document.

Confirming the current version of every prescribed document on the day of filing is a five-minute task that removes an entire class of failure.

The corollary changes how preparation time should be allocated. Effort spent perfecting the analytical case has no value if the file doesn't clear the gate, and clearing the gate has no value if the case then fails on merit.

Your Submission Will Be Summarised by Someone Junior, and the Summary Is What Travels

A file in a public office accumulates notings. A dealing official records what was received, what the scheme requires, whether requirements are met, and what they recommend. The next officer reads that noting and adds their own.

By the time the file reaches the person with authority to decide, it carries a chain of notings. The reading runs down that chain rather than through the original document.

The consequence is easy to state and hard to internalise. Anything in the submission that doesn't make it into the first noting has, for practical purposes, not been read by the decision-maker.

A technical certification, a completed statutory clearance, a signed offtake arrangement, an independent study supporting demand: each is decisive if it appears in the noting and close to invisible if it doesn't.

Whether it appears depends not on how important it is but on how easy it was to extract while reading under time pressure.

The remedy is structural. State each substantive point once, plainly, in a form that can be lifted into a noting without rewriting: a short declarative sentence, the figure, and the source.

Long paragraphs burying the key fact in the fourth clause don't survive. The official summarising isn't hostile. They're extracting, and what's hard to extract is left.

A summary table at the front, with project, cost, means of finance, employment, timeline and eligibility basis each carrying its annexure reference, is frequently the most valuable page in the file. It's the page the noting is written from.

Each noting is signed and dated, so an official adopting a figure has attached their name to it. That exposure explains behaviour applicants misread as caution: one who can't see where a number came from won't adopt it.

In a Public File, a Figure Without a Source Is Worse Than No Figure at All

In a commercial negotiation an unsupported figure can be argued or traded. In a public file it's a number an official can't adopt, because nothing establishes it and a later reader will ask what it rested on.

Their options are to attribute it explicitly to the applicant, which signals it's unverified, or to raise a query. Either way the applicant has spent a cycle.

An unsourced figure is worse than no figure. One asserting a specific number with nothing behind it puts into a permanent record a claim that can't be substantiated, and a reader who finds one untraceable figure reads the rest differently.

What counts as a source is narrower than applicants assume.

A published statistic from an identified official or industry publication, with publication and period stated. A technical report by a named professional carrying their qualification and date. A signed contract or firm quotation, referenced to its annexure. An operating history from audited accounts with the years identified.

What isn't a source: a market size described as widely accepted, a growth rate attributed to industry expectations, a comparison to unnamed similar projects, or a number that appears in the model with nothing behind it.

Derived figures are where careful submissions most often fail. A revenue projection isn't a source even when every input is sourced. It's a calculation, and the calculation must be traceable.

Showing the volume assumption, its source, the price assumption, its source, and the arithmetic between them converts an assertion into something an official can adopt on their own authority.

One version catches even careful applicants: the figure sourced when written and no longer current when read. A revised tariff, a superseded statistic, a quotation past validity. In a permanent record a stale citation is a defect, and it's generally noticed.

The Annexures Are Not an Appendix; They Are Where the File Is Actually Proved

In commercial documents an appendix holds supporting material so it doesn't interrupt the argument, and readers rarely go there.

In a public submission the relationship inverts. The main document asserts; the annexures are the evidence, and scrutiny works from the checklist to the annexure and back.

An annexure that can't be located against its checklist item is treated as not filed, however clearly the main document refers to it. The officer's task is to record that the requirement was met, and they can't record what they can't find.

The discipline is mechanical and repays effort out of all proportion. Every annexure numbered in checklist order. Every reference naming the annexure number and, where long, the page within it.

Every annexure carrying a cover sheet stating what it is, so the officer doesn't infer from the first page. Documents in the language the scheme requires, with certified translations where they aren't. Pagination continuous across the whole file, so a query can be answered by a page reference.

Two failures recur. The first is the annexure supplied but not indexed: present in the bundle, absent from the list, invisible to a scrutiny working down it.

The second is the composite annexure, where several distinct requirements are satisfied by one bundle. The officer must tick several checklist items against a single entry, and where the correspondence isn't explicit they frequently decline to.

Both are cured by making the index match the checklist item for item, which takes an hour.

There's also a question of what shouldn't be there. Volume isn't persuasive in this context and is faintly counterproductive.

A file padded with material the scheme didn't ask for makes the required material harder to locate, and an officer hunting through a hundred unnecessary pages for one certificate is an officer forming an impression.

The Same File Is Read by Several Departments, Each Asking a Different Question

A submission of any significance circulates: a technical desk, a finance desk, a legal desk, sometimes environmental or land or labour, and whichever authority holds the delegation at the amount involved.

Each reads the same file on its own criteria and each can stop it independently. The applicant sees only the aggregate outcome and can't tell which desk generated which query.

So a submission must satisfy several distinct readings at once, and a document optimised for one tends to underserve the others.

A file written for the finance desk can be thin on the technical basis of the capacity figure the finance analysis depends on. A file written by engineers can be immaculate on process and silent on how the working capital cycle was derived.

Neither is complete, and a file incomplete for one desk stops for everyone, because the desks are sequential more often than parallel.

Sequencing explains most of what applicants experience as delay. Each movement has a queue, and a query at the fourth desk returns the file to the applicant, re-entering circulation not always where it left.

A single avoidable query at a late desk can cost more elapsed time than several early ones. That's the strongest argument for preparing the whole file to the standard of the most demanding desk at the outset.

It also explains something that puzzles applicants: a query about a matter they believe was already answered.

Each desk reads independently against its own criteria, and an answer satisfying the technical desk may not address what the legal desk asks about the same paragraph.

The productive response is to answer the question actually asked, in the terms the asking desk uses. Pointing out that the ground has been covered reads, in a permanent record, as an applicant declining to answer.

A Sanction Is a Conditional Instrument, and the Conditions Are the Real Document

Applicants treat the sanction letter as the end of the process. It's more accurately the point at which obligations become specific.

A public sanction is conditional almost without exception: conditions precedent before disbursement, undertakings through the life of the benefit, reporting at intervals, and a right of recovery if they fail. The conditions are enforceable and recovery is real.

Evidence of the promoter's contribution brought in, of balance funding tied up, of a clearance obtained, of specified insurance in force. Each takes elapsed time, and several must generally be satisfied together before first disbursement.

Where the sanction carries a validity period, the conditions and the validity interact. An applicant who begins work on conditions after receiving the sanction may find the window closing while a third party takes its own time.

Reading the likely conditions from the scheme documents before sanction, and starting on the slowest early, converts weeks into days.

The continuing undertakings carry the longer exposure. Employment maintained, capacity operated, location retained, assets not disposed of. Each can be breached by an ordinary decision taken years later by someone who never read the sanction.

A recovery demand arising from a restructuring nobody connected to the original file is foreseeable, precisely because the conditions outlive the institutional memory of them.

Extracting the continuing obligations into a short schedule held by whoever will actually operate the business is a modest step that prevents it.

Reporting obligations deserve their own mention because failure is so often inadvertent. Periodic returns, utilisation certificates, progress reports, each with a form, a period and a due date.

A missed return is a breach on the record even where everything substantive is in order, and it surfaces at the least convenient moment.

Write for the Record, Not for the Reader in Front of You

The discipline this article describes reduces to a single reorientation, and it mirrors the one a credit proposal requires.

A commercial document is written for a reader who will decide. A public submission is written for a record, read by people who weren't present, at times nobody can predict, for purposes nobody has yet formed.

The official in front of you is one reader among several, and their most pressing constraint is that whatever they write down will be read by someone else later.

A submission that makes that easy progresses: complete, indexed, sourced, phrased so it can be adopted rather than merely believed.

One that doesn't is returned, and the return will be about form, because form was as far as anyone got.

None of this favours a well-resourced applicant over a modest one, which is worth saying plainly.

The requirements are published, the checklist is available before drafting begins, and the discipline is mostly clerical.

Confirm the current version of every form. Index the annexures against the checklist. Cite every figure to something a stranger could locate. State each material fact in a sentence that can be lifted. Read the conditions on the day the sanction arrives rather than the day something goes wrong.

A small applicant who does those things is filing a better file than a large one that hasn't, and the scrutiny desk can't tell which is which and isn't trying to.

The published rules of the specific scheme always govern, and they should be read first.

What this article adds is why those rules take the shape they do, which is generally the thing that makes them possible to follow well rather than merely to follow.