Live project queue
Every open project shows its stage, owner and next step, sorted so that held items appear first.
A manager oversight app for structural engineering firms shows the general manager every open project, who is assigned to it and where the work is waiting on a review, a client or a permit comment. For iOS and Android, SIZ Group handles the build, and the admin side is set up for the firm's principals and project leads.
A first release should answer one question for the general manager: what is stuck, and who owns it. That means a live project queue, engineer assignments with their current load and a list of work waiting on a review, a client response or a permit comment.
Dashboards with revenue trends, utilization charts and margin per project can wait. They are useful once the queue is accurate, and a firm that adds them first often finds the numbers do not match the project files underneath.
Engineering work is licensed by state and sealed by a responsible engineer. The oversight app should show which principal must review and seal each deliverable, and it should block a deliverable from being marked issued until that review is recorded.
Project and client data often include property owners' details, construction budgets and disputes. Limit the full project view to principals and project leads, and keep staff access to their own projects unless the general manager grants more.
Retention rules apply to project files and review records. The app should keep an audit trail for each sign-off and make sure a reviewed version cannot be overwritten without a record of the change.
The most common mistake is measuring utilization by hours logged rather than by work that is ready to move. An engineer can log a full week and still be waiting on a client, and a manager who reads only hours will push the wrong person.
Second, teams build the queue from the stage names in their project software, which may not match how the principals think about a job. Map the stages with the principals before the build, so the queue reads the way the firm talks about its work.
Third, the app gets connected to nothing. If a project lead updates the stage in a separate file, the queue stays wrong, and the general manager returns to asking around the office.
Every open project shows its stage, owner and next step, sorted so that held items appear first.
Assignments show planned and open hours for each engineer, so the general manager can rebalance before a deadline.
Each deliverable records its principal review and seal status, and it cannot be marked issued until both are recorded.
Projects waiting on a client, a permit comment or an internal review trigger a note to the owner and the manager.
A one-page report covers projects issued, time held and workload by person, ready to share with the principals.
Principals see the full firm, project leads see their own projects and staff see only what they are assigned.
Pricing begins at $4,500. The largest drivers are the number of project stages, the review rules, the number of systems the queue must read from and the reports the general manager needs each month.
We keep scope under control by agreeing a first release with the principals, then adding views once the team has run a full project cycle through the queue. Changes requested during the build are priced in writing before they begin.
A clear list of stage definitions and review rules before the build usually prevents the most rework, so that list is the most useful thing to bring to the free scoping call.
Principals will use the queue if the first thing they see is their own projects, with held items at the top. Demonstrate it with a real list in the first session, rather than a generic demo that nobody recognizes.
Ask project leads to update the stage at the same moment they change their working files, at least for the first two months. Make the update a single tap on the phone or a short screen on the desktop.
Hold a brief weekly review in the first month, where the general manager walks through the held list with the team and clears any item that no longer belongs there.
Track the number of projects that have a named owner and a next step on the day the queue is checked. Track how long a project sits in each held state, and how often a deliverable reaches review without the required sign-off.
Also watch the number of status questions the general manager has to answer each week. If those questions fall while held items fall, the queue is doing its job.
Review these figures at the end of each project cycle, using the firm's own project records as the baseline rather than any outside benchmark.
Usually not. The app reads project status from the systems the firm already uses and adds the view the general manager needs. Where a stage is missing, the project lead updates it in the queue, and the change is passed back to the source system the firm prefers.
It compares planned hours with the open work on each engineer's projects, and it separates out work that is on hold. An engineer waiting on a client is not shown as overloaded, which prevents a wrong reassignment.
Yes. A deliverable cannot be marked issued until the responsible principal has recorded the review and the seal status. That record stays with the project, so any later question can be traced back to its source.
Review the held list, check engineer load for the coming weeks and confirm that stage updates are current. Once the queue is trusted, this routine usually fits into one standing meeting.
On a free scoping call we will map your stages and review rules, and you will get the scope and price in writing.