Job Filing Process Notes

Job Filing Process Overview

  • Creating a Job Filing
    • Initiation through portal access.
    • Choosing relevant job types based on project requirements.
    • User authentication and access to the job filing module.

Steps to Create an Electrical Job Filing

  • 1. Logging In
    • User logs in with credentials specific to the job filing system.
  • 2. Navigate to Job Filing
    • Selecting the relevant electrical job filing option:
    • Clicked on job test your filing
    • Selecting alteration, indicating the type of job intended.
  • 3. Enter Job Details
    • Input basic job filing details:
    • Physical address or cross street for job location.
    • Job description, start date, and end date.
    • Save job application once minimal fields are filled.
  • 4. Applicant Information
    • Option to enter the owner's information or select previous applicant as owner.
    • Choices regarding owner types influence processing.

Fee Calculation Explanation

  • 1. New Work and Legalization Fees
    • User selects the building type for the job.
    • Specific fees for new work filings indicated (example: $40 filing fee).
  • 2. Parts Fee Calculation
    • Calculated based on the job scope.
    • Example calculation:
    • If one item is entered with a price of $8.96, parts fee = $12 × $8.96.

Issues and Bug Reports in the System

  • 1. Reported Bugs
    • Issues with the total fee calculations (e.g., $1.86 expected but incorrectly showing $2.98).
  • 2. Payment Calculations
    • Minimum payment structures enforced:
    • Users are required to pay at least a certain amount ($1.30) regardless of calculated fees.
  • 3. Fee Exemptions
    • Specific owner types (e.g., NYC agency) result in exempt fees.
    • Required documents need to be uploaded for exemption claims.

Post Approval Amendment (PA)

  • Adding Scope After Initial Filing
    • Process for updating initial job filings with additional scope using PA.
    • Limited editing capabilities observed in PA (e.g., some fields disabled).
  • Auto-Approve Feature
    • PAs don’t require a workflow; approvals are automatic upon submission.

Merging Changes from Post Approval Amendments

  • 1. Expected Merging Behavior
    • Changes made in PA should reflect in the original job filing after approval.
    • Example scenarios discussed where expected fields didn't merge correctly.
  • 2. Documenting Issues with Merging
    • Certain sections specifically highlighted for lacking merge functionality (e.g., electrical job categories not updating).

Validation and System Integrity Checks

  • 1. Need for CRM Verification
    • Validation of these issues needing access to the CRM side for verification.
    • Documentation and review expected from designated team members.
  • 2. Identify Specific Fields Affected by Bugs
    • Listing out specific fields that show inconsistencies or bugs to help in code troubleshooting.

Conclusion

  • Final remarks on the ongoing nature of the job filing and documentation process in the system, emphasizing error tracking and effective communication among team members for resolution.