If you were setting up a plumbing service company to run on a version of SeedCode Complete. How would you handle jobs? Would you make them events or projects?

Thank you.

They can of course be either, but I think they make sense as projects if jobs...

- have more than one invoice and you need to look at the job's total $$ as a whole, rather that just the customers total $$,

- or require the scheduling of multiple events, such as follow up visits, additional trips on site, etc,

- or they have estimates,

- or the job exists independent of the date they are scheduled. If, for example, you want to be able to say that you want to redo a shower for customer X but don't have a date yet. Using the project lets you get all that down and then schedule the actual on site work at a later date.

- out of the box, projects in Complete also have media (photographs, for example) associate with them, though you could of course add that to events as well.

- finally, projects have access to the Process and Milestones template engine (look on the settings tab) where events do not. These are probably only helpful for big jobs where you want to put things on the calendar as then job's status changes.

The job is probably best done as a single event if it is a one time thing and is invoiced just once. And of course you can do both, using Projects for "big" jobs only.

This idea of how you map the entities in your world to the nouns and verbs in SeedCode Complete is something you may go back and forth on. So there is a lot to be said for playing with it.

Hope that helps,

John

Thanks John. Very helpful.