These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Construction Projects PSA
- Features
- Field work and milestones
Field work and milestones
Record delivered packages and site milestones against the project they serve.
OverviewApproved Work Not Yet Billed×
Construction Projects PSA · Field work and milestones
New
Approved Work Not Yet Billed
Invoiced waits for the commercial lead
| Work package code | Project | Worker | Work date | Approved amount | Status | |
|---|---|---|---|---|---|---|
| WPC-547 | PRJ-2927 | CAS-5982 | 25 Oct | AA-961 | Approved | |
| WPC-182 | PRJ-4124 | CAS-8927 | 25 Oct | AA-605 | Approved | |
| WPC-677 | PRJ-4576 | CAS-7478 | 18 Oct | AA-336 | Approved | |
| WPC-997 | PRJ-9722 | CAS-7784 | 27 Oct | AA-350 | Approved | |
| WPC-568 | PRJ-1358 | CAS-8938 | 25 Oct | AA-921 | Approved |
6 of 6 records
WPC-547Work packages · WP-53550
ApprovedProjectPRJ-2927
WorkerCAS-5982
Work date25 Oct
Approved amountAA-961
What you can do
Connect delivery to the job and its next decision
Work packages describe delivered activity, with a worker, work date, hours, charge rate and billable choice. Site milestones describe the dated outcome the owner expects, the amount assigned to it and the person who owns it. Both point to a project. Keeping those references accurate lets a project manager compare delivery with the contract and lets a commercial lead decide when a milestone can enter billing.
A submitted work package enters a real approval workflow. It checks that the work is billable, has hours and belongs to a project. An approvable package becomes Approved, with a review decision and an operation receipt. If a guard fails, the record stays Submitted and the operation receipt records failure. The worker and Site Lead can correct the package and submit it again. Work Reviewer checks the recorded outcome before the team uses the work in a commercial review.
How the work is organized
- Work package detail. The description, hours, worker and charge rate explain what was delivered.
- Milestone responsibility. A due date and named owner keep the site outcome visible.
- Approval trail. Decisions and operation receipts show the result of the work package check.
What to agree during setup
Project Manager and Site Lead should agree what constitutes a work package, which activities are billable and who submits a package for review. Site Lead needs a consistent way to check hours and the project reference against field evidence before submission. Work Reviewer checks failed results and helps the crew resolve exceptions. Agree whether a package covers one day’s work or a distinct deliverable, then use that pattern for the pilot project.
For milestones, agree the scope of the deliverable summary and the amount the commercial team expects to invoice. Decide who can submit the milestone and who makes the approval decision. A milestone with a due date and owner is useful for site planning; it needs a project and amount before the invoice operation can move it forward.
Check the handoff on an actual case
A crew member completes a site inspection and records a billable work package with the project, hours and a plain description of the completed work. Site Lead checks the package and submits it. The workflow checks its billable choice, hours and project, records the decision and operation result, then marks it Approved. Work Reviewer inspects the outcome. If the check fails, the package stays Submitted with a Failed receipt for the crew to resolve.
Separately, the site milestone for the inspection has an owner, due date, amount and deliverable summary. Commercial Lead checks that the outcome is ready and approves it. The invoice workflow then checks its project and amount before marking it Invoiced. The work package and milestone remain different records: one shows delivered labor; the other governs milestone billing.
What your team sees
- Approved Work Not Yet Billed — Approved delivered packages awaiting the next commercial action.
- Field workboard — Draft, submitted, approved and rejected work grouped by status.
- Site Milestones Ready To Bill — Approved milestones for the billing handoff.
Follow the work through
Work package approval and Milestone invoicing show the decisions and outcomes.
What it keeps track of
Data model- Projects
- Construction projects with contract value, schedule, budget hours and realized gross margin.
- Work packages
- Delivered work packages for each project with hours, rates, approval status and billing amounts.
- Site milestones
- Site milestones with due dates, amounts, approval status and billing readiness.
- Review decisions
- Approval decisions recorded against service, time and expense subjects.
- Operation receipts
- Evidence of executed billing, approval and document operations.
Who uses it
Permissions- Site Lead
- Organizes field delivery; Crew Member records work; Work Reviewer checks package outcomes; Commercial Lead approves milestones.
Set up Construction Projects PSA your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.