You are here: Firm Author Help > Content Management > Summary of update methods

Summary of Update Methods

You want to select the update method that fits your firm standards. Listed are the various cases and how each of the update method will function during the check for updates process. For some cases, each method will act the same way, while some do not – consider the differences when deciding on the update method for your engagement teams. Refer to each item below for details on how the update method is applied under each firm option.

For each of the cases involving a procedure being updated, note that the Version of each procedure must be updated for each modification.

Note:

These examples are all procedures that have not changed ownership when firm author modified the procedure. When you modify a procedure you do not own, you will be asked if you want to change ownership of the procedure. When you change ownership, consider it to be two procedures – the original procedure is made unavailable to the user (hence it will be deleted during check for updates) and a new procedure is created by you that the user will have to add to replace the original procedure. The firm author is responsible for notifying the engagement teams of this change.

Modifications by the firm author to an existing procedure owned by the firm author

Case	User interactively updates individual documents	Update all existing procedures and document properties	Update all existing procedures, add new procedures
Updates made by the author/firm to an existing procedure. The firm marks the procedure as Required or procedure was already set as Required.	Procedure is always updated at the engagement level as firm has marked it as Required.
Firm author makes modifications to an existing Required procedure.	Procedure shows as “Out of Date” when the check for updates is selected at the engagement level. User can elect to update as required or keep customizations previously made and modify accordingly		Procedure is updated automatically at the engagement level
Updates made by the author/firm to an existing procedure. The procedure is NOT Required. No modifications were made to the original procedure at the engagement level.	In the client file update process, if the user does not use the Procedures dialog to indicate that this document is to be ignored, all procedures in the document are updated. If the document is not updated as part of the client file update process, the procedure shows as “Out of Date” when the check for updates is selected at the engagement level. User can elect to update as required or keep customizations previously made and modify accordingly.	Procedure is updated automatically at the engagement level.
Updates made by the author/firm to an existing procedure. The procedure is NOT Required. Modifications were made to the original procedure at the engagement level.	In the client file update process, if the user does not use the Procedures dialog to indicate that this document is to be ignored, all procedures in the document are updated. Procedure shows as “Out of Date” when the check for updates is selected at the engagement level. User can elect to update as required or keep customizations previously made and modify accordingly.

New procedure added by the firm author that does not currently exist

Case

User interactively updates individual documents

Update all existing procedures and document properties

Update all existing procedures, add new procedures

New procedures added by the author/firm.

The firm marks the procedure as Required

Procedure is always added at the engagement level as firm has marked it as Required.

New procedures added by the author/firm.

The procedure is NOT Required.

Added to firm content library but is not automatically updated to the engagement.
Dialog will appear to select procedures from content library. Click on each procedure to preview content before selecting.

Procedure is added automatically at the engagement level.

Firm author deletes the procedure permanently from the content library and from the standard work program/checklist

Case

User interactively updates individual documents

Update all existing procedures and document properties

Update all existing procedures, add new procedures

Required procedures are deleted by the author/firm from the content library and the document.

No modifications were made to the original procedure at the engagement level

Procedure status highlights that procedure is removed from content library.

Required procedures deleted by the author/firm from the content library and the document.

Modifications were made to the original procedure at the engagement level.

Procedure status highlights that procedure is removed from content library.

Procedures marked as NOT Required are deleted by the author/firm from the content library and the document.

No modifications were made to the original procedure at the engagement level.

Procedure status highlights that procedure is removed from content library.

Procedures marked as NOT Required are deleted by the author/firm from the content library and the document.

Modifications were made to the original procedure at the engagement level.

Procedure status highlights that procedure is removed from content library. Delete button is available first time in check for updates. After the first time, the procedure becomes a user procedure.

Firm author deletes the procedure from the standard work program/checklist

Case	User interactively updates individual documents	Update all existing procedures and document properties	Update all existing procedures, add new procedures
Procedures deleted by the author/firm from the document.	Procedures remain in the engagement document.
Procedure deleted from the content library. Procedure not included in the document but removed from content library	Procedures can be deleted from an engagement file. No automatic notification is available. Firms must ensure users are advised if this situation occurs.

New procedure is added to a work program or checklist at the engagement level

Case	User interactively updates individual documents	Update all existing procedures and document properties	Update all existing procedures, add new procedures
Procedures added at the engagement level. Note procedure did not exist in content library.	Engagement procedure is retained on update process.

Procedure is deleted from a work program or checklist at the engagement level

Case	User interactively updates individual documents	Update all existing procedures and document properties	Update all existing procedures, add new procedures
The procedure is set as Required.	Required procedures can never be deleted at the engagement level.

Procedures or document signed off as completed

Case	Update individual procedures manually	Update all existing procedures and document properties	Update all existing procedures, add new procedures
Procedure is signed off as completed.	User can elect to remove the sign off on the procedure prior to the update process. Update depends on state of procedure as outlined in Cases 1-6.	User can elect to remove the sign off on the procedure prior to the update process. Update depends on state of procedure as outlined in Cases 1-6.	User can elect to remove the sign off on the procedure prior to the update process. Update depends on state of procedure as outlined in Cases 1-6.
Entire document is signed off as completed.	The Check for updates options is disabled if the document is signed off as completed.	The Check for updates options is disabled if the document is signed off as completed.	The Check for updates options is disabled if the document is signed off as completed.

Procedure is made unavailable by the firm author

Case	Update individual procedures manually	Update all existing procedures and document properties	Update all existing procedures, add new procedures
Procedure is made unavailable by the firm author	Procedure will appear in the client file as Removed from Content Library
Procedure is included in the document at the engagement level	Procedure will be treated as a procedure engagement team has added, if they decide to keep the procedure

Document properties are updated by the firm author

Case	Update individual procedures manually	Update all existing procedures and document properties	Update all existing procedures, add new procedures
Document properties are updated by the firm author	Document properties are updated in each work program or checklist when Check for Updates is performed	Document properties are automatically updated in the client file

This online help system applies to all CaseWare Audit, Review, and Compilation products. Not all features are available in all products.

Summary of Update Methods

Cookie Notice