Civil3d For Cadastral Drafting
Since you are already using C3D, I would say stick with it. You are already using the Survey Database for linework and surfaces, which is what it does best. Don't use it for anything else - run data through the database, QC, create surface, then unlock points and detach the database. It's not good for much else.
I would caution against using C3D for projections and scaling from grid to ground. It can be done, but considering how the bulk of folks sharing drawing files across a project have little to no understanding of coordinate systems, it is usually best to keep everything in the drawing files to simple "no datum, no projection". I am not sure how it works in your neck of the woods but around here no one aside from about 30% of surveyors actually understands how to set up coordinate systems in C3D. Since you are already planning to use an outside adjustment program, the workflow will suit you just fine - IMO it is better to use a surveying-specific program to perform the analysis, adjustment and bring data to ground.
But if you really want to set up projections and the like, it will work. Labels can be set up to use geodetic distances, grid distances, ground distances, forward/reverse geodetic bearings, etc. Once you have your default label styles set up, it is a piece of cake to do the labelling. Point labels will also do geodetic, ground, grid, etc.
(I used to write simple scripts to bring GIS info and orthoimagery from state plane gride to local project coordinates - the engineers and architects were able to use those when needed, and this allowed everyone to be on the same page and avoid any strange scaling or transformation errors when Xrefing or importing other drawings. But this does prevent you from having the geodetic info at your fingertips in the drawing.)
C3D parcels take some getting used to, but once you learn them they can be used with great effect. It is easy to run map-checks and check for gaps/overlaps in basemaps. Not sure if you have used it before, but you can define data tables (ADEDEFDATA command) and add that data to C3D objects (ADEATTACHDATA) for land use schedules. It is a little-known and -used tool, but it is essentially like an attribute table in GIS. You can also export to GIS formats if you desire.
I have used Trimble Business Center's legal description writer, and it works pretty well - better than Civil 3D add-ons. But honestly, that was just because it was already included in the program. When I didn't have that I used Word macros to format the bulk of my legal descriptions (using the parcel map-check text as the basis). You always have to do typing and editing in the end, and the time/money savings are minimal, especially if you are paying money for a program that does what a macro can do for free.
I agree with Bob - I would avoid Carlson if you are already using C3D. The tools are already there in C3D, and you will just be adding another learning curve (and shelling out more money) for a program that is really geared toward surveyors who have always used Carlson and want that feel when working with C3D. It's a great program, just likely unnecessary for someone already working in C3D.
Cadastral mapping in its simplest form is adding a database to a lot polygon. You do not want to manipulate database entries from within Civil3d or even from base version autocad. As the database size grows, autocad processing speed slows down as it tries to send a query/update to the database. What we did for a past client was to draw the lot polygons either through digitizing basemaps or entering corner coordinates in vanilla autocad. Then we attached a unique lot number to each lot polygon as an attribute data. You could then create a database with the lot number as the database index number and add as much data columns as the client wanted. You then link that database to the autocad drawing using the attribute data of the lot polygon and you could then make a query for the lot information. This process also allowed you to divide the database encoding process among several encoders using Excel then export these into the final database software of the client.
Within Civil3d we set our Grid Scale Factor in the Transformation settings and then uncheck the Apply Transform Settings box. Whenever you need to reference in GIS data, aerial imagery, or any of the myriad of data we use these days that is on the State Plane Coordinate System you simply check the Apply Transform Settings box so that your data comes in on grid, import the file(s) and then uncheck the box. It’s really quite easy.
This is a great workflow. Will have to do this for local office projects.
We have always had problems trying to set up drawings to be georeferenced, as our survey base maps get referenced into engineering plansets, and then we receive plansets get referenced into layout basemaps for construction staking.
I work in a multidiscipline firm with about two dozen offices scattered across half the country, and the plansets we receive are from a mix of our own engineers, outside engineers (usually structural/MEP), and outside architects. It's rare to come across a drawing, even in our regional offices, that even has the correct units setting, let alone any projection or local coordinate set up. A good chunk of our survey people don't even fully understand what C3D projections mean and how they work or interact with other drawings. It can get tricky when someone in OR (Intl. feet) produces something for an office in WA (US survey feet) and forgets critical settings.
However, if your organization is small enough and/or sharp enough to maintain discipline in template and drawing settings, then it will work like a charm.