KPFF Consulting Engineers Shares Complete Project Records With Outside Parties Through Files.com Data Rooms

KPFF Consulting Engineers is a multidisciplinary engineering consultancy with roughly 1,300 employees across the United States. Its structural and civil engineers provide project design and forensic engineering services.

Decades of built work produce a second kind of engagement alongside design: forensic engineering. When a structure fails or a project ends up in dispute, KPFF engineers study the full documentary record to form opinions about what happened. That work runs on entire project file sets moving between KPFF offices and out to consultants, clients, and law firms, with each outside party limited to its portion of the record.

Complete Project Records for People Outside the Firm

The project record lives on KPFF's office file servers. Sharing it for a forensic engagement means pulling large sets of files off those servers and getting them to people outside the firm. KPFF had run that exchange on SharePoint, its general collaboration platform, and wanted a layer built for the job instead.

The people on the other end are outside counsel, client attorneys, and consultants: no KPFF systems access, no training on KPFF's tools, and no patience for a portal that fights them. Each engagement involves several of these parties, and each needs to see only its own portion of the record. KPFF wanted one place to hold the complete record for an engagement, with a boundary around each party's view. A collaboration platform built for people inside one organization is not shaped for controlled multi-party exchange with people outside it.

A Data Room per Engagement, Scoped by Group

What the practice needed was specific. Something that could hold the complete record for an engagement in one place. Something that put a boundary around each party's view, so outside counsel, the client's attorneys, and outside consultants each saw their portion and nothing else. And something that worked in a browser, for a lawyer who will never install software or get a KPFF network account.

KPFF selected Files.com to be that exchange layer and proved it on a forensic engagement in one office.

Files for each engagement came off KPFF's office servers into a dedicated folder on Files.com. The firm organized participating KPFF engineers and outside counsel into groups, then used Files.com's group-based folder permissions to define each party's view with one group assignment rather than permissions built person by person.

Outside participants could upload and retrieve project files directly through the browser, using their credentials or a Files.com share link. Engineers loaded the record, the engagement administrator reviewed what arrived, and each outside team gained access to the files it needed without KPFF shepherding every transfer.

From One Engagement to Three Offices

With the workflow in production, KPFF replaced collaboration-platform sharing with a repeatable data-room pattern.

• Sharing a complete record runs end to end: engineers upload, access is granted per team, and outside counsel retrieves the record themselves.
• People with no KPFF systems access move large project files on their own, without a KPFF engineer shepherding each transfer.
• Per-engagement administration is group assignment rather than individual-by-individual permissioning, so setting up the next party does not become a permissions project.
• Standing up a new engagement is a folder and a set of group assignments, which is what let the pattern travel: what began in one office now runs in three.

A Standing Pattern for Every Engagement

Today, sharing a project record has a known shape at KPFF. An engagement folder opens on Files.com, the engineers load the file set, and each party's team sees its portion once access is granted. What that replaced was file-by-file sharing through a collaboration platform that was never shaped for multi-party exchange.

KPFF did not fix SharePoint, and did not need to. It stopped asking a collaboration platform to do a data room's job. Moving a complete project record to multiple outside parties, each under its own access boundary, is its own kind of work. One engagement was enough to prove the layer that does it before three offices made it theirs.