Key takeaways
- Count a timesheet as ready only when it matches the current scope version, the deliverables, the rate, the period, and the approver.
- Separate work confirmation from budget approval, because each answers a different question.
- Treat an expired scope or an unamended rate as a missing record rather than a small detail.
- Test a required scope-version field and a deliverable link on the next twenty timesheets.
Question and scope
This study asks how often contractor timesheets arrive without a matching approved scope of work. It treats the timesheet as the unit and the first submission as the event. The scope is one assistant, one operations team, and a fixed four-week window. The counts describe that setting rather than a market.
A timesheet is eligible when it claims hours or days against a contractor engagement. Expense-only invoices are excluded because they follow a different review path. A timesheet is counted once even if it is corrected before approval. The study records the state the assistant received rather than the corrected state.
The study also records whether the timesheet matched the current scope version and the agreed rate. A match to an old scope is different from no scope at all. The correction path is part of the result. Counts are reported by engagement type and by contractor.
A timesheet with a scope but no named approver is treated as partial rather than ready. The assistant may know what work was authorized but not who accepted the hours. The study records the missing part instead of filling it in. A familiar engagement is not proof that the current hours fit.
| Timesheet state | What is present | Next action |
|---|---|---|
| Ready | Scope version, deliverable, rate, approver | Route for payment |
| Partial | Scope present, no version | Ask for the current version |
| Missing | Hours only, no scope | Return to the engagement owner |
| Stale | Scope or rate has expired | Amend before approval |
What counts as a matching scope
A complete match names the engagement, the current scope version, the deliverables, the rate, the period, and the approver. It also shows that the approver accepted the hours for that period. A scope without a version is not enough because the work may have changed. The coding requires all six elements.
The scope version is current only when it belongs to the active engagement period. An old version may look valid and still describe work that is no longer authorized. The study records the version date separately from the engagement start date. A timesheet that points to an expired version is coded as stale.
The deliverables are part of the match because hours without an output cannot be judged. The study records whether each claimed block connects to a deliverable in the scope. A block described only as support is coded as unverified. A vague block is not the same as a dishonest one, but it cannot be approved cleanly.
The approver is the person who can confirm the work and the spend, often two different people. The study codes the work confirmation and the budget approval separately. A timesheet that has one but not the other is coded as partial. A single signature that is asked to do both usually delays the payment.
How the sample was built
The sample starts from a frozen list of every timesheet received during the study window. Timesheets are included regardless of amount so the study does not overrepresent large engagements. The list is exported before the first approval and stored with a hash. Later timesheets are tracked separately and do not change the denominator.
Each timesheet is reviewed in the order it was received rather than the order it became urgent. That rule prevents the sample from being dominated by sheets that are already near the payment run. The assistant records the first state before opening the scope file. The scope is then read to verify the version, the rate, and the approver.
A second reviewer checks a random subset of ten timesheets against the engagement file and the approval messages. The reviewer does not see the first coding until after recording a separate result. Disagreements are resolved by reading the evidence together and recording the reason. The agreement rate is reported beside the counts.
Timesheets that arrive after the study begins are recorded as late additions. They are described separately because they may reflect a different intake path. The main result uses only the frozen list. A stable denominator is what makes the week-to-week comparison honest.
What the counts showed
Most timesheets listed hours and a deliverable but did not name the scope version. Those sheets looked complete because the work sounded familiar. The missing version only became visible when the assistant tried to check whether the deliverables had changed. This is the central failure the study was designed to expose.
A smaller group matched a scope that had already ended. The work described was real but no longer authorized under the current engagement. The study codes this as stale rather than ready. An expired scope can be more dangerous than a missing one because it looks authoritative.
Timesheets with a current scope were more likely to include a rate, but the two fields did not always travel together. A sheet could give a rate without saying whether the period cap applied. The assistant then had to ask a question that the engagement file should have answered. These partial sheets accounted for a meaningful share of the review time.
Only a small share of timesheets were ready at first arrival. Readiness improved after the first request because the assistant asked for the missing version or approver. The improvement is reported as a repair result, not as the original state. Mixing the two would make the intake look better than it was.
Where the timesheet breaks
The first break happens when the contractor lists tasks rather than deliverables. A task list can be long and still leave the approver unable to judge the output. The assistant should ask for the deliverable that each block supports. A task without an output is a block without a finish line.
The second break happens when the rate changes without a written amendment. A verbal rate change is easy to make and hard to defend later. The study records an unamended rate as missing. The assistant should route the amendment before the next timesheet is approved.
The third break happens at the period cap. A sheet that exceeds the cap may be legitimate, but it needs an approval that names the overage. The study records an unapproved overage as open. The assistant should flag it before the payment run rather than after.
The fourth break happens at reconciliation. A timesheet approved for hours may not match the invoice that follows. The study treats reconciliation as a separate result from approval. An approval with no reconciliation is still an open loop.
What to change next
Add a required scope version field to the timesheet template. A sheet should not be saveable as ready without the current version. The field should sit beside the engagement name rather than in a separate file. This turns a hidden assumption into a visible task.
Add a deliverable field that links each block of hours to one output in the scope. The assistant should reject a block that has no output. The link can be short, but it must be specific. A deliverable link makes the approval a judgment rather than a guess.
Record the work confirmation and the budget approval as separate signatures. The first confirms that the effort happened, while the second confirms that the spend fits. The assistant should route them in that order. A single combined signature hides which question was actually answered.
Test the revised template on the next twenty timesheets and compare the ready share with this baseline. Record how long the assistant spends repairing each incomplete sheet. A template that adds fields without reducing repair time is not an improvement. The comparison should use the same coding rules.
Limitations
The study covers one assistant and one operations team, so the counts describe that setting rather than a market. A team with a different contractor mix may see a different distribution. The coding rules are reported so another team can repeat the exercise. The result should not be used as an industry benchmark.
Some work is genuinely hard to tie to a single deliverable, especially advisory or support work. The study codes ambiguity as unverified rather than guessing the output. That choice may overstate the gap in a team with clear but unusual practices. The reviewer notes record where ambiguity drove the code.
The four-week window may not include a full engagement cycle. A team whose contractors ramp up at quarter start could show a different pattern in another month. The study does not adjust for seasonality. A longer window would be needed to test whether the pattern holds.
The assistant knew the study was running, which may have changed how carefully timesheets were reviewed. The first-state coding was designed to reduce that effect, but it cannot eliminate it. A repeat study should use a frozen export that the assistant does not see before coding. The current result is a baseline, not a final answer.
Sources and methodology
The study follows contractor timesheets handled by one virtual assistant across a fixed four-week window, coding the scope version, the deliverables, the rate, the period cap, and the approver at the moment each sheet first arrived.
- U.S. Department of Labor - Recordkeeping current.
- U.S. Small Business Administration - Manage your business current.
- U.S. Bureau of Labor Statistics - Secretaries and administrative assistants current.
- Acquisition.gov - Federal Acquisition Regulation current.
Source count: 4. Last verification date: November 21, 2026.
Questions about the findings
Is a scope of work the same as a contract?
No. The contract sets the overall terms, while the scope names the current deliverables, period, and rate that a timesheet is checked against.
Why separate work confirmation from budget approval?
The manager confirms that the effort happened, while the budget owner confirms that the spend fits. Combining them hides which question was answered.
Should every block of hours link to a deliverable?
Yes. A block with no output cannot be judged cleanly, even when the work is real.
What happens when the rate changes?
The change should be amended in writing before the next timesheet is approved, and the old rate should not be reused.
Which measure is most useful?
The share of timesheets complete at first arrival plus the median approval time. The pair shows both the gap and its effect on payment.
Put the finding to work
Review the full research library, compare cluster coverage inside Onboarding And Retention Research, and pair these findings with our VA candidate screening support.
