Next step to Contract signing

It depends on you teams level of engagement in the contract negotiations. Do you know the scope from the contract? Do you know the resources needed for the project. Was your IT department involved in the contract? At the very least, you would need a technical scoping call to understand the IT components and how the business plans to use the software, hardware or services. Developing a context diagram or system level diagram is a great way to understand the project. So what are the next steps:

1. Read the contract
2. Determine who does what
3. Start developing your staffing plan
5. Develop a scoping document
6. Start and complete the project charter
7. All these should be done in conjunction with Vendor project manager.

Nice threads here.
Number one always will be "read the contract"

Mr. MR-
The Main Contract usually dictates those Vendors/Subs that are REQUIRED to perform a Kick Off meeting for the Client. This is usually the most important Suppliers/Vendors/Subs and is supervised by the QC Department of the Main Contractor. (My Team)
I would never perform this task prior to Contract, since the specifics and ITP's are carefully laid out for the Client at these meetings.
However, the PM should NEVER issue a notice to proceed to a main vendor without conducting his/her own kickoff meeting with the Vendor which explicitly states the PM's priorities for the Project, and conveys that message directly to the Vendor's Principals.
Lastly, if you have waited until the kick off to produce a WBS for this particular Vendor your Project is in big trouble. As PM's we are the Dictator of terms to the suppliers, not recipients........

From the trenches!

M

Muthukrishnan ,

Since the contract might be a project for the supplier, they might do an internal kick-off meeting.
It is a good practice to have one with them anyway, make sure people are at the same place.