Revit family quality is more than file size. Dimensional accuracy, type behaviour, drawing clarity and schedule data also matter. Use a repeatable test sequence to preserve those functions while reducing unnecessary detail.
Record a reproducible baseline
Keep the original file. Record the application version, file size, product types and test project. Place the object once, then for example 100 times, and observe opening and interaction in the same views. The count is a comparison example, not a universal performance threshold. Use the same workstation, views and test arrangement for the before-and-after comparison.
Match detail to the task
Autodesk's family modelling guidance discusses unnecessary geometry, symbolic representation where appropriate and detail levels. It does not establish one universal kilobyte target. Simplify while keeping the shape, placement and technical information the team needs.
| Question | Test | Acceptance criterion |
|---|---|---|
| Is the small detail necessary? | Compare plans and sections | Required drawing clarity remains |
| Do types change correctly? | Select the smallest and largest types | Dimensions and connections stay correct |
| Is information retained? | Compare schedules before and after | Codes and units remain unchanged |
| Does repeated use work? | Reopen the same test group | No new warnings or view problems |
Change one thing and test again
When reducing hidden stitching geometry on a chair, do not simultaneously rename every parameter. Change the geometry first, compare both files in the same test arrangement and record the drawing difference. Then move to the next change. This makes it possible to identify the step that improved or damaged the result.
If the smallest door type distorts the frame, reject the change even if the file is smaller. If an equipment model has correct dimensions but a missing reference code, log that as a separate information issue. Distinguishing geometry quality from information quality helps route a correction to the right person.
Check parameters in the delivery scenario
Add every field needed for reporting to an actual schedule. Autodesk documents using shared parameters in schedules; seeing a familiar parameter name does not establish that the intended field is connected. With two instances of the same product type, define which values should be shared and which should change independently.
A useful decision record starts with five fields: product code, file revision, application version, tested types and unresolved issue. The pre-placement QA guide expands the placement test; the object selection checklist covers source checks. Keep a rejected candidate separate from the accepted release so another editor does not accidentally republish it.
Review the final release
Match the final file against its technical document again and explain what changed in the revision note. When comparing catalogue objects, avoid ranking their quality only by download size. Manufacturers can use the publication preparation guide to organise the handoff.
Revision checks for BIMNESNE publication
The uploaded file, TR/EN descriptions and technical document should describe the same product revision. When a dimension or type changes, update the corresponding description. Do not assume an older cover represents the new file: check the preview and downloaded file together.
Sources and editorial note
Autodesk: family modelling best practices and using shared parameters in schedules. The test arrangement is BIMNESNE guidance, not a speed guarantee or certification. The cover illustrates the concept of simplification.