Open the dialog
In Revit, go to Manage → Project Information.
Fill only the “F.ProjectInformation.*” fields
Click each field that begins with F.ProjectInformation. and enter the values.
Formatting rules (must follow exactly):
Use the vertical bar | between address parts, e.g.
237 S. Westmonte Drive, Suite 220 | Altamonte Springs, FL 32714
Use periods in phone numbers, e.g. 888.888.8888
Keep capitalization, punctuation, and spacing exactly as shown in firm standards.
Apply and verify on the sheet. Click OK, open the title/index sheet, and confirm the fields display correctly. If something looks off, reopen Project Information, correct the F.* value, and OK again.
The information below reflects project parameters, what they represent, and if they should need updating for every new project:
F.ProjectInformation.Architect.Address
Already complete - visible in project team section of the F.Index title block
F.ProjectInformation.Architect.Name
Already complete - visible in project team section of the F.Index title block
F.ProjectInformation.Jurisdiction
User can source the jurisdiction from the file named "Permitting Info - ?" typically located P:\CLIENT\ProjectName.0000\Admin\AHJ\ or can either ask Forum permitting department (Raquel Bryant) / or your Project Manager, Studio Director, or Principal
F.ProjectInformation.MEP.Address
Get F.ProjectInformation.MEP.Name first then look up on the internet
First - P:\CLIENT\ProjectName.0000\Admin\Agreements\RFP, here should be files that contain the consultant agreements
Second - ask your PM, SD, or Principal
F.ProjectInformation.Owner.Address
P:\CLIENT\ProjectName.0000\Admin\Agreements, the look for a file that contains in the name "Contract-", "LOA", or "COS"
See F.ProjectInformation.Owner.Name, get the name and then go to the Ajera Home dashboard and select Clients > look up the name and review the Mailing Address/City/State/ and ZIP
F.ProjectInformation.Owner.Name
Ajera > Project List > Select Project > Invoice > Client
Ask your Project Manager, Studio Director, or Principal
F.ProjectInformation.Project.Description
Typical verbiage: "Proposed new, [affordable,marketrate], age restricted, apartment and amenity". Verify with your PM, SD, or Principal
P:\CLIENT\ProjectName.0000\Admin\Agreements,
...the look for a file that contains in the name "Contract-", "LOA", or "COS", page 1 bottom description
Ask Project Manager
F.ProjectInformation.SecondaryInformation - Shared Parameter - text based user input - used for secondary information placed under 'Project Name' on index title block for sheet A1.01
F.ProjectInformation.Structural.Address - Shared Parameter - text based user input - used for project team section on index title block for sheet A1.01
F.ProjectInformation.Structural.Name - Shared Parameter - text based user input - used for project team section on index title block for sheet A1.01
F.ProjectInformation.01.Dist.Date - F.ProjectInformation.15.Dist.Date - Shared Parameter - text based user input - tied to 'Set Distributions' tag labels in the title block
F.ProjectInformation.01.Dist.Desc - F.ProjectInformation.15.Dist.Desc - Shared Parameter - text based user input - tied to 'Set Distributions' tag labels in the title block
F.ProjectInformation.Accessibility - Brokaw TBD
F.ProjectInformation.ApprovalRequirements - Brokaw TBD
F.ProjectInformation.GoverningRegulations - Brokaw TBD
Client Name - Shared Parameter - text based user input - used for project team section on index title block for sheet A1.01
Project Address - Shared Parameter - text based user input - used for project information section on index title block for sheet A1.01
Project Name - Shared Parameter - text based user input - tied to 'F.Title' tag label on title block
Project Number - Shared Parameter - text based user input - tied to 'F.Project.Number' tag label on title block
F.ProjectInformation.ProjectType - Brokaw TBD
F.ProjectInformation.ConstructionType - Future - Values derived from project setup questionnaire (Automation)
F.ProjectInformation.ExteriorFinishMaterials - Future - Values derived from project setup questionnaire (Automation)
F.ProjectInformation.NumberOfLevels - Future - Values derived from project setup questionnaire (Automation)
F.ProjectInformation.RoofType - Future - Values derived from project setup questionnaire (Automation)
F.ProjectInformation.StructuralMaterials - Future - Values derived from project setup questionnaire (Automation)
Verify AHJ requirements regarding submission sheet size. Check with Studio Director/Project Manager/Director Of Permitting Services.
30x42 default size
20x36 & 36x48 optional. Before using a match line in large projects or changing the scale of your plans verify if 36x48 may be used.
Reference CDs > Sheet Index
Reference CDs > Sheet Index
Optional use as a plot/printed date
Not used on A1.01, Uncheck box for both.
The Title Block on A1.01 Title Sheet is not the same as all other sheets, and is specific to the Index Sheet.
Select the "F.Index" type within the title block family.
If not a Florida Titleblock, coordinate State selection type parameter yes/no check box for the F.Index type only.
F.Grid.6x5 - (number of squares in each title block) TBD talk with Andrew
This is a type parameter that should be turned OFF prior to printing / submitting distribution sets
This note should be added to any progress set of drawings that may be forwarded to a 3rd party consultant. There may be occasions where the client may wish to send out for 3rd party reviews prior to final documents, in which case, we would still have the "Progress Set - Not For Construction" turned on, but the second note turned off.
This Drawing Issuance Does Not Include Sufficient Information to Perform Complete Accessibility and/or Envelope Review
The objects called Border are 4 Invisible lines that have a visibility parameter. They are on by default. This Parameter will be removed in a future phase.
.
MM/DD/YY format
Must be updated for each sheet individually or in bulk
On the Project Browser, select all the sheets.
Once al the sheets are selected, update date to format above
Ajera - Project List > under "Project Name"
Verify with your PM, SD, or Principal
This text should be included on any progress set of drawings that are sent out of the office until we are ready to issue the drawings for plan review.
Note reads: Progress Set - Not For Construction
.
The Issue History is a generic model schedule used to track project deliverables and revisions. While some items will be tied to actual Revit revisions, not all deliverables will require one. This schedule is required on the A1.01 Sheet for all projects.
To get the sheet to appear in the revision set: place a revision cloud on the sheet itself and override its line color to white.
This ensures the revision is captured in the title block and that the sheet is included in the set.
The user must also update the corresponding entry in the Issue History schedule with the revision number (if applicable), date, and description.
1.1. The "Issue History" schedule is located on sheet A1.01 - Title Sheet, Drawing Index & Issue History. The edit the schedule, locate the schedule under "Schedules/Quantities (all)", the schedule is called:
F.A1.Index.GenericModel.IssueHistory.Key
A. Revision Column (F.GenericModel.ScheduleIssueHistory.DeltaTag)
If the deliverable is tied to a formal Revit Revision, input the corresponding revision number here.
Revit revisions must be created using:
View Tab → Sheet Issues/Revisions
Do not create fake or “dummy” revisions.
If the deliverable is not tied to a revision, leave this field blank.
B. Date Column (F.GenericModel.ScheduleIssueHistory.IssueDate)
Enter the deliverable date in this format:
MM/DD/YY
Example: 08/06/25
Please note: This field controls the sort order, so proper formatting is critical.
C. Description Column (F.GenericModel.ScheduleIssueHistory.IssueDescription)
This field is for labeling the deliverable. Please use a list of Forum Standard (drop-down below under "Additional Information")
Always confirm the correct title with your Project Captain, Project Manager, or Studio Director before entering.
The following are shared parameters to the schedule (these are predefined and already loaded into the template):
F.GenericModel.ScheduleIssueHistory.DeltaTag → This will show the revision number (e.g., 1, 2, 3, etc.); again, not all deliverables are revisions and not all deliverables will have revision numbers
F.GenericModel.ScheduleIssueHistory.IssueDate → This will show the deliverable date in MM/DD/YY format
F.GenericModel.ScheduleIssueHistory.IssueDescription → This is where the description or title of the deliverable will go
Forum standard for deliverables within set distributions are as follows:
Schematic Design Set
Design Development Set
IFC Set (Issued for Construction)
GMP Set (Guaranteed Maximum Price)
In the Schedule Properties → Sorting/Grouping tab:
Sort by: F.GenericModel.ScheduleIssueHistory.IssueDate (Ascending)
Uncheck: Itemize Every Instance
Uncheck: Show Title and Show Headers (Appearance tab)
1.1. Sheet Number: Automatically fills when sheets are created.
1.2. Sheet Name: Auto-populates when named. Use Forum-standard nomenclature. If creating a new name, consult your PM.
1.3. Current Revision: Auto-fills with latest revision. Do not use dummy values. See separate section below for consultant workflows.
1.4. F.A1.Index.Sheet.Discipline:
For sheets in the main model: use ARCHITECTURAL SHEETS (all caps).
For sheets linked in consultant models: use STRUCTURAL SHEETS, MECHANICAL SHEETS, ELECTRICAL SHEETS, PLUMBING SHEETS.
This field is hidden in the final schedule.
Fill this in by selecting all relevant sheets and applying the value in bulk from the Sheet List.
1.5. F.A1.Index.Sheet.Sequence:
Controls grouping order within the schedule.
Follow this standard:
0 = Arch sheets before A5
1 = Structural sheets
2 = Arch sheets A5 and after
3 = Plumbing sheets
4 = Mechanical sheets
5 = Electrical sheets
2A.1. Once consultant Revit files have been received and collaberation in the cloud, user will link consultant Revit files:
Open a floor plan view
Go to Manage Tab > Manage Links > Revit Links
Add consultant models
2A.2. In Sheet List Properties > Fields tab:
Check "Include elements in linked files"
Now all consultant sheets will display in the master sheet index.
If consultant Revit models are not received, Forum will provide a discipline-specific Revit model for each consultant (e.g., one for Mechanical, one for Electrical, etc.). Each consultant is responsible for completing specific scope tasks within their assigned model so that the information can update live in our main file when linked.
The consultant must complete the following steps in their own model:
Consultants are responsible for filling out all sheet information within their provided model. This includes:
A. Sheet Number
B. Sheet Name
C. Current Revision
Revisions must be actual Revit revision clouds and not manually typed
Consultants must create their own revision entries (information to be provided by Forum) via:
View Tab → Sheet Issues/Revisions → Add Revision
Place revision clouds and tags directly on their sheets — these will auto-populate in the main model once linked
D. F.A1.Index.Sheet.Discipline
E. F.A1.Index.Sheet.Sequence
Go to View > Schedules > Sheet List
Consultants should see the sheet list autofilled with their own sheets and revisions
No formatting is required; this will display correctly when linked into the main model
For any exceptions or issues, please consult your Production Lead or BIM support.
Note: The text properties of the schedule are not to be changed. The below explainer is for documentation only not part of a workflow.
The “Discipline – Sheets” parameter is used as a grouping pseudo header value for each discipline within a schedule index. By default, this grouping pseudo header inherits the same font size as the "Body Text" style and unfortunately cannot be overridden independently.
Our objective was to make the grouping pseudo header appear larger than the body text. Revit does not allow direct formatting of the grouping pseudo header independently. To work around this limitation, we reversed the intended usage of the Body Text formatting:
Schedule Properties > Appearance: Set the Body Text to use the larger font size you want applied to the grouping pseudo header (e.g., Arial 1/8").
Return to the schedule view and click Unhide All to make the “Discipline – Sheets” column visible.
Select the column header (e.g., the letter "A" above the column).
On the ribbon, use the Font override (Forum standard Text Type/Styles are not listed, only the actual Fonts) and set it to a smaller font (e.g., Arial 3/32") to apply only to the column's body cells.
This override does not affect the grouped pseudo header text (which uses the global Body Text setting), allowing it to remain large.
In essence, we flipped the usage: the "Body Text" defines the size of the grouping pseudo header, while the visible data rows are overridden with a smaller font, creating the appearance of a proper visual hierarchy. This method relies on direct font overrides rather than standard text styles, making it a subtle but effective formatting workaround.
Note: These steps are for documentation purposes only and should already be set in the X Template.
In Appearance tab:
Set Body Text to desired header size (e.g. Arial 1/8")
In the schedule view:
Unhide columns A and B (F.Sheet.Discipline and F.Sheet.Sequence)
Select entire column(s) > Right-click > Font override: set to Arial 3/32"
This results in:
Group headers (Discipline names) appearing larger (via body text)
Sheet numbers/names appearing smaller (via override)
Re-hide columns A and B after formatting.
1.1. Go to View Tab > Schedules > Schedule/Quantities.
1.2. Select Sheets as the category. Name the schedule Sheet List.
1.3. In the Fields tab, add the following fields:
Sheet Number
Sheet Name
Current Revision
F.A1.SheetIndex.Discipline (shared parameter)
F.A1.SheetIndex.Sequence (shared parameter)
2.1. In Schedule Properties > Sorting/Grouping, configure as follows:
Sort by: F.Sheet.Sequence (Ascending)
Then by: F.Sheet.Discipline (Ascending) > Check 'Header'
Then by: Sheet Number (Ascending)
Check: Itemize Every Instance
3.1. In Schedule Properties > Appearance:
Uncheck: Show Title
Uncheck: Show Headers
Check: Show Stripe Rows on Sheets (Optional)
4.1. Drag the Sheet List schedule onto the cover/title sheet (A1.01 - Title Sheet, Drawing Index, & Issue History).
4.2. Click the lightning bolt symbol near center-right of the schedule to split it into multiple columns.
Leave 1/4" space between columns.
4.3. Resize row height:
While on sheet A1.01 - Title Sheet, Drawing Index, & Issue History
Click on schedule > In Properties panel, set:
Resize Rows = All
Row Height = 0' 0 85/256" (approx. 1/3")
4.4. Alignment:
Align the bottoms of the schedules to the second-bottom grid line.
Begin alignment from the rightmost column (end of schedule) and move left.
To maintain consistency across all projects:
5.1. Default column widths:
Sheet Number = 0.5"
Sheet Name = 5.25"
Current Revision = 1.0"
5.2. If any Sheet Name wraps to 2 lines:
Resize Sheet Name column to 5.5"
Resize Current Revision column to 0.75"
Maintain total width of 6.75" across all combinations.
To resize, click on the header of the column (e.g., "B") and use the Resize tool in the top ribbon.
This ensures the discipline headers appear as visual separators without additional titles.
This guide outlines the steps used to create a perspective cover view using a camera (instead of a standard 3D view) to produce a clean, composed image for placement on the A1.01 Cover Sheet. Note: this view has already been established as a standard in the X template and is named F.CoverSheet. The appropriate view template has also been applied. This document serves to explain how that setup was achieved.
Navigate to the main floor plan (ground level).
On the top ribbon, go to:
View tab → 3D View → Camera
Click near the bottom-right corner of the building footprint in plan.
Drag your mouse outward to place the camera at a 45-degree angle from the building’s front-right face.
Pro tip: Place the camera about 100 feet in the X and Y directions from the building corner to get a good composition.
Open the new perspective view generated by your camera.
In the Properties Panel, apply view template:
F.A100.Cover
Note: The scope box will be OFF for this view.
Open A1.01 – Title Sheet, Drawing Index & Issue History
Drag the camera view from the Project Browser onto the sheet. The view is called F.CoverSheet
If the view appears too small or large on the sheet:
Select the placed view
On the top ribbon, under Modify | Viewports, click Size Crop
In the Size Crop window, check Scale (Lock Proportions)
Adjust either width or height based on how the building fits on the sheet
-Brokaw
For a perspective:
use Size Crop window to size the crop to the grid
Use walk to increase the size of the objects in the view
lock the view
Align the bottom of the view with the second row of the cover sheet’s grid
The image should not overlap the "Project Information" and "Issue History" blocks on the right of the sheet
If the sheet index takes up multiple columns or space on the left:
The cover image may be cropped and positioned in the top-right corner of the sheet
Projection Mode: Perspective
Eye Elevation: 5' 6"
Target Elevation: 5' 6"
Far Clip Active: Checked
Far Clip Offset: 500' 0"
Scope Box: None
View Template: F.A100.Cover
A clean, non-distorted, perspective image of your building
Properly scaled to fit approx. 75% of the sheet width
Never overlapping the issue history and project info blocks
Adjusted for layout based on the number of sheet index columns (if sheet schedule needs to take over more of the cover page, the perspective should shift to the top-right corner of the sheet; the image should adjust size based on the sheets)
F.GANN.Title Bar.Index.Non Parametric
Sheet Index - Click for more information
F.Tag.Revision Cloud
Revision Cloud Tag - Click for more information