- \n
- The AIA\/Deltek ABI fell to 44.7 in September 2026 and design contracts weakened to 43.7, so fees on existing projects now carry more financial weight.<\/li>\n
- Revision and approval hours leak because requests arrive through email, calls and markups and seldom become logged tasks tied to a project and a fee.<\/li>\n
- A revision log that records owners, scope decisions and time entries gives principals defensible evidence when they request additional services.<\/li>\n
- Connecting tasks, approval reminders and timesheets helps practices with several teams see revision effort before the fee runs out.<\/li>\n<\/ul>\n
At a glance<\/strong><\/p>\n
- \n
- ABI score (September 2026):<\/strong> 44.7, down from 47.2 in August<\/li>\n
- Project inquiries index:<\/strong> 53.2, a modest rise<\/li>\n
- Design contracts index:<\/strong> 43.7<\/li>\n
- Average backlog:<\/strong> 6.2 months at the end of Q3, down from 6.6 at the end of Q1<\/li>\n
- Weakest region:<\/strong> Northeast, at 39.1<\/li>\n
- Release date:<\/strong> October 21, 2026 (AIA\/Deltek)<\/li>\n<\/ul>\n
What did the September 2026 ABI show for architecture firms?<\/h2>\n
The September 2026 AIA\/Deltek Architecture Billings Index fell to 44.7 from 47.2 in August, meaning the greatest share of firms reported declining billings since May. Project inquiries rose modestly to 53.2, but the design contracts index dropped to 43.7. Clients are exploring projects without committing to them. For most firms, that means revenue now depends on projects already under contract.<\/p>\n
The ABI is a diffusion index, so a score below 50 means more firms reported declining billings than rising ones. AIA reported that average backlogs, meaning the months of contracted work still awaiting billing, fell to 6.2 months at the end of the third quarter from 6.6 months at the end of the first (AIA, 2026<\/a>). Multifamily residential firms saw backlogs fall from 6.2 months in March to 4.8 in September.<\/p>\n
Conditions vary sharply by region. Residential Design’s summary of the release lists the Northeast at 39.1 and the South at 43.1, while the West (50.7) and Midwest (50.6) hovered near the growth threshold of 50 (Residential Design, 2026<\/a>).<\/p>\n
According to AIA, 45% of firm leaders estimated their 2026 net revenue would be down from 2025, by an average of 2.9%. One Northeast sole practitioner summed up the mood: "Current work is carrying us, but new work looks scarce" (AIA, 2026<\/a>).<\/p>\n
\n
"This is an increasingly difficult environment for architecture firms," said AIA Chief Economist Richard Branch (Residential Design, 2026<\/a>).<\/p>\n<\/blockquote>\n
Why do revisions and approvals leak billable hours when billings soften?<\/h2>\n
Revisions and approvals leak billable hours because they arrive informally and get quietly absorbed into the base fee. A client email asks to relocate a stair, a consultant returns a markup or a design review runs long. None of it becomes a task with an owner and a time entry, so the firm cannot later prove the work happened.<\/p>\n
In a strong market, practices can absorb some unrecorded effort because new projects make up for it. When contracts slow, the same unbilled hours hit utilization and margin harder. Branch also pointed to growing caution among clients, which suggests approvals may take longer and push back the milestones that trigger invoices.<\/p>\n
Two contract terms frame the problem. Scope creep<\/strong> is the gradual growth of work beyond what the agreement describes. Additional services<\/strong> are the extra fees that owner-architect agreements typically allow for work outside the original scope. A firm can only claim them convincingly when it can show what changed, who asked for it and how long it took.<\/p>\n
![\"Marked-up](\"https:\/\/pub-0bf109f42f5d4bc78371f0fd6f01ffb2.r2.dev\/blog-images\/blog-task-management-software-for-architecture-firms-in-a-billing-slump\/71c931b3-a110-458a-84a2-ccb0982b0ca4\/task-management-software-for-architecture-firms-in-a-billing-slump-inline.webp\")
<\/p>\nWhy does manual tracking stop working as a practice grows?<\/h2>\n
Manual tracking stops working because people, projects and handoffs multiply faster than anyone can keep track of them. A five-person studio can reconcile revisions from a shared inbox and a spreadsheet. A practice with several studios, outside consultants and dozens of active projects cannot, because the revision history ends up scattered across individuals.<\/p>\n
Excel works well for simple tracking, so the spreadsheet itself is not the issue. The difficulty is that requests, approvals and hours live in separate places and are matched up only after the fact. By then, project managers have spent weeks asking colleagues for updates, and the right moment to raise a fee conversation has usually passed.<\/p>\n
Which architecture workflows decide whether revision time gets billed?<\/h2>\n
Eight recurring workflows decide whether revision and approval effort ever reaches an invoice. Each one produces data, such as requests, dates, owners, decisions and hours, which usually sits in separate inboxes and spreadsheets. When these workflows are connected, project managers can see the total cost of changes before the fee runs out.<\/p>\n
- \n
- Request intake:<\/strong> Comments by email, phone, PDF markup or meeting minutes each become one logged request with a date and a requester.<\/li>\n
- Scope decision:<\/strong> A project manager records whether the request is in scope or an additional service. If nobody records the decision, the work is free by default.<\/li>\n
- Revision assignment:<\/strong> One person owns the change, with a due date and the markups attached.<\/li>\n
- Consultant coordination:<\/strong> Structural and MEP (mechanical, electrical and plumbing) consultants respond, often raising fee questions of their own.<\/li>\n
- Client approval request:<\/strong> Revised drawings go out for sign-off at a defined milestone.<\/li>\n
- Approval follow-up:<\/strong> Chasing outstanding decisions, which is real effort that usually goes unrecorded.<\/li>\n
- Project timesheets:<\/strong> Hours are recorded against the project, the phase and the specific revision.<\/li>\n
- Additional-services documentation:<\/strong> The revision log and hours are assembled into a change proposal.<\/li>\n<\/ol>\n
![\"Hand](\"https:\/\/pub-0bf109f42f5d4bc78371f0fd6f01ffb2.r2.dev\/blog-images\/blog-task-management-software-for-architecture-firms-in-a-billing-slump\/6a3f228c-6c28-47e7-bfcf-9617a4e10b39\/task-management-software-for-architecture-firms-in-a-billing-slump-inline-2.webp\")
<\/p>\nHow does architecture project revisions tracking work in practice?<\/h2>\n
Effective architecture project revisions tracking treats every change request as a separate task linked to a project, an owner, a scope decision and time entries. The resulting log becomes evidence the firm can show a client, not something people have to remember. Our earlier Task Tracking Tool for Architects<\/a> guide covers design stages. This article focuses on revisions and approvals within those stages.<\/p>\n
Here is an illustrative scenario. After design development sign-off on a mixed-use building, the client emails asking to reconfigure the ground-floor lobby. The project manager logs it as revision 14, records the requester and date, and flags it as out of scope pending a fee discussion. The designer gets the task with the markup attached, and every hour goes against that task rather than a generic design code.<\/p>\n
When the revised plans are issued, an approval task with a deadline is created. Email notifications remind the task owner 48 and 24 hours before that deadline, and the project manager follows up with the client. At month end, nothing needs to be pieced together from memory. The documented hours turn a potentially awkward additional-services conversation into a straightforward review of recorded work.<\/p>\n
How should time tracking for billable hours be set up by project?<\/h2>\n
Time tracking for billable hours works best when every entry carries a project, a phase and, for changes, a specific revision task. Generic codes such as "admin" or "design" hide revision effort. Structured entries let principals compare hours used against the remaining fee while there is still time to act.<\/p>\n
- \n
- Project and phase codes<\/strong> that match the fee structure in the contract<\/li>\n
- Revision tasks<\/strong> flagged as in scope or additional, so hours can be filtered later<\/li>\n
- Approval follow-up tasks<\/strong>, so time spent chasing clients shows up as recorded work<\/li>\n
- Daily entries<\/strong>, because hours pieced together on Friday afternoon are rarely accurate<\/li>\n
- A weekly review<\/strong> comparing logged hours with the remaining fee for each phase<\/li>\n<\/ul>\n
Where can AI and automation help without replacing professional judgment?<\/h2>\n
Automation handles repetitive steps such as reminders before approval deadlines, recurring timesheet reviews and scheduled summary reports. AI can use existing task data and configured rules to help teams see which work needs attention first. Architects and project managers still decide scope, fees and what to say to clients.<\/p>\n
The practical gain is fewer manual follow-ups. AI suggestions about who should take a revision, or which tasks may slip, are only as reliable as the underlying records. If revisions and hours are not logged consistently, AI has nothing dependable to work from.<\/p>\n
What should you look for in task management software for architecture firms?<\/h2>\n
Look for software that links revisions, approvals and timesheets to the same project record, sends automatic reminders and produces reports without manual compiling. Permissions, clear ownership and quick daily time entry matter more than a long feature list. A very small studio may need much less.<\/p>\n
A connected platform is worth evaluating when several of these apply:<\/p>\n
- \n
- Multiple project teams or offices working at the same time<\/li>\n
- Frequent client revisions on fixed-fee contracts<\/li>\n
- Approval delays pushing back milestone invoices<\/li>\n
- Project managers spending hours chasing updates<\/li>\n
- Timesheets compiled by hand at month end<\/li>\n<\/ul>\n
By contrast, a sole practitioner with three active projects may be well served by a simple task list and a timesheet spreadsheet. Adopting a platform before the coordination problem exists only adds administrative work.<\/p>\n
How does TrackerSuite fit an architecture practice?<\/h2>\n
TrackerSuite is an AI-powered operations platform that connects tasks, reminders, timesheets and reporting. For an architecture practice, the value is in turning revision requests and client approvals into tracked tasks with owners, due dates and logged hours that principals can review without asking each team for updates.<\/p>\n
Capabilities listed on the TrackerSuite pricing page that map to these workflows include:<\/p>\n
- \n
- Task Tracker:<\/strong> Log each revision as a task and tag team members on it.<\/li>\n
- Email notifications:<\/strong> Sent 48 and 24 hours before a task is due, which suits approval deadlines and internal revision dates.<\/li>\n
- Recurring tasks:<\/strong> Schedule weekly timesheet reviews or monthly checks of hours against fee.<\/li>\n
- Attendance rules, check in and check out:<\/strong> Show who is working each day, alongside the tasks they own.<\/li>\n
- Performance score and reports, plus daily automated reports on WhatsApp:<\/strong> Give principals a regular summary.<\/li>\n
- Workflow add-on:<\/strong> Available with the Growth plan at USD 4.08 per user per month, it breaks large tasks, such as a multi-sheet revision, into smaller steps.<\/li>\n
- TAVI:<\/strong> Powers TrackerSuite’s AI-based predictive tasking.<\/li>\n<\/ul>\n
At the time of writing, the pricing page lists a Basic plan at USD 0 alongside paid plans. Firms that run project accounting in a separate system should confirm how task and timesheet data would move into it before committing.<\/p>\n
What this means for you<\/h2>\n
Start with one project that has a history of revisions, then expand:<\/p>\n
- \n
- Choose a pilot project<\/strong> with frequent client changes and a fixed fee.<\/li>\n
- Define revision and approval task types<\/strong>, including an in-scope or additional flag.<\/li>\n
- Log every change request<\/strong> as a task within a day of receiving it.<\/li>\n
- Set approval deadlines<\/strong> so automatic reminders prompt the task owner to follow up with the client.<\/li>\n
- Require daily time entries<\/strong> against the project, phase and revision task.<\/li>\n
- Review hours against fee weekly<\/strong> and raise additional-services discussions early.<\/li>\n
- Extend the process<\/strong> to other projects once the team trusts the reports.<\/li>\n<\/ol>\n
Does the same approach apply to lending, payment and venture capital firms?<\/h2>\n
Yes, as a side note. The habit that protects revision hours in architecture, giving every request an owner, a deadline and a record, applies wherever requests and approvals drive the work. Task management software for lending companies typically focuses on collecting documents and moving credit approvals forward, where an unanswered request stalls the whole file.<\/p>\n
Task management software for payment companies often supports merchant onboarding and compliance reviews, and task management software for venture capital firms usually tracks deal pipelines and due diligence requests. The principle is the same as in architecture: connect every request to an owner, a deadline and a record.<\/p>\n
FAQs<\/h2>\n
What does an ABI score below 50 mean?<\/h3>\n
A score below 50 means more architecture firms reported declining billings than rising billings that month. AIA describes the index as a leading indicator of nonresidential construction activity about 9 to 12 months ahead.<\/p>\n
How do architecture firms bill for client revisions?<\/h3>\n
Firms usually bill out-of-scope revisions as additional services under the owner-architect agreement. To do that, they need to show who requested the change, when it was approved and how many hours it took.<\/p>\n
How should architects track billable hours on revisions?<\/h3>\n
Record hours daily against a project, a phase and a specific revision task instead of a generic code. Weekly comparisons of hours against the remaining fee let project managers raise scope conversations early.<\/p>\n
Do small architecture firms need task management software?<\/h3>\n
Not always. A sole practitioner with a few projects may manage well with a shared list and a timesheet. Dedicated software becomes worthwhile when several teams, consultants and approval chains make tracking by hand unreliable.<\/p>\n
Conclusion<\/h2>\n
Softer billings make every unrecorded hour more expensive. Firms cannot control when clients sign new contracts, but they can control whether revision effort, approval delays and project hours get recorded as evidence. Task management software for architecture firms is most useful when it connects those three records on every active project. To see whether a connected setup suits your practice, compare TrackerSuite plans<\/a>.<\/p>\n
Sources<\/h2>\n
- Define revision and approval task types<\/strong>, including an in-scope or additional flag.<\/li>\n
- Email notifications:<\/strong> Sent 48 and 24 hours before a task is due, which suits approval deadlines and internal revision dates.<\/li>\n
- Task Tracker:<\/strong> Log each revision as a task and tag team members on it.<\/li>\n
- Revision tasks<\/strong> flagged as in scope or additional, so hours can be filtered later<\/li>\n
- Scope decision:<\/strong> A project manager records whether the request is in scope or an additional service. If nobody records the decision, the work is free by default.<\/li>\n
- Project inquiries index:<\/strong> 53.2, a modest rise<\/li>\n
- ABI score (September 2026):<\/strong> 44.7, down from 47.2 in August<\/li>\n