You have a government contract, new or newly troublesome, and you do not truly understand what it requires or how to bill it, or you are not even sure it covers your costs.
This guide gets you set up right: you read what the contract actually demands in rates, units, documentation, and deadlines, you check honestly whether the rate covers what a unit costs you, you set the documentation standard your front-line staff will follow, and you stand up the billing operation to bill it cleanly from the first claim. It is not a substitute for reading your own contract and knowing your own program rules, which are specific to your payer and your state and change over time. And it is not a promise that a contract is worth taking: part of this work is discovering that a rate does not cover your cost, which is a finding, not a failure.
What it will take: careful reading of the contract, honest cost numbers from finance, and time to build documentation and billing routines before the work scales. What must be true first: you have the contract in hand and access to your true cost of delivering a unit. If the contract is not signed yet, all the better, because this is the ideal time to learn what you are agreeing to.
Most reimbursement failures trace to a contract requirement nobody read closely: an exact unit definition, a documentation rule, a filing deadline, a rate condition. Pull out the essentials, and where a term is unclear, note it as a question for the payer or a billing specialist rather than guessing, because a wrong assumption here becomes a denial or a clawback later.
Open the Contract Requirements Breakdown →A contract that pays less than a unit costs you is a structural loss no billing skill can fix, and this is the moment to find out, before you build an operation around it. Using the true unit cost, staff time, documentation time, supervision, and overhead, compare it to the rate and decide whether the contract pays for itself, and if not, by how much it loses.
This is a structural decision, not a setup task. Route to renegotiating the rate where you can, to a conscious and funded decision to subsidize the work from other money if the mission demands it, to mission clarity and strategic direction for whether this work belongs in your organization, and to the financial health work for the numbers. Do not build a billing operation around a contract that loses money on every unit without the board deciding, with open eyes, to do so.
Because documentation is the cash, the single most important setup decision is exactly what a front-line worker must record for each unit to be billable and audit-proof. From the contract requirements, define what a worker must record for each unit: what, when, by whom, for whom, and the specifics the contract demands, in a form quick enough to actually do and complete enough to bill and defend. Then build it into how the work is recorded, so documenting is part of the service, not a separate chore done from memory later.
Open the Service Documentation Standard →A contract needs a billing routine that reliably turns documented services into submitted claims, or the documentation never becomes cash. Set up who prepares claims, how often, how they are checked before submission, how they are submitted, and how you confirm they arrived, and decide how you will see from the start what is billed, paid, and denied.
Keep the software and general systems light; the deeper technology work lives in the operations and systems work.
Open the Billing Operation Setup →Two edges. The specific billing rules of your program, what exactly is allowable, how a unit is defined, what an authorization requires, are jurisdiction-specific and change, and where the contract is genuinely unclear, confirm it with the payer or a billing specialist who knows this program, not a guess. And if the contract carries legal commitments, match requirements, indemnification, penalties, have a nonprofit attorney review it before you sign, because a term you did not understand can cost far more than the contract pays.
You can state exactly what the contract requires to pay you. You know whether one unit covers its cost. And your front-line documentation and your billing routine are set up before the claims start flowing, not patched together after they stall.
With the contract understood and the operation set up, most leaders move to Build the Billing Engine, to turn documented services into paid claims. Return to your Prioritized Billing Plan.