An RFI type is a kind of question the project raises, together with the defaults an RFI of that kind should start from. It saves retyping the same manager, the same discipline and the same due window on every RFI.
This topic includes:
What a type carries
| Default | Effect on a new RFI |
|---|---|
| Discipline | Fills the RFI's discipline. |
| Priority | Low, Normal or High. |
| Cost impact | Yes, no or unknown. |
| Schedule impact | Yes, no or unknown. |
| Due in days | The due date is set that many calendar days from the day the RFI is raised. |
| Manager | Fills the manager, and the ball-in-court if nobody else is named. |
| Distribution | The people this kind of RFI keeps informed. |
Note: the due date is held as a number of days, not a fixed date. A date on a template goes stale the moment it passes; a window does not.
The default types
A new project starts with Design clarification, Site condition, Specification conflict, Substitution request and Coordination. Rename them, add your own, or set one inactive to stop it being offered.
Edit them under Project Admin; only project and account administrators can change the catalogue.
How defaults are applied
Anything you state wins. The type fills only what you left blank — so choosing a type never overwrites a due date or a manager you set deliberately.