13.4 Design Strategy & Time Management

Design Strategy & Time Management

Quick Answer: A ten-hour OMR session rewards disciplined pacing, not artistic effort. Since PRBoA Resolution No. 14, Series of 2009, the Architectural Design and Site Planning subject is answered in multiple-choice form, so candidates who budget time across reading each brief, working out the design and site-planning resolution on scratch paper, evaluating the options against code, and marking the OMR answer — and who protect time for a code-compliance check before the session ends — consistently outscore candidates who linger on any one problem.

Knowing the correct problem-solving sequence for the PRC Architect Licensure Examination (ALE) design subject, covered in the previous section, is only half the battle. The other half is disciplined time management across that sequence, because a full-day session is long enough to feel unhurried in the first two hours and desperately short in the last two.

Budgeting Time Across the Session

While PRC does not publish an official minute-by-minute schedule for how a candidate must use the design session, review centers and experienced practitioners consistently recommend allocating time roughly in proportion to each phase's role, rather than letting any one phase expand to fill available time. A commonly recommended framework, scaled to a ten-hour session of multiple situational problems, looks like this:

This is a candidate strategy, not an official PRC requirement, but the underlying logic is sound regardless of the exact split: working out the design and site-planning resolution is where the bulk of the technical and code-compliance judgment lives, so it deserves the largest time block, while marking and final review, though important, should never consume time still owed to resolving remaining problems.

Common Time-Management Mistakes

• Over-investing scratch time on one problem. Fully detailing one problem's worked-out solution while several others remain unattempted is the OMR-format equivalent of polishing a single rendering at the expense of a complete plan: a beautifully resolved problem cannot compensate for items left blank, because every problem is an independent scoring opportunity.
• Not addressing every stated program requirement. Each situational problem's brief functions as a checklist in disguise: every listed space, area, or function is a clue to the correct option. Skipping a required room, or overlooking a stated code parameter, points to a wrong option that no extra scratch work on other problems can recover.
• Ignoring accessibility and life-safety basics under time pressure. As the session runs short, it is tempting to evaluate options without rechecking basic Batas Pambansa Blg. 344 (BP 344) accessibility provisions — including the current 1:20 maximum ramp slope under the 2024 Revised IRR — or Presidential Decree No. 1096 (PD 1096) life-safety provisions, but these are exactly the items the options are built to test, because they are objective and quick to verify.

If Time Runs Critically Short

When only a fraction of the session remains and not every problem can be fully worked out, the priority order should follow the same logic as the checklist below. First, make sure every problem has at least a marked answer — an educated guess on a flagged item is better than a blank, since blanks score zero with no chance. Second, protect the code-compliance judgments already made on problems you have resolved, rather than second-guessing them under time pressure. Third, use any remaining minutes to re-read the briefs of the hardest remaining problems and eliminate clearly wrong options before guessing. A session that ends with every item answered and the resolved problems defended consistently scores better than one where a few problems were perfectly resolved and the rest left blank.

A Final Mental Checklist Before the Session Ends

In the last minutes of the session, before the OMR sheet is surrendered, it is worth mentally running through a short, non-negotiable checklist rather than continuing to refine one problem's scratch work:

1. Program completeness — for each problem, has every listed space or function in the brief been considered in selecting the answer, even where the resolution stayed schematic?
2. Basic code compliance — does the chosen option respect BP 344 accessibility basics (such as the 1:20 maximum ramp slope under the 2024 Revised IRR and an accessible route to the main entrance) and PD 1096 setback and egress provisions (setbacks tied to the road right-of-way, adequate exit widths and travel distances)?
3. Consistent graphic judgment — where the item describes a plan, section, or elevation, has the chosen option been checked for the scale, poche, symbol, and consistency conventions covered earlier in this chapter?
4. No blank items — is every problem marked on the OMR sheet, with flagged items given a best-effort answer rather than left empty?

A set of answers that clears all four of these checks, even where some scratch resolutions stayed rough, communicates a complete and defensible response across the full problem set. That combination, completeness, code awareness, and judgment, is what the Architectural Design and Site Planning subject is actually built to measure, and it is the standard every candidate should hold their own OMR sheet to before the session ends.