Yes, AI tools can now produce real Revit elements, meaning families with categories, types and parameters placed on levels in a project, and they can edit those elements afterward. The more useful question is whether the result behaves like something a modeler built. You find out the first time the equipment specification changes a week after the unit went into the model. Someone then has to swap the size, renumber the unit and move it without leaving a trail of orphaned types and confused schedules.
AI agents that create and modify Revit models
The clearest public example we can point to is our own. The ArchiLabs Desktop page has a recording in which a manufacturer's PDF goes into the conversation and a native Revit family comes out, which is then placed in a project. The page states two things worth knowing. Dimensions the PDF didn't specify were approximated, and waiting periods were edited out of the video. Neither changes what the recording shows, but both tell you what to look for when you try it yourself: which dimensions came from the source, which were estimated, and how long a real run takes.
Desktop runs on Windows and edits native models in Revit 2023 through 2027, as well as native AutoCAD content. Families are one part of what it handles. The same workspace covers modeling, routing, schedules, tags, dimensions and sheets, and it accepts PDFs, spreadsheets, screenshots with markups and elements you've selected in Revit as input.
Other tools focus on different kinds of model work. Autodesk's Revit Assistant, built into Revit 2027 and later, now supports model modification as well as help and queries. BIMLOGIQ documents an Argus command that creates or updates sheets from an Excel mapping. That is model creation of a documentation kind, where the hard part is matching spreadsheet rows to sheets rather than getting geometry right.
What makes a created family usable
A family can look right in a 3D view and still be wrong in every way that matters later. Most of the difference lies in properties you can't see from the model view.
Category comes first, because it decides which schedules the element appears in, which tags work on it, how view filters treat it and how it behaves in coordination. Equipment created as a Generic Model can look perfect and then be missing from the mechanical equipment schedule. When you open a created family, check its category, family and type names, and parameters before anything else.
The split between type and instance parameters decides how the family behaves when things change. Dimensions that define a product size belong on the type, so every unit of that size stays consistent. Values that vary from one placement to the next, like an equipment ID or a mounting offset, belong on the instance. If those are reversed, editing one unit will either change all of them or force you to edit each one by hand. Try changing one dimension that's meant to be editable and see which elements respond.
The amount of detail should match how the model will be used. An early coordination family might need only a correct envelope, location and equipment ID. A later deliverable may need more data and more precise geometry. Tell the agent which one you need, or it will make that choice for you. If the family will be scheduled, confirm that the fields your schedule expects actually exist on it.
Approximations should be visible. A source PDF rarely has every dimension, and estimating the missing ones is reasonable. Ask the agent to list which values came from the document and which it estimated, so the next person knows what to verify against the final submittal.
Placement is part of the job
A family that's correct in the Family Editor can still land in the wrong place: on the wrong level, inserted at a corner instead of its center, rotated, or unhosted when it should be on a wall or floor. Give the agent the level, insertion reference, orientation and host, then check the result in both plan and section.
When you ask for a set clearance from a neighboring object, measure it yourself between the faces you meant. The distance reported in the conversation may have been measured from a different reference point. Our guide to reviewing AI-generated Revit geometry covers more checks for created geometry in its project context.
When the specification changes
The second request is where weak output shows. Suppose the engineer selects the next size up, the equipment gets a new ID and the unit has to move to make room for a duct run. With Desktop, you can hand over the revised cut sheet or a marked-up screenshot in the same conversation as the model.
A well-behaved agent reuses the existing family, switches the instance to a new or existing type for the larger size, updates the ID and moves the unit. A poorly behaved one creates a second family for the new size, leaves the old type behind, or places a new instance next to the original. Each of those leaves something a person later has to find: a schedule with two units where there should be one, a tag still attached to the old instance, or a type list full of near-duplicates.
Before the revision runs, ask the agent whether it plans to create a new type or family and why. Afterward, look for duplicate instances, unused types, and IDs that disagree between the schedule and the tag. Ask for a short note on what changed and which values are still approximations. That note lets a colleague pick up the model without replaying the whole conversation.
If you have a manufacturer PDF on your desk and expect a revision to follow, try both steps in ArchiLabs Desktop. Plans start at $19 a month plus usage credits, as listed on the pricing page.
Review generated model geometry across views and schedules to catch errors a single attractive 3D view can hide.