AI Automation6 min read

After the Tender Award: Milestone Reports and Invoicing with Claude Code

What changes once you win a government or enterprise contract, and how to run the workplan, meeting actions, milestone reports and invoices as repeatable recipes.

Haojun See

Founder & Director, On The Ground

Updated 4 November 2026

The short answer

Winning the tender is the start of the paperwork, not the end. A contract brings a workplan to keep, meetings to minute, milestone reports to file and invoices that must match the purchase order exactly. Each of those is a repeated job, which makes it a good fit for a written Claude Code recipe with a person checking what goes out. This is the Deliver stage of Ground Control. On a joint bid it is often the part we run for the team, so the field experts can stay on the work itself.

Set up one folder for the contract

Make one folder per contract, and put the source of truth in it on day one: • The award letter and purchase order, exactly as received. • The specification and your submitted proposal, because those are what you will be measured against. • The payment schedule and milestones, copied into one plain table. • A CLAUDE.md with the standing rules: who the buyer's contacts are, the reporting format they asked for, and "amounts and dates come only from the purchase order". Every recipe below reads from this folder, so the contract's own words drive the work.

Recipe 1: Turn the proposal into a workplan

Ask Claude Code to turn the submitted proposal and the milestone table into a dated workplan: each deliverable, its owner, its due date and the requirement it answers. On a joint contract, each partner's part is listed under that partner. A person checks the dates against the contract and agrees the owners. The workplan then becomes the checklist every later report is written against.

Recipe 2: Meeting notes into actions

After each meeting with the buyer, put your notes in the folder and ask for three things: decisions made, actions with owners and dates, and anything that changes scope. Scope changes matter most. Flag them to the person who owns the contract the same day, because a change agreed casually in a meeting can quietly break the price.

Recipe 3: Milestone reports

A milestone report says what was promised, what was delivered and the evidence. Ask Claude Code to draft it from the workplan, the deliverables in the folder and the meeting actions, in the format the buyer asked for. The rule that keeps it honest: every "delivered" line must point to a real file or a dated record. Anything without evidence is marked as not yet done. A person reads and signs off before it is sent. We used the same approach for a post-event report, finished in minutes instead of an afternoon.

Recipe 4: Invoices that match the purchase order

Government and enterprise buyers often reject invoices that don't match the purchase order. Ask Claude Code to draft each invoice from the milestone table and the purchase order only: the same reference number, item descriptions, quantities and amounts, and the milestone that has been accepted. Submit through the channel your purchase order or contract names, and keep the submission record in the folder. Our quote-to-invoice guide covers numbering and chasing payment.

What stays with people

People sign off everything that leaves: reports, invoices, and any reply about scope. Claude Code drafts and cross-checks; it doesn't send. Keep the buyer's documents and any personal data inside the contract folder, and follow the data rules in the contract itself. To see how a contract like this is found and bid for in the first place, read how to triage tenders and bidding with partners.

Frequently asked questions

Can AI write a milestone report for a government contract?

AI can draft it from your workplan, deliverables and meeting records, in the format the buyer asked for. Every delivered item should point to real evidence, and anything without evidence should be marked as not yet done. A person reads and signs off the report before it is sent.

Why do government invoices get rejected?

A common reason is a mismatch with the purchase order: a different reference, description, quantity or amount, or billing a milestone that hasn't been accepted. Drafting each invoice only from the purchase order and the accepted milestones, then checking it before submission, avoids most of these.

Who manages the project on a joint tender?

It is agreed per contract. On joint bids with On The Ground, we can run project management, milestone reports and invoicing, while each partner leads the delivery of its own field. Who does what should be written down before the bid is submitted.

AI Automation

How to Triage Tenders with Claude Code: Screen a Week's Bids Fast

AI Automation

10 Ways a Small Business Could Use Claude Duet

AI Automation

From Call Notes to Quote: Claude Code Sales Workflows for SMEs

PreviousHow to Bid for Singapore Tenders with Partners: A Joint-Bid Guide Next What Is Claude Duet? Anthropic's Proactive Agent for Business