KNOWLEDGE BASE ARTICLE

Behavior Management Plugin: Can a Submitted Behavior Log Be Converted Into a Referral?

Puredata Support Updated

 

Overview

In the Behavior Management Plugin, teachers may have the option to create a referral when submitting a behavior log entry. This is controlled at the time the behavior log is created.

If a teacher submits a behavior log but forgets to enable the Create Referral option, the existing log entry cannot be converted into a referral afterward.


Issue

A teacher created and submitted a behavior log entry but did not toggle the Create Referral option before submission.

After the log entry was created, an administrator attempted to edit the log entry and update the Admin Action field to a referral-related option, such as:

  • Referral to Counselor
  • Referral to Intervention Program

However, the log entry still did not appear under Referrals.


Can an Existing Behavior Log Be Turned Into a Referral?

No.

Once a behavior log entry has been created and submitted without the referral option enabled, a referral cannot be added to that existing log entry afterward.

Changing the Admin Action field after submission does not create a referral record and does not move the log entry into the Referrals area.


Why This Happens

The referral is created only when the behavior log is initially submitted with the Create Referral option enabled.

If the referral option is not enabled at the time of submission, the system creates only the behavior log entry. It does not create the associated referral record in the background.

Because the referral record was not created during the original submission, updating the log entry afterward does not generate a new referral.


What Administrators Can Do

There is currently no standard process to convert an existing behavior log entry into a referral after it has already been submitted.

If a teacher forgot to create the referral, the school should follow its internal process for handling the situation.

Common options may include:

  • The teacher notifies the appropriate school administrator.
  • The administrator reviews the existing behavior log.
  • The school determines whether follow-up action is needed outside the referral workflow.
  • If the school requires the incident to exist as a referral, the original log may need to be deleted and re-submitted correctly, depending on the school’s internal policy and data-retention expectations.

Important: Do not delete and re-submit behavior records unless the school confirms this is acceptable for its discipline documentation process.


Recommended Workflow

If a behavior incident should be submitted as a referral, the teacher should enable Create Referral before submitting the behavior log.

Teacher Workflow

  1. Create the behavior log entry.
  2. Complete the required incident details.
  3. Enable Create Referral if the incident should route through the referral workflow.
  4. Submit the behavior log.

Administrator Workflow

If a teacher reports that they forgot to create a referral:

  1. Review the submitted behavior log.
  2. Confirm whether a referral is required.
  3. Follow the school’s internal process for referral follow-up.
  4. If needed, ask the teacher or administrator to re-submit the incident correctly, based on local policy.
  5. Document any internal follow-up action.

What Does Not Work

The following actions will not convert a behavior log into a referral:

  • Editing the existing behavior log after submission
  • Changing the Admin Action field to a referral-related value
  • Updating the log entry through the admin portal
  • Saving the behavior log again after it was already submitted

These changes may update the log entry details, but they do not create the missing referral record.


Best Practices

  • Remind teachers to use Create Referral at the time of submission when a referral is required.
  • Include referral submission steps in teacher training materials.
  • Establish an internal school process for cases where a teacher forgets to create a referral.
  • Avoid deleting behavior logs unless the school has approved that process.
  • Review behavior logs regularly to identify incidents that may require administrative follow-up.
  • Document any manual follow-up outside the referral workflow.

Summary

A behavior log entry cannot be converted into a referral after it has been submitted if the Create Referral option was not enabled at the time of creation.

Changing the Admin Action field does not create a referral and will not cause the log entry to appear under Referrals.

If a referral was missed, the school should handle the situation through its internal process. If the school requires the incident to appear as a referral, the log may need to be deleted and re-submitted correctly, subject to the school’s documentation and data-retention policies.

Have more questions?

Submit a request and include screenshots, school name, and the page or process where the issue occurs.

Submit a request