Every timesheet gap found and every invoice drafted by Monday

Can a companion fill in the hours nobody logged?

It proposes them.

Asked to close the week, it lists each person’s existing entries, finds Thursday empty for two of them, and reads what it can legitimately see, the calendar you connected and the tickets you have open, to draft candidates: three hours against the migration project, one against the client call, each with its evidence attached.

Then it shows the person their own draft week. They correct two, confirm the rest, and it writes them. Nothing lands against a billable project until the person whose week it is says so.

The timer nobody remembers to stop

A companion starts a fresh entry, stops the timer that has run since lunch, and restarts the one you paused for a meeting, which removes the reason people batch-log a whole week from memory on Friday. Before logging against a project it reads that project’s task assignments, the only task ids the project will actually accept, rather than guessing from the global task list.

A time entry against the wrong task id does not fail loudly. It lands in the wrong bucket and shows up as an odd line on a client invoice a month later.

From logged hours to a sent invoice

Four native calls: list the time entries for the client and window, run the time report to aggregate them by project and task, create the invoice with those line items, and send it once you have read it. Recording a payment later is one more.

Every step before send is reversible. The send is not, so it waits for you. That single gate is what makes it reasonable to let a routine assemble the whole invoice run on the 1st of the month and hand you a stack of drafts. Agencies running billing inside their operations rhythm get the assembly back.

Do the hours match what the statement of work promised?

That answer needs the contract, the client thread and the time report together, and a companion has all three open in the sessions you are already signed into. So does “did this quarter repeat last quarter’s optimistic estimate” and “is there scope in that Slack thread that never became a task”.

It is research into your own delivery, and it is usually what the question was really about. The aggregated hours come out of Harvest and carry on into the document where the decision gets made.

Frequently asked questions