I am a tad confused...

How are you currently pulling the audit owner into your main list?  I assume you have a dropdown of audits and then based on the selected audit you get the owner - but how?  What data types are they?

Yeah. So I have a Column called Audit Type on my main list. I copied this column into my lookup column (which is also a drop down column) that then looks at an external list that also has an Audit Type column and then another column for Audit Owner. It brings over audit owner. These are text fields.

I'm also a tad confused. Why do you need to move something from a current list to a past due date list? Doing this seems to create an awful lot of overhead, when you could simply create a column as an indicator that that item is past it's due date, and then create views to separate out your current items from your past due date items.

These past due items move to a separate list so that the main list can be ready for review the next day. My groups have to review every single day so if someone doesn't review for 3 days the past due will have all 3 days in it to review AND the main list will be ready for the 4th day review.

having a little play in a bit ok will see where I get to.  luckily I still have my "testforjosh" lists

OK, I'm still not sure I understand this process. The workflow will automate marking your past due dates, so they will always be hidden from your main view, what happens to the items once they are past their due dates? Will those due dates get changed once a "review" takes place and they'll go back to the main list till their next due date? Or do they effectively become archived, never to be used again?

So, the site workflow moves the past due items to the past due list (based on the due date being past due) and resets the due date on the main list to next day. Once on the past due, another workflow runs as the reviewer completes, it archives to an archive list deletes off past due permanently. The purpose of doing this is to not interrupt the reviewer from ever doing that day's review that is due. Its less confusing for the end use to have separate lists to go to instead of views.

OK Josh so here is what I have, and please correct me if I have got it wrong.

Custom List:

Name = luAudits

Title column used for audit name

additional column called "Audit Owner Text" as single line of text.

TestForJosh list (same as your main list)

Column called Audit Type configured as follows:

PastDueList (same as your overdue list)

Column called Audit Type configured as follows:

so both of my lists have the corresponding look up to the audit owner text being pulled through.  Therefore when I create item in PastDueList from TestForJosh I only need to pass the Audit Type value.  the other one works all by itself.

Is that what you have?

Josh Shutts wrote: Also, I mentioned above that I could not figure out how to lookup using a column on the same lit I am running the lookup from. Is this possible? I can only figure out how to lookup to an external list. Can this be done? I really don't know what you mean by this though if I am honest??!!

You got it! That's exactly how I have everything. Do lookups affect workflows in any way?

Not that I've been able to replicate. What exactly is going wrong?

I think he means a self referencing Lookup, so the lookup column points to a column within it's own list rather than another list.

This can be done OOTB with SharePoint, couldn't confirm with Nintex forms myself as I don't have the product available to me currently.