From Signed Offer to First 90 Days: Build a Career Evidence Plan
Turn a signed offer, job description, interview notes, and manager expectations into a manager-reviewed 30/60/90-day plan with safe evidence logs and early-win criteria.
Career Guide | Published 2026-09-19
After you accept a signed offer, connect the job description, interview notes, written offer, and manager expectations to a working 30/60/90-day plan that you revise as you learn the role.
A post-acceptance career evidence plan connects four inputs: the job description, interview notes, written offer, and manager expectations confirmed after starting. Map each role promise to observable progress, stakeholder learning questions, a low-risk early win, weekly safe evidence, and day 1, 30, 60, and 90 review checkpoints. Revise the plan with the manager and keep confidential employer, customer, patient, employee, security, credential, and proprietary data out of personal planning tools.
This plan starts after the offer decision A signed offer changes the question. You are no longer deciding whether the role is worth accepting. You are preparing to learn what the job requires in practice, confirm how success will be discussed, and make your first contributions traceable without overpromising. That makes this guide different from the job offer benefits checklist and the two-offer comparison guide . Those pages help with the acceptance decision. It is also different from career cushioning , which is an ongoing readiness routine, and from a career evidence bank , which stores reusable proof across roles. Workflow Primary question What this guide adds Offer review Should I accept, and what terms or trade-offs need clarification? Carry the accepted role's relevant signals into a safe starting plan. Career evidence bank What proof from my work may be useful later? Capture new-role observations against current responsibilities and manager feedback. Career cushioning How can I stay ready while my situation changes? Focus on joining and contributing well in the role you already accepted. First-90-days continuity plan What was promised, what must I learn, and what evidence should we review? Connect role promises, questions, early wins, checkpoints, and safe evidence. Freeze the four source notes before day one Make one planning copy with the date and source of every note. Do not treat every source as equally certain. For planning purposes, the written offer records accepted terms, while the job description and interview notes preserve context that still needs to be tested in the working environment. Manager expectations are provisional until you discuss them after starting. Input Extract Label it as Next move Job description Responsibilities, outcomes, recurring decisions, relationships, tools, and working pattern. Role signal Group repeated wording into three to five practical promises to confirm. Interview notes Problems the panel emphasised, examples they explored, stakeholders named, and questions left open. Conversation fact or clearly marked interpretation Turn interpretations into questions instead of treating them as hidden requirements. Written offer Accepted title, start date, location or work pattern, and the terms you need to remember. Written reference Keep the original in an approved location. Do not rewrite it as employment advice. Manager expectations What your manager says matters first, how work is reviewed, and what can wait. To confirm after starting Ask for a shared version during week one, then revise the plan when priorities change. Keep facts separate from guesses. “The interview included a cross-team reporting responsibility” is a note. “My manager will expect a new reporting system in week two” is an assumption until the manager confirms it. Use the role-promise map A role promise is any outcome, responsibility, support, exposure, or working pattern that shaped your decision to accept. The map does not decide whether a statement is legally binding or guarantee that the work will happen. It gives you a precise list of signals to confirm, learn, and revisit with your manager. Start with a small set. For each promise, record where you heard it, what progress would look like, what you need before acting, and the safest evidence you could review. Use source labels such as written , interview , question , and confirmed . Role promise or signal Source How I will recognise progress Dependency or question First safe evidence Status A recurring team process I need to understand Job description and interview Can explain the inputs, decision rights, handoffs, and definition of done. Who owns the current process, which training is required, and what can change? Sanitized note about an observed workflow or approved deliverable. Unconfirmed Next role promise to confirm Written, interview, question, or confirmed Describe an observable change, not a score you cannot control. List the person, access, policy, data, or decision you need. Choose a deliverable, decision record, approved metric, or learning note. Unconfirmed Split the promise. Separate the outcome from the responsibility, support, and boundary. “Improve reporting” may contain several different jobs. Mark uncertainty. Use “to confirm” when the source was a recruiting conversation, an inference, or a phrase whose meaning depends on local practice. Choose evidence before activity. Decide what a useful record would be before you start producing work. That prevents a busy week from becoming an unreviewable list of tasks. Reconcile with the manager. After you start, ask which promises are still priorities, which have changed, and what success can be discussed at the next checkpoint. Turn uncertainty into stakeholder learning questions The first weeks should reduce uncertainty before they increase scope. The Chartered Institute of Personnel and Development describes induction as helping an employee learn about the new role and employer, including the organisation, team, responsibilities, objectives, performance expectations, and ways of working. Use that as a prompt for questions, not as a universal schedule. Read the CIPD employee induction guide for the broader employer-led context. Stakeholder Learning questions What to record safely Manager What matters by day 30, 60, and 90? What can wait? How do you want risks escalated? What is the feedback cadence? What would make you change priorities? Priority, decision owner, review rhythm, and your next question. Keep sensitive detail in the employer's approved system. Teammates and partners Who supplies inputs? Where do handoffs fail? What does ready or done mean here? Which channels and meeting routines matter? Names or roles only when needed, process labels, handoff dependencies, and links approved for your use. Customers, patients, users, or frontline colleagues What is in scope for this role? Which needs are already understood? What may I observe or discuss under the employer's rules? Aggregated themes or approved public information. Do not copy identifiers, records, case details, or quotes. HR, IT, security, or onboarding owner Which training, access steps, safety instructions, policies, equipment, and support channels are required before I work independently? Completion status and the official place to follow up, not credentials or internal security details. Ask the manager to choose the first three conversations if your role touches many groups. A list of every possible stakeholder is less useful than a short sequence with a reason for each conversation. Choose an early win by criteria, not visibility An early win should help you learn how the team works while producing a useful, reviewable contribution. It does not have to be a dramatic launch or a new system. In particular, do not change a customer, patient, production, financial, safety, or security process before you understand the approval path. Criterion Test before you commit Useful A named person can explain why the small deliverable or clarification matters. Reversible You can undo, pause, or discard the work without leaving an uncontrolled change. Within authority You know who approves the work and have permission to use the required systems or information. Observable You can point to a reviewed handoff, decision, learning artifact, approved metric, or completed step. Safe The work does not require moving restricted employer, customer, patient, employee, security, credential, or proprietary data into an unapproved tool. Teaches the system Completing it helps you learn the real workflow, stakeholders, constraints, or definition of quality. Early-win brief Problem or friction: Person who confirms the need: Small deliverable or decision: Definition of done: Approval, access, or policy dependency: Safe evidence I can retain: Manager review date: Get the boundary before the task. “I can draft a sanitized checklist for review” is a safer starting point than “I will redesign the process” when you do not yet know the controls or decision rights. Convert the map into a 30/60/90 plan Use the time boxes as planning prompts, not promises about how every job should work. A U.S. Office of Personnel Management onboarding model describes the first 90 days as the period from the first week through the first three months, with training, increasing workload, performance objectives, and early feedback. That is an illustrative model for why review points matter, not a universal probation or performance rule. See the OPM onboarding model for the source context. Window Emphasis Candidate outputs Manager conversation Before start Prepare, do not perform employer work. Four source notes, provisional role-promise map, stakeholder questions, and a safe early-win brief. Confirm first-day logistics and where official onboarding information will live. Days 1 to 30: learn and align Complete required onboarding, observe the workflow, meet priority stakeholders, and confirm role boundaries. Map version one, answered questions, access or training dependencies, and one scoped early-win proposal or deliverable. Which promises are real priorities? What should I stop, start, or defer? Days 31 to 60: contribute and test Own a bounded piece of work, document assumptions, and request feedback before expanding scope. Reviewed deliverable, safe weekly evidence, open risks, and a revised map with confirmed or changed promises. Is the evidence useful? What quality bar, decision right, or dependency am I missing? Days 61 to 90: deliver and calibrate Make the repeatable work clearer, surface trade-offs, and propose the next learning or delivery priorities. Evidence summary, lessons learned, unresolved questions, and a next-quarter draft aligned to manager feedback. What should continue, change, or be measured differently in the next period? The sequence may compress, stretch, or reorder. A regulated role, a seasonal role, a contract assignment, a promotion, and a new graduate role can require different onboarding. Revise the plan with your manager after starting and follow the employer's actual training, safety, access, and review process. Use review checkpoints to keep the plan shared Put the checkpoints on your calendar only after you know the team's normal cadence. Bring the map and evidence log as conversation aids. Do not use them to create a private scoring system or to infer a probation result. Checkpoint People to include Questions to answer Record Before start Manager or onboarding contact Where should I find official onboarding instructions? What should I prepare personally? Logistics and questions. Do not begin unapproved work. Day 1 or week 1 Manager, onboarding owner, and assigned buddy or partner if applicable What are the immediate priorities, required training, access steps, and escalation routes? Confirmed boundaries, dependencies, and map changes. Day 30 Manager What have I learned? Which early contribution is useful? Which assumption was wrong? Manager feedback, decisions, and the next scope. Day 60 Manager and relevant partners What evidence shows progress? What quality bar or dependency needs attention? Reviewed deliverable, open risks, and reprioritised promises. Day 90 Manager and any formal review owner What should continue? What should change? Which next-quarter goals and development questions need agreement? A concise evidence summary and a manager-reviewed next plan. Keep a weekly evidence log A weekly log is a memory aid for the next checkpoint. Keep facts, interpretations, and actions in separate lines. Evidence can be a reviewed deliverable, a decision you owned, a completed learning step, an approved metric, a clarified handoff, or a lesson that changed your next action. It does not need to be a self-rating. Week of: Role promise or outcome under review: What I learned: What I did or delivered: Safe evidence I can retain: (approved deliverable, sanitized metric, decision, or learning note) Signal or feedback from manager or stakeholder: Unresolved assumption, risk, or dependency: Question for the next review: Next action and owner: Privacy check: I removed restricted content and kept the source in the approved system. Use one entry per meaningful week, not a minute-by-minute diary. If a manager gives feedback in an employer system, keep the authoritative record there and write only the minimum safe planning note you need elsewhere. Keep the plan safe to store and share Do not paste confidential work into a personal planning tool. The safest continuity plan contains role signals, questions, sanitized observations, and approved evidence, not a copy of the employer's internal record. Before you save an entry, check each boundary below. An accepted offer can include personal information and employer-restricted terms, so keep the original document where the employer or your adviser permits it. The AskMyCareer privacy policy explains the platform's general data practices, but it does not override an employer's policy, a customer or patient duty, a security rule, or a confidentiality agreement. Employer confidential information: internal roadmaps, unreleased plans, private financials, contracts, internal URLs, source code, or non-public operating documents. Customer or patient information: names, contact details, account identifiers, records, case details, health information, or combinations that could identify someone. Employee or HR information: colleague names when unnecessary, performance notes, compensation, health information, investigations, or personnel records. Security information: vulnerabilities, incident details, architecture diagrams, access-control details, recovery procedures, or security test output. Credentials and secrets: passwords, API keys, tokens, recovery codes, private certificates, or authentication links. Never include them in a plan. Proprietary material: algorithms, designs, licensed content, private metrics, research, models, or work product that is not approved for external storage or sharing. Use role labels, broad categories, public links, and approved summaries only when they are enough for the planning task. If an example needs a number, use a truthful approved measure or leave the number out. If you are unsure, keep the source in the employer-approved system and ask the relevant manager, HR, privacy, or security contact before moving any content. AskMyCareer workflow Keep the accepted role connected to your evidence AskMyCareer can support the personal planning layer when your notes are safe to store. Use the job tracker to keep the accepted role, dates, stage, and your own next questions together. Use the career graph to structure sanitized roles, responsibilities, outcomes, skills, and evidence you are allowed to retain. Use Workspaces when a role-prep, career-strategy, or interview-story workflow helps you organise questions and follow-through. Keep the boundary clear: your employer's onboarding portal, training, safety instructions, access controls, policies, and manager feedback remain the source of truth for the job. AskMyCareer does not know those private systems and cannot replace employer onboarding. Treat any generated wording as a draft to verify against your real experience and the employer's rules. Open the job tracker Build your career graph Copy this one-page continuity plan Role and start date: Manager and review cadence: Top role promises to confirm: 1. 2. 3. What the job description says: What the interview notes suggest: What the written offer confirms: (Keep the original terms in the approved location.) Questions for week one: 1. 2. 3. Early-win brief: Days 1 to 30: learn and align Days 31 to 60: contribute and test Days 61 to 90: deliver and calibrate Checkpoint dates: Week 1: Day 30: Day 60: Day 90: Privacy boundary checked: Yes / needs review Bring this page to the manager conversation in week one. Replace assumptions with confirmed language, remove promises that no longer apply, and add the employer's actual onboarding steps. A plan that changes after you learn more is doing its job. Common mistakes to avoid Copying the job description as a plan A list of responsibilities does not show sequence, decision rights, dependencies, or what a manager wants reviewed first. Treating interview language as a guarantee Keep the signal, label the source, and ask what changed once you can see the team's current priorities. Choosing a high-risk project to look busy Start with a bounded contribution that teaches the workflow and has a clear approval path. Logging restricted data as proof Use a sanitized description or an approved record. Never move customer, patient, employee, security, credential, or proprietary details just to make the log look stronger. Never revising the map The manager conversation is part of the method. Update priorities, dependencies, and evidence after each checkpoint. Turning evidence into a private score Use the log to prepare a clear discussion about work, learning, and next actions. Do not infer a performance or probation outcome from your own labels.