New project setup checklist
A checklist for starting a project, grouped into admin, team and client, with a short note on why each item matters and a rule for what must be done before work begins.

A project that starts without a setup routine gets its problems early and pays for them late. This checklist groups the work into three areas: admin, team and client. Use it as written, or cut it down to the items that match your size.
How to use the list
Run the checklist once, at the start, before the first billable hour. Give one person ownership of it, usually the project lead. Mark each item done, not applicable or blocked.
A rule worth adopting: work does not begin until the items marked "gate" are done. Those items are in bold below. Everything else can follow in the first week.
Admin
This is the paperwork and the structure that protects you if something goes wrong.
- Signed agreement or accepted proposal on file. The scope, price, payment terms and the date it was accepted. Gate.
- Deposit or first invoice sent. Agree what must be paid before work starts, and send it. Gate.
- Project record created. One place with the client name, project name, dates and owner.
- Budget set in hours and in money. For example, 80 hours at $100 an hour is $8,000. Record both so you can compare later.
- Milestones and dates listed. Even a rough list of three or four stages.
- Billing plan agreed. Upfront, milestone-based or monthly.
- Time tracking ready. Every team member knows which project and task codes to use. Missing time is a known source of lost revenue, covered in where billable hours go missing.
- Folder and naming set. Same structure as your other projects.
- Change process written down. How a request outside scope is priced and approved.
Team
This section is about making sure everyone knows what they are doing, and how long they have.
- Project lead named. One person who answers questions.
- Roles assigned. Who designs, who builds, who reviews, who talks to the client.
- Hours allocated per person. Say a 40-hour build split as 24 hours for one person and 16 for another. The two add up to 40, and you can see it.
- Capacity checked. Compare the allocation with what each person already has booked, to avoid overload in week two.
- Kickoff meeting scheduled. Fifteen to thirty minutes, covering goals, scope, dates and who does what.
- Tools and access sorted. Accounts, logins and shared folders.
- Risks listed. Three things that could go wrong, with an owner for each. A dependency on client content is a common one.
- Review and handover points marked. When work is checked, and by whom.
Client
This section sets expectations before they become disagreements.
- Main contact named. One person who can answer, and the person who can approve.
- Approvers identified. Who signs off on each stage, and how long they have to do it.
- Communication plan agreed. Channel, frequency and who attends. For example, one weekly update by email and one call every two weeks.
- What you need from them listed with dates. Content, access, brand files, decisions. Late client input can push every date after it.
- Feedback window agreed. For example, five working days for each review round.
- Number of revision rounds stated. Two rounds, written in the scope.
- Kickoff call held. Confirm goals and success measures in their words.
- Welcome note sent. A short email with the timeline, contacts and next steps.
A worked example of the budget line
Say a project is quoted at $8,000 and you plan 80 hours at $100 an hour. Your project manager sets alert points: at 50% of hours, 40 hours; at 80%, 64 hours.
- 80 x 0.50 = 40 hours.
- 80 x 0.80 = 64 hours.
When the project reaches 40 hours you check whether half the deliverables are done. If they are not, you know at the halfway point, not at the end. HireOrSell offers budget tracking on projects, and full time tracking is part of the Pro plan; check the pricing page for current prices.
Adapt the list to the size of the job
A two-day job needs five items: agreement, deposit, one contact, a due date and a place for files. A three-month project needs the whole list. Do not run the whole list on small jobs, or the team will stop using it.
Keep a master version and copy it for each project. After each project, update the master with anything that was missing.
Who does what: a simple split
A checklist fails when nobody owns it. Give each section an owner:
- Admin items: the project lead or whoever manages contracts and invoices.
- Team items: the project lead, with input from the people doing the work.
- Client items: whoever has the relationship, usually the person who sold the job.
Set a due date for the whole list, such as two working days after acceptance. If an item is blocked, write down what it is waiting for and who will unblock it.
Close the loop after the first week
The setup is not finished until it has been used. At the end of the first week, run a five-minute check:
- Has every team member logged time against the right project?
- Has the client supplied the first items on your list?
- Is anything on the risk list now a real problem?
- Are the dates still right?
If two or more answers are no, hold a short call and correct course. A drifting start is much cheaper to fix in week one than in week five.
Next step
Copy the lists above into a document, mark the gate items and use it on your next project. At the close of that project, note which items you never used and which ones you wished you had.
Ready to run it all in one place?
Projects, clients, time tracking and invoicing in one platform.