Templates and organizations

A template holds the reusable setup for a document type. Its code and name make it identifiable; its effective dates and policy reference help a template manager decide which version belongs to a packet. Each template belongs to an organization. A packet points to its selected definition, so a later review can see which setup governed that revision. Mappings between source and target fields can be kept with the definition when information comes from another system.

• Organization. Keep people, templates and packets attached to the right entity.
• Definition. Use the template code and effective period to choose the working setup.
• Mapping. Review source and target fields before relying on transferred values.

Agree who maintains templates and how a new policy reference takes effect. A template marked active should still be checked against its effective dates for the packet in hand. Define the source of signer identities and how the signing order is reviewed. If a connected system supplies document data, agree the field mapping and version with its owner before the first packet is prepared.

A legal team updates the signing instructions for a recurring supplier form. The template manager records the new definition and effective period for the appropriate organization. A packet owner preparing a form chooses that definition and checks the signer order. The manager checks the definition linked to the earlier packet before changing its signing instructions. When a source field changes, the manager examines the mapping instead of silently treating a different value as the same data. A reviewer can then inspect the packet revision and policy reference together.

The handoff should be checked on a real packet, not just on a status label. Open the linked record and compare the people, revision and provider evidence behind the decision. If the record is returned or uncertain, keep it visible to the person responsible for the next action. The next team should be able to explain what was received, what was accepted and why the packet changed state.

When a definition changes, check its organization, effective dates and policy reference before using it on a new packet. The packet owner should also compare the signer identity and order with the intended document. If a mapping supplies a value from another source, the template manager checks its source field, target field and transform rule against the current input. The review decision then belongs to the packet revision that used that definition. For an older packet, inspect its linked definition and review record before assuming the current template describes its original instructions.

• Signing Template Register — Active definitions with effective dates and policy references.
• Prepared Packets — Prepared revisions linked to their chosen definitions.

Follow packet preparation and signer verification.