PIPU
Projects, Innovation & Preneurship UnitFaculty of Medicine - Zagazig University

Lifecycle & approvals

Every stage an idea passes through on its way to a finished project, who may move it, and what they may choose at each step. This is the behaviour the platform actually enforces — the server checks each move, so nothing here is advisory.

WHO

The four ranks

One ladder governs everything. A person's rank decides which moves they may make; the platform compares their rank against the minimum each move requires.

1
Student
Any signed-in member. Owns their own ideas, proposals and work.
2
Committee
Reviews and moves work through the pipeline. Runs projects, tasks and unit assignments, and runs live session attendance — opening check-in, scanning and marking.
3
Supervisor
Everything Committee can do, plus the final word on proposals. Manages accounts. Builds sessions — the programme, agenda and speakers — which the Committee then runs. Organizes rather than attends.
4
Admin
Unconstrained. The only rank that may remove an account.
Two rules that override rank. An owner may always drive their own item through its own steps — submitting, withdrawing, resubmitting, starting work — even as a Student. And a project lead is treated as Committee on their own project, so a student can genuinely run the project they founded.
Sessions split in two. Building a session — creating or editing it, and its agenda items and speakers — is a Supervisor act. Running it on the day — opening the check-in window, showing the rotating code, scanning identity codes and marking attendance — is Committee. A Student registers and checks themselves in; Committee and above organize rather than attend, so they never register.
owner the person whose item it is
note required cannot proceed without a written reason
final the chain ends here
FLOW

The chain

Idea → Proposal → Project → Tasks → Certificate — each step records the one before it, so any finished work traces back to the idea it started as.
Unit assignments are a separate track. They are chores and onboarding given to a member — not part of the idea chain. They are the only thing that is scored. See section 5.
1

Idea

starts at: Submitted · ends at: Approved, Rejected, Withdrawn

The lightest possible entry: a title and a pitch. Anyone may raise one.

Draftonly the author sees it
Submit →SubmittedownerHands it to the Committee.
Submittedwaiting on the Committee
Start review →Under ReviewCommitteePicks it up.
Pull back →DraftownerTake it back to keep editing.
Withdraw →Withdrawnownerfinal
Under Reviewthe Committee decides
Approve →ApprovedCommitteeReady to become a proposal.
Reject →RejectedCommitteenote required final
Send back →SubmittedCommitteeReturn it to the queue.
Withdraw →Withdrawnownerfinal
Approvedrests here
No further movesdoneA proposal is raised from it separately, which records the idea it came from.
2

Proposal

the only stage a Supervisor must sign off

The serious write-up: problem, solution, plan. It carries two review rounds, and the final word belongs to a Supervisor — not the Committee.

Draftonly the author sees it
Submit →Submittedowner—
Submittedwaiting on the Committee
Start review →Initial ReviewCommitteeFirst pass.
Pull back →Draftowner—
Withdraw →Withdrawnownerfinal
Initial Reviewthe Committee triages
Advance →Committee ReviewCommitteeSend it to the full review.
Request changes →Changes RequestedCommitteenote required
Reject →RejectedCommitteenote required final — the Committee may reject early, before it reaches a Supervisor.
Committee Reviewthe Supervisor decides
Approve →ApprovedSupervisorThe Committee cannot do this. Approval unlocks becoming a project.
Reject →RejectedSupervisornote required final
Request changes →Changes RequestedCommitteenote required — the Committee can still send it back.
Changes Requestedback with the author
Resubmit →ResubmittedownerAfter addressing the notes.
Withdraw →Withdrawnownerfinal
Resubmittedstraight back to full review
Advance →Committee ReviewCommitteeSkips the first pass — it has been seen already.
Request changes →Changes RequestedCommitteenote required
Reject →RejectedSupervisornote required final
3

Project

starts at: Planning · ends at: Archived, Cancelled

Raised from an approved proposal (or standalone). Whoever creates it becomes the lead and is treated as Committee on that project — but not for the one step that ends it.

Planningthe lead sets up
Start →Activelead Committee—
Cancel →Cancelledlead Committeenote required final
Activework is happening
Put on hold →On Holdlead Committee—
Move to review →In Reviewlead CommitteeDeclare it finished and ask for sign-off.
Cancel →CancelledCommitteenote required final — the lead cannot cancel once active.
On Holdpaused
Resume →Activelead Committee—
Cancel →CancelledCommitteenote required final
In Reviewthe Committee signs off
Mark complete →CompletedCommitteeThe lead cannot complete their own project — this is the one step their lead status does not cover.
Back to active →Activelead CommitteeMore work needed.
Completeddone
Archive →ArchivedCommitteefinal
Reopen →ActiveCommitteeCompletion is reversible until archived.
4

Task

inside a project · approved or sent back — never scored

A unit of work inside a project, given to someone on the team. Submitting is versioned: each submission is kept, and the reviewer is shown what changed since they last looked.

To Donot yet given to anyone
Assign →Assignedlead CommitteeThe person must be on the project team.
Start →In Progresslead Committee—
Cancel →Cancelledlead Committeefinal
Assignedwith the assignee
Start →In Progressassignee—
Mark as blocked →BlockedassigneeSomething is in the way.
Cancel →Cancelledlead Committeefinal
In Progressbeing worked on
Submit work →SubmittedassigneeNote, link and files. Each submit is a new version.
Mark as blocked →Blockedassignee—
Cancel →Cancelledlead Committeefinal
Submittedwaiting on a reviewer
Start review →In Reviewlead Committee—
Take it back →In ProgressassigneeWithdraw to keep working.
In Reviewthe reviewer decides
Approve →Approvedlead Committeefinal — counts towards the person's portfolio.
Request changes →Changes Requestedlead Committeenote required
What “Blocked” means. The assignee says the work cannot move for a reason outside their hands — waiting on a part, a permission, another team. It is theirs to set and theirs to lift. It exists so stalled work is visibly stalled instead of sitting in “In progress” looking healthy; the dashboard counts it as needing attention.
Changes Requested · Blockedback with the assignee
Resume →In Progressassignee—
Cancel →Cancelledlead Committeefinal
5

Unit assignment

separate track · the only thing that is scored

Given directly to a member — recruit onboarding, a chore, a piece of training. It has no project and no place in the idea chain. Unlike a task, it ends in a verdict and a score out of 100.

An assignment can be a form. It may carry questions — short text, paragraph, number, choose-one, choose-many, file upload — each optionally required. Leave the questions empty and it behaves as it always did: a note, a link and files.
Choice questions can mark themselves. Give a choose-one or choose-many question a correct answer and marks, and the platform scores it the moment it is handed in. Text and file answers are never auto-marked and count toward nothing — a person still sets the real score, pre-filled from the automatic mark. The answer key is never sent to the person answering, and a key on a text question is refused, because free text cannot mark itself.
Questions freeze once anyone answers. Answers are stored against each question, so re-cutting the form afterwards would silently re-point real answers. Edit the questions before the first hand-in, not after.
Unassignednobody holds it yet
Assign →AssignedCommittee—
Assignedwith the member
Start →In Progressassignee—
Unassign →UnassignedCommitteeGive it to someone else.
In Progress · Submittedbeing done, then handed in
Submit →SubmittedassigneeVersioned. Answers are checked against the questions here, not just in the browser.
Start evaluating →Being MarkedCommittee—
Take it back →In Progressassignee if allowedEach assignment decides. A quiz can lock on hand-in; an onboarding form can stay editable. Committee+ can always send it back either way.
Being Markedthe Committee marks it
Pass →PassedCommitteefinal — with a score out of 100, pre-filled from the automatic mark where the questions carried an answer key.
Needs rework →Needs ReworkCommitteenote required — goes back to the member.
Fail →FailedCommitteenote required final
Needs Reworkback with the member
Resume →In ProgressassigneeThen submit a new version.
ALSO

Things worth knowing

Every move is recorded. Each item keeps a history of who moved it, from what to what, when, and the note they left. That history is what the reviewer's "what changed since I last looked" view is built from.
Notes are not optional where they are marked. Rejecting, requesting changes, failing or cancelling all demand a written reason. The platform refuses the move without one — so nobody is ever told "no" without being told why.
Nothing is deleted. Withdrawn, rejected and cancelled items stay on the record with their history intact. Approved work follows the person into their portfolio.