[David Cutler]

Is it a setting in your email program @Doug McLean ? While I don’t use it on a regular basis when I just tried emailing a page from the thumbnail view the email was created in HMTL format.

We use Outlook for our email. When I checked my mail settings the default is to “Compose messages in this format: HTML”. I switched it to “Plain Text” and tried the same procedure as above and the email was created in “Plain Text”.

See screen shots below for where I found this settings.

[David Cutler]

@Jeff.Collins were you able to find a way to import these comments?

[David Cutler]

What version of Revu are you running @ChrisRiley ? I know others have been reporting issues with 20.80, 20.85 and 21.

[David Cutler]

@ChrisRiley have you seen this previous post from @troy-degroot ?

https://uchapter2.com/brainery/civil-design/forum/topic/creating-and-tracking-rfis/

You may be able to use Troy’s suggestion of having your RFI form as a template to insert into your documents…

[David Cutler]

I think @vince what he is asking is can you select multiple cutouts (say window and doors on an elevation view) and then paste that group of cutouts onto another markup. Does this sound correct @robgib0 ?

As a different approach Rob could you copy the markup that has the cutouts already and paste it onto your next markup area? Even if you had to change the properties or perhaps limits of the “new” markup it may be more efficient than cutting out all the areas.

[David Cutler]

That’s a good question @robgib0 , I’ve never thought to try it…

[David Cutler]

Missed the “email template” portion of you question… 🙂 Not sure how to change that…

[David Cutler]

I think the “consistency” is where I was getting messed up yesterday @Doug McLean

Reading through some of your XCON materials I think what I need to do is setup a template file with the query in our “new project” directory template and save the exported file to the same directory every time with the same name every time… I have the export columns setup to be generated consistently, now I need to be more disciplined in my file naming…

[David Cutler]

Understood on being stuck in the ruts @ChrisRiley – turning an organization – large or small – takes time and can be very difficult as I’m sure you are well aware. At the same time it sounds as if many of these same individuals started on paper systems and have grown to use Revu. Perhaps this is an opportunity for additional growth for them? I know that when I see an example presented by @troy-degroot , @Doug McLean , or @Vince I get inspired to see what new feature/tool I can utilize in my workflow.

[David Cutler]

Lots to digest here @ChrisRiley !

Have you considered establishing custom tools for each reviewer that include their custom layer assignment?

Another option might be to filter by reviewer, select all and then assign them to the appropriate layer.

Either would get the cat’s review comments onto the proper layers.

[David Cutler]

Great points @dhwalkellc – especially on the difference between estimating and buying out a project. Every industry, and company within that industry, have their approaches. Definitely interesting to hear everyone’s approaches.

[David Cutler]

I like the concept of rounding each piece @troy-degroot . I think I’d want to have a total both ways (straight measurement and rounded) so I would be able to better understand the waste that is being incorporated with the rounding. One could even incorporate a simple formula to calculate the waste in each run so you could avoid “over compensating”.

For example if you had 4 each 25 foot runs (100 lf neat length) you wouldn’t want to buy 2 each 20 ft sticks for each run (160 lf of pipe) as you would most likely have an extra 40 lf (or more) left over. At the same time I don’t know that I’d order exactly 100 lf either!

The other example would be 4 each 35 foot runs (140 lf neat length). I don’t think my superintendent would be happy if I ordered exactly 7 sticks and told him he had to use a bunch of 5 ft cutoffs to finish the last run. Here I probably would want 2 each 20 ft sticks per run so I’d order 160 lf.

Great discussion!

[David Cutler]

Always interesting to hear about the issues in other portions of the industry @Doug McLean

Do you make your allowances for waste? In your takeoff, in your data washing, or in your estimating system?

For example we measure storm drain piping from the center of the drainage inlet to the center of the next drainage structure. We then total all of the takeoff for a certain size – 18″ High Density Polyethene Pipe (HDPE) and enter that into our estimating software. Once it is entered – say 950 LF, we use that quantity for calculating our production. For purchasing we calculate and apply a waste factor so that we purchase 960 lf as the standard stick of pipe is 20 ft long. This can throw off your “typical” unit prices if say you are pricing a 22 ft long run as now you have 40 ft of pipe material cost in your item. Buying 2,000 lf for a 1,996 lf long run not so much.

Curb we run our takeoff and typically round up to the nearest 5 ft when we enter the item into the software.

Stone/Asphalt we typically round to the nearest 5 square yards.

Curious to learn how others handle this.

[David Cutler]

Coming up on a year since your post @Jeff.Collins . Have you made any progress promoting digital reviews?

[David Cutler]

While that sounds possible @Vince the “status” appears to be a running record of all statuses that have been applied with the most recent status being what would be displayed. So while your “current” status would be “blank” you’d still have the previous statuses listed in the column.