Having an agreement between developers and the build team will keep everyone's expectations in check.

Below should be the minimum of any document.

You need at least these items:
What output is expected?

What setup is needed?
Configuration:
Pre-requisites:

What input will be used?
VCS: Branch? Modules?

Perforce Knowledge Base: Branching work in progress shows how you branch work in progress.

Comments are mine. The commands are from Perforce with no known edits.
When I see strings hard coded, I want to abstract them into variables.
Maybe,
VCFOLDER=//depot
PROJECT=/project
LABELTAG=home
STREAMIN= < could be main/qa/QA a defined branch point.
STREAMOUT=work-project
LOCALIN=c:\app-src\project
LOCALOUT=c:\app-src\work-project

So this

p4 integ -v //depot/project/...@home //depot/work-project/...
xcopy/s/i $LOCALIN $LOCALOUT c:\app-src\work-project

would be

p4 integ -v $VCFOLDER$PROJECT...@$LABELTAG $VCFOLDER$STREAMOUT...
xcopy/s/i c:\app-src\project c:\app-src\work-project

REM Notice the use of the @home.
REM work-project is a new VCS folder.

p4 integ -v //depot/project/...@home //depot/work-project/...