License Applications

License Applications

Purpose and when to use this record

BriskReceive storesand review a business’s request for a municipal license applicationsbefore asapproval, partrejection, ofor conversion to an issued license.

At a glance

• Identify it by: Application Number, Status, Submitted Date, Requested Effective Date, and Review Due Date.

• Check its business context: Account, License Type, and Reviewed By.

• Why care: Names, periods, classifications, due dates, status, charges, and payments form an official account history. Correct them from the municipalsupporting module.filing, Thisapplication, generatedreceipt, referenceor ordinance.

• Why care: Status communicates workflow progress to other staff. Change it only when the underlying work, approval, payment, or handoff has actually occurred.

Before you begin

You need the Brisk permission for the action you are taking on license applications. If a Create, Edit, or Delete control is awaitingabsent, workflowdo review.not work around it with another user’s account; ask an administrator to review your role.

Have valid Account, and License Type records ready first. Those selections determine where this License Application belongs and which later screens can find it.

Create a recordLicense Application

TheCreate evidencea packetLicense identifiesApplication only after confirming that the viewsource document or operational event has not already been entered.

1. Select the business context first: Account, License Type, and sourceReviewed locationBy.

2. Enter the required identifying and operational values: Account, License Type, and Application Number.

3. Review Status deliberately; these choices control availability or workflow rather than merely describing the record.

4. Save the License Application, then confirm Application Number, Status, Submitted Date, Requested Effective Date, and Review Due Date on its detail page before continuing.

After saving: Complete the required review and fees before approval; an approved application should lead to the correct issued license rather than a duplicate business record.

Delete a License Application

Delete this License Application only when it was entered by mistake and no downstream history depends on it. Use a reversal, void, credit, counter-adjustment, or status correction for thisa action.real Confirmevent user-facingthat stepslater beforechanged.

approving

Before confirming, check for related Compliance Tasks, Licenses, and Municipal Charges. Brisk may refuse deletion when another record depends on this page.one; resolve the duplicate or use the supported correction workflow instead of breaking the trail.

On the confirmation page, verify Application Number, Status, Submitted Date, Requested Effective Date, and Review Due Date. After confirmation, return to the License Applications list and make sure only the intended License Application was removed.

ViewReview recordLicense Application details

The evidence packet identifiesUse the viewdetail page as the shared record of what this License Application currently means. Verify Status, Submitted Date, Requested Effective Date, and sourceReview locationDue Date before relying on it for a decision.

Follow Account, License Type, and Reviewed By to determine whether the issue is on this action.License ConfirmApplication user-facingor stepson one of those linked records.

Next check: Complete the required review and fees before approvingapproval; an approved application should lead to the correct issued license rather than a duplicate business record.

Edit an existing License Application

Edit this License Application to correct or complete the same source document or operational event; use the supported reversal or follow-up workflow when the business event itself changed.

1. Open the detail page. Compare Account, License Type, and Reviewed By with the supporting document or approved request.

2. Recheck Account, Status, Submitted Date, Requested Effective Date, and Review Due Date. These values are most likely to change license, compliance, filing, charge, payment, and official account history.

3. Save the change, return to the list, and confirm that the License Application now appears under the expected Status.

After the change: Complete the required review and fees before approval; an approved application should lead to the correct issued license rather than a duplicate business record.

Find and review recordslicense applications

The evidence packet identifiesUse the viewLicense Applications list to find the correct record before opening or changing it. Compare Application Number, Status, Submitted Date, Requested Effective Date, and sourceReview locationDue Date. Records with similar names or numbers can still belong to different Account, License Type, and Reviewed By.

• The initial order emphasizes Submitted Date, and Id. Select a column heading when you need a different comparison.

Open the License Application whose Application Number, Status, Submitted Date, Requested Effective Date, and Review Due Date match the task. If it is missing, clear the list filters and recheck Status rather than creating a replacement immediately.

Fields and business rules

Brisk stores 9 user-relevant fields for this action.License ConfirmApplication, user-facingincluding steps3 beforelinked-record approvingselections and 1 controlled-choice field. Create and edit screens may hide calculated or workflow-managed values from this page.full reference.

Editanexistingrecord

sourcelocation user-facingstepsbeforeapproving location user-facingsteps

Field	Required	What it controls
Account	Yes	The evidenceaccount packetassociated identifieswith thethis viewlicense andapplication.
License Type	Yes	The license type associated with this license application.
Application Number	Yes	The application number recorded for this action.license Confirmapplication.
Status	No	Current status of this page. license Deleteapplication. aAvailable record values: Draft, Submitted, In Review, Approved, Denied, Converted.
Submitted Date	No	Date recorded for submitted date on this license application.
Requested Effective Date	No	Date recorded for requested effective date on this license application.
Review Due Date	No	Date recorded for review due date on this license application.
Reviewed By	No	The evidencereviewed packetby identifiesassociated thewith viewthis andlicense sourceapplication.
Memo	No	The memo recorded for this action.license Confirmapplication.

What happens next

Complete the required review and fees before approvingapproval; thisan approved application should lead to the correct issued license rather than a duplicate business record.

Common mistakes and troubleshooting

• The record will not save: Recheck Account, License Type, and Application Number and any message beside the field. A required related record may also be inactive or unavailable to your role.

• The record saved but is not available where expected: Recheck Status, then clear the filters on the destination list. A saved record can still be inactive, unpublished, locked, unapproved, or in the wrong workflow state.

• The values look right but the result is wrong: Open Account, License Type, and Reviewed By from the detail page. Correct the specific relationship that is wrong instead of forcing a total or status to compensate for it.