▲ | reactordev 3 days ago | |||||||||||||||||||||||||||||||
It’s missing another option. Contract for a date, for a set amount of hours, until a completion date. There’s an hours version but it’s based on weekly hours, not total hours. There’s one based on date but not taking into account hours. | ||||||||||||||||||||||||||||||||
▲ | baobabKoodaa 3 days ago | parent [-] | |||||||||||||||||||||||||||||||
Could you clarify what you mean by "weekly hours, not total hours"? If you input weekly hours and a completion date, doesn't that achieve exactly what you want? The contract will be valid until the date that you specify, and during the time that the contract is valid, you can charge approximately the amount of weekly hours specified. For example, if you have agreed to charge 40 hours per week for 4 weeks, then that is the same thing as agreeing to 160 hours in total. The wording in the generated contract is such that you don't have to work the exact same amount of hours each week, you can work more during one week and less during another week. Perhaps you mean that you want to lock down an exact, specific number of hours, rather than allowing any sort of flexibility on the total number of hours? This would be better suited for the "project based billing" option, but as you said, that one doesn't have the option to set a completion date. The reason why it doesn't have the possibility to set a completion date is that it would create an ugly contractual situation in the case where the deliverables are not completed by the agreed-upon date. | ||||||||||||||||||||||||||||||||
|