Onboarding And Retention Research

How often do confidentiality acknowledgements go unsigned during onboarding?

A record-based method for counting hires who begin client work before a signed confidentiality acknowledgement and for separating a missing form from a missing explanation.

| 4 sources

How often do confidentiality acknowledgements go unsigned during onboarding?
4week cohort
1file per hire
3gate states
On this page
  1. Key takeaways
  2. Question and scope
  3. Definitions and evidence standard
  4. Sampling and measurement
  5. Findings and interpretation
  6. What the record shows
  7. Limitations
  8. Practical next step
  9. Sources and methodology
  10. Related research
  11. Questions about the findings

Key takeaways

  • Compare the first client access date with the signature date rather than relying on a check box.
  • Treat a signature without a recorded explanation as a separate condition from a missing form.
  • Report the gap in calendar days and inspect the longest case for immediate risk.
  • Move the acknowledgement ahead of the access request and test the order on the next five hires.

Question and scope

This study asks how often a new virtual assistant begins client work before a signed confidentiality acknowledgement is on file. It treats the hire as the unit and the first client task as the event. The scope is one role family, one onboarding file, and a fixed four-week starting cohort. The result describes that cohort and should not be read as a legal compliance audit.

A hire is eligible when the start date falls inside the window and the role touches client records. Hires in roles with no client data are excluded. A signature is counted only when the file shows a date and a document version. A check box without a readable record is treated as missing.

The study also records whether the hire received an explanation before signing. A signature collected without a walkthrough is a different condition from a missing signature. The explanation is part of the result, not a side note. Report the counts by onboarding owner and by client group.

A hire who starts on a weekend or a holiday is recorded with the first actual access date. The calendar date of the start is not treated as access if no client system was opened. The study uses the log rather than the contract date. This avoids counting a day when nothing could be seen.

Gate stateEvidenceAction
Signed before accessSignature date earlier than accessKeep the record
Signed after accessAccess date comes firstReport the gap
Unsigned with accessNo signature on filePause client work
Missing formNo document in the fileReplace and review

Definitions and evidence standard

Define the access date as the first day the hire could open a client record or client system. Define the signature date as the date on the acknowledgement record. A hire is out of order when the access date is earlier than the signature date. The gap is measured in calendar days, not in business hours.

Use the onboarding file, the access log, and the acknowledgement copy as evidence. A message that says the form was signed is not enough if the copy is missing. The study should record where the copy is stored and whether it is readable. A record that cannot be opened is treated as absent.

Separate a missing form from a missing explanation. A missing form has no document in the file, while a missing explanation has a signed document but no record of a walkthrough. Separate those conditions from a form that was signed after access by mistake. Each condition points to a different repair.

Use the same definition of client access for every role in the cohort. A shared dashboard that shows client names counts as access even if no record can be edited. State the systems included before reviewing files. An exception added later should be reported as a change to the method.

Sampling and measurement

Collect every eligible hire in the cohort and freeze the list before reviewing files. Include more than one onboarding owner and more than one client group. If a policy changed during the window, report it separately. Record the number of hires, owners, and client groups.

Measure the share with a signed record before access, a signed record after access, and no record. Add the number of days between access and signature for the late cases. Report the median gap and the longest gap rather than only an average. The longest gap often shows the case that needs immediate attention.

If a hire had no client access during the window, record that separately. A signature that is late but precedes any client task is not the same as a signature that follows live work. Report the no-access group beside the others. The separation keeps the risk measure meaningful.

Have two reviewers check the first ten files and compare their gate states. Discuss every disagreement and write the agreed rule in one sentence. Repeat the comparison at the midpoint of the cohort. A short calibration note makes the final counts easier to defend.

Findings and interpretation

Present the gate states before naming a cause. A large late-signature group may mean the form is sent after the account request rather than before it. A large missing-explanation group may mean the walkthrough was dropped when the start date moved. Read the actual files behind the largest group before suggesting a repair.

Compare the result with the number of hires who started in the same week. A busy week may produce more gaps because the onboarding owner is stretched. Report the cohort size with the result. The comparison keeps a volume effect from being read as indifference.

Check whether the late signatures were corrected before the first client task. A signature added before any client record was opened is a process delay rather than an exposure. Report the task date with the signature date. The pair shows whether the gate actually failed.

Compare the gate states by onboarding owner before combining them into one rate. One owner may send the form before the access request while another sends it after. Report the owners separately when the difference is large. The split shows where a process change would have the most effect.

What the record shows

The record should show the order of events, not only the presence of a signature. A signed form with no access date cannot prove that the gate worked. Report the signature date, the first access date, and the document version together. The sequence is the finding.

A missing explanation is a training problem, while a missing form is a record problem. A training fix may need a walkthrough, while a record fix may need a checklist change. Code the two conditions separately before recommending a change. The repair should match the condition.

The record also shows whether the hire had questions that were never answered. A signed form with a long list of open questions may be less understood than a short form with none. Report the questions with the signature state. That context turns a signature into evidence of understanding.

Limitations

The study measures the records that exist, not every conversation that occurred. A manager may have explained confidentiality in a call that nobody documented. The result therefore describes the file, not the full onboarding experience. It also cannot prove that the hire understood the document.

The access log may not capture every shared login or borrowed account. A hire may have seen client data through a channel the log does not record. State that limit beside the counts. The result should not be presented as a complete inventory of exposure.

Deciding whether a form was readable or whether a walkthrough occurred requires judgment. Two reviewers may disagree at the margin. Record the disagreements and resolve them with examples before reporting. A calibration set of ten files improves consistency.

Practical next step

Move the acknowledgement step ahead of the access request in the onboarding checklist. Make the access owner confirm the signature date before creating the account. Add one line to the request form that shows the date. Test the order on the next five hires.

Add a field that records who explained the document and when. The field can be a short list such as manager, people team, or security owner. A small list is faster than free text and easier to count. The note should take less than a minute to complete.

Review the change after one month and compare the gate states with the baseline. Keep the revision if it reduces late signatures without delaying useful work. If the pattern does not move, the cause may be the start-date process rather than the form. Read the test with the people who open accounts.

A short follow-up record should note whether the hire asked a question after signing. A question raised later may show that the first explanation was too general. Record the date and the answer beside the acknowledgement. The note helps the next hire without changing the signed document.

A short follow-up record should note whether the document version changed after the hire signed. A change may require a short refresher before the next client task. Record the old version and the new one beside the file. The note keeps the record honest without reopening a completed step.

Sources and methodology

The study reviews one onboarding file and the related access log for every eligible hire in a four-week cohort, coding the signature date, the first client access date, the document version, and whether an explanation was recorded.

  1. U.S. Federal Trade Commission - Data security current.
  2. NIST Special Publication 800-46 Rev. 2 - Enterprise telework and remote access current.
  3. U.S. Cybersecurity and Infrastructure Security Agency - Secure Our World current.
  4. U.S. Small Business Administration - Hire and manage employees current.

Source count: 4. Last verification date: November 16, 2026.

Questions about the findings

Is a check box enough proof?

No. The file should show a dated document version and a readable copy. A check box alone cannot show what the hire agreed to.

What if the hire signed on the first day but access came later?

That is the intended order. Record the signature date and treat the case as compliant unless the document version is missing.

Should the study include contractors?

Include them when they touch client records and are onboarded through the same process. Report them separately if their agreement differs.

How should a shared login be treated?

Record it as a separate exception. A shared login makes it harder to show who saw a record and when.

Which measure is most useful?

The share of hires with a signature before first client access plus the median gap for late cases. The pair shows both the gate and its cost.

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.

confidentialityonboarding recordsvirtual assistant research