H
HartaAgency proposal
01 / 12
Contract-aligned proposal · July 2026

From KLEM contract
to operating system.

A practical plan for translating the LOA’s cleaning scope, service frequencies, shifts, audit duties and evidence requirements into one manageable web system.

Prepared for FaisalHarta decision reviewWeb planning MVP
BAppendix B · scope, tools and chemicals
CAppendix C · SLA and assessments
D/Epenalties, records and proposed shifts
Harta Cleaning PlannerLOA pages 27–45 reviewed
H
HartaExecutive decision
02 / 12
The decision in front of Harta

Build a visual scheduler—or build the contract control layer.

Our recommendation: approve a contract-aligned planning MVP.

The LOA defines more than cadence. The system must connect every published assignment to the relevant contract scope, approved location, operating shift and service standard—while keeping the worker experience simple.

Agency recommendationContract traceability before workflow expansion
H
HartaContract map
03 / 12
How the LOA fits the system

Each appendix becomes a different type of control.

§

The LOA is the baseline—not the worker screen

Pages 27–45 · Appendices B–E

The planner translates contractual detail into simple work, while retaining the source, standard, approval and evidence behind it.

BScope library

Areas, services, frequencies, tools, chemicals and approved methods.

CSLA controls

Weekly joint review, Monthly Assessment and staffing obligations.

DCompliance records

Schedule, attendance, photos, complaints and other penalty-sensitive records.

EShift baseline

Three proposed shifts, with alternatives subject to Management approval.

Appendix B · Appendix C · Appendix D · Appendix ESource → rule → schedule → evidence
H
HartaProposed system
04 / 12
What we are proposing

Build the contract once.
Run KLEM through structured assignments.

§Contract library

Service standards

Outcome, detailed SOP, source clause and minimum frequency.

⌖Facility model

Exact locations

Site → zone → floor → specific room, area or asset.

↻Planning logic

Assignment rules

Group, shift, cadence, count, date or time, evidence and dependencies.

✓Control views

Operational proof

Web timetable, daily plan, reviews, exceptions and evidence status.

The timetable becomes an output.Managers maintain rules and approvals—not calendar cells by hand.
Recommended product principleContract-backed · location-specific · versioned
H
HartaOperating model
05 / 12
The operating model

One physical truth—then templates create simple work.

01
Physical hierarchySite → Court → Level → Location → Asset
Where
02
Stable identityCodes survive renamed displays and QR history
Traceability
03
Template + asset bundleStandard Mall Toilet generates the expected scope
Standard
04
Cleaning task ruleOutcome, cadence, shift, method and evidence
What + when
Physical tree ≠ operational group ≠ cleaning taskStable IDs preserve every future schedule and work order
H
HartaManager experience
06 / 12
The manager experience

Build the mall first—then plan against approved nodes.

KLEM · Draft hierarchy + plannerSurvey → Code → Template → Audit → Approve
Physical treeDraft
North Court
Central Court
South Court
Shared / Site-Wide
8 source levels
5 shared groups
Selected pathTree
▾ KLEM
▾ North Court
▾ G1
▾ Female Toilet 01
• Mirror 02
• Basin 01
• Waste Bin 01
Node inspectorDraft
CodeKLEM-NC-G1-TOI-F-01
TypeFemale Toilet · Amenities
TemplateStandard Mall Toilet · v1
Asset attributesSurface · height · access · quantity
StatusDraft · validation required
1 Validate court and level2 Count and code locations3 Generate and adjust assets4 Run completeness audit
Hierarchy specification v1.0 integratedNo schedule generation from incomplete or unapproved nodes
H
HartaShift governance
07 / 12
Contract shifts and operational approval

Show the baseline—and make every approved change explicit.

1Import baselineAppendix E proposed hours
2Compare operationCurrent KLEM working hours
3Record varianceReason, approver and effective date
4Publish versionAssignments use approved hours
5Preserve historyPast work keeps past shift truth
Important: “daily” is a cadence—not once per shift. Waste collection is the explicit timed exception: 3× daily at 12pm, 4pm and 10pm. Alternative shift hours still require Management approval.
8am–8pmMorning shift · Appendix E
10am–10pmDay shift · Appendix E
9pm–9amNight shift · Appendix E
Previous working model differs from the LOADo not silently overwrite either version
H
HartaContract controls
08 / 12
What compliance adds

The planner should prepare the evidence trail before work begins.

W

Weekly review

Appendix C
  • Weeks 1–3: Service Officer + Client
  • Week 4: appointed Auditor + Client
  • Agreed Service Audit Form
M

Monthly Assessment

Performance control
  • One agreed assessment date
  • Tiered outcomes below satisfactory
  • Published result and follow-up
E

Evidence

Appendix D exposure
  • Monthly Cleaning Schedule
  • Photos for specified activities
  • Attendance and approval records
R

Response

Exception control
  • Correct deficiencies immediately
  • Written reply within two days
  • Resolve complaints same day
Appendix C and Appendix DPlan evidence requirements at the assignment level
H
HartaWorker simplicity
09 / 12
How worker simplicity is preserved

Asset-level truth—without turning work into checkbox overload.

What the system retains

Exact locationKLEM-NC-G1-TOI-F-01
Generated assetsFloor · WC · basin · mirror · bins
Contract cadenceDaily + as required
Periodic rulesWeekly detail · periodic descale
EvidenceCompletion + exception photo
Template versionStandard Mall Toilet · v1
System translates
→
one clear outcome
KLEMToday

Clean toilet

North Court · G1
Female Toilet 01

Asset coverageIncluded
As-required requestOpen
SOPView
Start task
Simple worker outcome · structured asset coverageStandalone periodic jobs remain separate tasks
H
HartaOperational change
10 / 12
The operational changes

The hierarchy specification defines the production guardrails.

Current prototype
Required production change
Why it matters
Generic “Female Toilet” nodes
Counted locations + stable unique codes
Traceability: QR, complaints and history reach one real destination.
Asset names only
Surface · height · access · quantity · risk
Rule accuracy: method and equipment follow the actual asset.
Editable tree without lifecycle
Draft → approval → effective dates → inactive
Audit integrity: history is preserved; used nodes are never deleted.
Schedule can run from partial setup
Completeness audit before generation
Reliability: missing codes, templates, assets and dates block activation.
Keep physical geography separate from operational groups.Do not print QR codes before location-code approval.Do not let template updates rewrite historical work.
Functional specification v1.0Draft nodes now · production activation after site validation
H
HartaDelivery roadmap
11 / 12
What will happen

Move from a draft catalogue to an approved KLEM register—gate by gate.

0Validate

Drawings + terminology

Confirm court boundaries, Appendix II demarcation, G1–G3 meaning and official level sequence.

1Survey

Count and code

Walk each floor; register every toilet, lift, escalator, staircase, room and asset quantity.

2Configure

Templates + rules

Generate asset bundles, capture surfaces/access and attach contract-aligned task rules.

3Approve

Completeness audit

Resolve duplicates, missing parents, uncoded assets, orphan rules and periodic next-due dates.

→Operate

Pilot + history

Generate one month, issue QR-linked work, inspect, correct and preserve every version.

Gate 1: drawings and labels acceptedGate 2: location/asset register acceptedGate 3: completeness audit passed
Updated implementation sequenceNo production schedule before the hierarchy register is approved
H
HartaDecision and next actions
12 / 12
The recommended decision

Approve the hierarchy foundation—then build the planner on validated KLEM truth.

1
Obtain Appendix II and official terminologyConfirm North/Central/South boundaries and the meaning of Basement, LG, G1–G3 and L1–L3.
2
Approve the stable code standardKLEM-[COURT]-[LEVEL]-[TYPE]-[NUMBER], with asset codes underneath.
3
Run the physical site surveyCount every real location and capture assets, surfaces, heights, access and drawings.
4
Build and pass the activation auditNo timetable until codes, templates, task targets and next-due dates are complete.