What's yours?

Tapping in some of our community project pros to start us off! @Adam.Candy @Amber.Juarez @Chad.Burcaw @KevinPeters @tatumforrester @zdbourne @Djavan.Audebert @Jason Guidry @Robert Stein @Stephane.Gagnon @Mike.Cahill @David.Gray @yan.soe @hannahsinks @Brittany.Dodson @Vince.Sanderson @Hady.Elkholosy @apatni @Briccio Bolo @Chantel.Dexter @Marcus.Love @Adam.Cripps @AllenWoodward @ShirinT @emmanuel @David Dionne @jrbeyer @Stephen.Simpson

Share your perspective in the comments.

A) Accurate cost status isn't available until it's too late
B) Schedule updates don't reflect what's actually happening in the field
C) Too many disconnected "side" reports from too many sources
D) Risks and issues aren't surfaced until they've already made an impact
E) Something else? Tell us below.

What do you think is one of the most underrated features in InEight, and how do you leverage it in your day-to-day work?

Whether it’s a time-saving shortcut, a reporting capability, a workflow feature, or something else entirely, we want to hear what makes it valuable for you and your team.

👇 Share your answer in the comments below. Help start us off @Saakshi_Amrale @Rachel.Garcia @Paul.Hewitt @Brittany.Dodson @Pam.Magee @samehtalat @Kim_T @yuriwarwaruk @Dwayne.Leffers @Tommy.Hartford @AJOSE @Abdul Rafay@Andrew McDonald @brent driggers @macy.kite @Tomas @Morne.Kruger @Hira.Qayyum @Kaitlin.Cain @olivergr

At our end, it’s a bit of a mix. Some teams are still very Bluebeam-heavy, others are starting to use more of what’s available in the native viewer.

Curious what others are doing in practice:

• Are you doing markups directly in InEight, or still handling them outside the system?
• If you are using InEight, are you mostly using Bluebeam or the built-in markup tools?
• Do you have subcontractors in there doing markups as well, or is that kept internal?
• Are you putting any structure around it with workflows, or keeping it fairly loose?
• How are you managing redlines across revisions?

Just trying to get a sense of what’s actually working for people, what’s practical, what’s not.

Would be especially interested to hear if anyone has moved away from Bluebeam, or if most are still running both side by side.

So save your spot and join us on Zoom! Time will appear in your current time zone.

We have only a few that are being used consistently, so I'd like to know which tag labels are producing the most value either from a project management viewpoint or from a reporting and analytics one.

Join us on Wednesday, June 10 at 2:00 p.m. EDT when we explore how to give your team a clear view of where a job stands, where it’s headed, and what needs attention before it becomes a problem.

You'll learn proven strategies to:

• Align cost, schedule, and field progress in one system for a real-time view of project performance
• Build forecasts that reflect what’s happening now
• Manage changes with full visibility into cost, schedule, and contract impacts
• Build work packages that reflect how crews actually execute the work, while still tying back to schedule and cost for proper control
• Improve decision quality throughout the project lifecycle with a PMIS-driven document strategy

Registering is easy, just click the link here.

Here are a few highlights our users are especially looking forward to (and already enjoying):

✨ More Transparency Where It Matters
The Quantity Tracking layout update now features the Audit Log as its own tab—making it easier than ever to track changes, validate updates, and keep everything crystal clear. 🔍✅

📊 Control at Your Fingertips
Say goodbye to waiting—manual dashboard refresh lets users update data on demand. Because sometimes you just need the latest numbers now. ⏱️💡

📸 A Better Visual Experience
Reviewing field progress just got smoother with photo carousel previews in Daily Plans. Flip through images effortlessly and see the story unfold right in front of you! 🖼️➡️

What’s your favorite feature in 26.3 so far? Or what are you most excited to try?

Drop your thoughts below 👇 and let’s keep the conversation going!

We’re curious how different organizations are using Time‑Phased Forecasting and managing updates to forecasts.

A few quick questions:

• ⏱️ Are you actively using Time‑Phased Forecasting?
• 🔄 Can updates push directly to the Live Forecast, or is approval required?
• 👥 Who owns forecast updates — PMs, Project Controls, or both?
• 🔐 Any controls in place to avoid unintended Live changes?

There’s no one right approach — we’re looking to learn how teams balance flexibility, accuracy, and governance.

Share what’s working (or not) for you below 👇

From my perspective, this highlights an opportunity, both internally and with InEight to continue progressing AWP as a connective framework, particularly across Model, Scheduling, Control, Materials Management, and Document. The intent would be to strengthen integration and usability in support of field production and execution, rather than treating these areas as separate system or process layers.

I’m interested in how others view this.

What opportunities do you see to advance AWP, through integration, system alignment, or practical enhancements, when it’s treated as the backbone connecting planning, execution, and controls?

Where do you still allow email to be default?

I'm interested in what's working and if this is a common risk among your projects?

📊What’s the biggest friction point in your PO receipt workflow today?

1. ⏳ Waiting on sync/batch timing before moving forward
2. 📎 Supporting documentation (finding/naming/attaching) slows us down
3. 🔁 Rework (can’t edit → have to reverse + re-enter)
4. 🧾 Change order timing/sequence creates delays or confusion

Drop a comment with one tweak you’d love to see (or a workaround that actually works). Bonus points if it saves the field + office team time and improves audit-ready documentation. 💪

What would help most: faster processing, clearer status visibility, or simpler documentation capture? 👀

I wanted to share something I’ve been experimenting with lately regarding the integration between Primavera P6 schedules and the ineigh Control Module—specifically around aligning the activity structure with the Cost Breakdown Structure (CBS).

I’m currently testing an approach where I use Activity Codes in Primavera as my WBS/CBS framework. The idea is that this creates a cleaner, more consistent mapping when exporting the XER file and integrating it back into the ineigh control module. So far, it seems to simplify the alignment between schedule activities and cost elements.

I’m curious to hear from others who’ve gone through this integration process:

• Have you tried integrating an XER file directly with the Control Module?
• From your experience, is it more reliable to use the Activity ID or Activity Codes as the primary integration point?

Any insights, lessons learned, or pitfalls to avoid would be really valuable for anyone working on schedule‑cost alignment.

Looking forward to your thoughts and experiences

Is it how they communicate? How they handle risk? How they keep teams aligned when things get challenging?

In your experience, what behaviors or approaches truly set the top performers apart?

Extra points if you give them a shout out or @mention in this post 🏆

Join Rick Rients, Director of Client Solutions at InEight, as he kicks off the conversation with practical insights on aligning control structures, contract management, and change workflows across complex projects.

The session will then move to open discussion where peers can exchange experiences, ask questions, and compare how others are managing these workflows in real project environments.

Come hear how others are approaching these challenges and pick up ideas you can bring back to your own teams.

Save your spot and join us on Zoom. Hope to see you there!

I’m looking for quick insights on how your organizations are adopting the InEight field mobile apps:

• InEight Document (Field Use)
• InEight Compliance & Completions
• InEight Progress

A few quick questions:

• Where are you currently at with field adoption? (Fully adopted? Partially? Still piloting?)
• What successes have you seen?
• What challenges have you run into? (training, devices, connectivity, change management, etc.)
• Any tips, workflows, or lessons learned that helped drive adoption?

I'm excited to learn from the community’s experience!

Join Brittany Dodson and Michael Licarione of Orion as they share practical strategies to improve alignment, reduce rework, and strengthen coordination across field teams, project teams, and leadership.

Tap into actionable collaboration practices you can apply immediately to support stronger, more consistent project delivery.

Save your spot and join us on Zoom, hope to see you there!

For those using project controls and cost management modules, adoption is often the difference between “having the tool” and “getting the value.”

Quick poll:
What is the biggest adoption challenge your teams face today?

A. Duplicate entry / parallel tracking outside the system
B. Limited field or project team engagement
C. Training gaps or inconsistent onboarding
D. Processes not fully aligned with the platform workflow
E. Reporting value not clearly visible to teams
F. Other (share in comments)

How has your organization addressed this challenge, and what has actually worked?

Let’s compare notes and share practical ideas that help move adoption from “mandated” to “embedded"! 😀

Hi everyone,

I’m looking to compare workflows around the integration between InEight Documents and the Change module, and I’d love to hear how others are handling this.

When you’re managing change events, what’s your preferred approach?

Start in the Change Module

You create the issue or change event first, then push it into InEight Documents to generate the related documentation.

Start in InEight Documents

You create the document first (e.g., a change request, RFI, or supporting material), then push it into the Change module to initiate or link the issue.

If you’ve tried both approaches, what pros and cons have you seen?

We are currently working through the process of integration from Estimate to Control to streamline our processes and improve our handoff from Preconstruction to Operations. The main goal is to retain resource information for our operations teams so we can eliminate the need to provide side spreadsheets/access to the estimate for those personnel. We have run into a ton of hiccups throughout the process and have ended up implementing a ton of work-arounds (which is somewhat worrisome) in order to get to where we need to be.

Just curious from the community here on a couple things:

1. Is anyone doing this process successfully and willing to share some successful outcomes?
2. Would a seamless integration process from Estimate to Control (including subsequent packages) be value-add to more companies out there?

Thanks for any thoughts and comments you may have!

Which modules do you think are most important to understand when looking at the roadmap for data connectivity features?

Whether you're working in estimating, project controls, or field execution, your insights could help others better navigate upcoming changes and integrations.
Looking forward to hearing your thoughts and experiences!