G2

Kevin D.

IT Project Manager

Information Technology and Services

Mid-Market (51-1000 emp.)

10/2/2026

"Cleaner approvals across IT, security, and business teams"

4.5/5

What do you like best about Filestage?

Reviewer Groups have helped us separate each approval stage without losing the thread back to the same file. Reviewers can leave comments, approve a version, or request changes, and I can quickly see who has responded and who is still holding up the review. From a PM perspective, that distinction really matters, because an informal comment shouldn’t accidentally be treated as a formal approval. Once a document has gone through several rounds, the features I rely on most are Compare Versions, Auto-compare Text, and version history. Being able to review versions side by side, use an overlay, and automatically highlight added and removed text makes a big difference. On longer technical documents, it saves a lot of time because security or legal can focus on the sections that actually changed instead of rereading twenty pages. Automations also keep the process moving by kicking off the next review, updating status, setting due dates, or moving content forward after a decision. The biggest benefit for me is having to chase fewer people manually. I can step in when something is blocked or unclear, rather than becoming the reminder system for every approval. Review collected by and hosted on G2.com.

What do you dislike about Filestage?

The workflow can still get messy when each project creates its own variation. We ended up with several reviewer groups that were almost identical for security, compliance, and business approval, and that made ongoing maintenance harder than it needed to be. Templates and automations do help, but I’d like stronger tools to spot, compare, and consolidate processes that are essentially duplicates. Review collected by and hosted on G2.com.

What problems is Filestage solving and how is that benefiting you?

A platform update needed Architecture, Security, and Business approval before going to production, but the release documentation was still being passed around as PDFs over email. Security raised questions about an authentication change that Business hadn’t even seen yet, and in one meeting we realized two different people were approving two different versions of the same document. We moved the review process into Filestage and set up separate Reviewer Groups for Architecture, Security, and Business. With everything tied to a single proof, each revision stayed in one place instead of branching into multiple email attachments. Auto-compare Text also helped each team focus only on what had changed from one version to the next. We added an automation so the next stage couldn’t start until all required reviewers had submitted a decision. At first our setup was too strict, because we made a technical SME a mandatory approver even though their role was advisory. That meant the document kept getting blocked for no real reason. We adjusted permissions so they could still comment and provide input without holding up the approval decision. After that, we started exporting the Review Report alongside the release documentation, which gave us a clear record of who approved what and when. Filestage didn’t replace Jira for execution, but it did eliminate the version confusion, reduce clarification meetings, and give each release a much cleaner approval history. Review collected by and hosted on G2.com.