BlogHow-To

How to Track Engineering Projects, Time, and Billing

A working playbook for engineering firms on phase-based budgets, multipliers, utilization, subconsultants, and reimbursables — with the software stack that holds it all together.

Davaughn White·Founder
14 min read

A 22-person civil engineering firm closed the year 4% under target on a project portfolio that looked, in monthly reviews, like it was tracking just fine. Every status meeting said green. Every invoice went out roughly on schedule. The principal-in-charge found out in February — when the books closed — that three lump-sum projects had blown past their hour budgets between design development and construction documents, that two subconsultant invoices had been eaten because nobody marked them up before pass-through, and that the firm's senior PE had quietly slipped to 48% utilization while everyone assumed she was full.

None of that showed up in the monthly review because the review was looking at fees billed against fees earned, not hours burned against hours budgeted by phase. The dashboard said green because the dashboard was measuring the wrong thing.

If you run an engineering firm — civil, structural, MEP, geotech, environmental, controls — this story is probably familiar in shape if not in detail. The job is uniquely brutal on project economics: lump-sum contracts on knowledge work, multi-phase delivery against fee letters written six months before scope crystallizes, billable people who also sit on internal committees, subconsultants whose invoices arrive on their schedule rather than yours, and reimbursables that quietly drain margin one mileage log at a time.

This post is the playbook for tracking projects, time, and billing in a way that catches problems in week three, not month nine. It covers the project lifecycle, the four fee structures and how each one changes what you measure, the earned-value problem on lump-sum work, the multiplier math, subconsultant and reimbursable handling, document control, license tracking, and the software stack — what each piece needs to do, and how a consolidated platform like Deelo maps to it.

The shape of an engineering firm

Before the tracking, the org. A typical 5-50 person PE-licensed firm has four layers of billable and non-billable mix, and the way work flows through them is what makes engineering project management different from agency or consulting work.

At the top: principals and senior PEs. Stamping authority, business development, technical review. Target utilization of 50-65%. They are paid to win work, sign drawings, and unblock junior staff, not to charge eight hours a day to a project.

Middle: project managers and senior engineers. Often PE-licensed, often the actual technical lead on a project. Target utilization 65-75%. They run the design effort, manage the budget, talk to the client.

Production: EITs (engineers-in-training), staff engineers, CAD/BIM technicians. Target utilization 80-90%. These are the people doing the calculations, drafting the drawings, running the models. The firm makes its money on their billable hours.

Non-billable: admin, marketing, accounting, IT. Recovered through the multiplier on billable labor, not charged directly to projects.

Every system you put in place — time tracking, project management, invoicing — has to respect this structure. A senior PE charging 80% to projects is a problem (probably under-investing in BD or review). A technician charging 60% is a different problem (under-utilization). The same number means different things at different levels, and a system that doesn't separate them is a system that can't tell you what's wrong.

The project lifecycle, with billing milestones

Engineering projects move through a predictable lifecycle. Each phase is a budget. Each phase has billing milestones. Each phase is where a different kind of problem shows up.

Opportunity. Lead comes in (RFQ, referral, existing client, business development). Tracked in CRM. Effort here is non-billable BD time, recovered through overhead.

Proposal / fee letter. Scope drafted, fee estimated, contract terms negotiated. Hit rate on proposals matters — if your senior staff are writing proposals 30% of their hours and your win rate is 15%, you have a BD efficiency problem dressed up as a workload problem.

Contract. Signed agreement, scope locked, fee structure set. This is the point where the project officially starts in your project management system. Earlier, and you contaminate active project metrics with speculative work.

Kickoff. Internal mobilization, team assignment, schedule, first deliverable plan. Critical that the project budget is loaded into the system before the first hour is charged — late budget setup is how scope creep starts.

Design phases. The substantive work, typically split into three or four phases for a building or infrastructure project: - Schematic Design (SD) — concept, options, rough sizing. Typically 15% of total fee. - Design Development (DD) — system selection, key calculations, coordinated layouts. Typically 25%. - Construction Documents (CD) — full drawings and specifications for permit and bid. Typically 40%. - Construction Administration (CA) — RFIs, submittals, site visits during construction. Typically 20%.

These phase percentages are industry norms for full-service design contracts and shift with project type. Pure structural on a developer-led job often has a smaller CA share. Civil site/utility on a commercial development weights more toward CD. Geotech is usually front-loaded into a single investigation and report phase. The point is not the exact split — it is that each phase is a separate budget bucket against which hours and deliverables are tracked.

Permit support. Often folded into CD or a separate small phase. Tracking it separately matters when projects sit in plan review for months and the fee is being eaten by unanswered comment-response work.

Construction Administration. Drawings issued, project moves to bid and construction. CA phase starts. RFIs come in, submittals get reviewed, site visits happen. This is the phase where most firms lose money on lump-sum contracts because the work is reactive and effort estimates were made 12+ months earlier.

Close. Punch list, record drawings, final invoice, retention release, project archive. The phase where firms most often forget to invoice the last 5-10% because the team moved on.

Fee structures: what you actually agreed to bill

Four fee structures cover almost every engineering contract. Each changes what you have to track and where you bleed margin.

Fee structureTypical useWhat you trackWhere margin leaks
Lump sumMost private design contractsHours burned vs. budget by phase; physical % completeHours overrun on phases nobody monitored weekly
Hourly with cap (NTE)Smaller projects, study phases, due diligenceHours charged vs. cap; rate × hours billed monthlyApproaching cap without scope amendment in writing
Time and materialsOn-call services, design support during constructionHours and reimbursables, billed monthly with backupReimbursables not captured; rate sheet outdated
Cost-plus-fixed-feeFederal, state, and many municipal contractsDirect labor cost, indirect rates (FAR overhead), fixed feeAudit findings on overhead pool; unallowable costs charged
Percentage of constructionLegacy contracts, some institutional workConstruction cost estimate × agreed %; phase progressConstruction cost overrun shrinks effective fee per hour

Lump sum dominates private commercial work. The risk transfers to you: you said you'd do the work for $X, and if the design takes 50% more hours, you absorb it. That is the whole reason phase-based budgeting and weekly hour tracking matters more in engineering than in most professional services.

Hourly-with-cap looks safer until your PM lets the project run to 95% of cap before noticing. The recovery — a scope amendment to lift the cap — is awkward to ask for, and if your tracking is monthly instead of weekly, you find out late.

T&M is rare on private work because clients don't like open-ended invoices. It is common for on-call services, expert witness work, and design support during construction where scope genuinely cannot be predicted. The discipline here is invoice backup — every hour and every reimbursable needs to be defensible to the client's project manager.

Cost-plus-fixed-fee shows up on federal and state work and brings DCAA-style overhead accounting. Your overhead pool is audited, certain costs are unallowable, and your billing rates depend on a provisional indirect rate that gets trued up annually. If you do any federal work, your accounting system has to track this separately.

Percentage of construction is a legacy fee structure that mostly persists on institutional work. It looks like a clean way to scale fee with project size but punishes the design team when the construction estimate grows beyond what the design effort actually scales with.

The earned-value problem on lump sum

Here is the math that bankrupts firms on lump-sum work.

You win a project at $200,000 lump sum. You budgeted 1,400 hours at an average blended rate of $143/hour. The project is split across SD (15% / 210 hours), DD (25% / 350 hours), CD (40% / 560 hours), and CA (20% / 280 hours).

Week 6 ends. The project is in DD. Your team has charged 480 hours total. Your bookkeeper says you've billed $50,000 — 25% of the fee. The monthly report says the project is on track.

It is not on track. 480 hours against an SD+DD budget of 560 means you've already burned 86% of the hour budget for the first two phases. And looking at the deliverables, DD is maybe 60% physically complete. Linearly extrapolating, finishing DD will take another 130-160 hours. By the time DD closes, you'll be at 610-640 hours against a 560-hour budget for the first two phases.

That overage doesn't go away. CD will start under-budget by 60-80 hours. CA will be reactive and unpredictable. By project close, you are 10-15% over your hour budget at the same fixed fee. Your effective rate just dropped 12%.

The only way to catch this in week 6 instead of month 9 is earned value: every week, for every active project, three numbers get compared:

1. Hours budgeted to date by phase 2. Hours actually charged to date by phase 3. Physical percent complete by phase (PM's judgment, not a calculation)

When actual hours exceed budgeted hours faster than physical % complete is growing, the project is in trouble. The PM has to flag it, the principal has to know about it, and the conversation about scope amendment or internal absorption has to happen before another 200 hours go in.

This is the single most important operational metric for an engineering firm doing lump-sum work. A project management system that doesn't make it easy to see every active project's earned value at a glance is a system that will let you find out in February.

Multipliers: the number that decides whether you're profitable

Your billing rate is not your cost rate. Between them is the multiplier, and getting it right is the difference between a firm that breaks even and a firm that funds owner profit distributions.

The formula:

Bill rate = Direct labor rate × Multiplier

Direct labor rate is the employee's hourly cost (annual salary divided by 2,080 hours, or actual hourly wage). The multiplier is what you mark that up by to cover overhead, fringe, and profit. Industry norm is 2.8x to 3.2x for healthy firms. Below 2.6x and you are almost certainly losing money once you account for true overhead. Above 3.4x on competitive bid work and you are pricing yourself out.

A worked example. Senior PE at $80,000/year salary, $1,600/month fringe (insurance, retirement match, payroll tax), 2,080 hours.

Direct labor cost: $80,000 / 2,080 = $38.46/hour. With fringe: $38.46 + ($19,200 / 2,080) = $47.69/hour fully loaded.

Multiplier 3.0x on direct labor: $38.46 × 3.0 = $115/hour bill rate.

The multiplier breaks down roughly as: 1.0x direct labor, ~0.4-0.5x fringe and direct expenses, ~1.3-1.6x indirect overhead (rent, admin, BD, software, insurance, training), and ~0.1-0.3x profit margin. The squeeze comes when overhead grows faster than billable hours.

To run this metric correctly your time tracking has to know both the cost rate and the bill rate for every employee, and your project economics view has to roll up hours × cost rate against hours × bill rate × realization to give you actual project profitability — not just fees billed against fees earned.

Utilization: the leading indicator

Utilization is the percent of an employee's hours that are charged to billable client work. It is the leading indicator that the firm's hour budget makes sense and the lagging indicator that BD is keeping up.

Target utilization varies by role:

  • Principals / senior PEs: 50-65%. Lower is fine if BD effort is producing pipeline. Higher means they're under-investing in business development or technical review.
  • Project managers / senior engineers: 65-75%. The working layer of the firm — should be heavily billable but with real time for project management overhead.
  • EITs and staff engineers: 70-80%. Production-focused. Significantly under this means under-utilization or BD pipeline shortage.
  • CAD/BIM technicians: 80-90%. Almost pure production. Anything under 75% means scheduling problems or workload gaps.
  • Admin / marketing / accounting: 0-15%. Recovered through the multiplier.

Track this weekly. Track it by individual and by team. Track it as a four-week trailing average so single-week variance doesn't trigger false alarms.

A firm-wide utilization rate of 60-65% is healthy for most small to mid-size engineering practices. Above 70% sounds good but usually means you are under-investing in BD, training, and senior review — borrowed time that comes due later. Below 55% sustained means revenue cannot cover overhead and the firm is bleeding.

Subconsultants: the markup you forget to take

If you are prime on a project that includes geotech, surveying, landscape architecture, or specialty consulting, you are managing subconsultants. The work flows through you, the contracts flow through you, and the invoices flow through you.

Three things break here.

Markup. Industry norm is 5-10% markup on subconsultant fees, sometimes higher for federal work where indirect rates apply. This is your compensation for the risk of contracting through, the cash flow burden of paying subs before the client pays you, and the project management overhead of coordinating their work. Forgetting to apply the markup — or applying it inconsistently — is direct margin loss. Make it a default in the project setup, not a decision the PM has to remember.

Cash flow. You pay the sub when they invoice. The client pays you 45-60 days after you invoice them. On a $50,000 sub on net-60 terms, you are carrying $50,000+ in working capital for two to three months. Track AR aging by client and by project, and don't let subconsultant exposure compound.

Pass-through versus pass-through-with-markup. Some contracts (especially federal) require pass-through-at-cost with no markup. Some private contracts permit standard markup. Your project setup needs to know which mode each project is in so invoicing applies the right rule. Getting this wrong shows up as either client disputes (you marked up where you shouldn't have) or unrecoverable revenue (you didn't mark up where you could have).

Reimbursables: the slow margin leak

Reimbursables are the costs you incur on behalf of the client that get billed back: mileage, plotting, courier, permit fees, geotech borings, environmental sampling, lodging on out-of-town site visits.

The reason they leak: nobody owns them in real time. The technician drives to a site, doesn't log mileage that day, forgets by the time the monthly invoice runs. The plotter spits out a 30-sheet set, nobody bills the client for it. The PM pays the permit fee on a personal card and submits an expense report that never makes it onto the project invoice.

The rule of thumb: a firm without disciplined reimbursable tracking loses 2-4% of billable revenue every year. Across a $5M annual revenue, that's $100,000-200,000 walking out the door because of operational hygiene.

The fix is unsexy. Mobile mileage logging that defaults to project-coded entries. Plot tracking integrated with the document management system. Permit fees logged as billable expenses against the project at the moment the payment is made. Monthly reimbursable review before invoicing.

Document control: what the state board will ask for

Engineering firms are subject to state professional licensing boards that can — and do — audit. If a structure fails, a building leaks, or a project ends in litigation, the question becomes: what did you know and when, and can you prove it.

The records that matter:

Drawing revisions. Every signed and sealed drawing set with version history, who issued it, when, and what changed between revisions. This is non-negotiable.

RFIs. Requests for information from the construction team during CA. Logged, answered, dated, and tied to the drawing set in effect at the time.

Submittals. Contractor shop drawings and product data reviewed by the engineer. Approved, approved-as-noted, rejected — with dates, reviewer initials, and comment threads preserved.

Transmittals. Formal records of what document was sent to whom, when. The audit trail that proves you delivered the design.

Calculations. Often the most legally consequential records. Signed and sealed calculations supporting the drawings. State boards expect these to be retrievable for the licensing-period retention requirement (typically 7-10 years, varies by state).

A document management system for an engineering firm is not optional. It needs version control, audit trails, role-based access, and retention policy enforcement. The shared network drive with folder names like `2023-07_revised_FINAL_v2` is a state board complaint waiting to happen.

License tracking: the compliance you can't outsource

Every PE in your firm has a license that renews on a state-specific schedule, requires continuing education credits, and is required for stamping drawings in that state. If your senior PE's Texas license expires on June 30 and a project closes July 5, you have a problem.

What to track per employee:

  • Licensed states with license number and seal/stamp file
  • Renewal dates by state, with reminder lead time (90-day, 60-day, 30-day)
  • Continuing education credits completed and required, by reporting period
  • Discipline-specific certifications (LEED AP, ENV SP, PMP, OSHA 30, etc.)
  • E&O insurance certificate dates and limits
  • Background check / I-9 / W-4 on file for HR compliance

Most firms run this in a spreadsheet that nobody updates. The cost of getting it wrong ranges from a delayed stamp on a critical drawing set to a board complaint that suspends an individual license. An HR/people system with structured license tracking and proactive reminders pays for itself the first time it catches a 60-day-out renewal that would have been forgotten.

The software stack: what each piece has to do

Mapping the workflow above to software, an engineering firm needs seven functional capabilities. They can come from seven separate vendors, from a specialized firm-management platform, or from a consolidated work platform — but the capabilities have to be there.

CapabilityWhat it doesCritical features
CRMOpportunity pipeline, proposals, client relationshipsStages tied to win probability, proposal templates, BD activity tracking
Project managementPhase-based budgets, schedules, deliverablesMultiple phases per project, hour budgets per phase, earned value rollup
Time trackingHours charged to project + phase + taskMobile entry, project + phase codes, billable/non-billable flag, weekly approval
Resource planningCapacity vs. workload by person and teamForward-looking schedule, utilization forecast, skill/license matching
Document managementDrawing revisions, RFIs, submittals, transmittals, calculationsVersion control, audit trail, role-based access, retention policy
InvoicingMilestone billing, hourly billing, reimbursables, subconsultant pass-throughPhase-based invoicing, markup automation, AR aging, WIP report
HR / peopleLicense tracking, CE credits, certifications, payroll integrationPer-state license records, renewal reminders, compliance dashboard

The category leaders here — Deltek Vantagepoint, Ajera, BQE Core, ArchiOffice — are well known and have built deep capabilities specifically for AEC firms. They are credible options, especially at the 50+ person scale where the depth of AEC-specific features starts to clearly pay back the implementation effort and seat cost.

The trade-off operators face is implementation lift versus depth. The dedicated AEC platforms require meaningful setup, training, and ongoing administration — they assume the firm has a dedicated controller or operations lead who lives in the tool. For smaller firms (5-25 people) without that role, the implementation overhead and per-seat cost can outweigh the marginal feature depth.

This is the gap a consolidated work platform fills. Same seven capabilities, but on shared data and at small-business pricing. The next section walks through how that maps in practice.

How Deelo maps to the engineering workflow

Deelo is not an AEC-specific platform, and any honest comparison should say that out loud. What it is, is a work platform with the seven capabilities above on one data layer at $19 per seat per month for the entire suite. For an engineering firm with 12 people, that's $228/month for the platform — meaningfully less than per-seat AEC tools that range from $50-200/seat/month for comparable functionality.

The mapping:

Deelo CRM holds opportunities and proposal workflow. Pipeline stages mapped to the engineering proposal flow (lead, qualified, proposal out, contract negotiation, won). Activities tied to BD effort so you can measure cost-of-acquisition.

Deelo Projects runs the project management layer with phase-based budgets. Each project has SD / DD / CD / CA (or whatever phase structure fits — modify per project type). Each phase has an hour budget, a fee, and milestone tracking. Time charged rolls up against the phase budget. Earned value views show hours-budgeted versus hours-charged versus physical % complete per phase.

Deelo Time captures hours against project + phase. Mobile entry. Billable / non-billable flag. Weekly approval workflow with the PM. Direct labor rate and bill rate stored per employee so cost and revenue both roll up in real time.

Deelo Docs holds drawing sets, calculation files, RFIs, submittals, transmittals with version control, role-based permissions, and retention. The audit trail that defends the firm to the state board.

Deelo Invoicing generates milestone invoices by phase, hourly invoices with backup, and pass-through line items for subconsultants and reimbursables. Markup rules per project. AR aging built in.

Deelo HR tracks PE licenses by state, renewal dates with proactive reminders, CE credits, certifications, and E&O documents.

Deelo Customer Portal gives the client read-only access to project status, invoices, and document deliverables — reducing the back-and-forth email burden on the PM.

The pitch is not that Deelo out-features Deltek or BQE on AEC depth. It is that for a firm under 50 people that doesn't have a dedicated controller to administer a deep AEC platform, a consolidated work platform with shared data closes 80-90% of the capability gap at meaningfully lower total cost — and removes the integration tax of stitching seven specialized tools together.

The KPI dashboard you actually need

Once the data is in one place, the principal-level view is small. Six numbers, reviewed weekly:

  • Firm utilization rate (trailing four weeks, billable hours / total hours, by role)
  • Gross multiplier achieved (revenue / direct labor cost, year-to-date and trailing month)
  • Project profit % by active project (fees earned vs. cost of hours + reimbursables + subs)
  • Earned value flags — projects where hours-burned outpaces physical % complete by more than 10%
  • Backlog in months (signed unworked fees / monthly run rate)
  • AR aging — receivables over 60 and 90 days

These six numbers, reviewed every Monday with the PM team for 30 minutes, prevent the February surprise. Everything else — proposal hit rate, BD pipeline, individual utilization, project schedule slippage — feeds into those six, and gets reviewed at deeper cadence when one of the six flashes red.

See the engineering workflow on Deelo

Spin up a Deelo workspace, load one active project with its phase budget, and see what earned-value tracking looks like in practice. No credit card required. If it fits the firm, the entire stack — CRM, Projects, Time, Docs, Invoicing, HR — is $19 per seat per month.

Start Free — No Credit Card

Frequently asked questions

What is the right multiplier for an engineering firm?
Industry norm for a healthy small to mid-size engineering firm is a direct-labor multiplier of 2.8x to 3.2x. Below 2.6x and the firm is almost certainly losing money once true overhead is accounted for. Above 3.4x on competitive bid work and the firm prices itself out of opportunities. The multiplier breaks down roughly as 1.0x direct labor, 0.4-0.5x fringe and direct expenses, 1.3-1.6x indirect overhead, and 0.1-0.3x profit margin. Federal work uses provisional indirect rates that are audited and trued up annually.
How should hour budgets be split across SD, DD, CD, and CA?
A common industry baseline for full-service design contracts is 15% SD, 25% DD, 40% CD, and 20% CA. These shift with project type — pure structural on developer-led work often has a smaller CA share, civil site/utility weights more toward CD, and geotech is usually front-loaded into a single investigation phase. The exact split matters less than tracking each phase as a separate budget so problems in one phase don't get hidden by underruns in another.
What utilization rate should I target for my staff?
Targets vary by role. Principals and senior PEs typically run 50-65% because they're also doing BD and technical review. PMs and senior engineers run 65-75%. EITs and staff engineers run 70-80%. CAD and BIM technicians run 80-90% as production-focused roles. Admin, marketing, and accounting are typically 0-15% billable, with their cost recovered through the multiplier. Firm-wide, 60-65% is healthy; above 70% sustained usually signals under-investment in BD and review.
How do I avoid losing money on lump-sum engineering contracts?
Track earned value weekly on every active project. For each phase, compare hours-budgeted-to-date against hours-actually-charged against physical percent complete. When hours-charged outpaces physical percent complete by more than 10%, flag the project and intervene before another 200 hours go in. The single most common cause of lost margin on lump-sum work is finding out at month nine that hours blew past budget in months three through six because nobody was looking weekly.
What markup should I apply to subconsultant fees?
Industry norm is 5-10% markup on subconsultant fees for private commercial work, compensating the prime for contracting risk, cash flow burden, and project management overhead. Federal and some institutional contracts require pass-through at cost with no markup. Each project's contract terms determine which rule applies, so the project management system needs to know per-project whether markup is permitted and at what rate. Forgetting to apply markup that the contract permits is direct margin loss.
Do I need dedicated AEC software like Deltek Vantagepoint, Ajera, or BQE Core?
Dedicated AEC platforms are credible options especially at 50+ person scale, where the depth of AEC-specific features and built-in compliance workflows pays back the implementation effort and seat cost. For smaller firms (5-25 people) without a dedicated controller or ops lead administering the tool, the implementation overhead and per-seat cost often outweigh the marginal feature depth. A consolidated work platform with the seven required capabilities (CRM, projects with phase budgets, time, docs, invoicing, resource planning, HR) on shared data can close 80-90% of the capability gap at meaningfully lower total cost. The right answer depends on firm size, sophistication of project economics, and whether the firm does federal work that requires DCAA-grade overhead accounting.
How long do I need to retain engineering project records?
Retention requirements vary by state professional licensing board and by contract terms, but 7-10 years from project close is a common baseline for signed and sealed drawings, calculations, RFIs, submittals, and transmittals. Federal work and certain institutional contracts can require longer retention. Your document management system needs version control, audit trails, role-based access, and retention policy enforcement to defend the firm if a project ends in litigation or a state board complaint.

The firm that closes the year 4% under target on a portfolio that looked green every month isn't unlucky. It's running on the wrong scoreboard. The fix is not a bigger spreadsheet or a more aggressive monthly review — it's a system that puts phase-based budgets, weekly earned value, real utilization by role, and proper markup discipline in front of the principal every Monday morning, with the data already in one place. Whether that system is a dedicated AEC platform or a consolidated work platform like Deelo is a question of firm size and budget. The non-negotiable is that some system is in place before the next lump-sum project ships its first hour.

Explore More

Related Articles