FIRST MONTH FIELDBOOK / GUIDE
Edison onboarding: tell saved, submitted, and finished apart
A lightweight way to track assigned onboarding activities without creating a duplicate personnel file.
An onboarding screen can look reassuring long before every task is finished. A form may contain your entries without having been submitted. A submitted item may still need review. A completed activity may not appear where you expected because you are looking at a different list. For a new Tennessee employee, the practical challenge is to describe the state of the work accurately rather than checking every item as soon as it has been opened.
Tennessee HR Support directs employees to Onboarding from the Fluid Home to access onboarding activities. That official signpost is the starting point; the exact items and instructions that appear in your own account matter more than a generic checklist. This article explains a working method for tracking them. It does not submit tasks, inspect your records, or establish that a particular activity is required for every employee.
Start with the assignment in front of you
Read the title and instructions before acting. Identify what the task asks you to provide, whether another person is involved, and what completion should look like. If a due date is shown, record that date exactly instead of replacing it with a general “first month” reminder. An activity list can contain several different deadlines and dependencies at the same time.
If the task is missing or does not match your situation, ask the responsible agency contact. Do not choose a similar-looking activity simply to make progress. A form intended for a different appointment or employment category may create a record that someone later has to correct. An unanswered applicability question is a legitimate blocker, not a personal failure to finish onboarding quickly.
Keep your tracking list short. A task name, due date, status, and next action are usually enough. The official system holds the submitted information. Your working list should help you remember what remains; it does not need a copy of every field, document, or confirmation page.
Use status words that describe evidence
“Not started” means you have not begun. “In progress” means work remains before submission. “Submitted” means you observed a submission result. “Waiting for review” means the official instructions or responsible person indicate another step is pending. “Complete” should be reserved for the confirmation that the process actually provides. These are editorial labels for your notes, not claims about Edison’s exact status names.
A useful note pairs the label with the reason. Instead of “done,” write that the system displayed its completion status on a certain date. Instead of “broken,” write that a required field could not be completed or a particular error appeared. Keep the wording factual enough that another person can understand what happened without interpreting your mood at the time.
Do not manufacture certainty when the screen is ambiguous. The absence of an error may mean only that the last action did not fail visibly. If you cannot tell whether the action was submitted, check the official record before trying again. Repeating a submission can create confusion, and repeated clicks rarely resolve a question about the meaning of a status.
Track dependencies without taking over another role
Some activities depend on an account becoming available, a document being reviewed, or an agency contact answering a question. Record who owns the next step and when you last asked. That makes the issue visible without implying that you can complete the other person’s part. If it affects a deadline, tell the relevant person promptly rather than waiting until the date has passed.
A concise follow-up includes the task, the unresolved point, and the approaching deadline if one exists. Avoid sending the same request to multiple people without explaining the existing case or conversation. Parallel messages can produce conflicting advice, especially when each recipient thinks they are handling the original request.
If a colleague offers to complete something under your account, decline and ask for the approved assistance route. Help can mean explaining a field or identifying the right office. It should not require sharing credentials or allowing another person to impersonate your acknowledgment. Personal responsibility and system permissions remain important during onboarding.
Protect the record while keeping useful proof
Ask what confirmation you should retain and where it belongs. In many cases a reference or a status note will be enough for your own follow-up. If an official document must be stored, use the agency’s approved location. Do not create a personal cloud folder of employment forms because it feels easier to search.
Screenshots deserve the same care as documents. A small error message may appear beside sensitive fields, identifiers, or other people’s information. Prefer copying the exact error text where possible. When a support team requests an image, use the approved channel and remove unrelated information only in a way that does not misrepresent the issue.
An onboarding checklist should not store passwords, one-time codes, identity document numbers, or financial account information. It also should not become a public portfolio of your new role. The purpose is narrow: keep track of assigned actions until the official workflow is complete and any necessary follow-up is resolved.
Close the loop at the end of each week
Review unresolved items, not just the number completed. Ask whether a waiting item needs a follow-up, whether a deadline changed, and whether an instruction has been replaced. Move genuinely finished work out of the active view so that the remaining tasks stay easy to see. Keep any required records according to the agency’s instructions.
At a supervisor check-in, describe the few items that need help. “I have two activities waiting on clarification” is more informative than “Edison is not finished.” Explain which office you contacted and what response is outstanding. This lets the supervisor help with the actual dependency rather than giving you another broad reminder to complete onboarding.
The result should be a clear account of the process, not a perfect-looking list. Honest status labels prevent accidental duplicate work, make support requests easier to answer, and keep the new employee’s attention on learning the job. A list that admits uncertainty is more reliable than one that marks every opened item as complete.