An example. A designer logs 41 hours in a week: 34 on two client projects and 7 on internal work. The manager spots 3 hours logged to the wrong client, rejects the week with a note, and approves it after the fix. The fix moves those 3 hours to the right client, so project costs and the next invoice use the correct split, and the approval locks the week.
"},{"heading":"How PLYNTUM handles it","html":"A manual timer, weekly timesheets and attendance are on every plan, with hours logged against a task in a project for a client. From Core, each person submits a week, and a manager approves it or rejects it with a note. Submitted and approved weeks are locked against edits. Project cost in PLYNTUM counts all logged hours, so a weekly approval habit keeps cost and approved time the same. See time tracking and the timesheet template.
See also time and billing software, delivery cost and all terms in the glossary.
"}]},"faq":[["Who should approve timesheets?","The person who knows the work: usually the project or team lead, not finance."],["How often should timesheets be approved?","Weekly. Monthly approval turns a five-minute check into an archaeology project."],["Does PLYNTUM track time automatically?","Not today. Private desktop time capture is in development; hours are entered by timer or by hand."]]}