A project initiation checklist (for software system selection) should contain all the things you need to consider at the very start of a new software system selection project. The example project initiation checklist below contains 30 points to consider: What - is the software / system selection project?  Has the project proposal been approved by the board without any changes to the proposal? Or if the board has made changes, can you manage these?  Has sufficient funding been approved for the software selection phase?  Are the project objectives still the same as within the proposal?  Is the project scope (inclusions and exclusions), still the same as within the proposal?  Are the project deliverables still the same as within the proposal?  Have deliverables been defined for each stage within the software selection?  Have acceptance criteria been defined for each deliverable? When - will the project be undertaken?  Have the start and completion dates been defined and agreed?  Have dates for the key deliverables within the project been defined and agreed? Who - is involved with the project?  Provide names for: o project sponsor: o project manager: o project team: o key users: o user management (who are responsible for signing off the requirements and accepting the system selection deliverables)  Have all the roles and responsibilities been defined?  Have all the roles and responsibilities been communicated?  Do all resources (involved) have sufficient time available for the project?  Is project resourcing sufficient?  Do all resources have sufficient knowledge / skills to undertake their part in the project?  Have you prepared and issued a project organisational chart?  Does everyone understand their role within the project? How - will the project be carried out?  Have you determined your project management / system selection methodology?  Have you prepared a revised (or final) project plan / gantt chart?  Are responsibilities, milestones and deliverables clear?  Have these been issued and discussed with all involved?  Does everyone understand them?  Have you purchased tools to help you document your business requirements / select your new system? If requirements have yet to be specified, these RFI/RFP Templates can quickly help and save you time.  Have you set up project communications? eg planned regular (weekly) project meetings, defined an email list of other people to be kept informed?  Have you set up an issues escalation process?  Have you set up project monitoring? eg using a project management tool  Have you defined quality standards and specified how these will be maintained?  Have you reviewed your risk analysis and mitigation strategies?  Have you reviewed your project constraints / assumptions and checked that they are still valid?  Have you created project contingencies? eg additional time, funding or resources For more software selection information, visit: 10 Steps to select new business software / Stakeholder management tips / Sample project plan for business system selection / RACI matrix / Project initiation checklist / Software selection time-saving tips / Project issue log / Requirements gathering techniques / Reasons to write a good requirements specification / System design review / Risk assessment form / Risk assessment worksheet / Warning signs that your software selection may have problems / Project reporting form / Project status report template