01 / CUSTOM REVIT TOOLS & ADD-INS
Your workflows.
Your tools.
Inside Revit.
Custom Revit tools and interfaces built around the way your team models, documents, checks and delivers projects.
SCOPE / FROM A COMMAND TO AN ADD-IN
Different scales.
A clearly defined task.
The interface and the underlying functionality are scoped together. The right package depends on what your team needs to do.
Single-purpose command
One defined operation with agreed inputs, rules and outputs. A focused starting point for a recurring task.
Related toolset
Several commands that address related tasks and use consistent terminology and conventions.
Custom Revit panel
A tailored interface that groups agreed commands around how your team works. Interface scope is distinct from the tools behind it.
Company-specific add-in
A broader package of agreed functionality, interfaces and configuration, with its dependencies and deployment requirements reviewed together.
CUSTOM PANEL / ILLUSTRATIVE EXAMPLE
Group tools around
the work they support.
The groups below illustrate one possible structure. They do not mean that all of these tools already exist or are included in a project.
Custom Revit panel visual — real or approved demonstration asset required
Illustrative workflow groups
- Project Setup
- Structural Modelling
- Connections & Components
- Documentation
- Schedules & Data
- Quality Control
- Export & Reporting
- Utilities
Names, commands and grouping would be agreed around your own standards and workflows.
METHOD / CUSTOMIZATION
Define the operation.
Then define the interface.
Identify recurring operations
Review the current task, its frequency and the exceptions that matter.
Group commands by workflow
Identify related operations and where they belong in the interface.
Define functionality
Agree inputs, rules, outputs and the boundaries of each command.
Agree names and interface
Review terminology, placement and configuration with the people using it.
Test against agreed scenarios
Check expected outcomes and relevant edge cases in the agreed environment.
Deliver guidance and handover
Prepare the agreed installation, usage and handover material.
HANDOVER / POSSIBLE DELIVERABLES
Agree what
will be delivered.
The project agreement specifies the applicable items. This is a scope checklist, not a promise that every item is included.
- Agreed custom tools
- Tailored interface
- Installation / deployment guidance
- Documentation
- Configuration guidance
- Testing against agreed scenarios
- Handover
- Optional maintenance, if separately agreed
FAQ / SCOPE & WORKING ARRANGEMENTS
A few practical questions.
Can you build a tool specifically for our company?
A company-specific tool can be scoped around a defined task. Feasibility, inputs and acceptance criteria are reviewed before development is agreed.
Can multiple tools be grouped into one panel?
A panel can be considered for related commands. The grouping depends on command compatibility, target Revit versions and the agreed installation environment.
Can existing tools be adapted?
Potentially. Source-code access, permissions, licensing, dependencies and technical compatibility must be reviewed. Adapting an existing tool is not always feasible.
Which Revit versions can be supported?
Target versions are confirmed during scoping. API differences and dependencies affect compatibility and testing; support is limited to the agreed versions.
Can the tool follow our internal standards?
Provided naming, parameters, checks and interface conventions can be reviewed for inclusion. Discovery confirms what can be automated and what still requires human judgement.
Can we request changes after delivery?
Changes can be discussed after delivery. Their scope, cost and scheduling depend on the agreement and whether they are covered by an existing support arrangement.
Who owns the delivered code?
Code ownership, delivery of source files, reuse rights and third-party licensing are defined in the agreement. Source-code ownership is not automatically transferred.
Can the tool be maintained in the future?
Maintenance can be scoped separately. Updates depend on Revit changes, dependencies and the agreed support terms; perpetual maintenance is not assumed.
How is the project priced?
Pricing depends on agreed functionality, complexity, integration, testing and handover requirements. Scope is reviewed before a proposal is prepared; no universal fixed price applies.
What information is needed to begin?
A description of the task, current workflow, Revit versions, expected outputs and relevant standards is a useful start. Sample data, access and confidentiality requirements are agreed during discovery.
NEXT STEP / A-BIM.API
What should your team be able to do inside Revit?
Start with a recurring operation, an interface idea or a tool you wish existed.
Discuss a Custom Tool