Most firms assume they need an organized detail library before they can get value from Pirros. That's not the case. Pirros is built around a project archival approach: you upload your past Revit models, and Pirros automatically extracts and indexes every detail inside them — making everything searchable from day one, with no tagging or categorization required.

Rather than curating upfront, Pirros lets your standards emerge naturally over time. As your team searches for and downloads details, Pirros tracks usage patterns. Admins can then use that data to decide which details are worth promoting to firm-wide Typical standards — turning real project activity into a living, growing library. Learn more about the project archival approach →

Before your team can start downloading and reusing details, you'll need to set up a Container Model in Pirros. This is your firm's single source of truth — a dedicated Revit model that houses all vetted Typical details and stays in sync across your projects. Think of it as the home base that Pirros references when team members pull standards into active work.

Setting up your Container Model correctly from the start saves significant rework later. Read the full Container Model guide →

Once your projects are uploaded and your Container Model is in place, Pirros gives you two powerful tools to grow your Typicals library organically — without guesswork.

In order to begin building out a Typical detail library for your firm, you must first upload project details onto your Pirros database. See Add Project Details onto Pirros to learn how to upload project models.

When your Pirros library is filled with details from multiple projects, Pirros will provide you with Typical detail suggestions — surfacing details that appear regularly across multiple projects as strong candidates for firm standards.

To see Typical detail suggestions, navigate to the Management tab in the top navigation bar and click Pirros Library Builder. From there, admins can review recommended details and begin promoting the most relevant ones to the firm's Typicals library — turning everyday project data into a structured, data-driven curation process.

Admins have full visibility into all project details across every uploaded model. To manage the review process, admins can create Stashes — curated collections of details flagged for evaluation. This gives your leadership team a structured way to review, compare, and selectively promote details to Typicals, without needing to sift through everything at once. Stashes act as a holding area where quality control happens before details are published to the broader team.

Learn how to create and manage Stashes →

Once Pirros is rolled out to your team, your staff become active participants in building the library — not just consumers of it. As team members search for details across projects, they'll naturally identify gaps: details they frequently rely on that haven't yet been promoted to Typicals.

Encourage team members to flag details directly in Pirros when they find a project detail that should become a firm standard. Admins can then review flagged items and move them through the vetting process. This creates a continuous feedback loop where the people doing the work help shape the standards — keeping your library current, relevant, and grounded in how your firm actually builds.

Learn how team members can flag a detail for review →

Tip: Share a simple internal process with your team at rollout — even one line like "If you find a detail you'd reuse, flag it for review" — to set the expectation and drive consistent input from day one.