Prerequisite
Scheduling requires a model linked from Forma or Autodesk Construction Cloud. If your model was uploaded from your machine it cannot be scheduled — there is no way for Pirros to see it change. You can still run reviews whenever you like; you just start each one yourself. See Run a one-off review.
Scheduled reviews are what turn Pirros from something you remember to run into something that runs alongside production.
Three words you need
These get used constantly, so they are worth getting straight:
Milestone — a phase and a submittal date. "50% DD, due the 30th."
Review stream — the configuration inside that milestone: which model, which drawing set, which codes, and how often it runs.
Run — one execution of that stream. Runs accumulate into a history.
So: a milestone holds a review stream, and the review stream produces runs.
Setting one up
Go to the project's Schedule tab.
Create a milestone — give it a phase name and a submittal date.
Inside it, configure the review: select the model, the drawing set, and the codes.
Set the cadence — daily, weekly, or monthly.
From then on it runs on its own. A common setup is a weekly cadence that production staff work through, with the project manager reviewing progress on Monday morning.
You can scope a milestone tightly — an accessibility check at 50% SD covering only the A200 series, for instance — rather than reviewing everything every time.
Running a scheduled review early
You do not have to wait for the cadence. A scheduled stream can be run at any time using the same configuration — useful when a deadline moves or you want to check the effect of a day's work.
It counts as a normal run and joins the same history.
One review stream per milestone
Today a milestone holds a single review stream. If you need two different configurations — say, different codes or different sheet scopes — create two milestones.
Starting fresh
When you configure a new review you can choose to start with no history. This produces a clean result that has no memory of earlier runs — which also means it will re-create issues you previously dismissed.
Most of the time you want the opposite. See How runs build on each other.
Frequently Asked Questions
Q: Can I schedule reviews on a model I uploaded from my machine?
A: No. Scheduling needs a linked model, because Pirros has to be able to see the model change. An uploaded model is a snapshot from the moment of upload.
Q: What cadences can I choose?
A: Daily, weekly, or monthly. Weekly is the most common — production staff work through the findings and the project manager reviews progress on Monday.
Q: Can I run a scheduled review before its next scheduled date?
A: Yes. It uses the same configuration, counts as a normal run, and joins the same history. Useful when a deadline moves.
Q: Can one milestone have two different review configurations?
A: Not today — one review stream per milestone. If you need two configurations, create two milestones.
Q: Do I have to scope a milestone to the whole set?
A: No, and tighter scopes often work better. An accessibility check at 50% SD covering only the A200 series is a perfectly good milestone.
Q: What does "start fresh" do?
A: It produces a review with no memory of earlier runs. Nothing is auto-resolved, and issues you previously dismissed will be raised again. Most of the time you want the opposite — see How runs build on each other.