Keep one log for the first thirty days
A new hire asks the same question to several people in the first month. Each answer may be slightly different, and the new hire learns that the team is not aligned. A shared question log captures the question once and shows where the answer lives. The log does not need a new software system.
Use a simple table with five fields. Record the date, the question, who answered, the answer given and whether the question repeated. A supervisor can keep it in a shared document or the existing onboarding tracker. The value comes from reviewing it, not from the tool.
Record the question in the employee's words
Do not rewrite the question into policy language at the moment it is asked. The employee's words show which part of the process is unclear. A question about when the first break starts may reveal that the schedule was never explained. A question about who approves a swap may reveal a missing contact.
Link the question to the topic, not to the person asking it. Use categories such as pay, schedule, safety, access and training. The categories make repeats visible across different new hires. A pattern is easier to spot when the labels stay consistent.
Keep the language of the question even when the answer is complex. A short paraphrase can hide the exact confusion that the onboarding material failed to address. Store the original wording beside the category and the answer. The next reviewer can then see what the new hire actually asked.
Answer once and publish the answer
When a question repeats, the answer should move into the onboarding material. Update the checklist, the first-day guide or the FAQ that new hires already read. Tell the next new hire where to find it. An answer that lives only in a supervisor's memory will be asked again.
Keep the answer short and specific. A new hire needs the action, the owner and the timing, not a full policy summary. If the full policy matters, link to it and quote the relevant sentence. The short answer should not contradict the longer document.
Review the log at the end of each week
A weekly review takes about fifteen minutes. Read the questions, mark the repeats and choose one fix for the next week. Assign the fix to a person and a date. Without that step, the log becomes a record of frustration rather than a tool for improvement.
Look for questions that indicate a missing handoff. A new hire who asks the same access question three times may be waiting on a ticket nobody owns. A new hire who asks about pay twice may have received a confusing first deposit. The question is a symptom, and the fix should address the cause.
Give the new hire a way to see that the question changed something. A short note in the next check-in can say which guide or checklist was updated. That feedback encourages the employee to keep asking instead of guessing. It also shows the supervisor that the log is worth the small effort.
Separate a training gap from a documentation gap
Some questions mean the employee has not yet learned the task. Others mean the task was explained but the written material is missing or wrong. Record which one applies before changing the training plan. Adding more training to a documentation problem wastes everyone's time.
If several new hires ask the same question after training, the training likely skipped a step. If one new hire asks a question that others do not, the issue may be individual and deserves a direct conversation. The distinction prevents a manager from overcorrecting a single case. Ask the supervisor which explanation matches the evidence before changing the plan.
Share the log with the next supervisor
The supervisor who ran the first month may change. Hand over the log with the fixes that were made and the questions that remain open. The next supervisor should not start from a blank page. A short handoff note is enough when the categories and dates are clear.
Keep the log for the full first ninety days if the role has a long learning curve. The first thirty days are the most concentrated period, but some gaps appear only after the first schedule cycle. Extend the review when the work requires it. Do not keep it open indefinitely without a purpose.
Use the patterns to improve the next cohort
At the end of the quarter, compare the questions across new hires. Count the repeats, the categories and the time to answer. Choose the three most common gaps and fix them in the onboarding process. Track the same categories in the next cohort to see whether the fixes worked.
Use the manager policy answer consistency review and the week-one manager check-in receipt as related controls. The BLS onboarding and turnover context explains why early-tenure experience matters for retention. A question log turns everyday confusion into a short list of changes the team can actually make. Review the list at the end of the quarter and keep only the fixes that new hires confirm.