What is trust-based work operations?
Trust-Based Work Operations is an approach to managing service work that connects self-reported time, human approvals and financial accountability without relying on employee surveillance. This guide explains the model, the steps to run it in an agency or a team with contractors, and where its limits are. The steps work with any tools.
Last reviewed November 6, 2026. Free to start, no credit card.
The short definition
Trust-Based Work Operations is an approach to managing service work that connects self-reported time, human approvals and financial accountability without relying on employee surveillance.
Put plainly: people write down their own work, a person approves it, and the business bills clients and works out what contractors are owed from that same approved record.
This is a way of working that Honest Day is built around, not an established industry category or a standard. We use the name so the model is easy to talk about. Honest Day did not invent time tracking, approvals or privacy-friendly software, and other tools, Toggl among them, publish positions against surveillance features.
Why teams are reconsidering surveillance
Monitoring tools try to get accountability by watching: screenshots, activity levels, keystroke or app logs. They answer the question "was the screen busy?" The questions a service business actually has are different: was the client's work done, are the hours on this invoice fair, and what do we owe each contractor?
Watching also changes the relationship. People who know every minute is observed spend effort on looking busy, and good contractors tend to avoid clients who treat them as suspects.
There is a legal side too, and it varies by country and state. For example, the UK data protection regulator's guidance says monitoring of workers must be lawful, fair and transparent, and must not be excessive (ICO: data protection and monitoring workers). Check the rules where you and your people are, and ask an employment lawyer if you are unsure. This guide is not legal advice.
How trust-based accountability works
The model replaces observation with three records that anyone involved can check.
- The entry. A person records time against a client and project, with a note on what it was for. It is their own statement of what they did.
- The approval. A named person reviews the week and either approves it or sends it back with a question. Approved weeks are locked so they cannot change quietly afterwards.
- The money. The invoice and any contractor statement are built from the approved entries, so everyone can trace a number back to the hours behind it.
If the record is wrong, it is wrong in a visible way: a missing note, a week nobody submitted, a project over budget. You can see it and ask, which is the point.
What you need for it to work
- Clear rules up front. What counts as billable, how time is rounded, when the week is due.
- A simple way to log. If logging is a chore, people do it late and from memory. Timers, a week grid or plain-language entry all help.
- A reviewer who knows the work. Approval means something only if the approver can tell whether the hours make sense for the project.
- Consistency. The same process for staff and for contractors.
- A single source for billing. Invoices and contractor pay come from the approved record, not from a second spreadsheet.
- A reasonable conversation when numbers look off. The model depends on asking, not on assuming bad faith.
How self-reported hours and approvals work
Reporting your own hours is not the same as being unchecked. These habits make the record dependable:
- Log as you go. Record time the same day, with a note that a client would understand.
- Submit on a schedule. One submission per week keeps reviews small. A reminder to people who have not logged helps.
- Review against what was agreed. Compare the week with the scope, the budget and the deliverables, not with a count of hours at a desk.
- Approve or send back with a note. Say what to fix. Sending a week back is normal, not a punishment.
- Lock approved weeks. Corrections after approval become a deliberate change, not a silent edit.
How this connects to client billing
Billing is where the record earns its keep. Invoice from approved time and the invoice can be checked line by line: the client sees the same notes the team wrote, and nobody has to retype hours into a separate document.
The same logic applies to contractors. A statement for each person, listing their approved hours at their agreed rate, tells them what they are owed and gives you a record of what you paid. Whatever tool you use, keep payment itself separate and keep the statement as the paper trail.
Benefits and trade-offs
What you get
- Invoices you can defend when a client asks.
- Fewer disputes with contractors about what is owed.
- Visibility of margin by project from the same hours.
- A working relationship that does not start from suspicion.
What you give up
- Proof of effort. A record shows what was claimed and approved, not what happened minute by minute.
- A fit for regulated work that must be monitored by policy or law.
- Easy automation. Someone has to review the week.
- Some reliance on honesty. Notes, budgets and approvals make gaps visible but cannot prove effort.
How an agency can adopt this model
- Write the rules down. One page: billable or not, rounding rule, submission day, who approves.
- Pick one record. Every hour, for staff and contractors, goes in the same place against a client and project.
- Set the review rhythm. Weekly approval by the person who runs the project. Lock weeks once approved.
- Invoice from the approved record. No re-keying. Anything not approved by invoice day is a conversation, not a guess.
- Give contractors a statement. From their approved hours, with a status for when you paid.
- Read the margin monthly. Compare hours, rates and project revenue, and adjust scope or price where projects lose money.
A spreadsheet and a shared folder can run this model for a very small team. Our free timesheet templates and contractor timesheet are a start.
Which tools support the workflow
You need four capabilities: self-entered time with notes, a submit-and-approve step with locking, invoicing from the approved time, and a way to total what each contractor is owed. Spreadsheets cover the basics for a tiny team. Dedicated time trackers cover tracking and, depending on the plan, approvals and invoices. When you compare tools, check which plan holds approvals and whether the tool offers monitoring features you would have to leave switched off.
Our comparisons with Harvest, Toggl Track and Clockify show plan-by-plan details and where each is ahead.
How Honest Day implements the model
Everything in this section describes what the product does today.
- Self-reported time: timer, day view, week grid, calendar and plain-language entry, with notes and tags on every entry.
- Human approvals: people submit the week, a manager approves it or sends it back with a note, approved weeks lock, and a Friday reminder goes to anyone who has not logged. Part of Premium.
- Billing: invoices built from uninvoiced time and expenses, a client portal, and card and PayPal payments through the workspace's own accounts.
- Contractor statements: a statement per person and period from their hours at their cost rate, with a shareable link and a paid status. Honest Day does not send the payment.
- Profitability: revenue, cost and margin by project, client or person. Part of Premium.
- No surveillance: no screenshots, keystroke or app tracking, activity scores or leaderboards. If a timer runs while someone is away, it asks them when they are back whether to remove that time.
Honest Day is free for up to 5 members; Premium is priced by team size. See pricing. Where it falls short: no native mobile apps, no QuickBooks or Xero sync and no SAML single sign-on. The other limits are listed on the About page.
Questions
What is trust-based work operations?
Trust-Based Work Operations is an approach to managing service work that connects self-reported time, human approvals and financial accountability without relying on employee surveillance.
Is it an established industry category?
No. It is a name for a way of working that Honest Day is built around. It sits alongside existing categories such as time tracking and timesheet approvals and does not replace them.
Do I need employee monitoring software to keep teams accountable?
Not for the questions most service businesses have. A note on each entry, a manager's approval and a locked week let you check whether work was done and whether an invoice is fair. If your policy or a regulator requires monitoring, a trust-based model is not the right fit.
What if someone reports hours dishonestly?
Approvals, notes, budgets and reports make gaps visible, and the reviewer can ask questions. They cannot prove effort. The model relies on a reviewer who knows the work and on a reasonable conversation when numbers look off.
Can I do this without Honest Day?
Yes. The steps in this guide work with any tools, including a shared spreadsheet for a small team.
Does Honest Day pay contractors?
No. A contractor statement shows what each person is owed from their hours and records when you have paid. The payment happens outside Honest Day.
Related
Try it with one week of real hours.
Free to start, with no credit card. Up to 5 members on the free plan.