Grain - Fact or Dimension

I am designing a star schema for a registration form process for property with the following business objective
To analyze the number of forms generated, number of forms processed, number of days to process a form , registration status (valid,invalid,not responded) of the form
The grain of the system is  a registration form for every property to register.
Following is the design of the star schema I proposed

dim_reg
_______
reg_key
reg_id
reg_generate_date
reg_submit_date
reg_form_intake_start_date
reg_form_intake_end_date
reg_processed_by
...... 20 other attributes

dim_property
____________
property_key
property_id
property_address
property_city
property_state
property_zip
....other 10 attributes

dim_reg_form_type
_________________
reg_form_type_key
reg_form_type_id
reg_form_type_name

dim_generate_date
_________________
date_key
date_value
day_number
month_name
year
....other attributes

fact_reg
_________
reg_key
property_key
reg_form_type_key
date_key
number_of_form_received (default to 1)
number_of_days_to_process
number_of_form_processed (1 or 0)
...other facts

For every record in dim_reg a corresponding record exist in fact_reg i.e., its a one to one relationship

My question is Is this the right approach to model or can I move all the attributes from dim_reg to fact_reg

Do you only load processed forms? That is, do you ever need to update the number of days to process metric? If not, this design is fine. If you do, then you should adjust your design to an accumulating snapshot fact table.

We load all the forms (processed and not processed).

Thanks for the reply