In this context, "flag" is an informal term used to describe a custom field added to a record, typically a Boolean field (true/false) that acts as an indicator for a specific condition or status.

For your use case, the field would be added to the project table and could be named "Has Overallocated Resource" for clarity, or something shorter like "Overallocated Resources". This field would be set by the scheduled job, and if its value is true, your message would be displayed on the project form.

That said, I would probably skip the custom field and simply rely on the notification to start. Managing the flag—particularly unsetting it when resource allocations change—adds unnecessary complexity, especially if you don’t want to wait for the next job run (which could result in the flag indicating overallocation for days after the issue has already been addressed). You could always add the flag later if project managers prefer to see something on the project itself.