How can we help?

The Toolbox test add-in helps users create a focused LookAhead worksheet from a larger Excel-based planning or activity sheet. Instead of reviewing an entire source worksheet with all rows visible, users can generate a filtered worksheet that highlights activities inside a selected date window while still preserving the hierarchy needed to understand where each activity belongs.

In the current build represented by this repository, the main end-user workflow is the creation of a LookAhead sheet. The add-in reads the selected source worksheet, identifies the relevant date range, finds matching activities, includes the necessary parent hierarchy rows, and creates a new worksheet that is easier to review, share, and discuss.

This knowledge base is written for website publishing and is intended to explain the feature in plain language. It focuses on what end users need to know to use the add-in confidently, understand the generated output, troubleshoot common issues, and understand the basic usage information that may be recorded.

What the add-in is designed to help with

• creating a short-term planning view from a larger worksheet
• reducing the amount of schedule data users need to review at one time
• preserving WBS or hierarchy context in the filtered output
• producing a worksheet that is easier to scan in meetings or planning reviews

Typical users

• project controls teams
• schedulers and planners
• project managers
• site coordination teams
• teams preparing weekly or monthly planning views

Important scope note

This Rev.1 knowledge base is based on the feature set visible in the current repository snapshot. The implementation clearly describes:

• LookAhead worksheet generation
• session and usage summary tracking

If the full Toolbox add-in in production includes additional ribbon commands or tools beyond those shown here, this document should be expanded in a later revision so the website reflects the full product.

The LookAhead feature creates a new worksheet by filtering a source sheet down to the activities that fall within a selected forward-looking time period. It is meant to give users a practical planning view rather than a full copy of the original worksheet.

In simple terms

The add-in:

1. reads the active source worksheet
2. determines the selected LookAhead period
3. finds the relevant Start and Finish columns
4. checks which activity rows fall inside the selected date range
5. preserves the related hierarchy rows above those activities
6. creates a new worksheet
7. copies the source header into the new sheet
8. writes the filtered rows into the new sheet
9. applies consistent formatting for readability

What the add-in looks for

The current implementation is designed to work with a worksheet structure that includes:

• a two-row header block
• recognizable Start and Finish columns
• hierarchy rows
• activity rows

Supported row types in the current build

#### Hierarchy rows

• L0
• L1
• L2
• L3
• L4
• L5
• L6
• L7
• L8
• L9

These rows represent grouped hierarchy levels in the project structure.

#### Activity rows

• T
• SM
• FM

These are the activity row types currently described by the available implementation.

How the date filter works

An activity is generally included in the LookAhead worksheet when its Start date or Finish date falls inside the selected LookAhead window.

That means a row may appear in the output if:

• it starts during the selected period
• it finishes during the selected period

This gives users a focused list of upcoming work without requiring manual filtering in Excel.

Why hierarchy rows are included

If the add-in only listed matching activities, the worksheet would be harder to read and harder to trace back to its project structure. To keep the output meaningful, the add-in also includes the relevant hierarchy rows above each matching activity.

This helps users see:

• what area of work the activity belongs to
• which parent grouping it falls under
• how the filtered results fit into the wider schedule structure

Why the LookAhead sheet is not a direct copy

The generated worksheet is not meant to be a visual clone of a continuous range from the source sheet. It is a reconstructed planning view built from:

• matching activity rows
• required hierarchy rows
• the copied header section

Because of that, users should expect the output to be shorter, more focused, and visually organized for review rather than identical to the original source worksheet.

This section explains the normal end-user process for generating a LookAhead worksheet.

Before you begin

Make sure:

1. the correct workbook is open in Excel
2. the correct source worksheet is active
3. the worksheet contains the planning or activity data you want to filter
4. the worksheet includes recognizable Start and Finish columns
5. the worksheet structure has not been changed in a way that breaks the expected layout

How to generate a LookAhead worksheet

1. Open the workbook that contains your planning or activity sheet.
2. Go to the worksheet you want to use as the source.
3. Open the Toolbox add-in from the Excel ribbon.
4. Select the LookAhead function.
5. Choose the required LookAhead period if prompted.
6. Enter or confirm the target worksheet name if prompted.
7. Run the LookAhead process.
8. Wait for the add-in to generate the new worksheet.
9. Open the new worksheet and review the results.

What users should review after generation

After the sheet is created, review:

• whether the correct worksheet was used as the source
• whether the expected time period was applied
• whether the expected activities appear in the output
• whether the hierarchy context looks correct
• whether the worksheet name is clear enough for sharing

Best practices for users

To get the best results:

• start from the correct source worksheet
• verify the date range before running the command
• review the generated sheet before sending it to others
• keep the source sheet as the master working sheet
• treat the LookAhead output as a filtered reporting or planning view

Common use cases

Teams often use LookAhead worksheets for:

• weekly planning meetings
• short-term execution planning
• monthly coordination reviews
• filtered stakeholder reporting
• simplified distribution to users who do not need the full source worksheet

The LookAhead worksheet is built to be easier to read than the original source sheet while still preserving the key planning context.

What is included in the generated worksheet

The generated sheet typically includes:

• the original top header rows from the source worksheet
• the activity rows that match the selected date window
• the related hierarchy rows needed to preserve structure

Header behavior

The current design copies the top two header rows from the source worksheet into the new sheet. This helps preserve:

• column names
• grouped header layout
• merged header structure where present
• general header appearance

For users, this means the top of the LookAhead sheet should still feel familiar and recognizable.

Body rows

The body of the worksheet begins below the copied header. This section contains the filtered planning rows.

Users should expect to see:

• hierarchy or grouping rows
• matching activity rows
• a shorter, cleaner list than the source worksheet

What hierarchy levels mean

Hierarchy labels such as L0, L1, L2, and lower levels represent nested groupings in the project structure.

In simple terms:

• L0 is usually a higher-level grouping
• L1 is a subgroup under L0
• L2 is a subgroup under L1
• the same structure continues for deeper levels

This makes it easier to understand how each activity fits into the broader plan.

Formatting behavior

The header is copied from the source sheet, but the body rows are formatted using a consistent rule-based style after the data is written into the new worksheet.

For end users, this usually means:

• hierarchy rows may have distinct colors
• grouped levels may have different text emphasis
• the body may not look exactly the same as the source worksheet

This is expected behavior. The goal is to create a readable and consistent planning view, not to preserve every source formatting detail row by row.

View behavior

The generated worksheet may also apply viewing settings such as:

• gridlines turned off
• top rows frozen
• the sheet scrolled to the top
• an initial selected cell near the first data row

These adjustments are intended to make the worksheet easier to review immediately after it is created.

What users should expect

Users should expect the LookAhead worksheet to be:

• shorter than the source worksheet
• focused on a selected planning window
• grouped for readability
• useful for review, communication, and short-term planning

Users should not expect it to be:

• a complete copy of the source worksheet
• a replacement for the master planning sheet
• a guarantee that every visual detail from the source will be preserved exactly

This section covers the most common issues users may encounter.

The LookAhead sheet is missing expected activities

Possible reasons:

• the activity falls outside the selected LookAhead period
• the wrong source worksheet was active when the tool was run
• the worksheet structure does not match the expected layout
• the row is not one of the supported activity types
• the Start or Finish data is not recognized as expected

What to do:

1. verify the selected date range
2. check the activity dates in the source worksheet
3. confirm that the correct source worksheet was used
4. rerun the process after reviewing the source data

The generated sheet contains fewer rows than the source sheet

This is expected. The LookAhead worksheet is supposed to contain only:

• matching activity rows
• supporting hierarchy rows
• the copied header rows

It is not intended to show every source row.

The formatting looks different from the original worksheet

This is also expected in many cases. The header is copied from the source, but the body of the LookAhead worksheet uses a consistent rule-based format.

This means:

• some colors may differ from the source
• some font or row-level styling may not match exactly
• the overall layout is intended to be cleaner and more consistent for review

The worksheet is grouped but not identical to the source

That is normal behavior. The output is rebuilt based on matches and hierarchy preservation. It is a filtered planning view, not a full clone of the original worksheet.

Column widths do not look ideal

Excel sizing can vary depending on:

• copied source widths
• merged cells in the header
• font sizing
• the final content length

What to do:

1. review the generated worksheet
2. manually adjust column widths if needed before sharing

The wrong worksheet was generated

Possible reason:

• the user ran the tool while a different worksheet was active

What to do:

1. return to the correct source worksheet
2. run the LookAhead process again
3. remove or rename the incorrect output sheet if needed

The output is hard to interpret

Possible reasons:

• the hierarchy structure in the source sheet is inconsistent
• row labels are not familiar to the user
• the workbook contains mixed planning conventions

What to do:

1. review the source sheet structure
2. confirm how hierarchy and row types are used in your organization
3. review the output with your planning or project controls lead if needed

Does the add-in modify my original worksheet?

The current LookAhead workflow is designed to create a new worksheet rather than overwrite the source worksheet.

Does the LookAhead worksheet include every source row?

No. It includes only the relevant activity rows for the selected date window plus the hierarchy rows needed to preserve structure and readability.

Why are parent rows included even when they do not contain dates?

Parent rows are included to keep the filtered results understandable. Without them, users would lose the structure that explains where the matching activity belongs.

Why does the output not look exactly the same as the source sheet?

The header is copied from the source, but the body is formatted separately using a rule-based style. This helps produce a cleaner and faster-generated output.

Can I edit the generated LookAhead worksheet?

Yes. Once the worksheet is created, users can typically review it, resize columns, add notes, and make presentational adjustments in Excel as needed. Teams should still follow their own internal document-control practices.

Is the LookAhead worksheet intended to replace the master schedule?

No. It is best treated as a focused reporting or planning view derived from the source worksheet.

What should I check first if a row seems to be missing?

Check:

1. the selected LookAhead period
2. the activity's Start and Finish dates
3. the source worksheet used when the command was run
4. whether the row type is supported by the current implementation

Can the LookAhead worksheet be shared with others?

Yes. That is one of its main practical uses. Users should still review the worksheet before sharing it to confirm that the output reflects the intended date range and planning context.

The current repository also shows lightweight session and usage summary tracking in the add-in.

What may be recorded

Based on the available implementation, the add-in may record usage summary information such as:

• a session identifier
• session start time
• session end time
• total active usage duration
• counts of button or action usage

Why this may be used

Usage summary tracking is generally used to help administrators or product owners understand how the add-in is being used. It is typically intended for usage insight and support planning rather than for changing project data.

Temporary local data

The implementation indicates that temporary session information may be stored locally during use so that the add-in can recover or flush a usage summary if Excel closes unexpectedly.

What this means for end users

• the tracking is related to add-in usage sessions
• it does not appear to be part of the LookAhead worksheet content itself
• it may record interaction counts and timing information

Important publishing note

This repository snapshot does not define:

• your organization's privacy notice
• your retention policy
• your log destination
• who can access usage summaries
• how long tracking data is retained