A plain description of the first weeks of a remote engagement, written from doing this since 2020 — not a sales pitch.
"Remote Revit modeler" covers a wide range of arrangements in practice. Some firms want someone to sit inside their central model and behave like an extra team member for a few months. Others want one deliverable — a set of existing-conditions plans, a DD package — handed off and reviewed at the end. Both work, but they start differently, and most of the friction I've seen over the years comes from not being clear about which one it is before work begins.
The first days of a new engagement are rarely about geometry. They're about getting into the firm's Autodesk Construction Cloud (ACC) or BIM 360 project, understanding the worksharing setup, and reading whatever standards document exists — sheet numbering, line weights, family naming, how views are organized on sheets. Firms that have this written down (even informally) save both of us a week of back-and-forth. Firms that don't usually just point me at a finished project from a similar building type and say "match this," which works fine too, it just takes an extra round of questions up front.
In practice, most of the day-to-day happens over email and a shared drive, with a call scheduled when something is easier to explain by screen-sharing than by writing — usually once a week, sometimes more during a heavy CD push. Because I'm several hours behind the US, the most efficient pattern I've found is: I send an end-of-day summary of what moved and what I need clarified, and it's waiting when the team starts their morning. Questions that arrive by their early afternoon usually get a same-day answer from me.
I don't keep a separate copy of the project as the "real" one. I work inside the client's central model, so there's never a merge-back step where two versions of the building have to be reconciled. If the firm needs to pull me off a project, or if I disappear tomorrow, the model and the sheets are exactly where they'd be if a full-time employee had built them — nothing lives on my machine that isn't also in the firm's system.
The recurring failure mode isn't technical, it's scope drift: a "quick DD update" that quietly grows into a CD set without anyone agreeing on it explicitly. The fix is boring — write down the phase and the deliverable at kick-off, and flag it out loud the moment the ask changes, rather than just absorbing the extra work. The second most common issue is missing source data for existing conditions (see the companion piece on documenting existing conditions without a site visit) — a remote modeler can't measure a wall that nobody photographed.
If you're deciding whether this setup fits your project, the practical next step is usually the shortest one: send the scope and I'll tell you honestly whether it's a good fit before any commitment is made. See How I Work for the full breakdown, or the day-one checklist for exactly what to send to get started fast.
Send me the scope, and I will reply with a time and price range, typically within one business day.