Blog
Project Scheduling for Structural Design Offices
Structural design offices manage a chain of dependent deliverables rather than one single task. A project may begin with surveys and architectural information, continue through structural analysis and design to Eurocodes, and finish with reinforcement drawings, steel detailing, calculation reports and issued drawings. Between these stages, engineers must coordinate with architects, contractors and other disciplines, respond to comments, and protect agreed issue dates.
That is why project management software for structural engineering can be more useful than a simple task list. A structured schedule makes the sequence of work visible, assigns accountability and shows how a late input or review can affect downstream deliverables. Microsoft Project Professional 2024 provides a dedicated desktop environment for structured planning, tracking and reporting, helping offices manage scope, deadlines and responsibility in one plan.
Why structural design projects need more than a task list
A basic task list may say “complete design” or “prepare drawings”. These descriptions are too broad for a structural project. They do not show which information is required first, which engineer owns the work, when a review is needed, or what must be complete before drawings can be issued.
A useful structural engineering project schedule breaks the commission into deliverables that can be planned and checked. For example, the structural package might include:
- Review of the architectural model, drawings and project brief.
- Check of survey information, existing structure data and design assumptions.
- Structural scheme development and selection of the calculation approach.
- Analysis model preparation and loading assumptions.
- Member design and verification to the applicable Eurocodes and project requirements.
- Reinforcement drawings, bar schedules and concrete details.
- Steel member, connection and fabrication information where relevant.
- BIM coordination, clash review and responses to design comments.
- Internal checking of calculations, drawings and revision information.
- Issue of calculation reports and construction drawings.
These activities have different owners, durations and dependencies. Analysis cannot be finalised before the design information and assumptions are sufficiently stable. Reinforcement detailing may depend on the approved member sizes and openings. A drawing issue may depend on both the design review and the response to coordination comments.
Microsoft Project Professional 2024 is suited to offices that need more control than disconnected lists or informal messages. The professional project-management edition helps turn a broad objective into scheduled activities, assigned responsibilities and measurable milestones. It does not replace structural analysis software, BIM authoring tools, document control or engineering judgement. Its role is to organise the work around those specialist tools.
Build a schedule from survey to issued drawings
Start with the delivery stages that the client and project team recognise. Then divide each stage into activities that have a clear output. This gives the schedule a practical structure without forcing every engineer to report every small action.
1. Define the main deliverable groups
Create high-level groups such as information review, scheme design, analysis, design development, detailing, coordination, checking and issue. These groups provide an understandable summary for project meetings. Under each group, add the activities needed to reach the next decision or issue date.
For example, “reinforcement drawings” may be divided into drawing setup, foundation plans, floor plans, sections, schedules, internal review and revision after comments. The correct level of detail depends on the project size. A small house extension does not need the same structure as a multi-storey commercial building, but both benefit from visible review and issue milestones.
2. Add information and decision milestones
Structural work is often delayed by missing or changing information. Record milestones for receipt of the architectural background, confirmation of the structural brief, issue of site information, approval of the design approach and receipt of coordination comments. These milestones make external dependencies visible.
Include decision points such as “scheme accepted”, “member sizes agreed” or “drawing package ready for checking”. A milestone is useful when it represents a real project event, not simply the end of an arbitrary period.
3. Link activities in the correct sequence
Connect activities so the schedule reflects how the office actually works. A typical sequence might be:
- Receive and review project information.
- Confirm assumptions, loads, constraints and design scope.
- Prepare the analysis model and perform initial checks.
- Develop the structural design and record calculation outputs.
- Coordinate the design with architecture, services and other disciplines.
- Update calculations and drawings after coordination.
- Complete internal checking.
- Issue the approved calculation report and drawing package.
Not every activity must wait for the previous one. While one engineer develops the analysis model, another may prepare drawing templates or review available architectural information. A structured schedule helps the project manager distinguish genuine parallel work from work that is only apparently independent.
4. Set issue dates as visible commitments
Drawing and report issue dates should be milestones or clearly identifiable activities. Separate design completion, checking and issue where the process requires all three. This prevents a package from appearing complete when the calculations are finished but the drawings still need checking or coordination.
Track analysis, coordination and review dependencies
Structural design offices often lose time at the boundaries between disciplines. The structural engineer may be ready to complete a design, but an architectural opening changes. A services route may require a beam revision. A coordination review may identify a column that conflicts with a façade element. These are schedule events, not just email conversations.
Use the schedule to show the relationship between technical work and coordination. A practical sequence can include:
- Issue the preliminary structural model or drawing information for coordination.
- Allow time for review by architecture, building services and other relevant disciplines.
- Record the date for consolidated comments.
- Plan the structural response and any necessary recalculation.
- Update affected reinforcement, steel or general arrangement drawings.
- Complete a focused internal check before the next issue.
Do not treat every comment as a full redesign. Classify the work internally by its likely effect: information clarification, drawing amendment, local design change or wider structural change. The schedule can then reflect the actual work and its effect on later deliverables.
For BIM coordination, the schedule should also distinguish model preparation, model exchange, review and response. BIM software remains the place where the model is created and checked. The project schedule provides the delivery framework: who must prepare information, when it is expected, and which subsequent tasks depend on the outcome.
Calculation and checking activities deserve particular attention. A calculation report may contain multiple design elements, assumptions and revisions. Plan time for the engineer to complete the design, for an appropriate person to check it, and for corrections to be made before issue. The same principle applies to reinforcement and steel detailing. A drawing can be visually complete while still requiring technical review.

Manage revisions, deadlines and team workload
Revision is normal in structural design. The challenge is to understand whether a revision affects one drawing, one design element or the entire delivery sequence. A project schedule helps the office assess the work before accepting a new deadline.
Make revision work visible
Create a separate activity or revision group for significant changes. Record the trigger, affected deliverables, responsible engineer and required review. For example, a change to a stair opening may affect a slab analysis, local reinforcement, several sections and the calculation report. Showing these activities separately is more reliable than adding “update drawings” to an old task.
Small amendments can be grouped when they are genuinely minor and handled by the same person. Larger changes should remain visible because they may consume time planned for another commission.
Plan workload by responsibility
Assign activities to roles or named team members according to the office’s working practice. Useful responsibilities may include project engineer, design engineer, BIM technician, reinforcement detailer, steel detailer, checker and project manager. The aim is not to record every minute. It is to see whether the same person is expected to complete several critical activities at the same time.
Review the schedule for conflicts around common bottlenecks. In many offices, the limitation is not the number of designers but the availability of a senior checker, a specialist detailer or a person who must coordinate several disciplines. If two projects require the same person before the same issue date, the conflict should be visible early.
Protect deadlines with review time
Do not place the checking activity after the promised issue date. Work backwards from the required issue and allow time for technical review, corrections, coordination responses and final preparation. The schedule should show the difference between the internal target and the external commitment when the office needs that protection.
Microsoft Project Professional 2024 is useful here because it provides a structured way to represent activities, dependencies, assigned responsibility and milestones. It does not decide whether a structural calculation is adequate, automatically approve drawings or remove the need for a competent checker. It helps the team see the delivery plan on which those professional decisions depend.
Create useful progress views for project meetings
A project meeting should answer practical questions: What is complete? What is late? What is waiting for information? Which issue date is at risk? Who needs support? A schedule becomes valuable when it provides answers without requiring a long explanation.
Prepare progress information around the project’s deliverables rather than around software activity. A useful meeting view can group work into:
- Not started: planned work with no meaningful progress.
- In progress: active analysis, detailing, coordination or review.
- Waiting: work blocked by information, a decision or another discipline.
- Ready for checking: deliverables that need internal review.
- Issued: calculations, drawings or models released for the agreed purpose.
- At risk: activities or milestones that may affect the next commitment.
Use milestones to focus discussion on decisions and issue dates. A long list of completed minor actions can hide a late calculation package. A milestone-based review keeps attention on whether the next deliverable can be issued with the necessary checks.
For internal reporting, compare the planned sequence with the actual position and record a short explanation for important changes. “Awaiting revised architectural openings” is more useful than simply marking a task late. It tells the project manager what action is needed and whether downstream work must be rescheduled.
Which planning approach fits a structural design office?
| Approach | Best suited to | Limitations | Recommendation |
|---|---|---|---|
| Basic task list | Very small commissions with few dependencies and one main person responsible. | Weak visibility of sequence, review time, workload conflicts and issue risk. | Use for simple internal reminders, not as the main plan for complex structural packages. |
| Spreadsheet schedule | Offices needing a lightweight overview of dates, deliverables and responsibilities. | Can become difficult to maintain when dependencies, revisions and parallel projects increase. | Suitable for simple or short projects if the team maintains it consistently. |
| Microsoft Project Professional 2024 | Offices managing multiple deliverables, dependencies, responsibilities, milestones and reporting needs. | Requires an agreed scheduling method and regular updates; it does not perform engineering analysis or document control. | Recommended for structured project planning from design initiation through issued drawings. |
How to introduce a structural project schedule
- Choose one live project with a clear upcoming deliverable.
- List the project stages and the drawings, calculations, models and reports expected from each stage.
- Add information, decision, checking and issue milestones.
- Assign responsibility and link activities that genuinely depend on one another.
- Review the plan with the engineers and adjust it to match the office workflow.
- Update progress before project meetings and record causes of important changes.
- Reuse the structure as a template, while adapting it for project size and technical scope.
Keep the schedule realistic. A plan that includes every possible task but is never updated will not improve delivery. A concise plan with clear deliverables, dependencies, review points and issue dates is more useful than a detailed plan that no one trusts.
For structural and civil engineering offices, Microsoft Project Professional 2024 is a suitable choice when a basic list no longer provides enough control. It helps organise scope, deadlines, accountability and reporting around the actual outputs of design work. Genuine Microsoft licences are available from KEYFORREST with instant electronic delivery; see the current price on the product page.
Domande frequenti
Can Microsoft Project Professional 2024 perform structural calculations?
No. It is project-management software for planning, tracking and reporting. Structural analysis, member design, detailing, BIM authoring and calculation checking still require the appropriate specialist tools and professional processes.
What should a structural engineering project schedule include?
Include information receipt, design assumptions, analysis, calculations, coordination, reinforcement or steel detailing, internal checking, revisions, calculation reports and drawing issue milestones.
How detailed should the schedule be?
Make each activity large enough to manage but specific enough to have one clear output, owner or review point. A major drawing package may need several activities, while a minor amendment may be grouped.
Should coordination reviews be separate tasks?
Yes, when they affect the delivery sequence. Showing model or drawing exchange, comments, responses and revised issue work makes external dependencies and deadline risks easier to manage.
Is Microsoft Project suitable for a small structural design office?
It can be, especially when the office handles several projects, repeated drawing issues or shared checking responsibilities. For a very small and simple commission, a well-maintained task list or spreadsheet may be sufficient.