Review the sheet package before it goes out.
Review sheet names, numbers, and title-block information before a drawing package goes out. Define your rules and how the team should correct the issues the app finds.
Use this template to build your own app with Conduit. Describe your requirements in plain English and review the plan. Conduit writes the code; you test the result and ask for refinements.
When to use this starter
Project teams checking drawing packages and correcting sheet information before release.
Bring these details
- The selected sheets or sheet set that belongs to the package.
- Your sheet naming and numbering conventions.
- The title-block and issue metadata required for this release.
Shape the first version
- Check the selected sheets against the package rules.
- Flag missing or inconsistent sheet and title-block information for review.
- Define a guided correction or confirmed batch-update flow for the changes you want the app to make.
A brief you can adapt
Start with this example, then add your project’s requirements and rules.
Build a Revit tool to review selected sheets before an issue. Check sheet names and numbers against our conventions and flag missing title-block fields. Show the current and proposed values before any correction. Ask me which fields and rules apply to this package.
Check the result before sharing it
- Test one compliant sheet and one sheet missing required issue metadata.
- Confirm the app checks only the intended package.
- Review proposed corrections before applying them, then verify the sheet and title-block values in Revit.
From your first build to your team
Test your generated app in Revit, refine it in the Builder, and choose the version to deploy. One Desktop Runner install delivers assigned Conduit-built apps to each teammate and keeps them updated.
Your versions stay in Conduit. Every app reports how it’s running for your team, helping Conduit diagnose problems and make improvements.
Ready to make it yours?
Build your team’s version of Sheet Manager.