"LOD 300" alone says almost nothing. For each kind of element, this page lists what must be drawn in 3D and which Revit parameters it must carry at each level, and which BIM uses need it. A BEP or contract can point to these rows, and a model checker can test them.
The BEP Builder's LOD matrix sets the level of each element type at each stage. This page is what each of those cells means. Each level adds to the one before; geometry and data are listed separately because they mature at different speeds.
LOD 500 means the model was checked in the field after construction, to a stated accuracy. It is not a step above LOD 400, and it is never assumed: the owner asks for it, pays for it and says who surveys.
It should usually carry less than LOD 400, not more. Facility management needs the right elements, where they are and the data to run them; it does not need fabrication detail or design-stage parameters nobody will read again. Read as the top of a scale, LOD 500 has led teams to model and fill in far more than the owner ever used.
So at LOD 500 this specification keeps a parameter only if an operations use needs it (handover, maintenance, asset register, space management, commissioning, existing conditions), if it identifies the element, or if it is first asked for at LOD 500. Connections, supports and fabrication parts from LOD 350 and 400 are dropped. A dash in the LOD 500 column marks what is left out.
The idea is explained in LOD Planner's LOD 500 explained. The BIMForum LOD Specification leaves LOD 500 out because it is field verification, not more geometry or information.
All wording on this page is OpenBEP's own. The levels are organised like the BIMForum LOD Specification, which may be cited but not copied; clearance zones and connectors follow good practice in manufacturers' object guides such as the bimstore Bible. Revit names are built-in parameter names, to verify for each Revit version; shared parameters come from the OpenBEP list. IFC targets follow IFC 4.3 property sets. Uniformat II and MasterFormat numbers are our mapping, to check against the edition your project uses. Which BIM use needs which requirement is our own judgement, still to be validated with practitioners. Text: CC BY 4.0.
Data file: spec.json. The BEP Builder reads the same file, so the two never disagree.