SchemeFlow Help

Best Practices ​

Use these best practices to get the most out of SchemeFlow and avoid common issues.

1. Always Update Maps Before Issuing ​

Changes made in the map editor are not applied to your document until you click Update.

Before sharing or issuing a report, always do a final pass to ensure all maps have been updated.

Why this matters

Prevents outdated or incorrect maps appearing in issued documents.

2. Save Company Styles for Reuse ​

Use Company Styles to save the map's layout, data layers, layer visibility, and map styling.

Why this matters

Keeps the map configuration available for reuse.

3. Don't Edit or Remove SchemeFlow Tags ​

SchemeFlow templates contain tags and placeholders that control:

  • Map insertion
  • Dynamic content
  • Sidebar interactions

These should not be edited or removed.

Why this matters

Editing tags can cause maps or content controls to stop working.

4. Use the SchemeFlow Sidebar as Your Control Centre ​

Use the SchemeFlow sidebar to manage maps, templates, and reviews while working in Word.

Keep the sidebar open to ensure actions like insert, update, and save are applied correctly.

Why this matters

Reduces mistakes and keeps your workflow predictable.

5. Position Your Cursor Carefully When Inserting Maps ​

Maps are inserted exactly where your cursor is placed in the document.

Before clicking Insert, always click into the correct paragraph or section.

Why this matters

Prevents maps appearing in the wrong part of the report.

6. Use Layers Strategically ​

Use separate layers for different types of information:

  • Points
  • Lines
  • Polygons
  • Buffer zones
  • Data layers

Rename layers clearly (e.g. Site Access, Study Area, Amenities).

Why this matters

Keeps maps organized and easier to edit, update, and reuse.

7. Use SVGs for Custom Icons and North Arrows ​

Where possible, upload SVG files instead of PNGs for icons and north arrows.

SVGs scale cleanly and remain sharp at any size.

Why this matters

Improves print quality and presentation clarity.

8. Run Reviews Before Sharing ​

Before internal or client issue, run the relevant Reviews for:

  • Inconsistencies
  • Missing information
  • Reference or clarity issues

Address any flagged issues and run the review again if needed.

Why this matters

Reduces QA cycles and avoids avoidable errors.

9. Save Templates Only from the Correct Document ​

When editing or uploading templates:

  • Ensure the correct Word document is open
  • Confirm the SchemeFlow sidebar is visible
  • Then click Save Template

Why this matters

Prevents accidentally saving the wrong document or overwriting templates.