Revit Modeling Services: What Should You Receive?

A Revit modeling service should deliver the information needed for an agreed use: design development, multidisciplinary coordination, drawing production or documentation of existing conditions. The deliverable is a defined package, not simply an RVT file.

Autodesk describes Revit as a design and documentation platform supporting models, drawings and schedules. That capability does not mean every modeling engagement includes every output; the scope must identify which ones are required. Revit Fundamentals.

First choose the intended use

• Model production: create specified elements and properties from agreed source information.
• Coordination: review model interfaces, track issues and support decisions across disciplines.
• Construction documentation: prepare an agreed set of sheets, views, annotations and schedules.
• Shop drawings: prepare fabrication or installation information for defined systems and review responsibilities.
• As-built documentation: update information against agreed field evidence, with limitations recorded.

A modeling quotation may cover only the first item. Ask separately about BIM coordination and shop drawing production if your project needs them.

Specify the model package

Record the Revit version, discipline breakdown, project coordinates and required links. Identify the source drawings and revisions. List the elements to model and the properties that must be populated; a blanket instruction such as “everything at LOD 300” leaves too much open.

Agree how uncertainties will be handled. If a source drawing omits a dimension, the modeler needs a question, an explicitly recorded assumption or additional information. A plausible-looking object should not silently replace missing design information.

For a sample handover, ask the receiving team to open the model in the agreed environment, check the links and inspect a representative area. Confirm that the files can support the intended workflow before repeating the process across all areas.

Specify drawings and schedules separately

A useful drawing brief names the sheet list, scales, required views, title block, annotation conventions and revision status. Define whether the scope includes creating details or only arranging supplied information. A drawing view extracted from a model still requires checking for legibility and completeness.

For schedules, list the fields and units, the included elements and any grouping rules. Review a sample against the model. A schedule can look complete while omitting objects that do not match its filters or categories.

Illustrative example: an office fit-out package might include partition plans, reflected ceiling plans and a door schedule. That does not automatically include fabrication drawings for joinery, a structural design or a complete MEP coordination service. Put those boundaries in the scope.

Agree exchange files and review records

The receiving team may need native models, PDF sheets and additional exchange formats. Specify each one, the intended recipient and how it will be checked. Opening a native model successfully does not establish that a separate export contains all required information.

Request a delivery register identifying file names, revisions, issue dates and purpose of issue. Include a list of outstanding questions and known limitations. Where coordination is included, the issue record should identify unresolved items and who owns the next action.

A practical acceptance checklist

1. 1Completeness: compare delivered models and sheets with the agreed list.
2. 2References: check coordinates, levels, linked files and source revisions.
3. 3Information: inspect representative elements and required parameters.
4. 4Documents: check sheet references, annotations, schedules and revision consistency.
5. 5Exchange: open each required file type in the receiving workflow.
6. 6Review: confirm which checks were performed and record outstanding issues.
7. 7Handover: identify who accepts the package and whether additional revisions are included.

The sample checks do not replace the project's complete QA process. They help expose a mismatch between what was purchased and what was delivered before final acceptance.

What changes the cost and delivery time?

The number of disciplines, reliability of the inputs, complexity of elements, required properties, drawing count and revision rounds all affect effort. A small area with dense services can require more work than a larger repetitive area. Compare quotations using the same scope rather than floor area alone.

If existing conditions are uncertain, identify how they will be verified. A model made from old drawings is not automatically field-verified. Scan to BIM may be appropriate when a point cloud is needed, but capture access and visible coverage still limit what can be documented.

Questions to ask before you order

Are drawings included in BIM modeling?

Only if the scope says so. Request the sheet list and the required review stage; do not assume that every view needed for construction will be prepared with the model.

Can one file serve design, fabrication and operations?

It may support several uses, but each requires its own information and checks. Agree the intended uses explicitly and identify who is responsible for specialist design or fabrication decisions.

What should I send for a proposal?

Send the intended use, discipline and element list, available source information, requested model version, drawing list and deadline. Use the proposal comparison checklist or discuss your package through the Revit modeling service.