Smart Project Copy

Use Smart Project Copy to preserve and transfer customized specification content from one project to another.

Smart Project Copy manages customized paragraph content through a combination of best practice instances and sync states. These mechanisms give you control over when to share changes and when to update content in other projects.

With Smart Project Copy, you can:

• Sync to save your user modifications in a paragraph as part of a best practice instance.
• Sync to load the current content in a best practice into a paragraph added through best practice automation.
• Tag a user-added paragraph as best practice.

This feature is currently available only for paragraphs. Smart project copy works with both project parameter best practices () and global best practices ().

Understanding Sync States

Smart Project Copy uses sync states to indicate whether a paragraph's content matches its associated best practice instance.

• A synced state means the paragraph content and best practice instance are aligned.
• An out‑of‑sync state means the content has diverged and requires an explicit action to either share changes or load updates.

Sync states do not force updates. Instead, they provide visibility and control over when shared content is refreshed.

Type	Synched or Default Tag	Out-of-Sync Tag
Project Parameter Best Practice
Global Best Practice

Saving Modifications to Best Practice Instance

With basic best practice tagging, tagging a baseline paragraph creates a best practice instance that reflects the paragraph content at the time of tagging. Subsequent changes to that paragraph are not shared with other projects.

Smart Project Copy lets you save later changes and sync them with the best practice instance. When you modify the source paragraph of the best practice, its best practice tag (/) changes to an out‑of‑sync state ( / ). An out‑of‑sync state indicates that the paragraph content differs from the best practice instance and requires you to sync content to share changes.

For the source paragraph of the best practice instance, you can choose whether to:

• Sync the paragraph changes to the best practice instance and making the modified content the new shared version. To do so, click the out‑of‑sync tag.
• Keep the best practice instance unchanged and allow project‑specific changes to remain local.

This feature enables you to decision ensures that updates are shared intentionally and that further changes in one project do not automatically affect others.

Loading Modifications from the Best Practice Instance

When you create an eligible new project and add the required parent content, Specpoint applies best practices by adding the current version of each tagged best practice paragraph. These paragraphs initially display the synced best practice tag (/).

If the source best practice paragraph is later modified and synced to the best practice instance, the corresponding paragraph's tags in the new project changes to an out-of-sync state ( / ). An out‑of‑sync state indicates that the project's paragraph differs from the best practice instance and does not update automatically.

Clicking the out‑of‑sync tag allows you to load the updated best practice content into the project. You can also choose to retain the project's current version of the content, allowing you to preserve any project-specific changes.