In Timekit terms, a project is a configuration of a specific booking workflow. 

Depending on what kind of booking experience you're building it may consist of several specific booking blueprints. What booking type, what confirmation flow, which resources can be booked plus a whole range of other configurations - is collected in a project.

Example - Advisor booking
You have a team of advisors ( resources) who handles incoming bookings from customers during weekdays from 9 a.m to 4 p.m. The bookings get allocated randomly between available advisors and each advisor receives a booking confirmation they'll have to accept manually. 

These configurations about the advisor's availability, how their bookings should be confirmed and how the bookings should be allocated are all collected in a specific project that defines this booking's blueprint.

Example - Conference room booking
Your conference room could also be a resource that can be booked by employees or residents in an office community and is available 24/7 all days of the week. Booking requests for the conference room will be confirmed automatically when it's available and residents receive an SMS reminder 30 minutes before the reservation starts.   

These configurations of how bookings should be confirmed and whether residents should be reminded via email or SMS are all collected in a specific project that defines this booking's blueprint.

Ready to create a project? Check out these articles on how to create projects.

Note: Working with the Timekit API, configurations of booking blueprints is not collected in projects.
Learn more about booking blueprints on the API 

Perhaps these articles could be relevant for you:

Did this answer your question?