10 Things Every Project Manager Should Do Before a Project Starts

Before a project officially starts, the foundation is already being built. A strong start does not happen on the first day of work. It happens during planning, review, coordination, and proper communication before crews, contractors, vendors, or stakeholders begin moving.

For project managers, coordinators, site supervisors, estimators, or anyone involved in project delivery, the early stage of a project can determine whether the work runs smoothly or becomes a constant cycle of confusion, delays, extra costs, and finger pointing.

Here are 10 things every project position should always do before a project starts.

1. Understand the Full Scope of Work

Before anything begins, make sure the scope of work is clear. Do not rely only on a quick email, a basic quote, or a verbal explanation. Review the full work requirements, drawings, specifications, site notes, photos, exclusions, assumptions, and any client expectations.

A project can go wrong quickly when the team starts with different understandings of what is included. The project manager should know exactly what is being performed, what is not being performed, and where the scope may still be unclear.

2. Review the Site Conditions

A project should never be planned only from paper. Site conditions can completely change the way work needs to be completed. Before starting, review access points, staging areas, working hours, parking, loading zones, ceiling heights, hidden conditions, occupied areas, safety concerns, and existing damage.

Photos and site notes should be collected before work begins. This protects both the contractor and the client by documenting the condition of the site before any work takes place.

3. Identify Risks Early

Every project has risks. Some are obvious, while others are hidden until work starts. A good project manager looks for these risks before the project begins.

This can include material delays, permit requirements, weather impacts, unknown site conditions, access restrictions, lead times, tenant coordination, engineering requirements, or possible damage to existing finishes. The earlier these risks are identified, the easier they are to manage.

4. Confirm the Schedule and Critical Dates

A project schedule should be more than a rough start date and hopeful completion date. Before starting, confirm the expected duration, major milestones, key deadlines, delivery dates, inspection dates, and any restrictions that could affect progress.

The schedule should also account for realistic working conditions. Drying time, curing time, material lead times, inspection delays, and coordination with other trades all need to be considered. A rushed or unrealistic schedule usually creates avoidable problems later.

5. Confirm Roles and Responsibilities

Before the project starts, everyone should know who is responsible for what. This includes the client, board, property manager, project manager, site supervisor, trades, suppliers, engineers, designers, and inspectors.

Clear responsibility prevents confusion. It should be understood who approves changes, who answers site questions, who communicates with residents or stakeholders, who orders materials, who schedules trades, and who signs off on completed work.

6. Review Budget, Allowances, and Exclusions

The project team should fully understand the approved budget before work begins. This includes the contract value, allowances, unit rates, contingency amounts, change order process, and any exclusions.

Many disputes happen because someone assumed something was included when it was not. Reviewing the financial side before startup helps avoid uncomfortable conversations once the work is already underway.

7. Confirm Materials, Products, and Lead Times

Materials can make or break a project schedule. Before work starts, confirm what products are being used, whether they are approved, whether they are available, and when they can be delivered.

This includes flooring, paint, hardware, doors, fixtures, equipment, specialty products, and any custom items. If substitutions may be required, they should be reviewed and approved before they affect the schedule or final finish.

8. Establish the Communication Process

Every project needs a clear communication structure. Before startup, confirm how updates will be shared, how often updates are expected, who receives them, and what format they should be in.

This may include daily reports, weekly updates, progress photos, site meeting minutes, email summaries, or schedule updates. Clear communication helps prevent misunderstandings and keeps stakeholders informed before problems grow.

9. Review Safety, Access, and Protection Requirements

Before work begins, the project team must understand safety expectations and site protection requirements. This includes personal protective equipment, public safety, dust control, floor protection, elevator protection, resident notices, lockout procedures, fire safety, and emergency contacts.

Protection of existing finishes is especially important in occupied buildings. If walls, floors, elevators, doors, or common areas need protection, this should be planned before materials and workers arrive.

10. Hold a Proper Startup Meeting

A startup meeting is one of the most valuable steps before a project begins. This meeting should bring together the key people involved and confirm the scope, schedule, responsibilities, site rules, access, risks, communication process, and next steps.

This does not need to be overly complicated, but it should be documented. A simple meeting summary can prevent future confusion and create a clear record of what was agreed to before work started.

Final Thoughts

The success of a project is often decided before the first tool is picked up. When project managers take the time to properly review the scope, confirm responsibilities, identify risks, and communicate clearly, the project has a much better chance of staying organized, on schedule, and within budget.

A strong project startup does not eliminate every problem, but it gives the team a clear structure for dealing with issues when they appear.

In project management, preparation is not extra work. It is the work that protects the project.