You typed what a construction controller does. The results handed you a job description.
Supervises payroll. Reviews invoices. Oversees budgets. Manages financial reporting.
That is how a job board talks to a candidate. It is not how an owner should buy the work.
A construction controller, each month, should hand you a short package you can sit with: WIP inputs that are current job by job, a job cost review the field can argue with, pay applications ready for your signature, retainage and cash you can see, and an over- or under-billing position you can explain. If that package is late, the title on the org chart does not matter.
This is that package. Not a hiring-guide list of daily duties.
What should land on your desk
Five things. If any of them is missing, you do not have controller work. You have leftover bookkeeping and an owner still doing the rest at night.
1. WIP inputs, current, job by job
Percent complete and cost to complete get refreshed with the people closest to the work. When a number moves, there is a short recorded reason. The schedule is usable because the inputs are current... not because someone re-ran last month's percentages.
When WIP does not feel trustworthy, the formulas are rarely the villain. Somebody has to keep the inputs current every month, job by job. That is the first thing a controller owes you.
2. Job cost review
Cost codes, commitments, change orders, and labor hit the job the way you bid it. A PM can sit with the report and argue about the work, not about which bucket an invoice landed in. Margin fade shows up while there is still time to act on the job... not as a surprise after the punch list.
3. Pay applications prepared for your signature
Quantities, stored materials, retainage, previous applications, and backup are assembled so you approve. You do not rebuild the app the night before it is due. The controller prepares. You (or your designated responsible party) sign.
4. Retainage and cash visibility
What is held, what is eligible for release, what is stuck on punch list or paperwork, and how that shapes the cash you thought you had. Ten percent (or whatever your contracts hold) is not a rounding error. If nobody owns it, you will feel profitable and broke at the same time and blame the wrong report.
5. Over- and under-billing you can explain
Billings versus cost and percent complete create a position: billed ahead of performance, or performed ahead of billing. Bankers and sureties read that whether or not you have explained it to yourself. You should get a one-page story... where you stand, why, and what changed... not a mystery plug after the fact.
The monthly checklist (use this page; do not wait for a download)
This is the owner-facing list. A one-page version of the same checklist may show up later as an optional leave-behind. It will not be a gated workbook, and it will not be the internal operating file. For now, this table is what you should get every month.
| What you should get | What "done" looks like | What "not done" looks like |
|---|---|---|
| WIP inputs, job by job | Percent complete and cost to complete refreshed; changes have a recorded reason | Same percentages as last month; nobody can say why a job moved |
| Job cost review | Variances vs the bid and vs last month; change orders in; a PM can argue the work | Cleanup archaeology; codes do not match the estimate |
| Pay apps ready to sign | Quantities, stored materials, retainage, prior apps, backup assembled | You rebuild the app at 10pm |
| Retainage / cash visibility | Held, eligible, stuck... and what that does to the next weeks of cash | Retainage sits on the balance sheet with no release plan |
| Over- / under-billing story | One page: position, reason, what changed | A plug you cannot defend to a banker |
| A date that holds | Published cadence; exceptions visible; work in your system | "We'll get to it" after the month already closed |
If you cannot point to a person and a date for each row, controller work is still on you... regardless of who you already pay.
A date that holds, inside your system
The package is not useful as a heroic weekend. It is useful when it lands on a published date, inside the books and job-cost tools you already run.
You keep the instance. You keep the history. You keep the signature authority. The controller prepares and reviews. Your designated responsible party approves payments, vendor setups, and anything that moves money or commits the company.
Job boards often list "review and approve invoices" as a daily controller duty. That is a candidate sentence. It is the wrong owner definition. Approving money is a management function. It stays with you.
How a month actually runs (owner view)
Job boards write daily duties. Owners need a week-by-week picture. Yours will not match this calendar exactly. The order is what matters: field inputs first, then the package, then your approvals.
- Cut with the field. PMs and supers give percent complete and cost to complete on the jobs that are still open. Not a guess from last month. Not a finance-only number.
- Sit job cost. Variances against the bid and against last month. Change orders that hit the field but not the billing schedule get named. Codes that drifted get pulled back to how you bid.
- Refresh WIP. Inputs update job by job. Every material change gets a short recorded reason. The schedule is now current enough to use.
- Build the billings. Pay applications for the cycle get quantities, stored materials, retainage, prior apps, and backup. They wait for your signature. They do not go out unsigned.
- One page on cash and position. Retainage held / eligible / stuck. Over- or under-billing you can explain. What that means for the next weeks of cash.
- Hand it to you on the published date. You read it. You ask the two jobs that look off. You approve what moves money. The controller does not.
If step 1 is skipped, everything downstream is theater. That is why "they sent me a P&L on the 12th" is not the same as having a controller.
What this is not
Not a day-in-the-life for job seekers. Supervising payroll, managing IT, and "overseeing financial strategy" are how postings fill space. They do not tell you whether month six on job 18 is still honest.
Not "month-end close" as the product. Close is a container. The product is WIP currency, job cost truth, pay apps you can sign, retainage you can see, and an over-/under position you can explain.
Not a replacement for your outside advisors. A controller does not perform audit, review, or tax work. Your tax and assurance people stay in their lane. They should receive cleaner schedules to work from... not a second set of books.
Not an automatic full-time hire. Needing this package every month is not the same decision as opening an FTE seat. That fork lives in Should You Hire a Controller? and Fractional Controller or Full-Time Hire.
Bookkeeping can be fine and still miss this list
A lot of owners under $10M find this page after searching construction bookkeeping services, because that is the familiar phrase. Fair enough. Bills need to be paid. The bank needs to reconcile. Invoices need to go out.
Bookkeeping answers: did the transactions get recorded.
Controller work answers: are the job inputs current, is billing tied to the work in place, and can you trust margin and cash this month.
If retainage, cost codes, and over-/under-billing only get attention when someone outside the company asks, you are past pure bookkeeping... even if every transaction is posted. The dividing line is in Construction Bookkeeper vs. Controller: Where the Job Changes.
Same list whether you hire or get the work run
Whether the person is on your payroll or running a published cadence in your instance, the monthly package does not change.
If you are pricing a seat, do not decide from the salary line. Load the cost... taxes, benefits, match, PTO, equipment, recruiter... then face ramp, vacancy, and concentration risk. That ladder is in What a Controller Really Costs a Contractor.
If someone else will run the work, ask the control questions before you hand over access: who signs, who holds the mailbox, who stays in the field, what they refuse to do. That list is 12 Questions to Ask Before Outsourcing Construction Controller Work.
How BlueCollar Financial Operations talks about this month
BlueCollar Financial Operations is construction controller services for contractors who need this package on a date that holds, inside their own system. Owners who still search construction bookkeeping services are welcome at the door; the work we mean is the list above... not ledger-only bookkeeping under a new label.
We prepare and review. You keep the signature, the mailbox, and the field. We perform no audit, review, or tax work.
This article does not publish a BFO price. Fit is a conversation about how you bill, how you cost jobs, and which rows in the checklist are late.
What to do this week
- Print or copy the checklist table. Mark each row: current owner, current date, last time it was actually current.
- Circle the rows you personally still own after 8pm.
- Decide whether the next move is a full-time seat, a construction controller cadence, or fixing bookkeeping consistency first.
- If you are about to hand the work to anyone, run the control questions before you share logins.
