Headline signal

A defined sample, not a verdict. Source: Method note. This is contextual evidence, not a claim about this company or a performance guarantee.

Key takeaways

  • Define the population before sampling.
  • Separate completeness from correctness.
  • Publish the limitation beside the finding.

Question and scope

This is a proposed research protocol, not a report of completed findings. It asks how much of the account effort is visible in the time record. The result would describe the record, not the team. Separate what was observed from what was assumed. The QBR pack should link the claim to the source. A record that cannot be reproduced is not a control.

The protocol does not measure whether the effort was productive. It measures whether the work was recorded. A short note with four fields is easier to use than a long narrative. Keep the evidence with the record rather than in a separate log. A record that cannot be reproduced is not a control. The review should leave one owner and one date.

Population and unit of analysis

Define the population as account tasks during a stated week. The unit is one task, with the time, the account, and the category recorded. Test the rule on one real account before applying it to the book. Review the first few notes together before the process expands. The renewal brief should show the value and the risk. The meeting note should keep the client's words.

Link the task to the account so the same work is not counted twice. Keep the boundary visible in the place where the work is assigned. Record the exception and the person who approved it. A control that depends on memory is not yet a control. A record that cannot be reproduced is not a control. The account lead should see the evidence before the client conversation.

Definitions and measures

Define visibility as the recorded time divided by the estimated effort. Report the ratio and the categories with the largest gap. A control that depends on memory is not yet a control. Keep the original note beside the corrected version. The QBR pack should link the claim to the source. The account plan should distinguish a fact from a forecast.

Report the unrecorded work separately, such as internal meetings. Name the owner in the same line as the action. Use the same format for every handover so the next reader can scan it. Ask whether a new reviewer could act on the record without a conversation. The QBR pack should link the claim to the source. A record that cannot be reproduced is not a control.

Evidence standard

Compare the time record with the task log and the meeting calendar. A total without the task detail is weak. A control that depends on memory is not yet a control. If the source is unclear, route the question instead of guessing. A record that cannot be reproduced is not a control. The QBR pack should link the claim to the source.

Record the date and the reviewer. Keep the boundary visible in the place where the work is assigned. Keep the evidence with the record rather than in a separate log. Test the rule on one real account before applying it to the book. The account plan should distinguish a fact from a forecast. The account lead should see the evidence before the client conversation.

Sampling and collection

Use a census of the week. If sampling is necessary, stratify by account. Update the template when the same question appears twice. Keep the evidence with the record rather than in a separate log. The QBR pack should link the claim to the source. A record that cannot be reproduced is not a control.

Pilot the comparison on a few tasks and compare the reviewers. Clarify how a wait is treated. A short note with four fields is easier to use than a long narrative. Update the template when the same question appears twice. The QBR pack should link the claim to the source. The escalation bridge should name the next client update.

Analysis and reporting

Report the visibility ratio by category. Show the accounts with the largest gap. Present the results as a description of the record, not a judgment about the team. Record the exception and the person who approved it. The escalation bridge should name the next client update.

Limits and sources of error

The estimate may be subjective. The calendar may not include informal help. A control that depends on memory is not yet a control. Write the deadline as a date and a local time. The account plan should distinguish a fact from a forecast. The account lead should see the evidence before the client conversation.

Review cadence

Repeat the review after a timekeeping change or at the same interval each quarter. Assign the follow-up to the account director and set a date. Keep the evidence with the record rather than in a separate log. Use the same format for every handover so the next reader can scan it. The meeting note should keep the client's words. The account plan should distinguish a fact from a forecast.

Review table

Research control checklist
CheckAction
SourceVerify the evidence
OwnerName the decision maker

Methodology and limitations

This report synthesizes the cited first-party and institutional sources, then applies their published control principles to the bounded account-operations question described above.

The evidence is contextual. It does not measure this company, guarantee an outcome, or replace legal, security, financial, or commercial judgment. Readers should verify source dates, definitions, and applicability before acting.

Frequently asked questions

What does the protocol measure?

It measures whether the record supports a bounded decision, not whether the client is satisfied.

Sources

  1. U.S. Small Business Administration. 2026-11-09. Public guidance consulted for general context.
  2. U.S. Department of Labor. 2026-11-09. Public guidance on recordkeeping.
  3. GAO Green Book. 2026-11-09. Internal control standards for operations and reporting.