FYE360 FIELD-READY CHECKLISTS

Readiness begins before the pressure arrives.

Use these checklists to identify the people, information, access, equipment, evidence, decisions, and follow-up required at important points in the project lifecycle.

PROJECT LAUNCH

Project Launch

A practical approach to taking ownership of a newly assigned project, understanding the commitments, identifying the people who make decisions, gaining access to the required information, and finding what needs attention first.

  • Confirm the project assignment, what you are responsible for, which decisions you may make, what requires approval, how status will be reported, where issues must be escalated, and what needs attention first.
  • Identify the customer project lead, project sponsor, contractor project manager or superintendent, site contacts, internal team leads, and the person authorized to approve scope, cost, and schedule decisions.
  • Obtain access to the shared project folder, current schedule, portfolio or project system, communication channels, meeting calendars, reporting tools, and required software. Open each one and verify that it works.
  • Review the approved scope, current schedule, customer commitments, open risks and issues, missing information, and upcoming decisions. Record each next action with one responsible person and a due date.
DIGITAL SETUP

Set Up the Project Workspace

Create one dependable place to find the current schedule, decisions, actions, risks, meeting records, drawings, approvals, photographs, and customer commitments.

  • Create or locate the official portfolio entry and project folder, then confirm which record controls current status.
  • Use consistent file names and folders so another authorized team member can find the latest document without searching through email.
  • Turn meeting outcomes into recorded decisions and actions with one responsible person and a due date.
  • Verify that the project manager and assigned backup can reach the required files, systems, calendars, contacts, and approval records from their authorized devices.
FIELD WORK

Site Visit Preparation

Use the calendar invitation as the planning record, then arrive with the PPE, access, documents, equipment, contacts, measurements, and evidence plan required for the visit.

  • State the purpose, desired outcome, location, access instructions, attendees, equipment, and site contacts in the calendar invitation.
  • Attach or link the latest approved drawings, open questions, measurement list, and photo or evidence plan.
  • Send a written recap with findings, decisions, risks, owners, due dates, and required evidence.
MEETINGS

Meeting Preparation and Follow-Through

State why the meeting is needed, invite the people who can provide information or approve decisions, and turn the discussion into a written record of decisions, actions, due dates, risks, and unresolved questions.

  • Get added to recurring customer and contractor meetings early in the project.
  • Use recording or AI notes only after providing any required notice and receiving the necessary consent and approval.
  • Send the decisions, actions, responsible people, due dates, risks, and unanswered questions after the meeting.
PROJECT LAUNCH

New Project Intake Review

Document what was sold or authorized, what the customer expects, who is involved, which dates have been discussed, what the site requires, and which assumptions or missing details could affect the project.

  • Meet the contractor and site team early and request the current construction schedule.
  • Record third-party lead times, shutdowns, holidays, and schedule assumptions in the project record instead of leaving them in email or conversation.
  • Agree on how often the team will meet, how status will be reported, where urgent issues must be escalated, what evidence is required, and who may approve decisions.
READINESS DECISION

Go/No-Go Readiness Method

An industry-neutral method for classifying critical and supporting conditions and reaching a documented GO, NO-GO, or PENDING decision from current evidence.

  • GO requires every applicable critical item to be Complete or legitimately N/A.
  • One incomplete critical item produces a NO-GO, regardless of the percentage complete.
  • Industry-specific editions add the detailed requirements needed for specialized work.
See the neutral readiness method
PROJECT CONTINUITY

PTO and Emergency Coverage

Prepare the project so an assigned backup can understand the current status, handle urgent commitments, reach the right contacts, open the required records, and act within clearly defined authority while the project manager is unavailable.

  • Name one qualified backup and confirm what that person may approve or escalate before the coverage window.
  • Review upcoming milestones, customer promises, open risks, pending decisions, and urgent actions together.
  • Open the files, contacts, calendars, approvals, and reporting tools from the backup's account to verify access before coverage begins.
FINISH STRONG

Turnover and Closeout Review

Confirm that the deliverable works, the customer has accepted it, required training and records have been transferred, remaining items have owners and dates, and financial and administrative closeout is complete.

  • Record installation completion, operational readiness, customer acceptance, and financial close as separate events.
  • Assign every punch-list item to one responsible person with a due date and required completion evidence.
  • Archive approvals, training records, final documents, lessons learned, and customer acceptance evidence in the official project folder.
PTO COMMUNICATION STANDARD

Make your absence clear before someone needs you.

Your email and voicemail should state when you are unavailable, when you will return, and who is covering the work. Customers can then reach your proxy when action cannot wait or leave a message when it can.

Before you leaveConfirm the backup project manager can open the current project records, understands the customer situation and time-sensitive commitments, and has authority to handle the decisions that may arise.
OUT-OF-OFFICE VOICEMAIL

“Hello, you’ve reached [Name] with [Company]. I’m out of the office and will return on [Day, Date]. I will not be monitoring voicemail during this time. If you need immediate project assistance, please contact [Proxy Name] at [Phone Number] or [Email Address]. Otherwise, please leave your name, number, project, and a brief message, and I’ll respond after I return. Thank you.”

OUT-OF-OFFICE EMAIL

Subject: Out of Office | Returning [Day, Date]

Thank you for your message. I’m out of the office through [Date] and will return on [Day, Date]. I will not be monitoring email during this time. For time-sensitive project support, please contact [Proxy Name, Role] at [Email Address] or [Phone Number]. Otherwise, I’ll respond as soon as possible after I return.

Use real return dates and one clearly identified backup. If coverage differs by project, list the correct contact for each project instead of sending the customer through multiple people.
NEED SOMETHING BUILT FOR YOUR PROJECT?

Create your own working draft.

Turn your project details into an editable checklist, project-plan structure, or Gantt-ready sequence, then verify and shape the final result.

Open Project Builder