Problem guide
Project status lives in one person's head
Status lives in one head when the people doing the work have nowhere official to put it, so the real state of each job, order or case travels by phone to whoever keeps track. Software rarely helps on its own: in ServiceTitan a job reads In Progress from first dispatch until someone completes, cancels or holds it, and its help tells users to schedule a report of held jobs so they are not forgotten. Give every blocker a status, an owner and a date.

How it actually happens
Most companies have one person who knows where every job, order or case stands. It is often the project manager, the operations manager, a senior coordinator or the office manager who has been there longest. Nobody appointed them. They became the keeper because every phone call ended at their desk, and they were good at remembering.
Here is how it builds, as a general example from construction. A superintendent on a tenant build-out learns at 7 a.m. that the ceiling inspection slipped to Thursday. He texts the project manager. The project manager writes it in his notebook and moves the drywall crew in his head. The schedule in the system still shows drywall on Wednesday. At 10 a.m. the owner's rep calls the office, and the receptionist reads her the Wednesday date. At noon the drywall foreman calls the project manager directly, because he learned long ago that the board is not where the answer is.
Each step was reasonable. The superintendent told the right person. The project manager acted on it. The gap is that nothing wrote the change into a place anyone else could see. The status lived in a text thread and a notebook, and the system kept showing yesterday.
Other businesses run the same pattern with different nouns. A law firm's matter waits on the other side's documents, and only the responsible attorney knows. A clinic's patient waits on a prior authorization, and only one coordinator knows. A warehouse order is held for a short shipment, and only one customer service rep knows. The system shows the item open or released. The reason lives with a person.
Service work has the same shape on a smaller scale. A technician diagnoses a failed part, orders it, and types the reason into the job notes. In ServiceTitan the job stays In Progress until someone holds, completes or cancels it, so the dispatcher sees an active job and calls the customer to ask why the tech left. In Fieldwire the out-of-the-box task statuses have no waiting state, so a task stalled on an inspection looks the same as one being worked.
The cost shows up when the keeper is away. Vacations, sick days and a busy week all make the company slower, because every question has to wait for one person. It also shows up in disputes. Months later, when a customer asks why something ran late, the answer has to be rebuilt from texts and memory, and on an AIA job the owner may already have the architect's report of the deviation from your last schedule.
The fix is not to replace the keeper. It is to give the people doing the work a place to put the state, so the keeper's knowledge is written down as it happens.
The one-week cover test
Ask someone else to run status for a full week while the usual keeper is still in the building and available. Every question the substitute has to ask is a piece of status that was never recorded. Write each one down. By Friday you have the list of fields your system is missing.
Signs you have this problem
- Every question about where a job or case stands ends with somebody saying ask Mike
- The board or list shows work active that is really waiting on a part, a permit, a signature or an answer
- A week off for the project lead means customer calls go unanswered
- Status meetings are spent reconstructing what happened rather than deciding what happens next
- People write the reason work is stuck in a note that nobody in the office reads
What usually causes it
- Blockers are reported by phone or text to one person, who keeps them in a notebook or in memoryThe field-to-office split
- The system offers a free-text note where the office needs a status, so stuck work still reads as activeThe invisible queue
- When the work passes from sales to the project lead to the people doing it, each keeps their own picture and none writes it downThe handoff gap
Find your cause
Ask these in order. The first yes is usually where yours starts.
- Can anyone besides one person say, within a minute, why each open job, order or case is not finished?If yes: if not, the reasons are in memory. Build the short list of blocker reasons and require one on every stuck item.
- Does work show as active while it is waiting on something?If yes: the system has no waiting state in use. Turn on holds or a custom status and use it.
- Do people explain delays only in free-text notes?If yes: the office has to read every note to know the state. Move the reason into a field the list can filter.
- Did the last vacation of your project lead, coordinator or dispatcher cause missed calls or dates?If yes: the business depends on that person being present. Run the cover-for-a-week test before the next one.
How it breaks in each industry
- General contractors and commercial subcontractors
- The superintendent knows the job is waiting on a door hardware submittal and an inspection. The project manager hears about it by phone and keeps it in his notebook. Under an unmodified A201-2017, what the owner tells the superintendent binds the contractor, so status the superintendent holds is already the company's knowledge whether or not it reached the office.
- HVAC service
- The technician finds a failed control board, orders it, and leaves. Unless someone holds the job, ServiceTitan keeps it In Progress. If the tech holds the appointment after arriving, that appointment is marked Done, and the reason sits in whatever the tech typed.
- Commercial electrical
- The foreman knows a floor is waiting on the switchgear delivery date and the ceiling inspection. In Fieldwire, the out-of-the-box task statuses are three priorities plus Completed and Verified, and In Progress is a filter on start and end dates, so waiting work looks the same as active work unless the project adds a custom status.
- Law firms
- The responsible attorney knows the matter is waiting on the other side's documents and a hearing date. The matter list shows it open, the paralegal tracks deadlines in a separate calendar, and a client who calls while the attorney is in trial gets told someone will call back.
- Healthcare practices and clinics
- One coordinator knows which patients are waiting on a prior authorization, a referral or outside records. The scheduling system shows the appointment as pending, the reason sits in her notes or on sticky notes, and when she is out the front desk cannot tell a patient what is holding them up.
- Logistics and third-party warehousing
- A customer service rep knows an order is held for a short shipment, an address problem or a carrier pickup that did not happen. The warehouse system shows it released, and the client's question about it waits for that rep to come back from lunch.
Where it breaks between systems
- ServiceTitan job holds
- A job is placed on hold with a reason picked from a list that only administrators and users with permission can manage, and held appointments show at the bottom of the Dispatch Board. ServiceTitan's FAQ tells users to schedule a report of held jobs so they do not forget them.[1]
- ServiceTitan job and appointment statuses
- A job moves to In Progress at first dispatch and stays there until it is completed, canceled or put on hold. A job can be completed early with appointments not done, and it shows Hold only when all appointments, or the last one, are held.[2]
- ServiceTitan appointment holds after arrival
- Dispatched, Working, Canceled and Done appointments cannot be held; the job has to be held instead. Putting an appointment on hold after the technician has arrived marks that appointment Done.[3]
- Jobber visit notes
- Jobber's help says a note left on a visit becomes an internal job note, who can read it depends on a notes permission, and a note saved offline stays on the device until it syncs. Only the 100 most recent notes show on an item. A note is not a status.[4]
- Housecall Pro private notes
- Private notes on a job or estimate are visible to admins, office staff and field techs but not customers, and keep a history of who edited them and when. Nothing on the page ties a note to a job status.[6]
- Fieldwire task statuses
- Fieldwire's help lists Priority 1, 2 and 3, Completed and Verified as the default task statuses; In Progress, Today and Overdue are filters driven by start and end dates. Custom statuses exist only on Pro, Business and Business Plus plans.[8]
- Procore Daily Log
- Only an Admin can mark a day Complete, which locks its entries until an Admin reopens it. The Scheduled Work log keeps pulling live data from the uploaded schedule, so a completed day can show later schedule changes when it is revisited.[9]
- Procore and Sage 300 CRE
- The integration carries financial records, not field conditions. By default, exports to Sage wait for an accounting approver, and projects that were in progress or created before the integration was connected cannot be synced without paid professional services.[10]
- Housecall Pro dispatch contact
- An account can name a single Dispatch and Messaging point of contact, no more. Every customer reply to an automated text goes to that person, and every job booked online is assigned to them automatically.[7]
By the numbers
No industry association or government survey publishes a figure for this. The measurement below gives you your own.
Rules that apply
- AIA A201-2017, Sections 3.9.1 and 3.9.3, the superintendent[11]
- Under the unmodified form, the contractor keeps a competent superintendent at the site who represents the contractor, and communications given to the superintendent are as binding as if given to the contractor. The superintendent cannot be changed without the owner's consent, which may not be unreasonably withheld.
- AIA A201-2017, Section 3.10.2, the submittal schedule[11]
- The contractor submits a submittal schedule for the architect's approval and keeps it current. If submittals do not follow the approved schedule, the contractor is not entitled to more money or time for the review delay. A submittal status known only to one person can cost that claim.
- AIA A201-2017, Sections 4.2.2 and 4.2.3, the architect's site visits[11]
- The architect visits at intervals suited to the stage of construction and reports to the owner known deviations from the most recent construction schedule the contractor submitted. The owner can hear about a slip from the architect before hearing it from you.
- FAR 52.236-6, Superintendence by the Contractor[12]
- On federal fixed-price construction above the simplified acquisition threshold, the contractor directly superintends the work or keeps on it a competent superintendent, satisfactory to the contracting officer, with authority to act for the contractor, until the work is completed and accepted (prescribed at FAR 36.506).
Measure it in your own shop
From: The list of open jobs, orders or cases from your system, the held or on-hold report if you have one, the notes and logs on those items, and an hour with the person who usually knows.
- Print every open item older than seven days. Next to each, write the status the system shows.
- Without looking at notes, ask the usual status keeper to say what each item is waiting on, who owns it and when it should clear. Write the answers down.
- Now check the system for each answer: a hold reason, a status, a dated note. Mark each item as recorded, partly recorded or not recorded.
- Count the items where the system status disagrees with what the keeper said.
Reading it: The share of items marked not recorded is how much of your status lives in one head. The disagreements are items the office would handle wrong on a day that person is out. If both are near zero, the problem is elsewhere, usually in how fast the people doing the work update the record.
What does not fix it
- A rule that everyone keeps the system updated
- If the system offers only a note box, people will update the note box. Without a status that means waiting, the list still shows the work as active.
- A weekly status meeting
- The meeting moves the knowledge from one head into a room once a week and then back. Nothing is left on the record for the next phone call on Tuesday.
- Integrating the project system with accounting
- The Procore and Sage 300 CRE connection carries budgets, commitments and costs, not whether a floor is waiting on an inspection. Status is not in the data that syncs.
What to try this week
- List what work can wait onWrite the short list of reasons work stalls in your business: parts, permit, inspection, customer approval, a signature, an outside answer, a vendor, access. Six to ten reasons is plenty. Every stuck job, order or case gets one.
- Make the reason a field, not a notePut the reason where the office can filter by it. In ServiceTitan that is a hold reason from an admin-managed list; elsewhere it can be a custom status or a tag. A paragraph in the notes does not count.
- Give each blocker an owner and a dateNext to the reason, write who is chasing it and when it is expected to clear. The date matters more than the detail.
- Run the held list every morningPrint or schedule the report of held or blocked work and go down it at the start of the day. ServiceTitan's own FAQ says to schedule that report so held jobs are not forgotten.
- Cover the keeper for a weekHave someone else run status for five days while the usual keeper is still in the building. Everything they have to ask about is something that was not written down.
Where do-it-yourself stops
These steps get the blockers out of one person's memory and onto a list. The list still depends on the person doing the work picking a reason, someone in the office keeping it current, and the record and the schedule agreeing about what is active. The lasting fix is a tool built around how your work actually stalls, so the person who hits the blocker sets the state in one tap and the office sees it the same minute. That is what a Workflow Spec designs.
Questions people ask
How do I stop work on hold from being forgotten?
Give each held item a reason from a fixed list and review the held list every day. ServiceTitan's help recommends scheduling a report of held jobs for exactly that reason, and shows held appointments at the bottom of the Dispatch Board.
Why does a job show In Progress when nobody is working on it?
In ServiceTitan a job stays In Progress from the first dispatch until someone completes, cancels or holds it. In Fieldwire, In Progress is a date filter, not a status. Unless someone sets a waiting state, the job reads as active.
Is what we tell the superintendent binding on the company?
Under an unmodified AIA A201-2017, section 3.9.1 says communications given to the superintendent are as binding as if given to the contractor. That makes the superintendent's knowledge of a problem the company's knowledge.
Can a note serve as the status?
Only if someone reads it. Jobber turns visit notes into internal job notes whose visibility depends on a permission, and a note saved offline waits on the device until it syncs. A status the list can filter is more reliable.
Does integrating our systems fix this?
Usually not by itself. Integrations between project and accounting systems move financial records. The reason work is stuck has to be captured somewhere first, and most often it is not.
Next step
How we fix this
This guide is how to find it and work around it. If it keeps coming back, it is rarely the only thing costing you. We come on site, find the issues costing you the most, and fix them, starting with the most pressing.
Fox & Santiago, Genesee, Idaho. We work nationwide, for clients across the United States, from our headquarters in Genesee, Idaho.
