FIRST MONTH FIELDBOOK / GUIDE

Edison TN and your first 90 days in state service

A practical orientation map that separates a working login, completed onboarding, and learning the job.

Edison TN is one of the names a new Tennessee state employee encounters before the workplace has become familiar. It may appear beside an instruction to complete a task, check a record, or speak with human resources. The useful starting point is to understand its role without expecting one screen to explain your entire new job. Tennessee HR Support identifies Edison as the state’s enterprise resource planning system, covering several employee and administrative functions. It is a tool within your employment, not a substitute for your supervisor or agency instructions.

This guide is written for a person joining Tennessee state government. It is not a login page, an official onboarding program, or a source of account support. We cannot see your records and do not need your employee ID, password, or documents. The timeline below is an editorial way to organize the first three months. Your agency’s schedule, assigned tasks, and individual deadlines take priority over that timeline.

First, identify the people behind the screens

Before making a long checklist of systems, make a short list of people. Who is expecting you on the first morning? Who handles equipment problems? Who answers a question about your appointment paperwork? Who should receive a message if you cannot arrive on time? These may be different people. A single friendly contact can introduce you to the right offices, but should not be assumed to have authority over every issue.

Keep that contact list in an approved location you can reach when you need it. An office telephone number saved only inside an inaccessible work account is not much help during a first-day access problem. Ask what information you may retain outside the work system and follow the answer. Avoid transferring staff directories, internal documents, or protected work information to a personal account simply for convenience.

The official HR description of onboarding includes orientation, paperwork, meeting colleagues, and learning about the role and agency culture. That mix matters. A person can finish a set of electronic tasks while still not knowing the team’s handoff process. Conversely, someone can feel socially settled while a required administrative step remains unresolved. Track both sides rather than treating a successful first login as the finish line.

Before day one: replace assumptions with confirmations

Confirm the reporting location, arrival time, entrance, and person to meet. If the appointment is remote or hybrid, ask which arrangement applies to the first day rather than assuming that the eventual schedule applies immediately. A building address, mailing address, and training venue can all be different. Confirming these details is a modest preparation step with a large payoff when the morning is busy.

Review the instructions you actually received. Sort them into items to bring, actions to complete through an official service, and questions that require a reply. Do not send identity documents or financial information to an address copied from an unfamiliar message without verifying it through the agency. This publication links to official information; it does not accept onboarding documents or complete employment forms for readers.

The best pre-start list is short enough to use. Include the confirmed meeting details, the requested materials, and unresolved questions with the relevant contact. Save the larger reading list for a separate page. Otherwise an urgent instruction, such as a changed location, can disappear among dozens of links that are useful but not immediately necessary.

First week: distinguish access from authorization

Use the official Edison destination supplied by the state or your agency. Tennessee’s first-time access help points new users to the First Time Login/New Hire route and its instructions. Follow the current official sequence rather than a copied walkthrough from an old discussion. If your screens or eligibility differ, stop and use official support instead of trying another person’s account or repeatedly guessing credentials.

A successful sign-in tells you that the account works. It does not establish that every function you need has been assigned, or that you are authorized to perform every action you can see. Ask your supervisor which tasks belong to you and which belong to another role. This is particularly important in a first week when the names of systems, teams, and approval steps are still blending together.

Tennessee HR Support places onboarding activities under Onboarding from the Fluid Home. Use that as a signpost, not a promise that every employee sees the same list. Open your assigned items, read what each asks, and distinguish an item you saved from one you submitted. When a task depends on someone else, record that dependency rather than repeatedly pressing a button in the hope that it will move.

Keep a completion record that is small and safe

A useful personal working list contains the task name, its due date as given by the agency, the current status, and the next action. It does not need to contain document numbers, account credentials, or copies of sensitive attachments. A note such as “asked HR about missing item on Tuesday” is often sufficient to keep the issue visible while the official system remains the authoritative record.

Choose status words that tell the truth. “Read” is different from “acknowledged”; “submitted” is different from “accepted”; “waiting for a reply” is different from “complete.” If there is a confirmation screen, check what it actually confirms. Do not infer final approval from the absence of an error message. Ask the responsible office how to verify completion when the display is ambiguous.

A new employee may have several deadlines running at once. Do not combine them into a single assumed first-month deadline. For example, the current ParTNers for Health new-employee enrollment page describes a 30-calendar-day enrollment period that includes the hire or eligibility date. That is a reason to consult the benefits office promptly, not an instruction to use this article to choose coverage. Other forms and agency tasks may have different schedules.

Learn the job in observable pieces

During the first weeks, ask what a good finished piece of work looks like. A general instruction to “learn the process” is hard to evaluate. An authorized example, a demonstration, or a supervised practice task gives you something concrete to compare with your own work. Ask which version of a procedure is current and who owns it when instructions appear inconsistent.

Keep questions close to the activity that produced them. Instead of collecting a vague list of things you do not understand, note the step, the expected outcome, and the point where you became uncertain. Bring those questions to the agreed check-in. This makes it easier for a colleague to give a useful answer without having to reconstruct your entire morning.

Do not build a private archive of real cases merely to document progress. Use approved training examples, authorized references, or brief descriptions that omit protected information. Your learning notes should help you work safely, not create another place where the agency must manage sensitive records. Ask before copying screens, exporting reports, or keeping examples on a personal device.

At 30 and 60 days: review what is still dependent

The value of an early check-in is not the number of boxes you can show as complete. It is the chance to identify a missing permission, unclear expectation, or recurring obstacle before it becomes normal. Bring two or three examples of work you can now do, the tasks where you still need review, and any administrative issue whose owner is unclear.

The 30- and 60-day markers in this guide are planning suggestions, not universal state review dates. If your supervisor uses another schedule, use it. The question remains the same: what should you be able to do independently next, and what support is needed to get there? A clear answer is more useful than trying to appear fully settled before you are.

When an issue carries forward, give it a next action and a person. “Access problem” is a label; “IT asked for the exact error, which I will send through the approved channel today” is a plan. Keep your supervisor informed if the issue blocks assigned work. Do not quietly substitute a colleague’s account or an unofficial tool to avoid an uncomfortable progress conversation.

Before the first 90 days are over

Tennessee HR Support says a supervisor completes an interim review within the first 90 days of onboarding. Ask how that will be scheduled and what you should prepare. A brief record of assignments, feedback, training, and unresolved dependencies can support a useful conversation. It should not be inflated into a claim of formal approval or a guarantee about your employment status.

Look back at the questions you asked in the first week. Which are now answered? Which are still unresolved because the situation changed? Update the contact list and retire obsolete instructions in accordance with agency records practices. The goal is not to keep every note forever; it is to make the next month easier to navigate than the last.

Edison becomes less mysterious when each screen is connected to a real task and a responsible person. A sound start is not knowing every menu. It is knowing where the official information lives, what you are authorized to do, how to verify a completed step, and when to ask for help. Those habits remain useful long after the new-employee label wears off.