Weekly submissions

A weekly submission gives a manager one dated record to review. It names the worker, the week beginning date, the organization and the parent work package. Hours and revision travel with the status, so the person making the decision can tell which submitted version is in front of them. The Operations Overview brings submitted weekly timesheets into the same view as authorized work packages and the exception queue. A manager can start with a week under review and follow its work package back to the project.

• Prepare the week. A team member checks the parent work package and organization before entering the weekly total. The worker and week beginning date make the submission identifiable to the reviewer.
• Submit for decision. The record moves from Draft to Submitted. The revision matters because the approval checks it before changing the status.
• Keep the result. A valid approval changes Submitted to Approved, records a review decision and a completed operation receipt. A blocked attempt leaves the weekly record as it was and writes a failed receipt.

Agree which project manager reviews each organization’s weekly submissions and how a worker’s text name maps to the team’s roster. Decide when the week begins and how to reconcile the weekly hours with dated time entries. The weekly submission belongs to a work package and organization; the time entries hold their own team member and project references. Check the entry approval outcome during the pilot before the manager decides the weekly record. Set a policy for revision changes before a manager starts reviewing a submitted week. The manager should be able to explain the hours accepted and identify the version that was accepted.

Take a worker who has logged several days against a project task. The team member enters a weekly submission for that work package and organization, with a positive total and valid revision, then sets it to Submitted. The project manager compares the work package and week with the dated entries. On approval, the weekly status becomes Approved and the decision and receipt are available for review. Now try a submitted record with zero hours or an invalid revision. The attempted approval should write a failed receipt and should leave the submission unchanged. This rehearsal shows the difference between a review outcome and an attempted operation. It also gives the delivery lead a concrete example for the exception queue.

• Weekly Submissions Awaiting Approval — Submitted weeks with their worker, dates, package, hours and revision ready for a project manager’s decision.
• Timesheets Awaiting Approval — Individual entries still Submitted in the related project, with their own approval outcome to inspect.
• Failed Operations — Blocked attempts that need investigation before another approval attempt.

Start with preparing a project week, then review submitted time. Use the data model when mapping existing records to the first pilot.